@Twiceroadsfool@Enscape3d@seanmpage@Rev_Design It's not really "reverting" back, but restoring the previous behavior ("concurrent use" license behavior in the new system). 4.1 requires users to set up a Chaos account, which can be automated by implementing SSO (which we did). So users input organization email and get a lic.
@Twiceroadsfool@Enscape3d@seanmpage@Rev_Design Tested the shared cloud licensing yesterday, works like pre-4.1. It basically installs a license server on each workstation to achieve that but is all transparently managed.
@Twiceroadsfool@PrlxTeam Gotcha, yeah it's a downside I do not like at all :) I think it's shameful to create a good new feature and introduce crap like this.
@Twiceroadsfool@PrlxTeam Ah ok so you're alluding to creating sheet "sets" in past versions by having sheets in different files and making fake tags etc.
@Twiceroadsfool@PrlxTeam I found it too easy to mis-reference with the new functionality. Maybe sheet collections are a good thing, just not at all a fan of the ease in producing incorrect references. Doesn't feel well thought out.
@Twiceroadsfool@PrlxTeam What do you honestly think about Sheet Collections and the fact that you can have bad references to a duplicate sheet in another collection?
@Twiceroadsfool@IMAGINiT_Tech A "service account" that for automation purposes is not a "shared account". Those are two different things. A shared account is what violates EULA as you're trying to skimp on licenses. With a service account for this specific purpose, you are actually increasing license usage.
@Twiceroadsfool We use a common service account that is assigned to all projects, then use an automation solution, in this case @IMAGINiT_Tech#Clarity to set up the publishing schedules.
@Twiceroadsfool@Bjorni_K@autodesk@AutodeskAEC Yeah we have the registry key and it's still functional (Access does not load in the tray) but it's still installed and runs as a process. Highly annoying. See previous Tweets for complete removal.
@Bjorni_K@autodesk@AutodeskAEC Of course it'll be a goose chase as they'll keep changing the package ID. Which is why probably outright blocking some of the files permanently is the way to go if they want to play this game.
@Bjorni_K@autodesk@AutodeskAEC We updated #Revit 2022 and I know the checkbox in all the custom installs is purposely left unchecked. So at this point this checkbox is meaningless and it finds its way in via ODIS. That's the definition of a Trojan Horse to me.