BB24

It's a kludge but you could Run a command line to fire off a scheduled task which calls a script to do this. schtasks /create /ru SYSTEM /sc ONSTART /tn PostProcess /f /tr "%SystemRoot%\Files\PostProcess.cmd" http://technet.microsoft.com/en-us/library/bb490996.aspx Setup the PostProcess.cmd with all of your steps.

I suggest taking the "apply drivers" package out of the task sequence to eliminate that as a possible conflict. The laptop will likely still build (albeit with a lot of missing drivers). Or create a new driver package with only the network and storage drivers being installed. If that works and doesn't change your Add/Remove Programs control panel, then you can add drivers to the package a few at a time.

You might try looking at the DISM.log file to see which .dll are getting called for your graphics card). Are you doing an "apply all drivers" or do you have each graphics driver categorized for your specific Lenovo models?

Did you check the DC for a login from the client or the network routers/switches to ensure that they are assigning an IP (assuming DHCP)? If nothing else login locally on the client and see if you can see the network from there - maybe you have a network or firewall rule that is blocking the client to DC communication?

By chance is your laptop connected to a KVM? We noticed this issue with certain desktops using the Intel graphics chip; they wouldn't show the correct video and with USB FullMedia until they were removed from the KVM. Seems to have occurred after the SCCM 2012 R2 upgrade for us.

Aaron, My guess is that the problem is with a setting in the UDI Wizard, some variable that is getting set and then disallowing the remaining installation (perhaps filtered off). I recommend three things: 1) Add a "Pause" step in your task sequence (create a package with your favorite scripting language - example below) and add it after your UDI steps. Dim strComputer strComputer ="." ButtonCancelClick Function ButtonCancelClick On Error Resume Next ret = MsgBox("This system has been paused. You can press the F8 key to open a command window to perform additional steps or click OK or Cancel to continue.", vbOK + vbQuestion + vbSystemModal) End Function 2) When it gets to the Pause step, you should be able to press the F8 key to bring up a debug window (this assumes that you enabled your image with "Command Prompt Support" - Check the WinPE settings for this 3) Run the OutputTSVariables.wsf script and pipe to a text file (OutputTSVariables.wsf > c:\tmp\variable.log). Open with CMTrace/Notepad. This should show you what the values of all the variables are post UDI Wizard. Here's the MS link for some of the built in variables: http://technet.microsoft.com/en-us/library/bb632442.aspx

We've done tests with this in our lab in the past. Our task sequences will fail if they are more than 3 days out of whack. Interestingly it only fails if it is > 3 behind the current date. If the BIOS is ahead, it doesn't seem to impact SCCM installs. You might be able to leverage the wmi class win32_currenttime and compare the Day, Month and Year to a Now() function to account for a potential failure.

Unsure of the issue but: "Failed to open Software\Microsoft\Sms\Mobile Client\Software Distribution registry key. The client should not get checked for RWH OpLock Type" is a false positive.

I believe if you have a driver that exists on the DP, then the system will crawl through all the drivers and install it if it finds it "needs it." On the specific driver itself there should be an option of "Enable this driver and allow computers to install it". I think if you remove it, it will not be installed through this behavior, but would still be installed through your package install.

Run the following from an administrative command prompt: wmic /namespace:\\root\cimv2 path win32_computersystem get manufacturer It should return your Mfg information. As a .vbs you could do something like (I apolgize for the sloppy coding): strComputer = "." Set objWMIService = GetObject("winmgmts:" & "{impersonationLevel=impersonate}!\\" & strcomputer & "\root\cimv2") Set colItems = objWMIService.ExecQuery("Select * From Win32_SystemEnclosure") For Each objItem in colItems strComputerManufacturer = objitem.Manufacturer ' This should be the name you are looking for strSMBIOSAssetTag = objitem.SMBIOSAssetTag ' This will return a value if it is set (YMMV as Peter33 notes above) strSerialNumber = objitem.SerialNumber Next 'WScript.Echo "Manufacturer: " & strComputerManufacturer 'WScript.Echo "Asset Tag: "& strSMBIOSAssetTag 'WScript.Echo "Serial Number: " & strSerialNumber If strComputerManufacturer = "HP" or strComputerManufacturer = "Hewlett-Packard" Then strComputerManufacturer = "HP" XX = strComputerManufacturer ElseIf strComputerManufacturer = "Dell Inc" Then strComputerManufacturer = "DL" XX = strComputerManufacturer ElseIf strComputerManufacturer = "Lenovo" Then strComputerManufacturer = "LN" XX = strComputerManufacturer Else strComputerManufacturer = "??" End If ZZ = strSMBIOSAssetTag SN = strSerialNumber WScript.Echo "Mfg: " & XX WScript.Echo "Asset: " & ZZ WScript.Echo "Serial: " & SN

Is your IP space set correctly; i.e. are your Boundaries correctly defined?

