Updating Visual Studio 2022 - Failing
Hello,
I am trying to package in KACE SMA under Scripting to update Visual Studio 2022 from v.17.7.4 to v.17.9. The script looks like this:
The certificates is added to the store successfully. But Visual Studios 2022 does not get updated. Below is the output log. Has anyone been able to update an existing install of Visual Studio?
Output Log
Running as SYSTEM Directory DOES exist: C:\ProgramData\Quest\KACE\kbots_cache\packages\kbots\1326 Launched Process: vs_Professional.exe Launched Process: vs_Professional.exe Creating process returned non-zero: C:\ProgramData\Quest\KACE\kbots_cache\packages\kbots\1326\vs_Professional.exe --noWeb --wait --passive --config $(KACE_DEPENDENCY_DIR\VS2022_17.9.2.vsconfig: (0) The operation completed successfully. Error Code: 0 Status Code: 1Activity Log
verify - directory_exists Checking if directory exists: C:\ProgramData\Quest\KACE\kbots_cache\packages\kbots\1326 verify - on_verify_success verify - on_verify_failure verify - launch_program Launching program: 'C:\ProgramData\Quest\KACE\kbots_cache\packages\kbots\1326\vs_Professional.exe' '--update --wait --passive' wait='true' verify - on_verify_success verify - on_verify_failure verify - launch_program Launching program: 'C:\ProgramData\Quest\KACE\kbots_cache\packages\kbots\1326\vs_Professional.exe' '--update --wait --passive --norestart --installpath "%PROGRAMFILES%\Microsoft Visual Studio\2022\Professional"' wait='true' verify - on_verify_success verify - on_verify_failure verify - launch_program Launching program: 'C:\ProgramData\Quest\KACE\kbots_cache\packages\kbots\1326\vs_Professional.exe' '--noWeb --wait --passive --config $(KACE_DEPENDENCY_DIR\VS2022_17.9.2.vsconfig' wait='true'Debug Log
Running kbot: runkbot 1326 1709829543 KBotScript::LogScriptInfo - Start id=1326 name=Copy of Update Visual Studio 2022 - RSD Team version=1709829543 type=policy execute disconnected=false logged_off=true execute events KBotScript::LogScriptInfo - Finish KBotScript::LogScriptInfo - Start id=1326 name=Copy of Update Visual Studio 2022 - RSD Team version=1709829543 type=policy execute disconnected=false logged_off=true execute events KBotScript::LogScriptInfo - Finish KBotScriptManager::CleanupDependencies - clean up dependencies in kbot directory C:\ProgramData\Quest\KACE\kbots_cache\\packages\kbots\1326\ CleanDependency: file UpdateVS2022.zip is part of the dependency list, keep the file runkbot ----- launching [path='C:\ProgramData\Quest\KACE\kbots_cache\packages\kbots\1326' program='vs_Professional.exe' parms='--update --wait --passive' wait='true'] ----- runkbot ----- completed [exitCode=0] ----- runkbot ----- launching [path='C:\ProgramData\Quest\KACE\kbots_cache\packages\kbots\1326' program='vs_Professional.exe' parms='--update --wait --passive --norestart --installpath "%PROGRAMFILES%\Microsoft Visual Studio\2022\Professional"' wait='true'] ----- runkbot ----- completed [exitCode=0] ----- runkbot ----- launching [path='C:\ProgramData\Quest\KACE\kbots_cache\packages\kbots\1326' program='vs_Professional.exe' parms='--noWeb --wait --passive --config $(KACE_DEPENDENCY_DIR\VS2022_17.9.2.vsconfig' wait='true'] -----Answers (2)
Confused what you're doing here. Is task 2, 3, and 4 running the same thing with slightly different parameters? Can you combine that into a single task?
Task 3 is it supposed to be missing the dashes before update?
Also in Task 3, %PROGRAMFILES% is probably going to point to 'C:\Program Files (x86)' because the SMA client is 32 bit. Is that intended or are you trying to hit C:\Program Files? (We are on v 13.0 and I only see a 32 bit agent. Not sure what's in 13.2. I see in v14 the agent will be 64 bit) Just something to check.
Why does your verify do nothing? Normally I would do a check to make sure the setup file exists and if that fails break.
Verify - a file exists
$(KACE_DEPENDENCY_DIR)\vs_Professional.exe
On success run that file.
That way if some some reason the installer doesn't push out properly it will fail.
The issue was when trying to get the update from the web even though --noweb was specified. The department who wanted the software packaged decided they will just install it manually. I can't find a way in ITNinja to close this entry.
Thank you,
Dinah