Copy link to clipboard
Copied
I've discovered that there are ways that I can host multiple meetings simultaneously from the same computer, and my questions are whether there are any issues or problems with doing so. The first method is having one meeting active in a browser window while a second meeting is active in the add-in, and the second method is by hosting one meeting inside the Microsoft Windows virtual PC emulation on my Mac laptop while a second meeting runs in the Mac OS itself. In both cases, I can simply toggle between the meetings with relative ease, but this somehow seems like it could create technical problems. Does Adobe have an official opinion on this type of use? Are there any behind-the-scenes technical issues that could arise from doing this? Does anyone else use Connect in the manner and, if so, have you ever experienced any problems?
Copy link to clipboard
Copied
Let's start with the potential licensing issue you have. If you are are on a Named Organizer (Host) licensing model, then this use case is against your End User Licensing Agreement (EULA) with Adobe. A Named Host can create as many rooms as they want/need, but may only use one at a time. If you have the Concurrent user licensing, then there is not issue, as each meeting you are running is occupying an additional concurrent user license. Meaning if you have 4 meetings running at the same time, then you are occupying 4 of your total concurrent user incenses.
Assuming you don't have an licensing conflict, you shouldn't need to play the multiple browser/OS game. I have had multiple meetings open at the same time on the same account in one browser many times. Being on the Concurrent User license I am able to do this, and it works well when teaching the use of Connect via Connect. This way I can play with a room that doesn't have all my students in it, so when I demonstrate ending a room or removing a user, I don't exclude anyone in the training room. I'm not sure if there is an official option for this type of use, since it is not a terribly common use case, but I believe you shouldn't need to jump through the hoops you are currently jumping through.