Peter van der Woude

I asume the client is in the correct collection for the advertisement, so I would look at the execmgr.log on the client.

AFAIK, that can't be done with Search Folders...

With SCCM Client Center (http://smsclictr.sourceforge.net/) you've got a whole lot of option to manage specific clients

PXE is now managed through the Distribution Point, so most of the (error) message can be found in the distrmgr.log

Can be done by using the SDK. There are some pretty straight forward examples here: http://msdn.microsoft.com/en-us/library/cc145334.aspx

You could use something like net user, see also: http://support.microsoft.com/kb/251394

Are the client machines multihomed? See also: http://support.microsoft.com/kb/325919

This usually means that the client is outside of your boundaries... So I would start double checking the ipranges/subnets of your boundaries and compare it with the ip of the new client(s).

Remove WSUS (including local data), Add WSUS and then add the Software Update Point.

That's indeed correct if they are all in the root folder.

First of you don't have to integrate them... and the fact that it's two totally separate environments, makes it even a better case to keep them separate.

The commandline of the Program can just be INSTALL.bat without the %~dp0. You only need to use %~dp0 within a batchfile.

Did you let SCCM configure WDS? Or did you use an existing WDS environment?

I don't really see the advantages of keeping them seperate.. Maybe you can start with telling why you would want to keep them seperate, while you only want to use SCCM for the deployment.

You are probably missing the correct NIC driver in your bootimage... (you can check the smsts.log to verify)

I had that once at a customer to, that it had problems with upgrading the client. As a solution we first ran an uninstall (script) for the SMS client and then pushed the SCCM client.

Saves as HTA and see what it does I do think that there are some varaibles that have to be changed to your situation, but you will probably run in to that very quickly

Probably not supported, as it's never supported to update beta's or rc's...

Do you have enough rights to install a db on the remote server?

You will get the most exact results by searching in the PnP devices... So something like this: select * from Win32_PNPEntity where DeviceID like '%yourdeviceid%'. Just search with wbemtest for the exact information you need.

This not a 'real' error, it just happens if nobody was logged on... Did you, by any change, select that the program can only run on a specific platform? If not, then what else is in the execmgr.log and what is the advertisement status?

Nope, that's not needed when it's the same computer.

I actually meant the settings under Component Configuration.

As far as I know and I've heard Mac OSX won't be supported in ConfigMgr 2012 (yet)... So the only way to manage Mac's in your environment is third party tooling and Quest is at this point probebly your best option.

Take a look at the installation logs...