![]() ![]() Write-Log "Uninstalling AutoDesk Desktop App, because it's crap" -Source 'Post-Installation' -LogType 'CMTrace'Įxecute-Process -Path "C:\Program Files (x86)\Autodesk\Autodesk Desktop App\removeAdAppMgr. Remove-Folder -Path "$envProgramData\Autodesk\SDS" Write-Log "Removing $envProgramData\Autodesk\SDS folder" -Source 'Post-Installation' -LogType 'CMTrace' Stop-ServiceAndDependencies -Name 'AdAppMgrSVC' Write-Log "Stopping AdAppMgrSVC Service" -Source 'Post-Installation' -LogType 'CMTrace' FYI Autodesk changed their installer in Revit 2021 (again) and it is not using the regular (classic, whatever) installer per their own documentation. Stop-Process -name AutodeskDesktopApp -Force Write-Log "Stopping AutodeskDesktopApp Process" -Source 'Post-Installation' -LogType 'CMTrace' # Remove Autodesk Desktop App, we don't want that crap! Write-Log "Removing $Username local admin account" -Source 'Installation' -LogType 'CMTrace' Replace the adsklicensing-installer.exe with the newer file download above, for me this is image\setup.xml""" -WindowStyle 'Hidden'.You'll need to modify the manifest GUID to suit your environment.We zip up the deployment file, this speeds up distribution.(or whatever is latest at time of reading this) It also fixes the issue with the Desktop App installer hanging - which we then nuke after it's installed. This gets around a bunch of issues, including the inability for SYSTEM user to create symbolic links. Basically, we install it via PSExec using a temporary admin user. This issue is not fixed with the latest adsklicensinginstaller-10. Most issues stem from the fact that the SYSTEM user that SCCM Application install framework uses, does not have the ability to create symbolic links. There are numerous people with issues with packaging/deploying Autodesk 2020/2021 applications as required, including during OSD. As a general rule, if someone has flair, they almost definitely know what they're talking about. Microsoft employees typically have MSFT Official flair, and MVPs usually have MSFT Enterprise Mobility MVP with a link to their personal site/blog.Please send mod mail if you qualify and would like flair set for your account. Flair is reserved for Microsoft employees and MVPs.System Center Configuration Manager and Endpoint Protection.Listing of Local ConfigMgr-related User Groups (largely outdated) URL shorteners cause this almost every time, but so do strings of apparent gibberish like WSUS and PXE sometimes. It might have been caught by the spam filter. error_code: 997, pipe_name: \\.Post your SCCM tips and tricks, requests for help, or links others might find useful! Post not showing up? T13:48:30.694 ChannelWin::Listen: WaitForSingleObject timeout. The process also changed for AutoCAD 2023 and it seems that for silent installation, it is now required to create a deployment and use their new Installer.exe to run a deploy action which then runs in silent mode. ![]() ![]() error_code: 997, pipe_name: \\.\pipe\adsk_dda_sdk T13:48:30.693 ChannelWin::Listen: WaitForSingleObject timeout. error_code: 997, pipe_name: \\.\pipe\adsk_dda_pl T13:48:30.692 ChannelWin::Listen: WaitForSingleObject timeout. T13:48:03.058 ChannelWin::Listen: Connected signal emitted for pipe: \\.\pipe\adsk_dda_dlm When I look at the DDA.log in C:\Windows\System32\config\systemprofile\AppData\Local\Autodesk\ODIS I see this: I'm able to run it fine off a SCCM distribution point (network share) as a local admin and system (using psexec) but it hangs when I deploy it as a task. In our case, I have it setup as a package. ![]()
0 Comments
Leave a Reply. |