Jump to content


jonathan173

Established Members
  • Posts

    5
  • Joined

  • Last visited

jonathan173's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. Just wanted to comment on this post after reading it and having the same symptoms with a totally different resolution. Running SCCM 2012 R2 I discovered that from the initial install of SCCM 2012 there was a MP object for my primary site server residing in the System Management container at the FOREST level as well as the child domain. Once removed there were no longer two separate versions of my management point in Active Directory and policy assignments resumed without further action. Hopefully no one else has the same issue but if you do give this a try.
  2. After pouring through this issue for days I finally came up with the resolution to the problem. From within ADSI Edit for the child domain the MP point was showing the correct version, but when I checked the PARENT domain the version was still the old version of 5.00.7782.1000 in the System Management container. Not sure why my primary site is the only one showing at the forest level but that's another issue I'll address later. I edited the msSMSCapabilities attribute of the MP entry to the correct version and voila! All the clients are successfully installing from this management point. Hope this helps out anyone!
  3. Here is the part of the ccmsetup.log on the client that I've found most interesting. My current primary site/MP is running the R2 Preview as of today in an all out exhaustive attempt to correct my issues. Again, all components for this site are installed on this Windows Server 2012 system. The MP name retrieved is 'TDG-SA-SCCM.***' with version '7782' and capabilities '<Capabilities SchemaVersion="1.0"><Property Name="SSLState" Value="0"/></Capabilities>' ccmsetup 8/30/2013 12:20:20 AM 2916 (0x0B64) MP 'TDG-SA-SCCM.***' is compatible ccmsetup 8/30/2013 12:20:20 AM 2916 (0x0B64) The MP name retrieved is 'TDG-SA-SCCM.***' with version '7884' and capabilities '<Capabilities SchemaVersion="1.0"><Property Name="SSLState" Value="0"/></Capabilities>' ccmsetup 8/30/2013 12:20:20 AM 2916 (0x0B64) MP 'TDG-SA-SCCM.***' is compatible ccmsetup 8/30/2013 12:20:20 AM 2916 (0x0B64) Retrieved 2 MP records from AD for site 'SRL' ccmsetup 8/30/2013 12:20:20 AM 2916 (0x0B64) Retrived site version '5.00.7782.1000' from AD for site 'SRL' ccmsetup 8/30/2013 12:20:20 AM 2916 (0x0B64) SiteCode: SRL ccmsetup 8/30/2013 12:20:20 AM 2916 (0x0B64) SiteVersion: 5.00.7782.1000 ccmsetup 8/30/2013 12:20:20 AM 2916 (0x0B64)
  4. I think you are following me, but I have tried that. I did so by taking the check out of the Publish to Active Directory box as well as removing the entries manually and waiting for the site to republish the entries. Oddly enough, as i'm typing this up i'm watching a successful deployment of the client package install after changing the SMSSiteCode to " " instead of the actual site code of SRL in the Client Push Installation properties. The only downside to that is now the client doesn't know what management point to use.
  5. I recently upgraded to SCCM 2012 SP1 CU2 per the guidelines on here and somehow managed to goof up my client deployment from my primary site. All my secondary sites are deploying correctly but within the ccmsetup logs i'm getting a "Client version '5.00.7804.1000' is not compatible with the site 'SRL' version '5.00.7782.1000'. Fail the installation. ccmsetup 8/29/2013 3:42:16 PM 4276 (0x10B4)". I can only assume it's because earlier in the log I see "Retrieved 2 MP records from AD for site 'SRL'" with it defaulting to the oldest version of 5.00.7782.1000 for SiteCode: SRL. It does see the updated version at 5.00.7804.1000 on the "second MP" it finds in AD but they are both the same server, same name. The only difference between the two MP names is the domain name is capitalized in the new one, the old one is not. Does this make sense? All component status's are green and all secondary sites seem to be working. The IP address boundaries have been added to the boundary group managed by this server. I can't seem to make it clear out the old version from AD after removing the management point role and distribution role and reconfiguring everything back as it should be. Any ideas? All help will be greatly appreciated!
×
×
  • Create New...