First Time Bulk Upgrading Windows 10 to 11 via Lansweeper

[LanSweeper1952]

I’m brand new to Lansweeper and  I’m trying to deploy Windows 11 to about 30 Windows 10 machines on our domain. Right now, we use WSUS, but no feature updates for Windows 11 are showing as available, even though in WSUS “Windows 11” is selected under Products and “Upgrades” is selected under Classifications. Lansweeper reports that all devices are capable of upgrading.

I found a script that seems like it could do the install:
$dir = 'C:\temp\win11'
mkdir $dir -Force
$webClient = New-Object System.Net.WebClient
$url = 'https://go.microsoft.com/fwlink/?linkid=2171764'
$file = "$dir\Windows11InstallationAssistant.exe"
$webClient.DownloadFile($url, $file)
Start-Process -FilePath $file -ArgumentList "/QuietInstall /SkipEULA /auto upgrade /NoRestartUI /copylogs $dir" -Wait

When I run this manually, it seems to launch the Windows 11 installer, but I want it to run quietly in the background and only reboot the machines after 5 PM so the upgrade will be done and ready to use Monday morning.

I’m a bit confused about how to deploy this through Lansweeper in a way that’s automated and respects the timing. Any guidance or examples would be hugely appreciated.

Thanks!

[DavidPK]

Hi 

When running commands via the Lansweeper deployment module, keep in mind that what you're effectively doing is sending CMD commands down to the targeted computers, to be run in the user context of the Run Mode user. Most feedback received, that isn't related to Deployment connectivity, is returned directly as a result of running the command on the computer in question.

With this in mind, ordinarily, you should be able to troubleshoot most deployment packages by running the command in your package in a CMD that's running with the same user as your selected Run Mode. The output, if run in the exact same user context on the exact same machine, should match the one received in the Deployment\Installer Logs page.

We, unfortunately, cannot provide in-depth support for creating, modifying or troubleshooting custom deployment packages. Some tips though: 
• Make sure the package itself has a logical path, both for failure and success actions. Check which was the last step performed by the package, via the installer logs.
• If the last performed step was your command step, run this command in similar circumstances in a local CMD. It's possible you're only getting feedback that the .ps1 file was indeed run, but the command contained within it may have failed still, this feedback would be thrown in PowerShell most likely and not CMD. PowerShell feedback is unlikely to be parsed through.
Here's a couple of links on deployments for reference going forward: 
• Deployment requirements: https://www.lansweeper.com/knowledgebase/deployment-requirements/
Creating your deployment packages: https://www.lansweeper.com/knowledgebase/creating-a-deployment-package/