Autodesk Network Deployments – Best practices

Issue:

What are the best practices to create successful Autodesk network deployments?

Best Practices:

  1. Create a network shared folder on the network.
  2. Keep the share name simple and short. Do not include spaces in the share name, and do not create the shared folder too deeply on the drive. Try to keep close to the root of the folder. Example: \\ServerName\Deployments. The reason is because the Windows share path limit is 256 characters. Spaces count as a character and so do dashes and underscores. The Autodesk deployments have quite a few subfolders which can also eat up the Windows 256 characters quickly.
  3. Create a subfolder for each product that you will be using to create a network deployment. Example: \\ServerName\Deployments\2022\Acad or \\ServerName\Deployments\2022\RVT
  4. The users will need full read access to the network share where your deployments are located
  5. If you plan to create a network log file, make sure that individual users or group of users have read/write access to the log file share.
  6. Try and use UNC (Uniform Naming Convention) shared paths instead of mapped drives. Example: \\ServerName\Deployments\2022\Acad However, if you map a drive from your shared network folder, make sure that all users map the folder to the same drive letter or the install will fail.
  7. Create the Autodesk deployments on FAT/FAT32/NTFS file systems only. Autodesk doesn't test or support other file systems, such as DFS, NFS, AIX, LINUX/UNIX, and file systems on network attached storage (NAS) devices. Creating the deployments on the DFS, NFS, AIX, LINUX/UNIX, and file systems on network attached storage (NAS) devices doesn’t mean you can’t get it work, but it is not supported by Autodesk.
  8. Do not create deployments over a WAN or use a VPN. These are typically very slow and can lead to errors in the deployment.
  9. Disable antivirus software before you begin creating the deployment and installing the deployment.
  10. Avoid moving deployments between servers. If you must move a deployment, please follow this blog to update files in the deployment that will need to be changed so the deployments will work correctly. https://resources.imaginit.com/support-blog/how-to-move-an-autodesk-custom-install
  11. Test the new deployment(s) by installing it to only one workstation before adding to production.

About the Author

Ken Williams

Installation Technical Support Specialist<br><br>Ken Williams has over 20 years of experience as a systems administrator helping organizations with installation, configuration, and maintenance. At IMAGINiT, Ken puts his knowledge of Microsoft, SQL, servers, and Autodesk to work ensuring clients are able to stay up-and-running, install their software easily, and maintain their solutions.

Follow on Linkedin More Content by Ken Williams
Previous Article
AutoCAD: When using External Reference file performance slows
AutoCAD: When using External Reference file performance slows

Drawing becomes slow when Loading , Editing, Using the Reference Palette, and When working with the Drawing.

Next Article
Enhanced Pressure Parts Libraries for Civil 3D Trials Now Available!
Enhanced Pressure Parts Libraries for Civil 3D Trials Now Available!