woensdag 12 november 2008

SCCM migration issues

Hello,

It's been a long time that I have posted something because I was very busy prerparing a SCCM migration by one of my clients.

The goal:

Upgrade SMS 2003 SP3 hierarchy.
One of the primaries was located on a VM Ware and this one needed to be migrated to a physical 64-bit machine.

Most issues I had was located on this primary.

I did first an in-place upgrade of the VM Ware.

The upgrade wizard failed all the time with fatal errors during the installation of the INBOX_MANAGER. After investigating for hours (I needed Microsoft support for this) we noticed that there were corrupt ct2 files in the hman inbox.
We removed the corrupt files and executed a site reset hoping that the wizard should continue installing the failed components.

Originally we thought SMS was working, but after a while I noticed all my clients had error 401 in their ccmexec.log. The complete SMS console was green so no issues following SMS. After some investigation again we discovered that IIS was running in 5.0 compatibility mode. Normally SCCM should change this but probably because of the failure of the wizard this task was skipped.

When trying to remove the limited status of IIS we noticed that the after IISRESET the option was always checked again. After some hours we discovered that the service "Internet Printing" was preventing IIS to stop this compatibility mode.
When removing the Internet Printing everything worked.

So far the in-place upgrade of the VM Ware...

The next weekend I had to move the VM Ware to physicall hardware.

I took an SMS backup with the "backup site" task.
When trying to restore this data with Site Repair wizard... gues what... FATAL ERROR.
After some attempts I gave it up and restored the SQL database manually.
The restore of the SMS data luckily succeeded via the Site Repair Wizard.

All SCCM stuff was working, only OSD was suddenly very slow.
This patch resolved the OSD issue:

http://support.microsoft.com/kb/955955

So this was a short description of my SCCM rumbles ;-)
The misery someone can have in case the wizard are failing...
Locations of visitors to this page