They might love it if it worked as advertised (let you pause the other session so you could work on the one you were trying to launch) and didn't completely freeze the computer.
But the license agreement, for the past several years (since a few months after the named user licensing started and everyone complained about the issues it caused with scenarios like the following) you could have two sessions on two different computers simultaneously.
I could run a session on one computer, walk away from it and launch a session on another computer to test something or to hold a meeting or whatever, and all was good. It wasn't until I accidentally tried to launch a session on a third computer (like I accidentally tried to do earlier this week while testing plotter configurations across different computer builds) that I would receive the message (which, that version would log you out of one of the other computers if you chose the option or it would close the session that you were trying to launch).
This version, which says that it will "pause" the other session if you choose that option (or you can end the session that you're trying to launch), froze the computer up entirely... I couldn't click anything in the dialog, I couldn't click on anything outside of the dialog, I had to completely restart via the good ole Ctrl/Alt/Del. I checked for and installed all Autodesk updates just in case I had something out of date. Tried it twice more after that, same result every time.
I understand what they're trying to do, and, if it worked it might not be so bad. The newer license agreement that I went in and checked said that you could have a second session on a second computer if the first session was sitting idle (which is the case in my scenario).
"For purposes of this section only, “access” does not include batch processing, renders, idle usage (i.e., when the Software is open but there is no user input) or similar activities that may run in the background of the Software (“Background Activities”). For the avoidance of doubt, Your Authorized User’s access of the Software to perform Background Activities does not count toward the concurrent use limits set forth in this section."
<Edit> to include date of agreement change >
"Last updated: January 15, 2025"
But what I got this morning did not work so I can't say whether it's a viable and/or workable alternative to the previous method or not.
-Gary
Gary J. Orr
GaryOrrMBI (MBI Companies 2014-Current)
aka (past user names):
Gary_J_Orr (GOMO Stuff 2008-2014);
OrrG (Forum Studio 2005-2008);
Gary J. Orr (LHB Inc 2002-2005);
Orr, Gary J. (Gossen Livingston 1997-2002)