If you already have a dedicated server that is functioning as the WDS role, you do not need to enable the role on the SCCM 2012 server/DPs. Instead all you will need is to build boot images (.wim files) from the SCCM 2012 environment using the 2012 toolkit. Within the image it will then know which server(s) to get the policies, task sequences, etc. For example in our environment we have a SCCM 2007 environment and brought up SCCM 2012. We have a dedicated WDS server with both 2012 and 2007 boot images presented in the PXE menu. Depending on which image is selected it then contacts the appropriate servers for advertisements/deployments/task sequences. (I know MS doesn't support this mixed environment, but our experience suggests it still works). If you are asking about using the PXE service on your existing 2007 sccm server, I defer to others.

Did you already try adding the TSvariable OSDPreserveDriveLetter = False in your task sequence? http://sccmfaq.wordpress.com/2013/02/14/sccm-2012-sp1-install-windows-7-to-drive-letter-c/

I believe we saw this with our z420. Check your versions and .inf files. I don't remember the specifics, but we had a conflict with a later version driver Here are the SCSIAdapter classes we are using for our build: Intel® C600 Series Chipset SATA RAID Controller 3.1.0.1068 iaStorA.inf Intel® C600 Series Chipset SAS RAID Controller 3.1.0.1082 iaStorS.inf Intel® C600 Series Chipset SATA AHCI Controller 3.1.0.1068 iaAHCI.inf Also the System class: Intel® C600/X79 series chipset SMBus Host Controller - 1D22 9.2.3.1013 patsmb.inf

Is the other security device PTT? http://community.spiceworks.com/topic/294633-dell-latitude-10-problem

I am I correct in assuming that the other system that you built and it stored the key is not the same type of hardware (not a Latitude 10)? I also assume that your system (the one not recording to AD) is joining the domain? Is the msTPM-OwnerInformation attribute value completely empty or at least have "<not set>"

I didn't see these two registry keys in your log - is this occurring earlier? --> Set TPM AD Backup Policy (REG ADD "HKLM\Software\Policies\Microsoft\TPM" /v "ActiveDirectoryBackup" /t REG_DWORD /d 1 /f) --> Set TPM Require AD Backup Policy (REG ADD "HKLM\Software\Policies\Microsoft\TPM" /v "RequireActiveDirectoryBackup" /t REG_DWORD /d 1 /f)

If you are doing this during OSD provisioning, you could have an .hta form that you present, assign checkboxes to Task Sequence variables and use the variable as an install filter during the sequence based on what is selected.

So you want to run the task sequence based on a value(s)? If you use the Options tab and Add Conditions you can leverage the wql "like" For example: WMI NameSpace: root\cimv2 WQL Query: Select * From Win32_ComputerSystem Where Manufacturer Like "Lenovo%" or WMI NameSpace: root\cimv2 WQL Query: Select * From Win32_ComputerSystem Where Name Like "CompLab%" You can also add multiple conditions that must all be true/false for the step to run. You can use custom task sequence variables as well in your condition or even look at a file. Lastly, if you are scripter, you can use that too. Hope that helps.

Have you already reviewed these articles: http://social.technet.microsoft.com/Forums/en-US/winservergen/thread/3747b974-ba4f-41e4-abd9-a2e7a38e994b, http://www.bootix.com/support/problems_solutions/pxe_e55_proxydhcp_service_did_not_reply_to_request_on_port_4011.html Assuming your setup (option 60) is good, are their multiple NICs on your system you are trying to build?

Sounds like a network communication issue. Are you running the BMP client on the same subnet as the 2012 server? If not, do you have your network switch setup for ip helper for the protocol/port?

For the site that does not have a PXE/WDS server, but does have a DP, couldn't you use Boot Media that would serve the PXE function?

--> Join domain (restart) If you are going to backup your policies is AD --> Set TPM AD Backup Policy (REG ADD "HKLM\Software\Policies\Microsoft\TPM" /v "ActiveDirectoryBackup" /t REG_DWORD /d 1 /f) --> Set TPM Require AD Backup Policy (REG ADD "HKLM\Software\Policies\Microsoft\TPM" /v "RequireActiveDirectoryBackup" /t REG_DWORD /d 1 /f) Add the TPM Ownership information --> (manage-bde -tpm -o <C0mpL3Xpa55word>) Once you enable Bitlocker you take ownership over it (assuming you use the built in command) You can also setup a default TPM PIN if you wish with complex password if you wish, but it requires 3 reg keys REG ADD "HKLM\Software\Policies\Microsoft\FVE" /v "UseEnhancedPin" /t REG_DWORD /d 1 /f REG ADD "HKLM\Software\Policies\Microsoft\FVE" /v "UseAdvancedStartup" /t REG_DWORD /d 1 /f REG ADD "HKLM\Software\Policies\Microsoft\FVE" /v "UseTPMPIN" /t REG_DWORD /d 1 /f (change "usetpmpin" to a mode that matches your ownership step) Set the PIN password manage-bde.exe -protectors -add <driveletter:> -TPMAndPIN C0mpL3xp@55w0rD (tpmandpin will match your PIN mode) Be aware that if you do set a TPM PIN, you will want to suspend Bitlocker before any reboots that might be required by software installations Command line (manage-bde.exe -protectors c: -disable)

I believe your namespace should be: \\root\cimv2\security\microsoftvolumeencryption ProtectionStatus = 1

You would probably need to download the *wdm.exe file from AMD (http://support.amd.com/us/gpudownload/windows/Legacy/Pages/radeonaiw_vista64.aspx?type=2.4.1&product=2.4.1.3.13〈=English), package it and then install it like a 'dirty driver install' You might be able to run the .exe on the nc6400 and after it installs identify the .inf and the dependent files, then add those files to a directory, then import that driver into SCCM. You would probably want to leverage driver Categories for that to be cleaner.