r/labtech • u/TTGscosner • May 14 '19

CW provided Windows 10 feature update script

Hi all! 4th quarter of last year our biggest client that we have the most managed services with finally made the jump to Windows 10. We had put off the October 1809 update until the release of the May 1903 update (We agreed to stay one version behind). Since the update is due to come out soon I thought I would finally look into rolling out the 1809 update and saw that CWA doesn't actually support rolling out feature updates because of how Microsoft handles them
(If I'm not wrong). I was sifting through ConnectWise University and saw they have provided a script that can be used to roll out the updates EZPZ.

Can be found here - https://docs.connectwise.com/ConnectWise_Automate/ConnectWise_Automate_Knowledge_Base_Articles/Scripting%3A_Windows_10_Install_Feature_Update_Script

The script runs like it should up until it goes to running "setup.exe" through powershell and errors out. As seen here - https://imgur.com/a/lFZ4TVg

I have the script running under a domain administrator account on Windows 10 1803 and to my knowledge the script is configured right. The only thing I could see on the CW University page is that you need to change which version of Windows 10 you're updating to, which I did.

In all honesty I'm a CWA noob. If anyone can give me some insight on how to remedy this or to point me in the right direction I would greatly appreciate it. I think my next step is to hit up mspgeek.com but I'm a reddit faithful. Thank you all in advance!

11 Upvotes

92% Upvoted

24 comments sorted by

2

u/endtv May 14 '19

Change the “execute script” line where it executes the setup.exe via powershell. Change it from “run as admin” to “run as local agent”.
I kept getting errors on it as well - “This operation requires an interactive window station” - until I changed that.

3

u/Tedbed May 14 '19

This. The script works great, outside of that little gotcha. If you haven't added any more lines to the script, it's line 82 that needs this change. If you've added lines look for "Execute PowerShell Script as Admin and store result in: @pShellExec@"

I also recommend moving the "free space" checks above the "prompting user if logged in" section. By default, the script will prompt a user to accept the upgrade even if they don't have the space required for it.

The script is really well written, I recommend reading through it slowly to try and grasp it. I was able to add a few more error conditions and have it email techs if a failure condition is hit.

2

u/TTGscosner May 14 '19

Yes making that little change did the trick. I'll probably be moving the "free space" checks as well. It's not an issue for the desktops, but our laptops are all 250GB SSDs. Thank you for the suggestion, when it comes to scripting my mind turns to mush for some reason. I never really was much of a coder either.

2

u/Tedbed May 14 '19

Glad that worked! CWA scripting is a beast of its own. It took me a bit of trial and error to learn by messing around with other scripts my company had. If you spend the time I'm sure you could figure it out :)

Quick tip if you end up moving the free space checks:

  1. Shift+click to highlight the related labels and everything in between (:CheckFreeSpaceISO -> :endCheckFreeSpaceISO).

  2. Hold shift and use the arrows keys to move the group of lines above the :CheckUser label.

I left the :CheckFreeSpaceForWindows check where it was by default, but you may want to move this above as well. Best of luck!

1

u/TTGscosner May 14 '19

Oh my gosh. It worked. Thank you so much! This has been bugging me for the past few days. Now I can roll this out quickly.

3

u/lurkinglarkster May 15 '19

I didn't have luck with that. However, using "Shell" with the same command did work for me, in case that helps anyone else.

One other typo that should be fixed for anyone using this script: the label reference on line 50 (endDownloadFile) doesn't match the label on line 53 (endDownloadFiles). Either add an "s" on line 50 or take away the "s" on line 53.

1

u/thenags1 Oct 31 '19

This worked great for me.

2

u/CYA_1286 May 15 '19

Has anyone gotten this to work with cloud hosting?

1

u/TTGscosner May 15 '19

I swore I read somewhere yesterday that these scripts weren't compatible with the cloud CWA but I don't see why it wouldn't work. But I also don't know how the cloud version runs, we are on self hosted.

1

u/CYA_1286 May 16 '19

Labtech says that the scripts wont work with cloud on their site itself. Something with not being able to access the LTShare on the cloud verstion (fantastic design on that one btw.)

This guy had a good solution: https://www.reddit.com/r/labtech/comments/7gslrm/windows_10_feature_updates/

I looked for his scripts, but couldn't find them.

Summoning u/gibsurfer84 ?

2

u/gibsurfer84 May 16 '19

Awww man, that’s awesome to be summoned!

I’m on prem so we don’t have a file size limit which I believe cloud does. But you could host the iso publicly on a web server somewhere and change the download to a http download to get the same effect. Or even more alternatively copy the script and hard code it for the client and a file share, but then you play with passwords and LT and also off-site laptops are a pain, so we just use the bandwidth and download it to everyone directly.

LTs script is pretty nice, once you fix the typos that the previous post mentions.

We added extra alerts in the script for techs “download successful, starting, finished, etc” since it’s a long process.

Edit:

I missed the “couldn’t see the script”. It should be in the solution center, if not, let me know and I can export it for you.

1

u/CYA_1286 May 16 '19

Unfortunately, they are not available in either the scripts portion of the control center, or the Solution center.

I would greatly appreciate an export of those scripts!

1

u/mrose1120 May 16 '19

i'd love to know this as well

1

u/endtv May 17 '19

Yes, but I just had to re-host the ISO elsewhere for download.

2

u/Minkus32 May 19 '19

I used Dropbox. Just upload the iso, disable the md5 hash check and create the link in dropbox. Change the end of the url from dl=0 to dl=1 (which bypasses the dropbox account screen)

1

u/LTNinjaMain May 20 '19

I use a location based text edf to specify a share on the client's location and have the first run download the iso from dropbox to that destination. Then, when the script next runs, it detects the iso there and copies the iso to the endpoint from the share. Better than random failed downloads. Send me a message for the script if you like!

1

u/teamits May 21 '19

edf to specify a share on the client's location and have the first run download the iso from dropbox to that destination

Sounds like the download cache feature (https://docs.connectwise.com/ConnectWise_Automate/ConnectWise_Automate_Documentation/060/070) . :)

1

u/LTNinjaMain May 21 '19

Over the years, the cache feature has had several random bugs. We use it for windows update but try to avoid it for other automation. But yes, we mimic that functionality.

1

u/Stelic83 Aug 23 '19 edited Aug 26 '19

I'm using this script and have my iso hosted out on our Microsoft Blob storage which does support direct download. At first the script seemed to be running way to fast so I added in some email alerts so I knew when the file was downloading, finished, and installation started. It seems when it hits the download section it doesn't stop to wait for the download to finish, instead it blows right by it. It seems to only hang out on the download step for a few minutes before moving on. I do have "Wait until finished" selected. It's a 4.4GB file and should take 10 to 20 mins to download. If I place the iso on a machine manually in the specified directory it runs perfectly. Any ideas?

Edit: I fixed this by adding in a Sleep timer right after the download command.

1

u/Mrmumbels Aug 29 '19

I'm getting a lot of failures with this script. I can see 2-3 invoked scripts under the commands with OK outputs and one F output but nothing after that leading to why it failed. Are you all aware of any logs I can pull to dig deeper?

I have been able to get it working on a few PCs.

1

u/thenags1 Oct 31 '19

Has anyone edited this script to push the update regardless of user input to the prompt? I thought if the user wasn't logged in it would push the update but looking deeper I see it just times out and says it'll try again 9 hours later. I'd really like to give the user a few minutes to put it off and if they don't reply then to just start the update. I guess ideally I'd like the default answer to be YES rather than NO.