BB24

By the way, I have found changing the _smstssitecode variable with the tsenv2.exe, while it works makes the system Unapproved in our mixed-mode environment. It is a simple matter of Approving it, but just a note of warning.... 1E requires you to register (free) with them to download the file.

Not sure if this is what you are looking for: http://matthewcevans.com/blog/2010/07/20/disable-client-popup-message-for-sccm-task-sequences/

Storage driver would be my guess. Also try another USB slot. I've been burned by one port being USB2.0 and the other USB 3.0 and not having the USB 3.0 driver in my build.

Can you clarify what you mean by "it didn't find anything"? I am interpretting your statement to mean that when you attempt to boot from the network (usually pressing F12), you don't see any boot images to choose from. Are you running WDS on a separate server or are you running it on the SCCM 2007 server? If this is a separate server OS is your PXE service running on? Are you certain that the Windows Deployment Service is running - try restarting it to be sure. If you are having communication problems during the PXE request stage, are there any messages that appear on screen?

The log file you've provided shows success until after it partitions the hard drive. My assumption is that you are applying the OS shortly after that in your TS. I'd check the following properties at Apply OS Image step. Is it pointed to the correct Image Package Are you using an unattended or sysprep file (custom install)? What is your destination value set to? Do you have any options set that might be filtering?

