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,


Thursday 11 April 2019

CONT - In-Place Upgrade OS of SCCM Server using CD.Latest

To upgrade the OS of SCCM server from Windows Server 2012 R2 to Windows Server 2016, the upgrade method of Lift & Shift migration is used. The new server with Windows Server 2016 operating system has to be prepared and the below steps that has been implemented. 

1) BACKUP MAINTENANCE TASK

Automate backup for Configuration Manager sites by scheduling the predefined Backup Site Server maintenance task. This task has the following features:
  •  Backs up the site database
  •  Backs up specific registry keys
  •  Backs up specific folders and files
  •  Backs up the CD.Latest folder
EXPORT THE SITE BACKUP
  •  In the Configuration Manager console, go to the Administration workspace, expand Site Configuration, and select the Sites node.
  •  Select the site for which you want to enable the site backup maintenance task.
  •  Click Site Maintenance Tasks in the ribbon.
  •  Select the Backup Site Server task and click Edit.
  •  Select the option to Enable this task. Click Set Paths to specify the backup destination.
Backup folder include:
  1.  CD.Latest folder
  2.  SiteDBServer folder
  3.  SiteServer folder
  4.  BackupDocument.xml
  5.  ConfigMgrBackup
  6.  Smsbkup
RUN THE SETUP
  • Navigate to the location where you put the backup folder and open cd.latest folder.
  • Double click on the splash to run the System Center Configuration Manager Setup Wizard and click Install

  • Choose “Recover a Site” options
  • The “Recover a Site” option is chosen basically is to restore all the configuration of SCCM server which was previously configured. The backup of the configuration will use backup folder that successfully export to selected path. 

  • On Site Server and Database Recovery Options, attached the SCCMBackup folder.
  • In my environment, I saved the backup folder in E:\ named SCCMBackup. 
  • Enter the Product Key
  • For Product License Terms, accept the License Terms and Privacy Statement to continue installation of System Center Configuration Manager. 
  • Attached the prerequisite that have been downloaded.
  • For Site and Installation Settings, set the Installation folder as D:\ as previous installation. 


  • Database Information set to E:\Program Files\Microsoft SQL Server\MSSQL13.MSSQLSERVER\MSSQL\DATA

  • Begin Install 



Footnote: If you encounter any issue or problem, feel free to comment this page...

CONT - Pre-Requsite Installation In-Place Upgrade OS of SCCM Server

This guide can be use for new SCCM installation.

1) Setup Roles and Features for register service account in local administrator group.

Access from the new server. Right click to the Menu and click Computer Management.

Computer Management (Local) > System Tools > Local Users and Groups > Adminsitrators
At administrator properties and add targeted account.

2) Install Role and Features in a Server Manager.


Table below are the checklist of the roles and features that need to be installed by run the ConfigMgr Prerequisite Tools. Click on this link to get the installer  ConfigMgr Prerequisites Tool 3.0.4





Description
Roles
Features
Server Manager Role
Common HTTP Features
Default Document
Application Deployment
NET Extensibility 3.5, ASP.NET 3.5, ISAPI extensions, ASP .NET 4.5, NET Extensibility 4.5
Security
Windows Authentication
IIS 6 Management Compatibility
IIS Management Console, IIS 6 Metabase Compatibility, IIS 6 WMI Compatibility, IIS Management Scripts and Tools

3) SQL Server 2016 Installation

  • Mount *.iso of same version of SQL Server 2016 with old SCCM Server and run the setup.exe with Run as administrator
  • Navigate to Installation options and choose New SQL Server stand-alone installation and all features to an existing installation.
  •  For product Key, enter the product key and click Next.
  •  For License Terms, read and accept the license terms. Click Next;
  • For Global Rules, rule check begins;
  •  For Microsoft Update, uncheck the check mark Use Microsoft Update to check for updates and click Next;
  •  Next, select instance: MSSQLSERVER and click Next;
  • Run Check is in progress
  • For Feature Selection, select Database Engine Services, Reporting Services and click Next;
  • For Instance Configuration, use Default instance and click Next.
  • For Server Configuration, enter Services Accounts with password and go to collation tab;
  • For Database Engine Configuration in Server Configuration tab select Windows authentication mode and add Current User, and Local Administrators Group;
  • In Data Directories, you may change directories path as per your setting:
  •  For Reporting Services Configuration choose Install only, we configure it later. Click Next;
  • For Ready to Install check yourself and click Install;
  • For Complete click Close and reboot system.
