Peter van der Woude

You indeed have to "manually" adjust the package source directory. If you are using local path(s) it's a simple copy action, if you are using network share it might involve changing all packages. For the last scenario, there are multiple scripts are the community, but this one is probably the simplest to use; http://blog.coretech.dk/kea/updated-version-of-the-package-source-changer/

Are you sure those devices are capable of power management? See also: http://technet.microsoft.com/en-us/library/gg699376.aspx

Access denied on your downloads that sounds like a problem with your network access account.

I think he is using custom diskpart commands to clean the disk.

The reporting is build on standard SQL reporting services, so you're able to just navigate to the reports via your web browser.

As it's every minute and marked as critical then, yeah, that will impact the application... Especially looking at the error, it seems a problem on your database (permissions).

Do they also show recent policy requests?

Erhmm... what exactly are your trying to do... Initial problem states that the push installation never starts, but your last comment is that you succesfully pushed a client installation... So what exactly is the problem?

Is it by any change a workgroup device? If so, you need to add the SMSMP property to your client installation properties.

Depends. If it's an available deployment there is nothing to clear.

Main advantages are the buildin scripts and monitoring of the deployment, but that doesn't add up for everybody. It really depends on the usage and the users. You can make it as difficult, or easy as you want, but in the end it all depends on if it's manageble and if it's what you or the customer wants.

That's indeed the only error. It seems to be that something goes wrong with partitiioning your disk, which causes the OS (and by that the client) to install on the wrong partition.

The error code 12029 means ERROR_WINHTTP_CANNOT_CONNECT. So that means there is something not working with connection to the internet. Keep in mind that it's the device, that your console is running on, is the one that will actually download the update.

The first thing I like to note is that if you're downloading the updates yourself (via the wizard) that it's the device, that your console is running on, that's really contacting with internet. Second thing is that you cann't download updates twice to the same package, from different locations. This would mean you have to configure a separate package for that location. Another thing you might consider is a Pull DP.

You should see the Role and the Scope separate from eachother. With the role you define the rights of the user, in this case read + write (from the two roles together) and with the scope you define the objects the user can access, so if that's that specific package that means that the user has read + write access to that specific package.

Also, your CCMsetup.log shows a 1603 error, which is a very generic MSI error. You might want to look at the client.msi.log for even more information.

It's all about the Security Roles configured within the "Only the instances of objects...". With a Security Role you define the rights that a user has and with a Security Scope you define on which objects the user has those rights. For more information, see: http://technet.microsoft.com/en-us/library/gg712284.aspx#BKMK_PlanningForRBA

OR, it really needs ConfigMgr 2012 R2...

Weird... you could try running it locally on the DP and with run as administrator...

Is it recieving policies (easy way to check is by looking at the Actions tab, it should show more then two actions)?

Your log file states "failed to evaluate", did you check the detection method of the application?

When the client installation fails, check the ccmsetup.log file.

Copy the files back from the distribution point. Easy method is via the Content Library Explorer (part of the ConfigMgr Toolkit).

Why? I would be a bit more specific, with a IP range...

First of all, don't use GPOs to set the location of WSUS, as ConfigMgr will do that via a local policy. Second, I was talking about ConfigMgr client policies and not about GPOs. Is your client assigned to a site?