IDSP install with Civil3D license
@Anonymous
Not sure what you mean by...
@Anonymous wrote:
...
All of our users are on subscription licenses, some with full IDSP and some with just Civil 3D.
...
Maybe you're just using the original term "Subscription"... Subscription licenses are now term based and your licenses are Maintenance licenses. I know it's maintenance because you still have suites. Is that correct, or did you upgrade your maintenance licenses to subscription (Term) licenses?
It make a big difference as suites aren't available for subscription and no longer sold as a product.
Answer: (if you have maintenance licenses)
You should build a network deployment from the suite with all of the products included. Afterwards, you should navigate to the Tools folder and use Create/Modify Deployment shortcut to create another configuration from the existing configuration but this time uncheck all of the products except Civil 3D.
The idea behind this is to have one deployment with multiple shortcuts that reference separate ini files to install the necessary products.
Let me know if you moved to subscription.
If this information was helpful, please consider using the Accept Solution
@Anonymous
@Anonymous wrote:
Hmm yeah I'm not sure what you mean. We used to have on-prem network licenses for IDSP that were shared, using the license manager. We then moved our design team to named (managed) subscriptions that are managed through the online portal and assigned to each individual user using their AutoDesk ID. The portal still calls it IDSP 2018.
Your company may have moved your suite licenses over to Collection licenses. However, you can only move to the same license type as your maintenance, so you guys may have kept your suites on maintenance and purchased new Single-User licenses...
@Anonymous wrote:
...
I understand that I can create multiple deployments to satisfy the different requirements,that's what I am trying to avoid. We use SCCM and the users access these through Software Center, I would prefer it if we only needed to manage a single package.
The suite deployment should be configured as a Standalone deployment. The user would only be able to use the product that's been assigned to them. So, if you install the entire suite on the machine and the user only has access to C3D, then that's all he'll be able to use. In addition, if that same user need Navisworks, you can convert the license for Navisworks to network while C3D maintains the Single-User license.
Hope that make sense.
If this information was helpful, please consider using the Accept Solution