Hi, I have seen that the agent after a reinstallation (via agent or pxe) is not fully working.The server is running in native mode. In the general tab it says "Site Mode=unknown".A machine policy refresh or restart of computer does not help. I have tried to repair the agent via "install client" in the console.It does not help. A complete uninstall/install fixes it. Is there any way to see the cause of this in the log? ThanksMikael

Do you have SLP & MP published on active directory

Is your AD schema extended for Configuration Manager? Is your site publishing to AD? If so, then the client will detect the site mode from the site object in AD, and install accordingly. If not, then you have to use command line switches to tell the client to install into native mode. See: http://technet.microsoft.com/en-us/library/bb680980.aspx

Yes on both, I only have the problem when reinstallaing a client (osd). If i remove/uninstall the agentand install the agent manually it seems to work. Canit have something to dohaving than one CM or SMS sevrer published in AD? (not same boundary) But then...strange.

I don't know of any issues with this an OSD. You'd need to ask the OSD guys about this in their forum. I'd look at the ClientIDManagerStartup.log and see what it says. After a reinstall, the client has to register again. That would show the registration process.

We have the same issue for 2 month or so. When it displays site mode unknown then client doesnt work properly. He receives advertisements but never execute them, cannot report softwarupdate status. We also noticed that client repair does not help, only uninstall / reinstall or ccmclean and then push client. With this in mind, I manually created a osd image, before sysprep I removed all sms certificates, uninstalled config mgr client, deleted smscfg.ini ( http://technet.microsoft.com/en-us/library/bb694095.aspx). But that all doesnt help. 50% of servers after osd deploy have this issue..we have a mixed mode installation, no ad extension. For 2-3 month it worked fine, so I dont think that there is a problem with publishing to ad. clientidmanagerstartup.log below, can someone explain: Entering CCCMIDStartup::ExecuteInternalClientIDManagerStartup20.02.2008 17:10:265160 (0x1428)Evaluated SMBIOS (encoded): 59004B0036005800300032003000360032003400ClientIDManagerStartup20.02.2008 17:10:265160 (0x1428)SMBIOS unchangedClientIDManagerStartup20.02.2008 17:10:265160 (0x1428)SID unchangedClientIDManagerStartup20.02.2008 17:10:265160 (0x1428)HWID unchangedClientIDManagerStartup20.02.2008 17:10:265160 (0x1428)Skipping SMS_RemoteClient_ClientIdUpdated event since client is in provisioning mode.ClientIDManagerStartup20.02.2008 17:10:265160 (0x1428)GetSystemEnclosureChassisInfo: IsFixed=FALSE, IsLaptop=FALSEClientIDManagerStartup20.02.2008 17:10:265160 (0x1428)Computed HardwareID=2:A97E66F6FAB1CA2090D1E44D34A0B450FF816520Win32_SystemEnclosure.SerialNumber=<empty>Win32_SystemEnclosure.SMBIOSAssetTag=<empty>Win32_BaseBoard.SerialNumber=24755310Win32_BIOS.SerialNumber=YK6X020624 Win32_NetworkAdapterConfiguration.MACAddress=(removed) ClientIDManagerStartup20.02.2008 17:10:265160 (0x1428)Persisted hardware IDs in CCM_ClientIdentificationInformation=@:HardwareID1=2:A97E66F6FAB1CA2090D1E44D34A0B450FF816520HardwareID2=58CD10860100037AClientIDManagerStartup20.02.2008 17:10:265160 (0x1428)RegEndPoint: Event notification: CCM_RemoteClient_ReassignedClientIDManagerStartup20.02.2008 17:10:315384 (0x1508)RegEndPoint: Received notification for site assignment change from '<none>' to 'SVS'.ClientIDManagerStartup20.02.2008 17:10:315384 (0x1508)RegTask - registration has timed out or must be cancelled. Setting timeout event.ClientIDManagerStartup20.02.2008 16:11:204964 (0x1364)RegTask - timeout event does not exist. This is expected if registration was not (yet) executed on startup.ClientIDManagerStartup20.02.2008 16:11:204964 (0x1364)Entering CCCMIDStartup::ExecuteInternalClientIDManagerStartup20.02.2008 16:14:403636 (0x0E34)Read SMBIOS (encoded): 59004B0036005800300032003000360032003400ClientIDManagerStartup20.02.2008 16:14:403636 (0x0E34)Evaluated SMBIOS (encoded): 59004B0036005800300032003000360032003400ClientIDManagerStartup20.02.2008 16:14:403636 (0x0E34)No SMBIOS ChangedClientIDManagerStartup20.02.2008 16:14:403636 (0x0E34)SMBIOS unchangedClientIDManagerStartup20.02.2008 16:14:403636 (0x0E34)SID unchangedClientIDManagerStartup20.02.2008 16:14:403636 (0x0E34)HWID unchangedClientIDManagerStartup20.02.2008 16:14:403636 (0x0E34)GetSystemEnclosureChassisInfo: IsFixed=FALSE, IsLaptop=FALSEClientIDManagerStartup20.02.2008 16:14:403636 (0x0E34)Computed HardwareID=2:57B81F2C0AB0A5D7E0DF60D26504732D6CF61540Win32_SystemEnclosure.SerialNumber=<empty>Win32_SystemEnclosure.SMBIOSAssetTag=<empty>Win32_BaseBoard.SerialNumber=24755310Win32_BIOS.SerialNumber=YK6X020624 Win32_NetworkAdapterConfiguration.MACAddress=(removed) ClientIDManagerStartup20.02.2008 16:14:403636 (0x0E34)HardwareID1 changed from 2:A97E66F6FAB1CA2090D1E44D34A0B450FF816520 to 2:57B81F2C0AB0A5D7E0DF60D26504732D6CF61540ClientIDManagerStartup20.02.2008 16:14:403636 (0x0E34)Persisted hardware IDs in CCM_ClientIdentificationInformation=@:HardwareID1=2:57B81F2C0AB0A5D7E0DF60D26504732D6CF61540HardwareID2=58CD10860100037AClientIDManagerStartup20.02.2008 16:14:403636 (0x0E34)RegTask - registration has timed out or must be cancelled. Setting timeout event.ClientIDManagerStartup20.02.2008 16:16:082428 (0x097C)RegTask - timeout event does not exist. This is expected if registration was not (yet) executed on startup.ClientIDManagerStartup20.02.2008 16:16:082428 (0x097C). . . RegTask - registration has timed out or must be cancelled. Setting timeout event.ClientIDManagerStartup21.02.2008 09:48:322364 (0x093C)RegTask - timeout event does not exist. This is expected if registration was not (yet) executed on startup.ClientIDManagerStartup21.02.2008 09:48:322364 (0x093C)Entering CCCMIDStartup::ExecuteInternalClientIDManagerStartup21.02.2008 09:48:444424 (0x1148)Read SMBIOS (encoded): 59004B0036005800300032003000360032003400ClientIDManagerStartup21.02.2008 09:48:444424 (0x1148)Evaluated SMBIOS (encoded): 59004B0036005800300032003000360032003400ClientIDManagerStartup21.02.2008 09:48:444424 (0x1148)No SMBIOS ChangedClientIDManagerStartup21.02.2008 09:48:444424 (0x1148)SMBIOS unchangedClientIDManagerStartup21.02.2008 09:48:444424 (0x1148)SID unchangedClientIDManagerStartup21.02.2008 09:48:444424 (0x1148)HWID unchangedClientIDManagerStartup21.02.2008 09:48:444424 (0x1148)GetSystemEnclosureChassisInfo: IsFixed=FALSE, IsLaptop=FALSEClientIDManagerStartup21.02.2008 09:48:444424 (0x1148)Jens

Hi, I will open this case under OSD. In the tests I have madeI have seen thiswhen doing a reinstall of an OS without partitioning/format. /Mikael

I always repartition and reformat, so this should not be the problem Jens

Hi,Did anyone find a solution to the problem where the site mode is indicating unknown under system properties of the SCCM agent? I amexperiencing the same problem at the moment. My software distribution has not been working properly for a couple of days but now I know it had to do with this problem, what ever it is causing it.To get it to work I uninstalled the SCCM agent manually and installed it manually again. Voila - then it just worked!How can I resolve this problem so it will work in my automated OSD task sequence?/Fredrik

Do you have a server locator point installed? "FredrikSE" <=?utf-8?B?RnJlZHJpa1NF?=> wrote in message news:696f178c-8df7-46a f-b3de-0f6b2c364225...Hi,Did anyone find a solution to the problem where the site mode is indicating unknown under system properties of the SCCM agent? I amexperiencing the same problem at the moment. My software distribution has not been working properly for a couple of days but now I know it had to do with this problem, what ever it is causing it.To get it to work I uninstalled the SCCM agent manually and installed it manually again. Voila - then it just worked!How can I resolve this problem so it will work in my automated OSD task sequence?/Fredrik

I've just been hit by this same problem.Site is mixed mode, AD Extended. SLP is also installed.Existing clients seem to be fine, but those deployed by OSD recently have this issue.Only change that I can think of is we've updated the gold image to XP SP3, not that that should make a difference :(http://www.microsoft.com/technet/security/Bulletin/MS08-067.mspx If you don't ever patch anything, for god sake make sure this patch is on.......

Has anyone figured this out yet? I have been trying to figure this out for the last 2 weeks and have gotten nowhere. I am using Windows 7 Professional with SCCM 2007 SP2. Thanks!

Not that it may help you CADLKID but my problem was down to trying to assign the client to a different site during osd. I.E. We built the image through the install and capture task sequence, with the prepare config manager client step on our "SC1" site.We then deployed the WIM to our SC2 site, but looking at the logs when the client was trying to re-install it was trying to reference our SC1 site still for some reason, resulting with it going into "unknown" mode. We ended up building our reference machine, manually uninstalling the SCCM client and then manually capturing the WIM, all worked fine then. I'm about to re-build our gold image so will try it automated again this time and will let you know if I get the same problem. Cheers,Stevehttp://www.microsoft.com/technet/security/Bulletin/MS08-067.mspx If you don't ever patch anything, for god sake make sure this patch is on.......