Peter van der Woude

Some drivers, often mentioned as BAD Drivers, just don't have the ability to be (good) installed without the executable...

Correct, but it does gives more insight in what has to happen. You lost me here... a. What does Unknown Systems has to do with the model not being in WMI? b. How do you use the Collection Variables on Unknown Systems? How do you then connect the variable to the machine?

And then you have to manually put the clients in the correct collection? If so, why not making it easier by using a WMI Query like: Select * From Win32_ComputerSystem WHERE Model LIKE "%Model%"?

Did you add the advanced features to your view (View > Advanced Features)?

Correct, that's indeed what I meant. So in this case, just ignore the error.

The most of these settings can be done in the MAintenance Tasks (http://technet.microsoft.com/en-us/library/bb632595.aspx). So take a look there to see how long your client data is saved.

Where are creating the variables?

Did you already check the answer on your question on MyItForum: http://www.myitforum.com/forums/tm.aspx?tree=true&high=&m=223603&mpage=1#

Did you check the smsts.log for errors?

I know its a 1E -product and that's about it... Maybe somebody else can jump in here....

Do these clients even download the package?

But does this mean that there a few BDPs that fail to all the clients that are trying to download?

A hash mismatch is almost always a difference in the Package Source version. Did you check if all the Distribution Points have the same Package Source version of the Packages? If so, just do a Package Refresh on the problematic DPs (see also: http://technet.microsoft.com/en-us/library/bb892806.aspx).

Also, I merged both topics into one, as it was double posted.

Lets start with, that I think that having multiple BDPs is a good reason to enable Binary Differential Replication (BDR). As BDR is used to update package source files with a minimum of additional network traffic (take a look here: http://www.petervanderwoude.nl/post/ConfigMgr-2007-and-Binary-Differential-Replication.aspx). Now back to the issue, the machines that fail what do they have in common? Same DP? Same ...??

Are you experiencing that particular issue (about the software updates browse error dialog box) then? Because only then should this update be applied and otherwise its just a waste of your time trying to install it...

That's default behaviour from Vista/7/2008/2008r2. The default install.wim from the installation dvd will always install on D:. To make it install on C: you have to capture your own wim image.

What about the default SCCM Database? When you don't use Unknown Computers, you already have to add a computer by its Name and MAC Address. The computer will stay in the OU where it was, when it is a new computer it will be added to the specified OU in the Task Sequence.

Lets start with saying that the only supported way is ccmsetup.exe /uninstall. There are some alternatives that sometimes work, msiexec /x and ccmclean (old SMS team). Take a look here for more information: http://social.technet.microsoft.com/Forums/en-US/configmgrsetup/thread/c27eb3be-210a-4b4c-aaa8-f6f98dbb5232

Correct, you need to create a Computer Association for that.

I would start with the ClientIDManagerStartup.log, the LocationServices.log and the ClientLocation.log

This tells me that client is communicating with the server yet. Did you check the logs?

Option 1. - Possible, you would need at least port 80/443, 445 and optional 8530/ 8531 (see: http://technet.microsoft.com/en-us/library/bb632618.aspx). Option 2. - Possible, but it indeed needs an AD and you need to open some ports between the Sites (also see the link).

Congrats Niall! Very well deserved!!!

I would think that you're not using the correct installation files of R2, it looks like you are trying to install a evaluation version of R2.