Announcing Windows 10 Insider Fast Build 16257 PC + 15237 Mobile Insider

magilla said:

I missed some of the posts -- now I see that we have a rollback problem --- fudge!

Yes, Sir..... seem to have this latest build stuck in the mud. Can't go forward and can't go backward.

magilla said:

I missed some of the posts -- now I see that we have a rollback problem --- fudge!

WE don't, they do. Looks like they caught this one in time.

Last part sound familiar?

Tweet

— Twitter API (@user) View on Twitter

f14tomcat said:

Sound familiar?

Tomorrow is another day

Geeks, anyone willing to test this? Although a business / enterprise feature, this test can be done on every PC and VM, causing absolutely no harm. It only collects some data, saving it in a .csv (Comma Separated Values) on your desktop. You need to run W10 build 15063 or later.

New Windows 10 deployment system for business and enterprise clients is called Windows AutoPilot. I have been testing it, when it works it's perfect, but I've met an interesting issue.

How AutoPilot works is it registers devices to organisation using three values: device serial number, Windows product ID, and device hardware hash, same data which is base for so called hardware signature used to register W10 digital licenses. With new devices this is not an issue, organisations get this data from hardware manufacturers. When device is registered, Windows and all organisation's software can be deployed without IT department never seeing the device or even never being on same network.

The problem is used devices. To get the data on a used device, user or admin needs to run a PowerShell script on each device which collects the data, saving it to a .csv file, which can then be uploaded to Microsoft Store for Business to register device. I have been trying and trying, having no issues in running the script and collecting required data on BIOS based physical hardware and both BIOS (Gen.1) and UEFI (Gen.2) Hyper-V virtual machines, but the script always fails on UEFI based physical hardware. I thought it to be Secure Boot related issue but have confirmed it's not.

To test if the script works on your machine, if it manages to collect required data, simply run an elevated PowerShell and set script execution policy to Remote Signed:

Set-ExecutionPolicy RemoteSigned -Scope Currentuser

You will be asked to accept policy change. Press Y and Enter. Next, install the script:

Install-Script -Name Get-WindowsAutoPilotInfo -Force

If NuGet package provider for PowerShell is not installed, you will be asked if you want to install it. press Y and Enter.

That's it. Now run the script:

Get-WindowsAutoPilotInfo -OutputFile $env:userprofile\desktop\Test.csv

Notice please: Script and required NuGet provider will together take less than 200 KB storage space on your hard disk.

Was the Test.csv file created on desktop, does it contain device serial, product ID and hardware hash (.csv is normal text file, open with Notepad)?



Or did it fail?



I am mostly interested to hear if script fails on every UEFI based physical machine, and if it works on any VM or BIOS based physical machine?

Thanks in advance!

Kari

Kari said:

Geeks, anyone willing to test this? Although a business / enterprise feature, this test can be done on every PC and VM, causing absolutely no harm. It only collects some data, saving it in a .csv (Comma Separated Values) on your desktop. You need to run W10 build 15063 or later.

New Windows 10 deployment system for business and enterprise clients is called Windows AutoPilot. I have been testing it, when it works it's perfect, but I've met an interesting issue.

How AutoPilot works is it registers devices to organisation using three values: device serial number, Windows product ID, and device hardware hash, same data which is base for so called hardware signature used to register W10 digital licenses. With new devices this is not an issue, organisations get this data from hardware manufacturers. When device is registered, Windows and all organisation's software can be deployed without IT department never seeing the device or even never being on same network.

The problem is used devices. To get the data on a used device, user or admin needs to run a PowerShell script on each device which collects the data, saving it to a .csv file, which can then be uploaded to Microsoft Store for Business to register device. I have been trying and trying, having no issues in running the script and collecting required data on BIOS based physical hardware and both BIOS (Gen.1) and UEFI (Gen.2) Hyper-V virtual machines, but the script always fails on UEFI based physical hardware. I thought it to be Secure Boot related issue but have confirmed it's not.

To test if the script works on your machine, if it manages to collect required data, simply run an elevated PowerShell and set script execution policy to Remote Signed:

