The term get-windowsautopilotinfo.ps1 is not recognized as the name of a cmdlet

Yesterdays changes [described in this blog] were probably bigger, but after a couple of suggestions in response to that update have caused me to publish another new version.

For the first change, you can now build a CSV file with the UPN of the user that should be assigned to the device. Just specify the -AssignedUser parameter like so:

Get-WindowsAutoPilotInfo.ps1 -GroupTag Blah -AssignedUser -OutputFile c:\mydevice.csv

That CSV can then be imported into Intune directly [it wont work with Microsoft Store for Business or Partner Center].

The next change adds an -AssignedComputerName parameter that can be used to specify the computer name that should be assigned when Autopilot deploys the device. This only works for Azure AD Join [sorry], and because you cant import a CSV file to Intune with this value it has to be done after the import is complete, hence it is dependent on the -online switch. Heres the syntax:

Get-WindowsAutoPilotInfo.ps1
[-GroupTag ] [-AssignedUser ] [-Append] [-Online] [-AddToGroup ] [-AssignedComputerName ] [-Assign]

Heres an example:

I specified a computer name of TEST-091 along with other values [group tag, assigned user, etc.]. You can see the timings for this as well, with it taking about three minutes to import the device into Autopilot and sync it back into Intune [which happens automatically], and then another three minutes to assign the Autopilot profile [a feat that isnt often duplicated many of my tests took closer to 10 minutes to do that].

So download [from Get-WindowsAutopilotInfo, now up to version 2.5] or install [using Install-Script Get-WindowsAutopilotInfo] the new version to try it out.