We're deploying Windows 7 from our SCCM 2007 SP2 site and are finding that everything runs perfect except that the SCCM client doesn't fully install - it remains in a Site Mode = Unknown after the deployment. We're deploying our images in a "Refresh" scenario - updating existing machines that are already in the domain with SCCM clients installed. Our custom image was created without a SCCM client installed. Our AD Schema is extended and we do have a Server Locator Point thrown in for good measure. I can fix the issue buy uninstalling and reinstalling the client but I'd like to get to the bottom of the issue without running any post-deployment scripts. The ClientIDManagerStartup.log shows this right after the client gets initially installed-It looks clean to me.Evaluated SMBIOS (encoded): 320055004100380030003900300057004D004C00SMBIOS unchangedSID unchangedHWID unchangedSkipping SMS_RemoteClient_ClientIdUpdated event since client is in provisioning mode.GetSystemEnclosureChassisInfo: IsFixed=TRUE, IsLaptop=FALSEComputed HardwareID=2:4D453644AE6AE7CAF902120ECC39BDADB638C4F9 Win32_SystemEnclosure.SerialNumber=2UA8090WML Win32_SystemEnclosure.SMBIOSAssetTag=2UA8090WML Win32_BaseBoard.SerialNumber=2UA8090WML Win32_BIOS.SerialNumber=2UA8090WML Win32_NetworkAdapterConfiguration.MACAddress=00:1E:0B:67:70:97Persisted hardware IDs in CCM_ClientIdentificationInformation=@: HardwareID1=2:4D453644AE6AE7CAF902120ECC39BDADB638C4F9 HardwareID2=A2B90600010000FARegEndPoint: Event notification: CCM_RemoteClient_ReassignedRegEndPoint: Received notification for site assignment change from '<none>' to 'DA0'. After uninstalling and reinstalling the client, this is what the log shows.....RegTask - Executing registration task synchronously.Read SMBIOS (encoded): 320055004100380030003900300057004D004C00Evaluated SMBIOS (encoded): 320055004100380030003900300057004D004C00No SMBIOS ChangedSMBIOS unchangedSID unchangedHWID unchangedRegTask: Initial backoff interval: 1 minutesRegTask: Reset backoff interval: 257 minutesRegEndPoint: Event notification: CCM_RemoteClient_ReassignedRegEndPoint: Received notification for site assignment change from '<none>' to 'DA0'.GetSystemEnclosureChassisInfo: IsFixed=TRUE, IsLaptop=FALSEComputed HardwareID=2:4D453644AE6AE7CAF902120ECC39BDADB638C4F9 Win32_SystemEnclosure.SerialNumber=2UA8090WML Win32_SystemEnclosure.SMBIOSAssetTag=2UA8090WML Win32_BaseBoard.SerialNumber=2UA8090WML Win32_BIOS.SerialNumber=2UA8090WML Win32_NetworkAdapterConfiguration.MACAddress=00:1E:0B:67:70:97RegTask: Client is not registered. Sending registration request...RegTask: Client registration is pending.RegTask: Client is pending registration. Sending confirmation request...RegTask: Client is pending registration. Sending confirmation request...RegTask: Client is registered.Raising event:[SMS_CodePage(437), SMS_LocaleID(1033)]instance of SMS_RemoteClient_Reassigned{ ClientID = "GUID:FF0B11BF-FDDA-47A9-87C5-C51CCB75F121"; DateTime = "20100219162125.149000+000"; LastAssignedSite = ""; MachineName = "4THXPTEST"; NewAssignedSite = "DA0"; ProcessID = 2744; SiteCode = "DA0"; ThreadID = 1156;}; Raising event: instance of CCM_Framework_ClientIdChanged{ ClientID = "GUID:FF0B11BF-FDDA-47A9-87C5-C51CCB75F121"; DateTime = "20100219162125.149000+000"; PreviousClientId = "Unknown"; ProcessID = 2744; ThreadID = 1156;}; Read SMBIOS (encoded): 320055004100380030003900300057004D004C00Evaluated SMBIOS (encoded): 320055004100380030003900300057004D004C00No SMBIOS ChangedSMBIOS unchangedSID unchangedHWID unchangedGetSystemEnclosureChassisInfo: IsFixed=TRUE, IsLaptop=FALSEComputed HardwareID=2:4D453644AE6AE7CAF902120ECC39BDADB638C4F9 Win32_SystemEnclosure.SerialNumber=2UA8090WML Win32_SystemEnclosure.SMBIOSAssetTag=2UA8090WML Win32_BaseBoard.SerialNumber=2UA8090WML Win32_BIOS.SerialNumber=2UA8090WML Win32_NetworkAdapterConfiguration.MACAddress=00:1E:0B:67:70:97Persisted hardware IDs in CCM_ClientIdentificationInformation=@: HardwareID1=2:4D453644AE6AE7CAF902120ECC39BDADB638C4F9 HardwareID2=A2B90600010000FA Orange County District Attorney

