Make sure to fully close the setup program.Ignore the error message that the shortcut cannot be created “ Cannot create folder AutoCAD 2000“, you will need to create the program shortcut by hand once the installation is finished.Once you have set the Destination Folder to c:\acad2000, install as normal.Setting AutoCAD 2000 custom install directory to c:\acad2000 In the setup program, navigate through each setup dialog as normal, except when you get to the installation folder, ** it’s vitally important to make sure you install to c:\ acad2000 (not Program Files (x86)\AutoCAD 2000 as usually prompted)** e.g.Once the setup starts, stop and read the next step….Now, I know it’s unheard of these days, but at this point expect to wait at least 45 minutes for your AutoCAD 2000 setup.exe program to fully appear – please be patient.For AutoCAD 2000, the Migration Wizard almost instantly pops up.Read, understand and follow all the prompts.Now click the “ Run Old Installer” button.Next, using the ‘…’ button select your AutoCAD 2000 CD.Select the 2nd tab titled “Old AutoCAD Installer Reviver” by clicking on it.Now, start the Longbow Converter tool by double clicking the Longbow Converter shortcut on your Desktop… .Before starting, we recommend turning off Windows UAC.Obtain your copy of the Longbow Converter here.If you need a hand getting started with PDT feel free to reach out. Honestly I would go down the PDT path, as it makes life so much easer, you are still able to use MEMC as it intended either user or computer targeted deployments and it is a process that is easy to repeat and understand once you get past the very small learning curve. The previous install was a bat file that had to to be run multiple times via software centre due to uncontrolled reboots and failed logic. Post install tasks included adding a whole bucket load of regkeys to HKU, and any user that had already logged in, installing office addins and replacing default shortcuts with custom shortcuts with specific icons and command line switches. It enabled me to map the drive, and also make sure outlook has been opened at least once(caused integration issues when running the app but not a install failure), than closed outlook and office apps for the actual install. Not an Autodesk install, but I recently had the absolute joy of packaging and deploying a legal App which install 10 odd prereqs, than a very specific Oracle package via a mapped drive pointing to a Linux server using Powershell Deployment Toolkit. Then I had to change the Collection.xml file change the toĪnd also need to be changed since they also point to the network share.Īfter these changes, I deployed it and tried it and everything worked as intended.Īnd I have given the domain computers read and write permissions on the network share \Installer.exe -i deploy -offline_mode -q -o. To fix this I created an Application (you can also create a package), the content location was set to ‘Image’ and not ‘Autocad’ folder (if you download a package you get an Autocad folder and inside it, there is an Image folder, log folder, install.bat, and summary.txt) then Installation program was set as As a general rule, if someone has flair, they almost definitely know what they're talking about.Ĭould be permissions - ccmagent will be running as system account, youĪpparently now when using Autodesk’s package builder with the "distribute" setting, the package builder uses absolute path (in my case) when I checked the ‘install.bat’ and ‘Collection.xml’, both of these files used absolute paths to my network share, so if you distribute the package with SCCM it will download the package but when it comes to running it, install.bat will attempt to run the installer on my network share. 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. Post your SCCM tips and tricks, requests for help, or links others might find useful! Post not showing up?
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |