Windows Autopilot Device Preparation aka Autopilot v2 Step by Step Guide

-

 Windows Autopilot device preparation aims to simplify device provisioning, enhance the overall setup speed, and improve troubleshooting capabilities. This is also known as Windows Autopilot v2. The Windows Autopilot device preparation doesn’t require importing the device hash and it simply uses the device serial number to identify a device as a corporate device.

When using Windows Autopilot device preparation, the device should not registered with Windows Autopilot service. If the device is already registered with Windows Autopilot service, you need to deregister the same. Otherwise, the Windows Autopilot policy will take precedence.

Please see the complete article on my new blog https://techuisitive.com

https://techuisitive.com/windows-autopilot-device-preparation-aka-autopilot-v2-step-by-step-guide/



Comments

Post a Comment

Popular posts from this blog

SCCM Software Distribution Troubleshooting

-
Image
1.    Content Monitoring and Validation from Console The below article provide details of content monitoring and validation from console. https://blogs.technet.microsoft.com/inside_osd/2011/04/06/configuration-manager-2012-content-monitoring-and-validation/ 2.    Reports SCCM reports should be the first thing to check the software deployment status. By looking into the report you can determine the scope of failure such as large scale failure, location based failure or client specific issues. A large scale failure may be caused by an issue with package or programe while issue can be related with specific client if deployment failure rate is low and limited to few clients. There are multiple reports available for each category.  All Software Distribution reports can be found in below folders under Monitoring > Reporting > reports. ·          Software Distribution – Collections · ...
Read more

Powershell - List AD Organizational Unit and GPOs linked to them

-
The below script will search Active Directory for all Organizational Unit which contain specific name and list them along with all Group Policies linked to those OUs. Example: The below command will get a list of all OUs which name contains 'Test'. It will also show the details of all GPOs linked to OUs. Usage Example: .\Get-OUList.ps1 –OUName “Test” #Script [ CmdletBinding () ] Param (   [ Parameter (Mandatory = $True ) ]   [ string ] $OUName   ) $invocation = ( Get-Variable MyInvocation ) . Value $directorypath = Split-Path $invocation . MyCommand . Path $outputfile = $directorypath + "\Result.csv" $OUName = "*" + $OUName + "*" $Results = @() $OUList = Get-ADOrganizationalUnit -Filter * | Where-Object -FilterScript { $PSItem . distinguishedname -like $OUName } foreach ( $OU in $OUList ){     $LinkedGPOs = Get-ADOrganizationalUnit -Identity $OU | select -Expa...
Read more

Troubleshooting System Center Endpoint Protection (SCEP) Client

-
Image
Microsoft System Center Endpoint Protection provides an antimalware and security solution for the Microsoft platform. This can be integrated with System Center Configuration Manager. I have consolidated the information which are useful for SCEP client side troubleshooting. 1. Managing Endpoint Protection client with Command Line Interface – MpCmdRun.exe The MpCmdRun.exe (Microsoft Antimalware service command line utility) is very useful tool to manage local Endpoint protection client with command line.  The MpCmdRun.exe is located in C:\Program Files\Microsoft Security Client folder. On Windows 10 machines, the MpCmdRun.exe is available in C:\Program Files\Windows Defender folder. When executed, this command automatically creates a log file named as MpCmdRun.log in C:\Users\ username\AppData\Local\Temp folder. This log file records the commands that are executed using MpCmdRun.exe. Few of most commonly used command lines are listed below. For a complete l list of av...
Read more