Peter van der Woude

From where are you copying? The package or a share?

9 out of 10 it has to do with the WebDAV settings, so start with looking at those.

You need to create a Hyper-V host first. Then on a Hyper-V guest you can install the OS you want.

AFAIK there is no possibility to do an inplace upgrade of 2007 to 2012.

Take a look here: http://www.myitforum.com/forums/OSD-certificate-for-boot-Media-in-Native-mode-is-a-nightmare-m225360.aspx (it's all about the common name) The command certutil -setreg policy \EditFlags +EDITF_ATTRIBUTESUBJECTALTNAME2 is needed when you need to use multiple SANS (like with Internet Clients)

You can use USMTUtils for that: http://www.petervanderwoude.nl/post/using-usmtutils-exe-during-a-task-sequence-with-configmgr-2007/

For checking the Reporting Point you have to look in SCCM. For creating a user for SQL (Google is your friend): http://technet.microsoft.com/en-us/library/aa337545.aspx

I am not totally sure about this one. I would say that the main point is (overlapping) Boundaries and as long as you don't create overlapping Boundaries you'll be fine.

Did you configure WSUS and/ or SCCM (Software Update Point)?

Always good to hear possitive feadback!

A reason to go for targetting users is when you've got, what we call, "flexworkers" (multiple people that share multiple computers). Another reason might be the tooling that is used for approving the use of an application (webbased applications where a user can request software and the manager can approve, like ConfigMgr 2012 but without the connection to a computer).

"The fix" mentioned in that post is that the partionsize is to small for the installation.

That sounds like All Systems.

This is an example of all machines that have Office installed (Keep in mind that this is a query based on information from ADD/REMOVE PROGRAMS. To get this information you need to run Hardware Inventories): select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System where SMS_R_System.ResourceId in (select SMS_R_System.ResourceId from SMS_R_System inner join SMS_G_System_ADD_REMOVE_PROGRAMS on SMS_G_System_ADD_REMOVE_PROGRAMS.ResourceID = SMS_R_System.ResourceId where SMS_G_System_ADD_REMOVE_PROGRAMS.DisplayName LIKE "Microsoft Office Professional%") and SMS_R_System.Client = 1

Just create a Query-Based collection, which checks wether or not the software is already installed.

Nope, that is done in the step Prepare OS.

Hi Vinesh Rathi, You can find all the documentation about OSD and W7 in this part of the forum: http://www.windows-noob.com/forums/index.php?/forum/63-deploy-7/

Did you extend the AD for SCCM? If not, did you supply SLP information during client install?

It's probably not using your NAA during Software Deployment either. By default it first uses the computername$ for that. I would check the NTFS and share rights on the DP.

Check the clients IP/ AD Site and compare it with your Boundaries.

Hopefully there should be something like, failed, or error, or retrying, etc.

WINS is not needed at all. For WORKGROUP computers you need to supply the FQDN of the MP.

Is this part how it's supposed to be in your envirnment?

You need to check the UpdatesStore.log, the UpdatesHandler.log and the UpdatesDeployment.log for more information.

Did you check the logs?