Share via

Installation warning "verify site server permissions to publish to Active Directory "

  • Article

Question

Friday, November 8, 2013 7:51 AM

hi all,

I've create a scurity group named "sccm-servers" and the primary site server - "server01" is member of this security group now. surely, I've granted the security group with related permissions to "System Management" .

but, when splash runs, it always get the warning "verify site server permissions to publish to Active Directory", if I tried to granted only the computer - server01 with related permissions to "System Management", then the warning dispeared.

Q:

- does the security group work for this scenario? (the seucrity group has been created for more than one week, the computer account has been joined the group for more than one week.

All replies (7)

Friday, November 8, 2013 7:57 AM ✅Answered | 1 vote

Hi,

It works perfectly to use a security group for this. Make sure that you've selected that the permissions should be applied to "this object and all descendent objects".

Tim Nilimaa | Blog: http://infoworks.tv | Twitter: @timnilimaa

Friday, November 8, 2013 8:55 AM ✅Answered

It's a known issue. You get this warning any time when the permissins for AD Container are not assigned direct to the CM computer account. Just ignore it. After Installation check the AD Container and you will see that the COnfigMgr could publish its info in AD.

Friday, November 8, 2013 8:02 AM

Thanks.

yes, I'm sure that the permissions have been applied to "this object and all descendent objects".

Friday, November 8, 2013 12:52 PM

 I concur with all of the above -- IMO using a security group is the preferred method of assigning permissions for this (and just about everything else).

Do note that you must reboot the server after you add it to a security group though to refresh that server's token so that contains the group membership. This won't change the "false" warning noted above, that's a known issue as stated.

Jason | http://blog.configmgrftw.com

Tuesday, September 29, 2015 9:38 AM

I am going to install ConfigMgr 2012 SP2.

Is it fixed for this version ?

Tuesday, September 29, 2015 9:47 AM

The Warning is still displayed when installing ConfigMgr 2012 SP2. As dekac99 said, this is a known issue that you can ignore if you use a security Group for assigning permissions.

Simon Dettling | Twitter

My posts are provided 'AS IS' without warranty of any kind.

Tuesday, September 29, 2015 10:34 AM

Thanks