Set-ExecutionPolicy RemoteSigned -Scope Currentuser

You will be asked to accept policy change. Press Y and Enter. Next, install the script:

Install-Script -Name Get-WindowsAutoPilotInfo -Force

If NuGet package provider for PowerShell is not installed, you will be asked if you want to install it. press Y and Enter.

That's it. Now run the script:

Get-WindowsAutoPilotInfo -OutputFile $env:userprofile\desktop\Test.csv

Notice please: Script and required NuGet provider will together take less than 200 KB storage space on your hard disk.

Was the Test.csv file created on desktop, does it contain device serial, product ID and hardware hash (.csv is normal text file, open with Notepad)?



Or did it fail as shown in screenshot:



I am mostly interested to hear if script fails on every UEFI based physical machine, and if it works on any VM or BIOS based physical machine?

Thanks in advance!

Kari

On physical, UEFI. This is before it got loaded to spreadsheet. I'll do a VM next.

Code:

Windows PowerShell
Copyright (C) 2016 Microsoft Corporation. All rights reserved.

PS C:\Users\dhubb\Desktop> Set-ExecutionPolicy RemoteSigned -Scope Currentuser
PS C:\Users\dhubb\Desktop> Install-Script -Name Get-WindowsAutoPilotInfo -Force

NuGet provider is required to continue
PowerShellGet requires NuGet provider version '2.8.5.201' or newer to interact with NuGet-based repositories. The NuGet
 provider must be available in 'C:\Program Files\PackageManagement\ProviderAssemblies' or
'C:\Users\dhubb\AppData\Local\PackageManagement\ProviderAssemblies'. You can also install the NuGet provider by running
 'Install-PackageProvider -Name NuGet -MinimumVersion 2.8.5.201 -Force'. Do you want PowerShellGet to install and
import the NuGet provider now?
[Y] Yes  [N] No  [S] Suspend  [?] Help (default is "Y"): y
PS C:\Users\dhubb\Desktop> Get-WindowsAutoPilotInfo -OutputFile $env:userprofile\desktop\Test.csv
PS C:\Users\dhubb\Desktop>

f14tomcat said:

On physical, UEFI. This is before it got loaded to spreadsheet. I'll do a VM next.

I can't understand this! I've only been able to test this on four UEFI devices, all fail, you got it working in first run! What's wrong on my laptop and tablet (and my neighbor's laptop and desktop, after my tests failing asked them to test, too, both failed).

Anyway, thanks for testing this.

VM machine (VMWare):

Code:

Windows PowerShell
Copyright (C) 2016 Microsoft Corporation. All rights reserved.

PS C:\WINDOWS\system32> Set-ExecutionPolicy RemoteSigned -Scope Currentuser

Execution Policy Change
The execution policy helps protect you from scripts that you do not trust. Changing the execution policy might expose
you to the security risks described in the about_Execution_Policies help topic at
http://go.microsoft.com/fwlink/?LinkID=135170. Do you want to change the execution policy?
[Y] Yes  [A] Yes to All  [N] No  [L] No to All  [S] Suspend  [?] Help (default is "N"): y
PS C:\WINDOWS\system32> Install-Script -Name Get-WindowsAutoPilotInfo -Force

NuGet provider is required to continue
PowerShellGet requires NuGet provider version '2.8.5.201' or newer to interact with NuGet-based repositories. The NuGet
 provider must be available in 'C:\Program Files\PackageManagement\ProviderAssemblies' or
'C:\Users\dhubb\AppData\Local\PackageManagement\ProviderAssemblies'. You can also install the NuGet provider by running
 'Install-PackageProvider -Name NuGet -MinimumVersion 2.8.5.201 -Force'. Do you want PowerShellGet to install and
import the NuGet provider now?
[Y] Yes  [N] No  [S] Suspend  [?] Help (default is "Y"): y
PS C:\WINDOWS\system32> Get-WindowsAutoPilotInfo -OutputFile $env:userprofile\desktop\Test.csv
PS C:\WINDOWS\system32>