Peter van der Woude

In general it works pretty much the same, there are just some new features and more supported situations. See for more detail: http://technet.microsoft.com/en-us/library/hh974416.aspx

This is not a SCCM error, this is an error from the installer. So take a look at the installation log files of the application for more information.

You pretty much answered your own question. The biggest problems are the overlapping boundaries and the different domains. Because in domain a only site a is published in the ad (including the boundaries), so when a client in domain a looks in the ad it will only find site a... You need to manually assign the clients (during installation, or script) and make sure they can reach the other domain...

It's definitely not ideal, but you could try to work with a delay on one of the PXE servers replies.

That's because the content is already on the DP, try redistributing it from either the properties of the package, or the properties of the DP. The size of the DP storage totally depends on the number of packages and the expected growth.

Try initiating a heartbeat via the client, if that doesn't solve the problem start looking at the client log files.

Do they have to perform manual or push installations?

Did you look at the scanstate.log to see at what point it hangs?

What did you all configure to deploy the software updates? Also what log files did you check?

Take a look here for a similar thread and lots of informational links: http://stackoverflow.com/questions/5034076/what-does-dp0-mean-and-how-does-it-work

I would like to hear your experience with this product and some reasons why you are looking at a product like this.

Remove the driver from the repository, delete the driver package and start over.

Is it by any change a Nvidia video driver? If so, the newest versions solve this problem.

ConfigMgr 2012 does not use a Server Locator Point anymore, that functionality is now integrated in the Management Point

I think you are looking to configure some requirements on a Deployment Type, in that case take a look here: http://technet.microsoft.com/en-us/library/gg682174.aspx#BKMK_Step61 and http://technet.microsoft.com/en-us/library/gg682048.aspx

There should be more information, as that's not a "real" error...

Correct.

An Application can have a lot of (self created) Dependencies and/or Requirements. With that you can specify where and where not it can be installed. Besides that you can also decide not to make the software available to the specific user.

Yes, that's possible.

To just deploy an application you don't need to go any further then step 3.

You need to give (a lot) more information... All advertisements? always? all clients? did you check the client logs? etc...

It looks like a bad SQL version. You need at least SQL 2008 R2 SP1 CU6, or SQL 2008 R2 SP2.

It's a batch variable that resolve to the directory of the batchfile.

Yeah, you're right for some reason I assumed you where talking about client communication to the MP.

Removing the boundaries from the SMS 2003 would solve your overlapping boundaries problem. Boundaries are used for Site Assignment and Content Locations.