Jump to content

Matthew Mclaughlin

Members
  • Content Count

    12
  • Joined

  • Last visited

Community Reputation

0 Neutral

My Information

  • Location
    UK
  • Agent Count
    < 500 Agents

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Hi @Jonathan88 What is it that you would like to know?
  2. Hello @ErinC I made this blog post that may help! https://www.msp-blog.com/connectwise-automate-windows-10-build-upgrade-script/
  3. @Aenabs Thanks for coming back, I'll run through the updated script you've made and check it out, sounds promising! I get that you have the ISO's staged at each client, but what about when Windows releases the next ISO after 1903/1909 etc, how do you re-deploy those ISO files to your clients Servers?
  4. @Aenabs Is there a version check in the script to modify to not apply the update if the version is below a certain threshold? I'm getting the results of some upgrades and the client PC's are actually on later versions of Windows 10 than the ISO I had deployed almost like they are downgrading slightly Here is one of the Followup emails showing what I mean: The results for the upgrade are as follows: OS Version successuflly changed after update. Old Version: Microsoft Windows [Version 10.0.18362.418] New Version: Microsoft Windows [Version 10.0.18362.239] I've since set up the 1909 ISO to be deployed so it's not a huge drama
  5. @Aenabs Scratch my previous post, I've managed to get it working using the File Copy as Admin function inside my script So I have it set up this way: 1 x script to download the ISO from the cloud to the server (Currently I'm downloading ISO's from Microsoft, but they only last 48 hours) I'm having difficulties storing ISO's in SharePoint as the shared URL isn't a direct URL to the file itself so any advice on how you're managing this (we're on hosted Automate so can't store ISO's here). ISO is downloaded into the Cache directory 1 x script to copy the file from cache to C:\ISO\windows10x64.iso on the local machines Your script then follows on with the upgrade which works great for us, we're just having the issue of clients not being alerted but we're scheduling the upgrades for around 6PM and emailing clients prior to leave machines on. I suppose my biggest issue at the moment is getting a public URL that I can script into the file download function so that clients without caching/servers can upgrade individually so any feedback on how you're achieving this would be amazing!
  6. @KI_EricS@danialbulloch Thank you both for the responses, they're full of useful information The 'test' client at the moment has a 2016 Domain Controller, all 50+ Windows 10 devices joined to the domain, Domain Admin creds set at location level and #whoami in command line from Automate shows the domain admin credentials, We've set caching up and Automate have remotely connected in to confirm it is correct however doesn't seem to be working so they are investigating that. I've just found an article to get a public URL from Microsoft for an ISO for 24 hours (I'm not sure if this is how you're getting them or if you're getting them from Visual Studio subscriptions etc so would be interested to here your thoughts on that, but I'm now creating a script to download the ISO to the server (is marked as a Master) and then to run a second script on client PC's to download the ISO from a UNC path on the server (is there a way to create variables for this so the script will work across all clients in automate possibly from EDF's? I tried last time to use File Copy as Admin from an EDF it didn't actually pull the location out of the EDF Thanks for all your help with this! It's been a nightmare.
  7. Hi @danialbulloch Thanks for the information and @KI_EricS it's very helpful! I'm having issues with Caching at the moment and Automate Support seem to think it's a known issue, are you able to offer any guidance on getting the ISO from a client server share (Accessible by all client PC's) to each client PC's LTSVC\Packages folder using the script? I've tried using File Copy/File Copy as Admin and it seems to continue failing We have a client with 50 Windows 10 Machines and downloading the ISO to each Computer from a shared web location would kill bandwidth
  8. Hello @Aenabs Out of interest, how did you get the script to copy the ISO to the local machine? Did you use variables so that the script works universally or do you have to modify it one by one? I can't find a realistic way to get the ISO onto each individual PC
  9. @Oddyseus1911 Unfortunately the file copy didn't work, I tried using the local server as the Automate Cache and the file copy still failed, Still looking for a way to get the ISO distributed to each client PC without buying some software. Also tried using robocopy in CMD via Automate but it didn't work. Would be interested to see how others are getting around this issue
  10. Hi @Aenabs We've still yet to achieve this, I've tried looking at possibly creating a script using the file download function to an internal server address, but with little success. I'm thinking next possibly to create an automate script using robocopy going forward to distribute the ISO but haven't had time to test it yet. Have you had any success?
  11. Hi All, After speaking with ConnectWise, I understand there is a script from the Solution Centre called 'Windows 10 - Install Feature Update' which requires you to deploy the latest build of Windows 10 to your LTShare, but that it's only a supported feature on-prem and cloud partners currently don't have support for this.. https://docs.connectwise.com/ConnectWise_Automate/ConnectWise_Automate_Knowledge_Base_Articles/Scripting%3A_Windows_10_Install_Feature_Update_Script As a potential workaround, ConnectWise have told me I can individually place the ISO under the LTsvc\packages folder on each machine. Rather than download 50 x 4GB ISO's for a client, I thought to use the server to then have Automate copy this locally, but I'm struggling. My plan was to create an EDF whereby we can enter at the location level the path to the ISO and then call this in a variable for the Script copy as Admin but it doesn't seem to unpack the variable path and the script fails. Has anybody else had any success upgrading from 1803/1809/1903 using Automate? Any help would be appreciated!
  12. Hi All, After speaking with ConnectWise, I understand there is a script from the Solution Centre called 'Windows 10 - Install Feature Update' which requires you to deploy the latest build of Windows 10 to your LTShare, but that it's only a supported feature on-prem and cloud partners currently don't have support for this.. https://docs.connectwise.com/ConnectWise_Automate/ConnectWise_Automate_Knowledge_Base_Articles/Scripting%3A_Windows_10_Install_Feature_Update_Script As a potential workaround, ConnectWise have told me I can individually place the ISO under the LTsvc\packages folder on each machine. Rather than download 50 x 4GB ISO's for a client, I thought to use the server to then have Automate copy this locally, but I'm struggling. My plan was to create an EDF whereby we can enter at the location level the path to the ISO and then call this in a variable for the Script copy as Admin but it doesn't seem to unpack the variable path and the script fails. Has anybody else had any success upgrading from 1803/1809/1903 using Automate? Any help would be appreciated!
×
×
  • Create New...