4) WSUS Server Roles Configuration

Role
Windows Server Update Services
Features
Default
Services
Default
Database
WID Database
Content Location
C:\Program Files\Microsoft SQL Server\MSSQL13
Once WSUS installation is complete, in the summary window on the Installation progress page, click Launch Post-Installation tasks. The text changes, requesting: Please wait while your server is configured. When the task has finished, the text changes to: Configuration successfully completed. Click Close.

In Server Manager, verify if a notification appears to inform you that a restart is required. This can vary according to the installed server role. If it requires a restart, make sure to restart the server to complete the installation. 

5) Windows Assesment and Deployment Kit 10

Software Version
Features Enabled
10.0.11732
Deployment Tools
Windows Preinstallation Environment (PE)
User State Migration Tool (USMT)

Click the link to download the WADK 10 and PE add-on

To be continued...

In-Place Upgrade OS of SCCM Server - Full Step by Step


The blog will share in details System Center Configuration Manager platform lift and shift configuration for pre-installation, during installation and post installation of SCCM Server 1806 Current Branch version. The physical design of the solution specifies how SCCM component and settings is deployed to match new operating system environment with same or upgrade on specifications of the server. 

The content will be:
1) Backup Maintenance Task
2) Lift and Shift Task / In-place Upgrade Task
3) Pre-Requisite Installation
4)Upgrade OS of SCCM Server from CD.Latest folder
5) Post Installation
6) Verification Checklist

Note: If you can't find the information of above topic in this page, you might select to the next page to continue. Thank you. 

In-place Upgrade OS of SCCM server will involve these below task:-

Server
Task
Period
Remarks
Old Server
Robocopy the required folder
 1 hour
Backup
Backup share permission
 0.5 hour
Old server snapshot
20 Minutes
Backup from site maintenance
15 Minutes
Copy the backup folder to new server
1 hour
Server Readiness
copy cd.latest to new server
20 Minutes
Unjoin domain and shutdown
10 Minutes
New Server
Server rename
10 Minutes
Reboot
5 Minutes
Setup Server Role and Features for SCCM
 30 Minutes
Pre-Requisite Installation
Install SQL 2016
20 Minutes
Install SQL 2016 SP2
15 Minutes
Install SQL Management Studio
6 Minutes
Install WSUS Server Role
20 Minutes
Install WADK
35 Minutes 
Recover a site SCCM (sccmadmin)
20 Minutes
Recover a site
Re-enter user password
 1 Minute

Post Installation
SCCM Agent Installation for new sccm server
15 Minutes
Set the memory for wsuspool
5 Minutes 
Synchronized the updates
1.5 hours
Install RCT *additional
15 Minutes
Server snapshot
40 Minutes
Verification
Generate the default report
5 Minutes
Import the custom report
15 Minutes
Test on updates functionality
 2 hours
Test on Application functionality
 1 hour

Footnote: Period time here is depends on the network speed and environment readiness. Could be shorter.

You might find pre-requisite for in-place upgrade OS of SCCM Server at this link.

To recover SCCM site by using cd.latest folder, here you go click me !

To be continued...

Friday 8 March 2019

SOLVED AADSTS50107 : Requested federation realm object "user10@abc.com" does not exist

You might encounter this error while deploy an Windows Autopilot Deployment for Hybrid Domain Join. Before that, make sure the pre-requisite for Autopilot Deployment is configured successfully. Here I share the main thing to check before deploy.

Device 
1)Windows 10 1809 version
2)Have an internet access connection
3)Have an access to local AD.

Intune
1)Device registered and grouped
2)Assigned deployment profile to the group of autopilot.
3)Assigned Domain Join Profile
4)Add Intune Connector and make sure to stay active

Azure AD 
1)Assigned EMS license to the user

Azure AD Connect
1)Successfully synced
2)1.1.89 version or later and configured as Hybrid Domain Join.

Intune Connector
1)Installed to Windows Server 2016
2)Have an access to internet and local AD.
3)Have a right to local AD to add computer object to local AD.


For this error, after checked on pre-requisite for Windows Autopilot deployment on AD environment. My situation is, currently I set  StaffID as User Principal Name (UPN). For Intune requirement might need email address for login credential. So, AD must change the UPN  to email address instead of StaffID. After change it, user can login to portal.manage.microsoft.com and register the device to Intune Company Portal.