Featured Posts

System Center Orchestrator 2012 overview At Microsoft Teched North America 2011, Adam Hall presented on System Center Orchestrator 2012. System Center Orchestrator is the new name for Opalis, aquired last year -- Microsoft's premier tool for...

Read more

System Center Operations Manager 2012 network monitoring This thursday, at Microsoft Teched North America 2011, Rob Kuehfus and myself will be presenting a breakout session (SIM354) on System Center Operations Manager 2012 network monitoring. Network monitoring...

Read more

SC Operations Manager Connector for VS Team Foundation... Using the System Center Operations Manager 2007 R2 connector for Microsoft Visual Studio Team Foundation Server 2010 (download CTP1 here), operations teams can easily forward application performance...

Read more

Teched NA 2011: Day 1 Keynote Microsoft's premier and flagship IT event, Teched North America 2011, kicked off today with they "day 1 keynote". Around 15 minutes before the keynote started, two DJ's were on stage playing 'Daft Punk...

Read more

Teched NA 2011: Day 0 summary While Teched North America 2011 officially starts tomorrow, day zero or better known as the pre-conference day is done. Several hundreds of people attended these technical one-day workshops which varied...

Read more

Configuring Group Policies for your ConfigMgr Servers

Posted by Kenneth van Surksum | Posted in AD Group Policy, System Center Configuration Manager | Posted on 07-06-2011

0

When you are installing System Center Configuration Manager (ConfigMgr) 2007 in environments where group policies are used to control the User Rights Assignment and Security Options security settings of the Servers, because if you don’t the settings coming from the ConfigMgr installation will be overwritten at the next policy refresh, which could result in interesting scenario’s. To mitigate this you have to provide the settings needed to make the Server work correctly to the Group Policy Administrators.

How to determine the Policy Settings:

In order to determine the correct settings, its best to build ConfigMgr in a test environment, where the servers are isolated from Group Policies when you are installing them. Start with detailing the configuration of the Security Settings of the machine in the state which you received it, or just after you installed the machine yourself. This can be easily done by exporting the User Rights Assigment and the Security Options settings using the Export List… options when you rights click the User Rights Assignment or Security Options node. Save the output, and make sure you detail the fact that this settings reflect your start position. (more)