Sunday, 19 January 2020

Windows Autopilot Hybrid Join Summarization


As per previous post main pre-requisite for Windows Autopilot deployment I've summarize the important configuration or pre-requisite for Windows Autopilot deployment. 

From the picture above, it is overall process for Windows Autopilot deployment from end-user perspective and administrator perspective. Let me elaborate on the process by the sequence. 

a) Windows 10 devices must 1809 version or later to deploy with Windows Autopilot. 

Once booted up and device must connected to the network that have an access to the local AD to succeed the process without using any VPN. (Note: VPN connection to On-Prem AD is not supported on Hybrid Domain Join for Windows Autopilot)

b) Network connection is required for the device to get connected to Autopilot Services and able to push the setting and policy configured.

c) Create the list of policy and profile below.

i- Register the device by import a hardware ID to the Intune and assign to Autopilot group
ii- Create an Autopilot Profile
iii- Create a Device Configuration
iv- Assign the profile to Autopilot group
v- Assign an Enrolment Status Page to the group
vi- Create and assign Domain Join Profile

d) From the Autopilot Services, it will connected to AAD to check if the user assigned with EMS license. In case user has no assign to the EMS license, it will not get the Autopilot Services and proceed to normal OOBE.

e) With AADC, ADDS users are synchronized to the Azure Active Directory.

f) Intune Connector must be installed on Windows 2016 server or later to start communication with Azure tenant.

Sunday, 21 April 2019

CONT - Post Installation after In-Place Upgrade OS of SCCM Server

A few steps must be configure after in-place upgrade OS of SCCM server to continue using the console on the new server. Administrator have to re-enter the user password same as previous user. Where you can find it? Navigate to Administration workspace, expand Security and select Administrative User. 

If your console has more than one user account, all the user account has to re-enter the password by right click to the user > Set > re-enter the password and verify to test the connection. 


Once it's successfully verified, it will require to test connection of data source for SQL Server. 


Done !

For your attention, administrator will need to re-configure for those configuration or settings on the new server will not gonna restore:
  • Email notification for alerts, 
  • Service account for reporting services point,
  • Custom report
  • Updates (need to resync)
  • SCCM agent to the new server of SCCM server,