For IT administrators and CAD managers, deploying software can often present unexpected hurdles. Recently, Autodesk’s Wei reached out to the community to address recurring deployment issues with AutoCAD for Mac, seeking more detailed feedback to improve the process. This article clarifies the recommended deployment methods and sheds light on common pain points, particularly for large-scale deployments in educational settings.
The primary recommendation from Autodesk is to utilize the officially documented deployment method for AutoCAD for Mac, which can be found at https://www.autodesk.com/support/download-install/admins/create-deployments/create-deployments-for-autocad-for-mac. This method is designed to ensure a smoother and more reliable installation, avoiding issues that can arise from manually unpacking the installer.
However, feedback from users, particularly those leveraging deployment tools like Jamf, indicates that a fully unattended installation remains a challenge. While the /setup --silent command has proven effective for many applications, some users report that AutoCAD 2023 fails to install unattended, especially when initiated during a system’s ‘check-in’ phase when no user is logged in. This is a significant impediment for administrators managing numerous machines, such as those in educational computer labs. Maya 2023 has also been cited as experiencing similar issues, sometimes halting during the installation process without providing a clear exit code.
Understanding Deployment Workflows
Deployment workflows typically involve packaging installers and executing post-installation scripts. These processes, often managed through policies in systems like Jamf, can be configured to run at specific intervals, upon user login, or even made available to end-users through a self-service application. Historically, some administrators have scripted the installation of loose PKGs found within the installer package. However, Autodesk has advised against this approach, emphasizing the official deployment method.
The current challenge lies in achieving a truly “hands-off” installation that functions reliably even when a user isn’t actively logged in. This is crucial for efficient management of large fleets of computers, where manual intervention is impractical. The issue particularly impacts the education sector, where devices may not be wiped and reimaged annually, requiring robust deployment solutions for staff and lab machines alike.
Beyond installation, other users have reported difficulties with licensing, unlicensing, and updating Autodesk applications, further complicating the administrative overhead.
Moving Forward
Autodesk’s direct engagement with the community signals a commitment to resolving these deployment obstacles. By providing detailed information about the specific issues encountered—such as the exact error messages, the scripts being used, and the environmental context (e.g., Jamf management)—administrators can help Autodesk pinpoint and address the root causes. The goal is to ensure that deploying AutoCAD and other Autodesk products on macOS is as seamless and efficient as possible, particularly for large-scale deployments in demanding environments like educational institutions. Further discussion on licensing and update issues is also encouraged from affected users to provide a comprehensive view of the challenges.