[anyweb]

This guide assumes you have installed SCCM 2007 SP1 and then configured it as outlined here in Part 1.


Step 1. We need to configure the Distribution Point (DP) and the Management Point (MP).

Open up the SCCM Configuration Manager Console, and highlight the SCCM server listed under site systems, in the right pane we'll see the role's we've already installed.



double click on ConfigMgr distribution point and place a checkmark in Allow clients to transfer content from this distribution point using BITS,...



Once done, click ok and Double click on Configmgr Management Point to bring up its' properties, put a checkmark in Allow devices to use this management point and click Apply.



At this point I checked my SCCM status (click System Status in the left pane, expand it, and choose Site Status, then your SCCM site code, then Component Status), this revealed there were problems with my Management Point which were preventing it from starting.



right-click on the Critical error, and choose Show Messages, All.



hidden inside one of the two re-occuring errors was this (you have to scroll in the error window to read it)

Quote

SMS Site Component Manager faild to install component SMS_MP_CONTROL_MANAGER on server WIN-2SDX7MZCDA7.

The WebDAV server extension is either not installed or not configured properly.
Solution: Make sure WebDAV is installed and enabled. Make sure there is an authoring rule that allow "All users" read access to "All content". Make sure the WebDAV settings "Allow anonymous property queries" and "Allow property queries with infinite depth" are set to "true" and "Allow Custom Properties" is set to false.

well, i know that Webdav is installed, but perhaps a slight configuration change is needed, so let's start up Server Manager and click on roles then select Web Server IIS and then Internet Information Services (IIS) Manager, then select your website listed under Sites (probably called Default Web Site unless you changed it). In the right side select WebDav Authoring Rules



Double click on WebDav authoring rules and you should see the rule you originally setup, click on Webdav Settings in the right pane.



so according to the error message above we need to verify the following:-

Solution:
Make sure WebDAV is installed and enabled. [it is]
Make sure there is an authoring rule that allow "All users" read access to "All content". [this rule is not setup yet]
Make sure the WebDAV settings "Allow anonymous property queries" and "Allow property queries with infinite depth" are set to "true" [they are currently set to false] and "Allow Custom Properties" is set to false.[it's set to true]


Ok, let's fix these WebDav problems starting with adding a new authoring rule. In WebDav settings, click on WebDav Authoring rules in the right pane



Next click on Add authoring rule under actions and make the changes as per below screenshot, click ok when done and you'll see your new authoring rule listed in Webdav.





Click on WebDav Settings now

make the changes above ("Allow anonymous property queries" and "Allow property queries with infinite depth" are set to "true", and "Allow Custom Properties" is set to false.)

Click Apply in the actions pane.



lastly you should change the WebDav Behaviour for Allow hidden files to be listed from False to True if this is going to be a Distribution Point using BITS (it is).





Note: if you are trying to Configure WebDav in Server 2008 R2 then please read this post.



Ok back in SCCM Configuration Manager console, under site status, right click on your SITE and choose Reset Counts, then All. Pressing F5 (refresh) on your keyboard should refresh the system status.



A quick look back in System Status for our Management Point, now we can see that it has installed and started properly



(to speed up the automatic installation of this, you can use ConfigMgr's Service manager and select the SMS_Site_Component_manager server and restart the service.)

[anyweb]

Step 2. Make sure the System Management container in Active Directory has the correct permissions for SCCM

In other words we will make sure the local computer (the server SCCM is running on, in this case WIN-2SDX7MZCDA7) has full access to this particular area in Active Directory. For more info on Creating and configuring the AD system management container For SCCM using Adsiedit described here.

Start up the Active Directory Users and Computers console.

Make sure that Advanced Features is selected under the View option.



Once it is, in the left pane select System, and then scroll down to the System Management Container.



Right-click it and choose properties, then select the Security tab, Verify your SCCM server computer account is listed in the Group or user names, scroll down to check, if it is not there then add it by clicking on Add.



Click on Object types as in the screenshot below



then select computers (by default it's not selected).

Click on OK and then click on Advanced to expand the view, then Find now.

When you see your server listed, highlight it and click OK. click ok again to add it to the Security tab.



Now that we have added it, we need to edit it's security permissions to make sure that the permissions apply to both the Container and descendant (formally child) objects. So let's click on Advanced.



At this point you should see your computername listed but with read permissions that apply only to This object only. We are going to change that to Full access to This object and all descendant objects. to do so highlight our computername and click on Edit.



In the window that appears click the drop down menu called Apply onto: and select This object and all descendant objects.

Once done, click on Full Control for the Allow permissions and don't forget to select Apply these permissions to objects and /or containers within this container only. Click ok when done.

In an enterprise, please verify the correct AD permissions for this container and set them accordingly, for advice on this please visit technet.

[anyweb]

Step 3. Publish this site in Active Directory Domain Services

Note: In Configuration Manager, Verify that the following setting is set

Highlight your SCCM Site right click, choose properties, Advanced.

For specify settings for publishing and secure key exchange




make sure to Select publish this site in active directory domain services





Next step > SCCM 2007 SP1 configuration guide - Part 3

The guide covers:-

Configuring the Client Agents, setting up client installation methods and configuring discovery methods.

If you appreciate this guide then please help me by Digging it

[p.andrew]

Hi there,

I followed your guide from installing sql to configuring sccm 2007 but I'm kind of stuck here on this post.

2 problems:
- when I'm configuring the management point, it frozen after I clicked the "OK" button
- after I restarted and configure the WebDAV for the all user - read access, it runs ok but then smsexec.exe eat up all the CPU usage

What did I do wrong?

[anyweb]

have a read of this and see does it help

[p.andrew]

wow!
That fixed it!

I've been struggling with this for 2 weeks now.
Thanks heaps!

To summarize: got to http://support.micro...kb;en-us;973065 and apply the hotfix.
Note: Even if you have SCCM2007 R2 installed, it still works.

[Abhang]

Hi guys,
I struggled for about 2 days getting SCCM site server up and running and installing the client software on a client in the domain. The Client Push Install did not work for me . The ccm.log said ccmexe service started on client machine. But on the client machine, the ccmsetup service started and stopped. The problem was the service manifest and other files were not downloaded in the ccmsetup folder. So, I manually issued ccmsetup /MP:<MP name> /noservice. This worked!
Could anyone let me know why this happens, there is something fishy about the Management Point settings on my site server?

[MasterScott]

I am at a lost I been reading along doing step by step but when i got to AD part System Management Container it not listed in my AD.I have view advance on but it missing. Any ideas?

[Peter van der Woude]

You need to create te container with ADSIEDIT (or give the SCCM Server rights in the SYSTEM Container)

Take a look here: http://www.windows-n...tive-directory/