We are also experiencing this problem.Specifying the SMSSLP and SMSMP and SITECODE in the command line of the Configuration Client manager Install package did not resolve this. Neither did specifying these parameters in the OSD. (SITECODE is the only one that cannot be set in OSD).SCCM is set to publish to AD. We have tested and set the permission. AD publishing is working.We have also added the DNS and WINS record entries so that sufficient fallback is provided.We have also checked if this could be a boundary issue. It is not.Still failing and showing Unknown and not being able to find the MP.So we worked around this issue First make sure your machine is a member of the domain. Sometimes the build in "Apply Network Settings" fails to join a domain in the first part of OSD. Workaround: Use the General > Join a Domain or Workgroup as a second fallback in your OSD after a reboot. If the machine is already a member of the domain it will continue. If it is not... well it helps that this step will ensure that the domain join is completed. This step will automatically reboot your machine. No need for a reboot step.Next you will need to reinstall the SCCM Client software. You do that with the following (Run a command line)msiexec /i "%windir%\system32\ccmsetup\{4CD82FBB-0AFC-4864-A089-15364DF5F14B}\client.msi" SMSSITECODE=[yoursitecode] SMSCACHEDIR="C:\" SMSSLP=[servername] SMSMP=[servername] SMSCACHESIZE=2048 /qb!Add a reboot step after this.After that the client is no longer in unknown mode and communication with the MP proceeds as designed.Good luck.

Do you have WINS in your infrastructure? Have you installed the .adm configuration files? If so, did you specified the FQDN of the ConfigMgr server?

Thanks for the good info. I'm still struggling with this. I'll try your suggestion and let you know how I do. Most all our deployments are REFRESH scenarios so the machines are already in the domain which I suppose makes the reinstall a bit easier.Orange County District Attorney

There is a strange error in the ADM file, when used in Active Directory Group Policy on a Windows Server 2008 Domain Server.You need to edit the ADM file and change the following line (use notepad) PART !!AssignedSite EDITTEXT VALUENAME "GPRequestedSiteAssignmentCode" MAXLEN 3 END PARTTO PART !!AssignedSite EDITTEXT VALUENAME "GPRequestedSiteAssignmentCode" MAXLEN 4 END PARTOtherwise you will only be able to input TWO characters in the GPO editor.

I tried the reinstall command on a machine manually however it didn't do the trick. I'm still at Site Mode = Unknown. I'm going to open a support ticket with Microsoft to see if they can help sort my issue out.Orange County District Attorney

Sandy,You have to reboot. When you do reboot after the reinstall workaround, you will immediately notice that the client is assigned to the site. Because the sitecode is shown (this should be the first indicator of success).Wait until at least a couple of client cycles completes. It should take no more than 30 minutes or so. After that reboot the client will show that it is assigned and mode should display "intranet". Refresh your SCCM Console and it should give more data.The client needs to do at least an inventory, and send a data discovery record and a heartbeat. This is done is one or two cycles.

