Once I create an uninstaller script I will post that. When deploying I found that this needs to be run as the user, that was the cause of the hang, I had the deployment set to run as SYSTEM. I just copied my PS script to the root of the folder for content source and run from there.Įdit 8/2/18: Made changes to script and traced root of issue mentioned in my comment below. We initially ran install_acs_64_allusers.js with the /AdminConfig switch to create the AcsConfig.properties file. I use this to deploy iAccess Client Solutions via an SCCM Application. Here's a script I created based off of the install_acs_64_allusers.js file provided by IBM. 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. Post your SCCM tips and tricks, requests for help, or links others might find useful! Post not showing up?
0 Comments
Leave a Reply. |