Configuration Manager Post In-place OS upgrade, CreateMedia.exe finished with error code 80004005

Another short post to highlight an issue after performing an In-place OS upgrade from Windows Server 2008 R2 to Windows Server 2012 R2 – Configuration Manager 1602

When attempting to create standalone media on a remote console, the error below was displayed in the CreateTsMedia.log 

Retrieving info for package H0100143.4

Content library is on remote system ‘SiteServer’
Cannot connect to remote registry on ‘SiteServer’ (frequent cause is remote registry service is not running) 
Trying to use WMI to read from the remote registry.
Failed to open to WMI namespace ‘SiteServer\root\default’ (80041003)
Unable to open WMI namespace ‘SiteServer\root\default’ (0x80041003)
Failed to connect to namespace ‘root\default’ needed to read remote registry values. The user who creates media has to be local administrator on remote DP on ‘SiteServer’ which contains media content.
Content library location could not be found.
Omitting package source ‘SiteServer’ because content library location or its usable drives cannot be read from registry of ‘SiteServer’
CreateMedia.exe finished with error code 80004005 

As you can see, the process is unable to read the content library location from the registry.

Content library location could not be found.
Omitting package source ‘SiteServer’ because content library location or its usable drives cannot be read from registry of ‘SiteServer’

After a while of troubleshooting, I discovered that the remote registry access had been removed from the below registry string, this entry bypasses restrictions for remote services.

remote-registry Once I restored this entry the process was able to complete on a remote console.

Further information about access to remote registry here 


Error opening remote console after Configuration Manger in place OS upgrade

Quick post about issues connecting to site with remote console after upgrading the server OS from Windows 2008 R2 to Windows Server 2012 R2

After the upgrade all remote console were unable to connect to the site


After reviewing the SMSAdminUI.log  on one of the remote devices, there were access denied errors.

\r\nSystem.Management.ManagementException\r\nAccess denied \r\n   at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode)
:System.Management.ManagementException\r\nAccess denied \r\n   at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode)

I granted one user local admin rights to the SCCM server, which was hosting the SMS Provider and the console access was restored.

I reviewed the DCOM permissions which were fine, however, the WMI permissions for the SMS Admins group were missing!

I check the WMI permissions using wmimgmt.msc and added the required permissions




I removed the local admin permissions and tested again. Console access was working again

More detail

In order to access a local or remote SMS Administrator console, users must be members of the SMS Admins local group. The SMS Admins group is explicitly granted Enable Account and Remote Enable on the Root\SMS namespace. The SMS Admins group provides its members with access to the SMS Provider, through WMI. Add Users to the SMS Admins group when they need to access the SMS Administrator console, but do not have to be Local Administrators

Console access troubleshooting


Configuration Manager Assessment

Things to consider when doing a Configuration Manager assessment:

Network environment:

What does your network topology look like?

What are the  WAN link speeds, network latency and bandwidth?

What network infrastructure and security devices are in place?

What ports and protocols are allowed through these devices?

What are the usage patterns for network resources, network utilization?

At which locations will you provide services?

What client systems are at each location?

How many devices are to be managed in total?

What users are at each location?

How do external/remote users connect to the corporate network?

Is support for 802.1X authentication required?

Is there a PKI implementation?

Is a POC environment available?

How are change requests handled?

Active Directory environment:

Do you have multiple AD forests?

What are the trust relationship if so?

Will you support computers in workgroups?

SCCM Operators

Who will use the system?

What tasks will they be required to do?

Server and Data Center infrastructure:

Is server infrastructure centralized in a few large data centers or is it distributed?

Are some data centers better connected than are others?

What are the hardware standards?

Is virtualization preferred?

Installed client base and hardware refresh cycle:

What is the hardware and operating system (OS) mix for the installed PC base?

How are new systems imaged?

Is PXE booting  to install images required?

What mobile devices are in use?

Is there a need to support embedded systems?

How often are systems replaced?

Are users allowed to bring their own systems?

Is there a planned OS upgrade?

Who are you deploying Windows to or for?

What OS are you deploying?

What applications do you want to deploy with the OS?

Will this be different for different user or system roles?

To which hardware models are you deploying the OS?

Will you support mobile device client such as smartphones, or Internet-only clients?

Will App-V be enabled for deploying virtualised applications?

How are clients being updated with Windows patches?

Are third party update patches required?

Existing SQL Server deployment:

Will you be using existing SQL servers?

Do these systems meet ConfigMgr requirements?

Are SQL servers clustered?

Are SQL reporting services deployed?

Storage and backup infrastructure:

What storage technologies are in use?

How is data replicated between storage systems?

Details of the design such as optimum server placement, hardware configuration,

and client installation methods depend on the IT infrastructure and services you

have in place.