I did reboot, however I did not wait for very long after before checking the ConfigMgr status in Windows 7. The client does get assigned to my site, however there are never more than two items in the "Actions" tab and there's a "Internet" tab as well. I hadn't been using the Site Assignment .adm template in our domain, only the installation properties one. I added the template and perhaps this will make a difference to me. We're at Windows 2008 in our domain and I can add our site code without a problem. Is there somewhere else that I'm missing that your fix refers to?Orange County District Attorney

You've Extended the Schema with success? You've created manually the System Management container in the System in the Active Directory Schema and gave the proper permissions to the server that has ConfigMgr in it? You've published correctly and successfuly the Site to the AD? Check those please and give feedback afterwards.

Yes, I have. I double, triple-checked it and the schema is extended.With help from Microsoft support, we've found that after installing the client as part of the OSD process, the client goes into provisioning mode and doesn't come out. There are a few registry values at HKLM\Software\Wow6432Node\Microsoft\CCM\CcmExec that apparently got set wrong. ProvisioningMode = true (should be false)SystemTaskExcludes = (should be empty, will be full of tasks if in provisioning mode)There's a similar thread on the same subject at http://social.technet.microsoft.com/Forums/en-US/configmgrosd/thread/5f33afe9-ca61-4a41-a192-fdb08c5cc619/We first tried adding a Run Command Line to the Task Sequence after the SCCM client installs but low and behold, after you uninstall the client, the Task Sequence dies. Duh. Obviously uninstalling and reinstalling works but it's tricky adding to the TS without it completely failing. I'm going to work on a script to add to the TS that will change the registry values and hopefully fix the issue.Orange County District Attorney

That's very weird... The package of ConfigMgr client, you've created how? You manually created the install pack or did you used the New -> Package from Definition ? (BTW: I'm Ghosterius... I've changed my profile for my company's profile definitly... Sorry for all the confusion)

I did it from New -> Package from DefinitionKeep in mind that I'm using MDT 2010 integration deploying my images. I've deployed Windows 7 images using MDT 2010 Lite Touch without any problems or SCCM client issues, it's just now with SCCM OSD that I'm seeing the issue.Orange County District Attorney

Did you ever solve this issue? We have the exact same problem.

Yes I did. Sorry I did not post my fix. Working with Microsoft support we found that tweaking a couple of registry keys put my images right. Right after the "Setup Windows and ConfigMgr" step in the PostInstall group I added two "Run Command Lines". There were two SCCM client settings in the registry that were getting set incorrectly. Here are the two commands I ran: REG ADD HKLM\SOFTWARE\Wow6432Node\Microsoft\CCM\CcmExec /v ProvisioningMode /t REG_SZ /d false /f REG ADD HKLM\SOFTWARE\Wow6432Node\Microsoft\CCM\CcmExec /v SystemTaskExcludes /t REG_SZ /d "" /f This fixed my issue and my clients are getting correctly installed and configured.Orange County District Attorney

Thanks for the quick response, I owe you a drink if you are ever in the UK!

hi i'm sorry to bump this old thread but i have the same problem as well. osd deployment runs perfectly except the site mode shows as unknown. if i uninstall and reinstall the client manually it works fine... i added those registry hacks already but it didn't work. could you help me with this?

Did you add them right after the "Setup Windows and ConfigMgr" step in the Task Sequence?Orange County District Attorney

Did you add them right after the "Setup Windows and ConfigMgr" step in the Task Sequence? Orange County District Attorney yes i did add them right after "setup windows and configmgr". after the osd i checked those two keys that they had the correct values: SystemTaskExcludes was empty and ProvisioningMode had a 'false' value but it stil shows as unknown.. do you have anything else in mind that i could check out?

Hi there, when adding this registry change into the task sequence were you addding this to the reference capture (.WIM) or target build?

Thanks for this fix Sandy it fixed our problem here,

Hi there, thank you for the suggested solution :-) Would you please explain ... when adding this registry change into the task sequence were you addding this to the reference capture (.WIM) or target build? Frank Mogensen

