My Win10 deployment includes DotNet35, so I've not run into a problem as of yet. I agree, there is no excuse for how poorly implemented it is. The quality of the software AutoDesk shovels out is DREADFUL. I've seen that hang on one machine, I reached over the user's shoulder and hit ENTER and it resumed the install.
#AUTOCAD 2006 ON WINDOWS 10 WINDOWS 10#
With Windows 10 two years old and Autodesk 2018, I would think that Autodesk would have these issues worked out by now. NET other than what the OS patching has done. The deployment itself was built back in May and all of the INI files are baseline. I am doing AutoCAD 2018 just to verify that I'm using the most recent deployment possible.
#AUTOCAD 2006 ON WINDOWS 10 HOW TO#
Beyond that, it doesn't seem to give any suggestions on how to get Autodesk products to install on Windows 10. The Autodesk knowledgebase article you link to talks about either upgrading from an older version of Windows with Autodesk products already installed or patching to the most recent Windows 10 update. At this point, there are 10 of 72 items remaining in the deployment and it's just stuck. It later stalled on installing "Autodesk AutoCAD Architecture 2018" and has been sitting on that all night (the computer is set not to sleep). When I ran the deployment, it initially took a long time to install the "Windows 2008 Visual C++" redistributable but it ultimately succeeded and began installing the other items including Revit 2018. I did do a "subst K: C:\Users\currentuser\AppData\Local\Temp" because I noticed when I tried this previously that I had a K: drive missing error.
I deleted everything in %TEMP% that I could before I rebooted just to make sure there would be no conflicts there. UAC is set to "Never Notify" with a subsequent reboot to make sure that was the set level. The deployment is normally set to be quiet but I disabled that for testing. I didn't install our anti-virus and disabled Windows Defender before attempting to install the deployment of Revit 2018 and AutoCAD Architecture 2018. Yesterday, I built a workstation with a fresh install of Windows 10 Pro and fully patched it so that is now as up-to-date as it can get. I just run it from the location on the server where I built it, which is a UNC path. If memory serves, Autodesk creates it's scripts in UCS-2 and batch really wants UTF-8.
If you go the convert to a batch file route - you also need to change the "encoding". How are you pushing it out?īy default the scripts are "SCCM" - but they can be converted into a batch file for example.
0 kommentar(er)
