Announcements

Between mid-October and November, the content on AREA will be relocated to the Autodesk Community M&E Hub and the Autodesk Community Gallery. Learn more HERE.

Group Policies for license assignment (Serial # - Product Code)

Group Policies for license assignment (Serial # - Product Code)

sherry_kennedy
Explorer Explorer
292 Views
1 Reply
Message 1 of 2

Group Policies for license assignment (Serial # - Product Code)

sherry_kennedy
Explorer
Explorer

We are a Global company with locations all over the US and in 88 different countries.

 

We currently have several different Autodesk products and Collections, Contracts and different serial numbers for the same products due to the products needing to be on different contracts (According to Autodesk). We create MANY install packages using SCCM with the license information included in the install and then assign users to the Active Directory group so they can install their software with their proper serial/Product code. Some of the install packages can be up to 20+ GB each. We do not have enough space to create all the packages we need.

 

It would be beneficial to have the licensing (Serial # - Product Code) assigned through Group Polices instead of having to create multiple software packages for the same Products due to all the different serial numbers. This would allow us to create 1 install package for each Autodesk Product we are licensed for and tie it to 2 different Active Directory groups each getting their own Group policy for licensing. This would also allow us to free up a lot of space and labor time creating all the multiple packages for the same products.

 

We need to create a few different packages for the Collections Applications which will take up at least 32+GB.  If we had packages created for all the products we are licensed for, the users of the Collections, could just be assigned to the proper AD group and the Group Policy.

 

Does anyone know if this is possible and if so, how would I do it?

0 Likes
293 Views
1 Reply
Reply (1)
Message 2 of 2

dgorsman
Consultant
Consultant

You shouldn't need different contracts; that sounds like a summary of a summary of an informal discussion.  You *might* need different contracts for operations in certain embargoed countries, but even so that shouldn't be that big of a deal.

 

Serial numbers are virtually irrelevant when using network licenses - all that's needed is to point the deployment build to the central license server.  And if you aren't on Enterprise Tokens you need to do so.  At that scale there's quite a few advantages.

----------------------------------
If you are going to fly by the seat of your pants, expect friction burns.
"I don't know" is the beginning of knowledge, not the end.


0 Likes