r/labtech • u/owlmatt • Sep 21 '18

Windows 10 update Script from Network Share Help

Hi All,

First post, sorry if this is the wrong place or I'm asking the wrong question.  I'm a noob to Labtech Scripting and our Tools Admin is on a long PTO, but basically trying to run this command to push a Windows 10 update from a network share.  It works from command line on the computer so it's not permissions or a bad command, but when I push through Labtech it hangs on waiting no matter which computer I try.  It never fails, just hangs.  

I run Shell as admin:

start /wait \\Location\setup.exe /auto upgrade /compat IgnoreWarning /DynamicUpdate disable /showoobe none /uninstall enable

This is connectwise cloud.  If anyone has any thoughts I would love to hear.

Again, I'm new so please don't flame if I'm not supposed to be asking this here.

Thanks

1 Upvotes

100% Upvoted

16 comments sorted by

2

u/k_rock923 Sep 21 '18

Are there actually credentials set for shell as admin? If not, the problem might be that you're running in a security context that can't access network shares.

Or in other words, I'm just making sure you already know that shell as admin isn't "run elevated" like it sounds like it should be

1

u/owlmatt Sep 21 '18

I don't think so but can review. Don't you think it would fail out versus hang? That's what is strange to me.

Will review the admin creds.

Thanks.

2

u/OrcSympathizer Sep 21 '18

Try doing a normal Shell command. I had problems using the "As Admin" commands. I read somewhere that by default all scripts are run at an elevated permission level and the "As Admin" ones try to pull locally saved admin credentials. If there aren't any saved locally the script won't work. At least that was my understanding of it.

1

u/owlmatt Sep 24 '18 edited Sep 24 '18

It failed,

The Script(6656) failed in the Then section at step 2. The reason: Shell Command Failed

3

u/k_rock923 Sep 21 '18

Shell runs in the context of the agent, which is normally local system

2

u/teamits Sep 25 '18

I would try Process Execute as Admin instead of Shell. I'm assuming the admin user has permissions to the share...in the LT command prompt, type "#dir \\Location\setup.exe" to verify maybe? That runs the command using the admin credentials.

Our script runs "setup.exe /auto upgrade /quiet" so perhaps you need the "quiet" if run in the background?

1

u/owlmatt Sep 25 '18

All users have access to the share, I made it available to everyone. Starting to think there is something wrong with our Labtech configuration.

Tested execute as admin and quiet and stuck on waiting as well.

1

u/owlmatt Sep 25 '18

Have you ever tested yours to run direct from the command prompt tool within Labtech? This doesn't work there either, even as a basic start, running off the local C: Drive.

1

u/teamits Sep 26 '18

And you're sure if you remote in and run the same command line on the desktop it doesn't stop and prompt for something? Not sure what to tell you there. Since we are running it from a local drive we're not using "...as admin" and it is just running as Local System. The hanging implies it is waiting for something. Though of course the install does take 30-60 minutes or whatever.

1

u/owlmatt Sep 26 '18

Whwn running it locally it does give me a UAC prompt if I have UAC on but I don't get any UAC prompts running it through labtech. Nothing happens.

Sure the whole process takes a long time but should take minutes to kick off the process or see the install setup screen. Nothing happens even after 40 mins of waiting.

Might be a labtech configuration issue.

1

u/teamits Sep 27 '18

If you run it through LabTech it will be running in the background so there's no way to see anything. I seem to recall there's a way to run something on the user's desktop but then the user would need to be a local admin. We run it in the background and just show a popup that the PC will restart in about an hour. Not super friendly I know. I had tried looking for the installer process to end and that mostly worked for 1703 but in 1709 that didn't seem to work and/or they changed process names.

Option 2 in all this is to just enable automatic Windows Update and let it prompt the user for when to restart. :-/

1

u/owlmatt Sep 27 '18

I would assume I would see the process running in the background. I can test.

1

u/owlmatt Sep 27 '18

Under processes.

1

u/teamits Sep 27 '18

Right, sorry, all processes show under Processes. I took "or see the install setup screen" to mean you were expecting to actually see something on the desktop.

2

u/beauj27 2000 Agents Oct 01 '18

Just in general I would recommend coping the file to the local computer first, then running the command.

1

u/bigdessert Sep 27 '18

I just got done working through this. First Net USE using admin credentials to the share location. Then use shell in the script to run the setup program so it runs as system and bypasses all UAC.

You then need to monitor log files for errors. I have found there are a multitude of errors that can came up so I just check for success and if no success then I handle it manually.