What are the settings of the advertisement - specifically the Distribution Points tab? Is this 2007 or 2012 (guessing 2007)? The smsts.log file shows lots of errors: Failed to locate the local data path. The files needed to resume the task sequence are missing. This could be because the task sequence finished while in Windows PE. Please check the largest available partition for SMSTSLog\smsts.log file for more information. Unknown error (Error: 80070002; Source: Unknown They suggest to me that it is missing packages needed for the installation.

Double-check your data source path. It could be too many characters especially if you have lots of subdirectories and the name of the file to be installed is long. I don't recall the exact length, but I've seen that error with an application package in my environment. We had to move the package to a different folder structure to shorten it.

Are you sure you have your storage driver in your WinPE? If it is rebooting on you, is it actually writing anything to the HD or just the RAMDrive (x:)? Change your BIOS to not reboot after failure to see if it failing to a blue screen.

Couldn't you create a collection with a query that just targets the Operating System Version? 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 inner join SMS_G_System_OPERATING_SYSTEM on SMS_G_System_OPERATING_SYSTEM.ResourceID = SMS_R_System.ResourceId where SMS_G_System_OPERATING_SYSTEM.Name like "Microsoft Windows 7 Professional%"

You can build the query through the console: For Query 1 Queries - New - Query Provide a name for the query Object Type - System Resource Edit Query Statement... Select Criteria tab Select the New criteria button (golden sparkle) Select... Attribute class dropdown = System Resource Attribute dropdown = Last Logon User Name Value = username <enter> Ok, Finish, Apply.... Alternatively you should be able to use the following WQL: select * from SMS_R_System where SMS_R_System.LastLogonUserName = "username" Replace username with the name of the specific userid (case sensitive). I don't know if you can get Query 2, I'm unsure if SCCM inventories all logons. Might be easier to write a vbs script to capture that information.

I am assuming your clients are Win 7 64-bit., otherwise the file locations will be different. C:\Windows\SysWOW64\CCM\Logs I believe the logs you want to examine are: UpdatesDeployment.log UpdatesHandler.log UpdatesStore.log Prior to digging into the logs I would: 1) Look at the systems in your collection (Properties - Advertisements) make sure they are reflecting the advertised package 2) Look at a client and see if the application shows up under Run Advertised Programs (Control Panel - Programs - Run Advertised Programs (32-bit) (RAP) If steps 1 and 2 are good but the application is not installing, make sure you've set your advertisement up correctly, namely that the advertisement start time is appropriate and that it is set as a mandatory assignment otherwise it will be an optional "pull" done through RAP.

To rule out a WQL problem, have you created the query using the query "wizard" specifically around the SMS_R_System.SystemGroupName value? In other words select the properties of your query, select the edit query statement..., select the criteria tab, and select the New criteria icon. It should pop-up the Criterion Properties screen. Criterion Type = Simple value. Press the Select...button and select the Attibute class as System Resource and Attibute as System Group Name. Ok out and select the Value... button which should show the AD Groups available.

Yep, ccmexec.exe is running. Is it showing any CPU cycles running or is it idle? I.e. it normally shows usage when the local agent is installing As far as I can tell, SCCM 2012 does not give you the option of where to run from. What you're descibing is where it was in 2007, and I can't find a similar option in 2012. My bad. Try here: Deployment Type properties, Content tab, Deployment options “Download content from distribution point and run locally”. I'm guessing you've already looked at this technet article: http://social.technet.microsoft.com/wiki/contents/articles/11447.troubleshooting-application-deployment-in-sccm-2012.aspx

Thanks Peter. I wasn't paying attention to the thread heading and forgot this was for SCCM 2012.

Amar, Please clarify what are you are asking. When you say "single application" are you saying a "package". When you are saying "deployment type" are you suggesting variant installations of the package? For example, your application actually contains a suite of sub applications. You want to be able to call within your OSD different types of installation based on some variable (like notebook systems get these applications, while kiosks get a different set). If this is true, you could do it a number of ways within the Task Sequence with task sequence variables and using different programs within the package itself. Eg. Task Sequence Variable = zTS_Application_Suite_Selection Package = Application_Suite Program_for_Application_Suite_Full_Install = Full_install.bat SubProgramA for Application_Suite_Install = SubProgramA.bat SubProgramB for Application_Suite_Install = SubProgramB.bat Task Sequence step Install Full Suite Check If zTS_Application_Suite_Selection = Program_for_Application_Suite_Full_Install then Run Program Full_Install.bat else Ignore Error go to next step. Install SubProgramA Suite Check If zTS_Application_Suite_Selection = SubProgramA for Application_Suite_Install then Run Program SubProgramA.bat else Ignore Error go to next step. Install SubProgramB Suite Check If zTS_Application_Suite_Selection = SubProgramB for Application_Suite_Install then Run Program SubProgramB.bat else Ignore Error go to next step. There are much cleaner ways to do this of course, this is just to help me understand what you are asking. I couldn't find the link to your document.

When it is installing (as a required application) check the task manager processes and see if the ccmexec.exe is running. If its not, then we know more if it is a client/server/package issue. Also, is your advertisement for the required application setup to "run program from distribution point" or "download content from distribution point and run locally?" (Advertisement - Properties - Distribution Point tab)

Yes - probably the install has a "hidden window" waiting for an interactive response. Did you try copying the package locally and then manually running the install script to see what happens as it installs?

Are you trying to build stand-alone media or bootable media? If stand-alone are you building it on DVD or USB? If DVD, the entire TS will need to fit on one DVD it will not split properly (despite what it tells you) and you will need to build it on USB.

I think your slashes are backwards. When I look at my queries they show up as 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.SystemGroupName = "domain\\Group Name x86....." Also, make sure you aren't including that quotation mark ahead of your select statement.

http://blogs.technet.com/b/smsandmom/archive/2008/12/09/configmgr-2007-task-sequence-may-fail-to-run-with-error-code-0x80072ee7.aspx

It's possible, but I think unlikely. Generally, only locked files will cause the issue. The other culprit could be an anti-virus program that might be preventing the change to the file.

Check the BIOS GUID/UUID - see if the Asset Tag information is missing or unique. We've seen this exact situation with systems where the motherboard has been replaced and the mfg did not set the BIOS information back up. If this is the case the motherboard will use a "default" UUID which when presented to SCCM is translated into the SMS BIOS GUID but it is not unique because it exists in the SCCM inventory (due to another system already using that GUID). Unfortunately if this is the problem, you will need to get the BIOS set, usually by the manufacturer.

I've seen this behavior as well. The only way we've overcome it is to "categorize" the particular model and then assign the specific model and driver. It is also possible that the deviceID that you have in your driver catalog is not found in the .inf file, thus it is defaulting to VGA..

Q: is the OOB/default App-V value for Microsoft, curious as to why you set it differently - is your Q: drive defined in your company?

I haven't seen that behavior before when importing new drivers but the symptoms look similar to when you build a new wim in a directory where a previous wim exists. In other words you might have some sort of file lock on the wim you are injecting the new driver to. By chance do you have that folder open in Explorer or some other application (or someone/something) else have that share open?