![]() With Saltstack I just copied the folder for my existing deployments into the saltstack windows repo, pointed to the installer setup.exe with the SLS file and passed the install flags in. ![]() It's not the cleanest (and certainly not the most space-efficient) way of deploying things but it gets the job done.įor PDQ we basically follow this guide to the letter: My experience deploying autodesk products is with PDQ and Saltstack, in both cases I used the deployment creation tool and have had pretty consistent success. What little help there is on line suggests installing a newer version of the license service first, or making changes to shell folder settings so they point to fixed locations - neither has made a difference so far.Īnyone come across this and have any suggestions, please? I'm trying to get these to install in context of the system account and with the script run as a scheduled task that copies the files to device and runs the install when complete Log says it can't reach network location 'revit 2020/' and then rolls back. It installs the content library and pre-requisites, but fails the main app with a 1603 error. I have a procedure in place to stage the install files on the local device, do the installation, then tidy up the files. Policy is to use Intune where possibly, but some of the autodesk stuff is huge and so won't work. As a general rule, if someone has flair, they almost definitely know what they're talking about.Īs part of a Win10 roll out and application rationalisation process, I need to roll out some Autodesk apps. 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. ![]() When you dig further, you will see that there is heavy reference to file locations hard coded to the installing user's profile under HKLM, and this is where the problem starts since users don't generally have the ability to write to other user's profiles, and even more so in Windows 7.Post your SCCM tips and tricks, requests for help, or links others might find useful! Post not showing up? You will find that others have posted on this site that this is not the case, but they also don't come out and describe how they were able to overcome this problem. May not sound like much of an issue, unless you are planning a mass deployment using something like SCCM where the account performing the install is likely not the logged in user but rather the System account. We discovered that the installation (by design) is taylored to properly work ONLY for the user that performs the install. You might have better success.Īnother thing to test is whether the install can be used by other users post install. You can do this while still using the a Network deployment by specifying the location that it will be copied locally to instead of a network share. ![]() ![]() I'd also suggest you consider copying the files local prior to starting the install. Be sure to follow the Network Administration and Deployment section carefully. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |