Tag: SCCM

Windows 10 1809 In-Place Upgrade SCCM

Windows 10 1809 In-Place Upgrade SCCM

Windows 10 1809 In-Place Upgrade using SCCM

I recently configured a Windows 10 1809 upgrade at a time when Microsoft had placed a block on the upgrade release due to driver issues among other issues. Whilst on my endeavour to get an upgrade working from 1803 to 1809 I came across issues which could possible save you time.

The upgrade process is fairly simple.

  1. Extract your Windows 10 ISO
  2. IMPORTANT, you must have at least the November 2018 CU for Windows 10 1809 KB4467708. Without this CU your in-place upgrade will fail. DISM the latest cumulative updates into the image, see my post on how to do this, click HERE.
  3. DISM any other settings you require such as language packs or removal of APPX packages. Note that if you already removed appx packages they will not re-install when you upgrade, however there are two new appx packages in 1809 that will install.
  4. Places the extracted files into a folder which SCCM can access.
  5. Add your 1809 OS to SCCM. Click Software Updates > Operating Systems > Operating System Upgrade Package
  6. Distribute the OS Upgrade package.
  7. Create a new Upgrade task sequence and keep the options as default.

 

Issues encountered

0x80004005 – this is an generic error code and does not tell us much. You have to check the following log files:

  1. SMSTS log file located in C:\Windows\CCM\Logs\SMSTS.log
  2. C:\$Windows.~BT\Sources\Panther\CompatData_…xml
  3. C:\$Windows.~BT\Sources\Panther\setupact.log

When investigating the log files I found the below error. It states that their is a mismatch in the language packs. In essence the Windows 10 ISO comes with English US language. However on my device I had only English UK. The device and OS media must match with the language. I therefore had to dism my language pack into the Windows 10 media. Ensure you generate a lang.ini file when you dism the language packs. I will write a post on how to correctly dism language packs.

<HardwareItem HardwareType=”Setup_MismatchedLanguage”><CompatibilityInfo BlockingType=”Hard”/><Action Name=”Setup_MismatchedLanguage” ResolveState=”Hard”/></HardwareItem>

That’s all for now folks. Let me know how you get on in the comments below.

Thanks
Kam

How to manually install SCCM 2012 R2 admin console

How to manually install SCCM 2012 R2 admin console

After you upgraded your ConfigMgr to the new Version you need to upgrade both the Clients and the deployed consoles for your IT staff.

Console upgrade

In the Installation Media go to SCCMISO]SMSSETUP\BIN\I386 and copy both “AdminConsole.msi” and “ConsoleSetup.exe” to an Application folder for deployment.

Folder

Then you need to create a package or application  with content to deploy the new console.


"ConsoleSetup.exe" /q TargetDir="%programfiles%\ConfigMgrConsole" EnableSQM=0 DefaultSiteServerName=FQDNSiteServer

1. create a new package, name it and define the source folder where you put the files in

SCCMR2ConsolePackage01

2. create a standard Programm

SCCMR2ConsolePackage02

3. configure the user experience

SCCM2012R2SP1AppConsole03

 

4. enter the installation program information

SCCMR2ConsolePackage03

Finish the wizard, distribute the package and deploy it to your clients.


 

Or you can create an application.

I won’t show the steps to create a  new application but you have to create a new deployment type “Script Installer”

1. create the deployment type, add the location to the folder you created earlier. then you need to define the

Installation program
"ConsoleSetup.exe" /q TargetDir="%programfiles%\ConfigMgrConsole" EnableSQM=0 DefaultSiteServerName=FQDNSiteServer
MsiExec.exe /X{7952AC6D-315A-4791-BDE3-0976D6E0AD72}

SCCM2012R2SP1AppConsole01

2.  define the deployment detection. I got that one from the AdminConsole.MSI.

Product Code

 

 

SCCM2012R2SP1AppConsole02

3. Next,next…Finish

4. Distribute content and deploy it to your clients


Client Upgrade

To Upgrade the client you can simply go into the administration Tab -> Site Configuration – Sites and select hierarchy settings and select the days in which all client should be upgraded.

hirachysettings hirachysettings02

This will create a scheduled task on the client which will trigger the client upgrade within the given time period. You can also run this task manually to upgrade the client

TaskScheduler01

This setting will always upgrade the clients to the newest version after you install a new UR!

If you don’t want to do this, you have to create an upgrade package. These packages will be created by the UR package and will be available for deployment after you installed the next UR.

To monitor this you can create a collections with these queries

All SCCM Clients below Version 5.00. 8239.1000

select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System WHERE Client = 1 AND ClientType != 3 AND ClientVersion IS NOT NULL AND ClientVersion < '5.00. 8239.1000'

All SCCM Clients at or above Version 5.00. 8239.1000

select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System WHERE Client = 1 AND ClientType != 3 AND ClientVersion IS NOT NULL AND ClientVersion >= '5.00. 8239.1000'

If you have any questions put them in the comment section.[/fusion_builder_column][/fusion_builder_row][/fusion_builder_container]