In many environments, tasks such as moving a license server or adjusting a client-side timeout can be difficult and time-consuming. Fortunately, there is an easy way to push out these settings to a Windows environment using Group Policy.
(Before we begin, please note that modifying Group Policy settings should only be performed by Information Technology professionals.)
Configuring License Servers
There are two settings that can be distributed easily via Group Policy. The first is the list of Autodesk license servers.
This GPO will either create or edit a System Environment Variable on the client computer, ADSKFLEX_LICENSE_FILE, which in turn edits the registry. This Environment Variable tells the client computer the name or IP of the license server(s), and this overrides other settings such as the LICPATH.LIC files for individual applications. Normally, this can be edited directly via the Control Panel (System – Advanced System Settings).
The Group Policy is generated as follows:
N.B.: This Group Policy will not have any effect on computers that do not use Autodesk products. As a result, there should not be any issues assigning this GPO to an entire office, even if many of the users are not using Autodesk software.
Configuring Client-Side Timeouts
Another setting which can be configured this way is the client-side timeout. This setting is used to control the amount of time the client will wait to communicate with a license server, before giving up. It is typically used when the client computer is using a WAN link to access a license server.
In this case, the process is the same as above. The difference is the values you will enter.
This increases the timeout to 30 seconds. You can vary the value as necessary.
As with the ADSKFLEX_LICENSE_FILE, this will not have any effect on users or computers that do not use Autodesk software.
For more details on these Environment Variables, please refer to the following Autodesk KB articles:
If you have additional questions regarding this topic, please reach out to us at email@example.com.