Hi,

We recently upraded sccm to 2012 R2 SP1.
We now have exactly this problem: http://billbjerrum.blogspot.be/2015_07_01_archive.html

The site system shows the correct entry.

My question: what's there to change in adsiedit ... in a safe way?
Found this entry (default naming context, CN=system,cn=system management)but can't just change it, right?
<ClientOperationalSettings><Version>5.00.7958.1000</Version>

---
SCCMsetup.log:

Client version '5.00.8239.1000' is not compatible with the site 'SLT' version '5.00.7958.1000'. ccmsetup 3/09/2015 11:02:36 17136 (0x42F0)
Params to send '5.0.8239.1203 Deployment Error: 0x87d0029d, Client version '5.00.8239.1000' is not compatible with the site 'SLT' version '5.00.7958.1000'.' ccmsetup 3/09/2015 11:02:36 72256 (0x11A40)

---

Please advise.

MPSetup.log gives:

<09/02/15 12:05:58> Installation was successful.

Hman.log doesn't give any errors.

Sitecomp gives:   MP Configuration for ourserver.ourdomain.com. SMS_SITE_COMPONENT_MANAGER 3/09/2015 12:13:25 7448 (0x1D18)

So don't see any issues there.

Compmon.log gives:

Failed to read the required Operations Management component registry key values on local computer; error = 6 (0x6). SMS_COMPONENT_MONITOR 3/09/2015 12:58:09 8736 (0x2220)
Failed to read in current property values and initialize COpsMgmtComponent object; error = 6 (0x6). SMS_COMPONENT_MONITOR 3/09/2015 12:58:09 8736 (0x2220)

So don't see any issues

You need to do like Torsten ask. Go look into the system management container in AD and make sure that the info is up to date. This is done with the publishing in AD the primary site account need to have full control of that container and it's child.

This is often a issue we see when people activate the AD publishing and either stop it or it break. When you update the primary site the data is not being updated in the container.

Review the log:hman.log

• Edited by Frederick Dicaire 20 hours 22 minutes ago

You need to do like Torsten ask. Go look into the system management container in AD and make sure that the info is up to date

>Didn't see Torsen ask that.

Like I mentioned in my Original post:

Found this entry (default naming context, CN=system,cn=system management)but can't just change it, right?
< ClientOperationalSettings><Version>5.00.7958.1000</Version>

5.00.7958.1000 is not the correct version, it should be 5.00.8239.1203

So that doesn't look ok/up to date for me.

As I posted: Hman.log doesn't give any errors at all.

We do have (on Sites, properties of site, tab Publishing, "Select the Active Directory Forst to which this site will be published") UNselected.
This is because we have multiple SCCM servers and this was the recommandation of Microsoft to have these simultaneously working.
However could this be the root

Thanks, I don't know the details but it was the conclusion "in order to have different sccm servers you absolutely cannot publish it in AD", this would cause issues with clients.
Note: I mean 1 sccm server for SCCM 2007, 1 for SCCM 2012 for clients, 1 SCCM server for servers.

Any way to update this manually then?

Well if you update it manually it's the same as using publishing. And why do something manually why you can let the software organically do it's work.

If you are using boundaries to do auto site assignment and you have overlapping boundary  that might be the reason they said to not publish.

If you aren't doing auto assignment and you specify during the install what site to look for i would leave the publish at enable.

• Edited by Frederick Dicaire 19 hours 50 minutes ago

Thanks, I don't know the details but it was the conclusion "in order to have different sccm servers you absolutely cannot publish it in AD", this would cause issues with clients.
Note: I mean 1 sccm server for SCCM 2007, 1 for SCCM 2012 for clients, 1 SCCM server for servers.

Well you said you did not publish to it.

But some one did because the information is in the system management container.

So why not simply enable it again since everything was working before and you clearly stated many time that you don't use automatic site assignment.

If that's basically not true then I wonder why Microsoft explictely advised us not to publish the new SCCM 2012 se