We are applying the registry change to the target build The registry key above is for a 64bit OS so remember if your running 32bit OS the registry keys will be slightly different... as below. REG ADD "HKLM\SOFTWARE\Microsoft\CCM\CcmExec" /v ProvisioningMode /t REG_SZ /d false /f REG ADD "HKLM\SOFTWARE\Microsoft\CCM\CcmExec" /v SystemTaskExcludes /t REG_SZ /d "" /f

Hi, i had the same issue here and could resolve the problem with this article - many thanks for it! I was interested why we have this problems here and i found a good article where he describes the problems and how to resolve it. This was our Problem: A Reboot step in the OSD Task Sequence is accidentally set to restart into the WinPE boot image assigned to the Task Sequence instead of the full Windows OS. This will cause the Task Sequence to end in WinPE. Because the ConfigMgr client is actually installed as part of the full Windows OS and not WinPE, and because the Task Sequence ends in WinPE instead of the full Windows OS, it cannot properly take the ConfigMgr client out of provisioning mode. Another Problems could be: A power Failure during OSD Task Sequence. In Windows XP and Windows Server 2003, if an application is installed during the Task Sequence that installs a custom Gina, the problem will happen, becaus XP and 2003 needs a custom OSDGina. For further Details follow this Link: http://blogs.technet.com/b/configurationmgr/archive/2010/09/13/solution-after-a-configmgr-2007-osd-task-sequence-completes-the-client-may-not-automatically-pull-down-policy.aspx Florian

When I add those registry keys the client does successfully register, but after I cannot install any software. I get an error stating SCCM is busy running another program or a reboot is pending. If I repair the client, everthing works. I tried adding a ccmrepair run command line to the task sequence, but it fails. Anyone seen this before? Thanks in advance.

This was the most helpful post I found regarding the Site Mode Unknow. Here is what I found in my Environment: Go it fixed. Think It was a combo of 3 issue. Here is what I found: Issue 1. The package was not set to run on Win7, but I don’t think it was the main thing, but may have contributed. Issue2. A "Restart Computer" task at some point after the "Setup Windows and ConfigMgr" task that is set to restart into the WinPE boot image assigned to the Task Sequence instead of the full Windows OS. This will cause the Task Sequence to end in WinPE. Because the ConfigMgr client is actually installed as part of the full Windows OS and not WinPE, and because the Task Sequence ends in WinPE instead of the full Windows OS, it cannot properly take the ConfigMgr client out of provisioning mode(In the logs I kept seeing that it was saying can’t take out of provisioning”). So I changed the restart option to the Windows OS instead of PE. Issue3. Here is the thing. This works, but only if I disable the Cisco VPN TS. I think this is because the Cisco VPN TS does a restart after its installed and looking at issue 2, probably boots it right back into PE. So I have the Cisco VPN client TS disabled on the x86 and the App Tree and when the image is finished 1)it shows site mode as Mixed and all the components are there (Remember how a lot of times only like 3 of them show up in confi magr)

FYI I had the same issue (site code = unknown after OSD) but ONLY on some models of laptops. Some newer laptops showed site mode = native right after osd, the older ones would remain in the site mode = unknown untill a full uninstall then re-install of the sccm client. The way I got it to work for all laptops consistantley was to remove ALL reboot steps in the task sequence. I had placed some after install software updates, but it is unnecessary to reboot manually since the install software update task reboots for you if it's needed. It seems that ANY reboot task can potentially screw things up, so just don't use them in an OSD task sequence. FYI All my reboot steps were indeed set to "currently installed default operating system" as others have mentioned is required. But my experience is that you can't have ANY reboot tasks, even if they are already pointing to the default OS, and not winPE. -Ben