Peter van der Woude

I would try to delete it from the all users, or run with user rights.

The operating system reported error 2148077575: The hash value is not correct --> Most of the times a Refresh of the packages on the DP resolves this issue

Did you take a look at the CAS.log?

At what point of the TS are you trying the installation?

Software Updates during the Task Sequence are seperate from Group Policies... The SCCM client uses it's own local policy to point to the Software Update Point.

Why are you trying to set the OSDStateStorePath variable in this situation? If you are using the default SMP and the default steps from the task sequence, then there is no need to manualy fill that variable...

Did you take a look at the smsts.log?

I don't realy follow what you've got configured now or not... Did the SCCM installation work-out? Can you install a client?

These are two different things.

WebDAV is not needed anymore with ConfigMgr 2012

First of, there is no need to set DHCP Options 66 or 67, only DHCP Option 60 is needed when DHCP and PXE/WDS are running on the same server. After that being said, I only see you write about adding boot images, but I don't read anything about creating a task sequence (and advertising it)....

It can be done during the Task Sequence as a software package (setup.exe -s), or it can be done during the Task Sequence as a driver package (first extract the driver).

There are no changes needed for Native Mode, the 'only' difference is the use of certificates.

Take a look here for some answers: http://blogs.technet.com/b/configmgrteam/archive/2009/05/14/faq-sql-reporting-services-integration-with-system-center-configuration-manager-2007-r2.aspx

You could add a GPO that by default opens the needed ports. NOTE: Keep in mind that the client gets installed as a normal package and it's not being pushed, so in fact it can't have anything to do with a firewall...

Did you try setacl?

Why not using a Secondary Site with a PXE Service Point (and Distribution Point) on the remote site?

If you are using a SUP then the MW's also affect the Software Update Deployments. If you are using WSUS standalone then the MW's have no affect.

Make sure that there are no Expired or Superceded updates in your packages. Btw there is in SCCM no real difference between a 'normal' TS or a 'MDT' TS. It just has some more preconfigured steps by default.

Driver problem during your Build and Capture??? Btw I can't find a real error in your logfile... at what point does it fail? Are there more smsts.log files?

Nope WAIK 1.1 is not working anymore with SCCM 2007 SP2. You need WAIK 2.0

The new computer will indeed start installing directly, as it is for the new computer an Advertisement that already could/should have run. Maintenance Windows are indeed your best option if you want installations to happen outside the office-times. Just keep in mind that the Maintenance Windows have influence on all Advertisement to those machines.

In general it works good, but you do read sometimes little issues caused by BDR.

I have to say that I didn't read this part the first time good Does this mean that you are running in Native Mode, or that you just 'messed' with the Certificates?

By default it will resend the whole package. If you Enable Binary Differential Replication on the package then it will only send the changes (http://technet.microsoft.com/en-us/library/bb693953.aspx).