If a Configuration Manager 2007 offline task sequence media is used to deploy an operating system on a client that does not have a network connection, the operating system is not registered

This article has been archived. It is offered "as is" and will no longer be updated.
When you run a System Center Configuration Manager 2007 stand-alone offline task sequence to deploy Windows Vista on a client that does not have a network connection, the Configuration Manager 2007 client may be unable to register Windows Vista after the installation of the offline task media has finished.

The ClientIDManagerStartup.log file logs the following error message:
RegTask: Client is not registered. Sending registration request...  ClientIDManagerStartup 30.06.2008 13:55:31     3904 (0x0F40)RegTask: Server rejected registration request: 3 ClientIDManagerStartup 30.06.2008 13:55:31     3904 (0x0F40)RegTask: Starting registration, attempt 2.           ClientIDManagerStartup 30.06.2008 13:55:31     3904 (0x0F40)RegTask: Initial backoff interval: 1 minutes         ClientIDManagerStartup 30.06.2008 13:55:33     3904 (0x0F40)RegTask: Reset backoff interval: 257 minutes     ClientIDManagerStartup 30.06.2008 13:55:33     3904 (0x0F40)Already refreshed within the last 10 minutes, Sleeping for the next 9 minutes before reattempt.    ClientIDManagerStartup            30.06.2008 13:55:33     3904 (0x0F40)RegTask - registration has timed out or must be cancelled. Setting timeout event. ClientIDManagerStartup 30.06.2008 13:56:52          2124 (0x084C)RegTask: Starting registration, attempt 3.           ClientIDManagerStartup 30.06.2008 13:56:52     3904 (0x0F40)Error initializing client registration (0x80040222).            ClientIDManagerStartup 30.06.2008 13:56:52     3904 (0x0F40)
The stand-alone media sets the BIOS time when Windows Preinstallation Environment (Windows PE) is initialized. Because the client on which the stand-alone media is installed does not have a network connection, it can incorrectly set the BIOS time. When this behavior occurs, the certificate is generated with a time stamp that is several hours later than the site server's current time. Therefore, the client has to wait for the certificate to be valid to connect to the management point.
To work around this problem, use one of the following methods.

Note Methods 2 and 3 assume that the BIOS time on the client is changed to +10 hours (10 hours later than the actual time).
  • Method 1

    After installation of the media, delete the System Center Configuration Manager certificates locally on the client in Microsoft Management Console (MMC), and then restart the Configuration Manager agent host. This step causes the client to create two new Configuration Manager certificates. These certificates are valid immediately.
  • Method 2

    After Windows PE is initialized and before the operating system is deployed from the offline task sequence media on the destination computer, change the system time in the BIOS to -10 hours locally on the client.
  • Method 3

    1. Create a VBS script that contains the following content:
      varTurnBackValue = -10strComputer = "."Set objSWbemServices = GetObject("winmgmts:\\" & strComputer & "\root\cimv2")objSWbemServices.Security_.Privileges.AddAsString "SeSystemTimePrivilege", TrueSet objDateTime = CreateObject("WbemScripting.SWbemDateTime")Set objOS = objSWbemServices.ExecQuery("SELECT * FROM Win32_OperatingSystem")For Each OS in objOS objDateTime.SetVarDate(DateAdd("h",varTurnBackValue,NOW)) OS.SetDateTime(objDateTime.value) Next
    2. Add a Run command line task to the offline task sequence after the Restart in Windows PE task that runs the script.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

Article ID: 961663 - Last Review: 01/16/2015 16:32:06 - Revision: 3.0

Microsoft System Center Configuration Manager 2007

  • kbnosurvey kbarchive kberrmsg kbtshoot kbexpertiseinter kbsurveynew kbprb KB961663
ERROR: at System.Diagnostics.Process.Kill() at Microsoft.Support.SEOInfrastructureService.PhantomJS.PhantomJSRunner.WaitForExit(Process process, Int32 waitTime, StringBuilder dataBuilder, Boolean isTotalProcessTimeout)