Peter van der Woude

Did you install Visio 2010 with the correct parameters during the sequence (as explained here: http://support.microsoft.com/kb/983462)?

Google: http://www.google.nl/#hl=nl&q=VBS+Editor&aq=f&aqi=g6&aql=&oq=&gs_rfai=&fp=6033a4ae16bb8ddc

Are you sure that its all configured correctly (including WEBDAV), because you get error HTTP error 401 which means: server requires authentication. Or did any other error show up?

This is your error: [LOG[Failed to correctly receive a WEBDAV HTTP request.]LOG]! [LOG[Failed to successfully complete HTTP request. (StatusCode at WinHttpQueryHeaders: 401)]LOG]! It looks a lot like that WEBDAV is configured, or not configured correctly.

As far as I understand this issue, I assume the AD is not extended for SCCM. Which means, like Konetie says, you need a Server Locator Point (SLP) to tell the clients where to find the Management Point (MP) of the Site. As the AD is not extended there is no use in searching the AD for a record that doesn't exist A client can only find an SLP, when the SLP is published in WINS, or when the SLP is specified in the installation properties of the client (http://technet.microsoft.com/en-us/library/bb694195.aspx)

Did you restart the machine already, as I suggested before?:

I think the clientmachine needs a restart, as this is what the log says (all the time): [LOG[shutdown has been requested]LOG] [LOG[installation will be cancelled due to shutdown. Windows Installer will return error code 1602.]LOG]

What does the ccmsetup.log say, after a Client Push Installation?

CCMSetup.log can be found in C:\Windows\ccmsetup on 64-bits machines or in C:\Windows\System32\ccmsetup on 32-bits machines. But as you install the client manually, I think this part is still going good. I think you should check the client logs in C:\Windows\SysWOW64\CCM\Logs on 64-bits machines or in C:\Windows\System32\CCM\Logs on 32-bits machines.

This has nothing to do with the Active Directory Discoveries, this is about computers which are already discoverd and then excluded from collections.

To fine-tune your script, just first try it by starting it without intervention of ConfigMgr, then try it as a Software Package and when that works put it in a Task Sequence.

Its not possible to exclude any subcontainers... I can only think of some workarrounds, like: - Move the container in the AD to a place outside the AD Discovery, - Deny acces to the container for the ConfigMgr Site Server (will create errors during discovery). - Turn of the recursion on the top-level and create multiple LDAP Queries to discover the other containers.

Not possible, you will allways need a collection to distribute software.

Agree... if you are not using SMS anymore, why not remove/ uninstall it? If for some reason it has to run, just stop it from publishing to the AD and remove the Boundaries.

It only has to be installed on both, when they both have to act as an Software Update Point.

As an add-on to Niall's correct answer, a little explanation. The client uses the AD to retrieve information about their Management Point. So when the AD isn't extended it needs another place to retrieve that information and that is a Server Locator Point. See also: technet.microsoft.com/en-us/library/bb693467.aspx

No, but it is a prerequisite of other roles, like a (bits-enabled) DP.

Take a look at point 34 on this link: http://technet.microsoft.com/en-us/library/bb632618.aspx

Mainly information about where to find the MP.

When the machine has to come in to the default Computers container, then don't select and OU at all.

Just run Discovery Data Collection Cycle would be enough (this generates a new hartbeat).

Can you connect to the admin$? Do you have a Restricted Groups GPO to delete local admins?

What exactly are you searching for? A way to automatically download software updates and create a deployment? If so, then its not possible. Or a way to let the deployment re-ocur? If so, then you should use weekly Maintenance Windows.

Take a look at the ccm.log

This can be done by implementing a HTA. There is already a Built-In HTA in MDT 2010 Update 1 (http://www.petervanderwoude.nl/post/User-Driven-Installation-with-ConfigMgr-2007-and-MDT-2010-Update-1.aspx). This Built-In HTA seems verry adaptable in your situation. Update 1: My blogpost is still about the BETA version, but there is already an official release. Update 2: I've also got some screenshots here: http://www.petervanderwoude.nl/post/What-does-the-user-see-when-running-an-OS-Deployment-with-e2809cModenae2809d.aspx At this point this feature was still called Modena, but now its (almost equally) implemented in MDT 2010 Update 1