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 

Advertisements

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.

ConfigMgr 2012 determine if there is a performance problem

The number one reason that small sites like this have performance issues is because of disk IO.  If this is a virtual machine, ensure that you are following the vendor recommendations for virtualizing SQL (don’t over commit processors/cores, ensure SQL data files, tempdb, and logs are on separate spindles, format SQL drives with 64KB block sizes, split SQL data files).

CPU does not matter too much. Disk i/o is more important. Also see http://technet.microsoft.com/en-us/library/hh846235.aspx#BKMK_ReqRemoteSiteSystems
MP replica might take some load off of an MP, but it also adds extra load because of SQL replication.
Content transfer can be scripted: http://technet.microsoft.com/en-us/library/jj821831(v=sc.20).aspx(in case you did not use a DP group).

Are you experiencing current perf issues with all roles on the site server itself? Can you describe these perf issues?

Have you setup a DB re-indexing and statistics rebuild agent task?

Have you run perfmon to baseline the perf of the system?

Is the system a VM on an over-committed host and/.or is it sharing spindles with other applications?

System Center 2012 Configuration Manager Best Practices

Taking Your Server’s Pulse

Build a FREE System Center 2012 Configuration Manager SP1 Lab in the Cloud

System Center 2012 Configuration Manager SP1 ( “ConfigMgr 2012 SP1” ) offers lots of great new capabilitiesfor IT Pros, but building a lab to evaluate, test and study ConfigMgr can be challenging if you don’t have spare hardware capacity in your data center.  In this Step-by-Step Guide, I’ll walk through the steps that I used to build my ConfigMgr 2012 SP1 demo and study lab in the cloud on the Windows Azure platform.  Click here

ConfigMgr SCCM 2012 SP1 Upgrade Known Issues

CM 2012 Service Pack 1 was released and available for download at Microsoft Volume Licensing (MSVL) site. More details here. Unfortunately, loads of people are reporting issues in the forums and through blogs. Microsoft has identified some problems with SP1. Upgrade checklist

1. ConfigMgr 2012 SP1 prerequisite checker will end up with loads of warnings if your primary server is having remote site Systems (MP, DP and SUP) in the different Domain without trust. Warnings will be related BITs, IIS and Server service. You may safely ignore those warnings. These warnings could be because of the account which runs prerequisite checker don’t have proper access on Remote Site System/s.

2. When you upgrade to ConfigMgr SP1, the built-in collections are overwritten in the site database. If you have customized a built-in collection, create a copy of that collection before you upgrade. More details kb/2739984/.

3. SUP/WSUS ports are getting changed to default ports. More Details here.

4. Client Agent Setting – update policy interval is not changing from 3 minutes to 60 minutes. More Details here.

5. It’s recommended to first uninstall the WAIK (Windows Automated Installation Kit) and then Install Windows Assessment and Deployment Kit (ADK) for Windows 8 before installing ConfigMgr 2012 SP1. More details about how to Upgrade SP1 in kb/2801416.

6. Client push fails with Authenticode Signature error. More details here. KB article /kb/2801987

7. SUP won’t work after upgrade. To avoid this, we need to ensure that CAS, Primary and Remote SUP site systems with WSUS patches KB 2720211 and KB 2734608.

8. Client installation error with MicrosoftPolicyPlatformSetup.msi here.

9. Disable Antivirus before upgrade to ConfigMgr 2012 SP1

10. Any existing Antimalware Policy (under Assets and Compliance > Endpoint Protection > Antimalware Policies) can’t be modified. More details here.

11. Make sure your SQL version in Secondary Server meets the supported configuration.

12. Some other miscellaneous issues related DP and security share related issues. More details here.

13. Boot Images are NOT getting updated after ConfigMgr 2012 SP1 upgrade. More details here.

14. Remote PXE (in DP role) doesn’t work until we disable the pxe ‘point’ and enable it again.

15. Already available List of KB articles or hotfixes for SCCM 2012 SP1. More Details here.

16. SMS Replication Configuration Monitor is reported in critical status. The replication link status is getting degraded and back to active within a minute. Loads of people are reporting this issue. See Technet forum article here.

17. Use Custom Web Site or Port Option is Grayed out on CAS Properties After CM12 SP1 Upgrade. More Details here.

18. CM 2012 SP1 Linux Client Error on Software Inventory. More details here.

Another Know issues listed down in ConfigMgr 2012 SP1 Technet release note.
1. A Migrated Configuration Manager 2007 Configuration Baseline Fails to Evaluate on Client Computers.

2. Software Update-Based Client Installation Fails Failed to publish sms client to WSUS, error = 0×80131622.

3. Virtual Application Fails to Install with Event ID 1008 in the Windows Applications and Services Logs.

4. Error Microsoft.Reporting.WinForms.ReportServerException when you run the Roaming User Profiles Health Report.