Fatal error during upgrade to SCCM SP1

First of all check the configmgrsetup.log file.

If SCCM and WAIK are not installed on the OS driver (another partition)

and you receive 1603 error during the Waik Installation, this is the reason:


During the ConfigMgr 2007 SP1 upgrade process:
WAIK was uninstalled automatically
WAIK was attempted to automatically install using default settings.When the upgrade attempted to reinstall the WAIK it defaulted installed to the default OS drive. This failed on my server.

Solution

Before attempting to run SP1
Uninstall WAIK via ARP (Add Remove Programs) (if the previous attempt of SP1 hasn't done it for you)
Install WAIK via the new copy in: . \SCConfigMgr07_UPD_EN\SMSSETUP\WAIK\
Run the SCCM SP1 upgrade again

ZTI ERROR - Unhandled error returned by zticonfigure: Object required (424) and Unable to find CustomSettings.ini, rc = 1

If you can find this errors somewhere in you log files you are probably refering in your CS.ini to a database value that does not exist.

Example:

In the past I used the column keyboardlocale in BDDAdminCorDB. In my CS.ini I had a line keyboardlocale=%keyboardlocale%

I removed the column because I use 'InputLocale' in place, but I forgot to remove the line out of CS.ini.

The result was that the "configure" action was hanging without prompting any error and my ztigather.log showed the errors of the title of this post.

After spending some days of troubelshooting I discoverd this was the root cause.

zti error opening sql connection: cannot initialize sspi package

When this error appears in your ztigather.log you have to add security.dll to your winpe.wim image of WAIK 2.0 to make a named pipe integrated security connection possible.
You can find the dll in the system32 directory of a Vista box.
Add this dll to the system32 directory of the wim file.


OR

you can install WAIK 2.1 this has named pipe integrated security connection on board by default.

Upgrade MDT

Microsoft released recently a new version of MDT. This newer version is providing a better support for Vista SP1 and Server 2008 AND is solving some bugs of previous version
(like one is descirbed in the previous post).

If you don't want to loose your Boot images, Task Sequences and MDT packages you can upgrade MDT.

Check Michael Niehaus's blog, he gives a very nice overview of the different upgrade scenarios and
explains the best manner to do it.

http://blogs.technet.com/mniehaus/archive/2008/03.aspx

Not able to change MININT-xxx name with MDT-ZTI-SCCM

Hi All,

If you want install PCs Zero Touch with MDT via SCCM and you notice in the ztigather.log that the PC is correctly gathering the correct value (machinename) out of the database but the value is not getting applied.

This in fact caused by bug into MDT, the reason is that that diskpart is choosing the first drive letter for the primary partition. The drive letter turns into E and the system cannot find the sysprep.inf. (in the postinstall phase this is file is supposed to get modified).

To solve this add following lines in zticonfigure.wsf starting from line 159.

ElseIf oFSO.FileExists("E:\sysprep\Sysprep.inf") then
sSysprepInf = "E:\sysprep\Sysprep.inf"oLogging.CreateEntry "Found Sysprep.inf at " & sSysprepInf & ".", LogTypeInfo

ADO connecton errors when trying to connect to MDT database

Hi all,

If you have following error in ZTIGather please check out my post on Technet.

Error: Unable to create ADODB.Connection Object"

Technet: http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=2952634&SiteID=17

Coming up...

Hello all,

I haven't got much time to publish new posts because I'm in the middle of the preparation of the upgrade scenario for SCCM and I'm also testing the new Microsoft Deployment to continue Zero Touch installations in an SCCM environment.

So keep on visiting this blog to discover my latest experiences regarding these topics!!

Nico