Jump to content


Search the Community

Showing results for tags 'WinPE '.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Cloud
    • Azure
    • Microsoft Intune
    • Office 365
  • General Stuff
    • General Chat
    • Events
    • Site News
    • Windows News
    • Suggestion box
    • Jobs
  • MDT, SMS, SCCM, Current Branch &Technical Preview
    • How do I ?
    • Microsoft Deployment Toolkit (MDT)
    • Official Forum Supporters
    • SMS 2003
    • Configuration Manager 2007
    • Configuration Manager 2012
    • System Center Configuration Manager (Current Branch)
    • Packaging
    • scripting
    • Endpoint Protection
  • Windows Client
    • how do I ?
    • Windows 10
    • Windows 8
    • Windows 7
    • Windows Vista
    • Windows XP
    • windows screenshots
  • Windows Server
    • Active Directory
    • Microsoft SQL Server
    • System Center Operations Manager
    • KMS
    • Windows Deployment Services
    • NAP
    • Failover Clustering
    • PKI
    • Windows Server 2008
    • Windows Server 2012
    • Windows Server 2016
    • Windows Server 2019
    • Hyper V
    • Exchange
    • IIS/apache/web server
    • System Center Data Protection Manager
    • System Center Service Manager
    • System Center App Controller
    • System Center Virtual Machine Manager
    • System Center Orchestrator
    • Lync
    • Application Virtualization
    • Sharepoint
    • WSUS

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 25 results

  1. Hello experts, I am doing project at school (Windows Deployment). I have installed Windows Server 2016 onto VMware Workstation (DHCP, DNS, WDS, SCCM2012 R2, SQL Server 2012 SP1, ADK 10.1) and want to deploy Windows 7 x64 to other empty workstation. After powering the workstation on, it picks IP from DHCP, loads image, and after preparing network connections it automatically reboots without showing anything. You can see it here. I have tryed to troubleshoot. PXE is enabled, image, OS updated at distribution port, credentials are ok, imported vmware drivers, time is ok. I also run ipconfig, the device got correct address from DHCP. I will put the smsts.log - it shows PxeGetPxeData failed with 0x80070005. I spent hours and hours and still cannot find the sollution. I found some article - would it be my problem? The network port or DHCP may not be allowing the network connection soon enough though. The OS boots, loads, and initiates the TS process and connection to the site before the network is ready. By the time you press F8 and perform an ipconfig though, it may have completed successfully but too late for the TS initialization. Common solutions include ensuring that portfast is enabled on the port or adding a delay to boot process using a prestart command configured in the boot image. Thank you for your advice and tips! smsts.log ipconfig
  2. Hi, I'm having trobule with refreshing Windows 10 computers from WinPE. We need to upgrade BIOS before BIOS Conversion step in CM1610 and set BIOS settings. When reinstalling an computer it fails at staging Boot image. I have tried to size up the disk so it can hold larger WinPE Boot image but it does not work. 2048 MB Recovery 1024 MB EFI 128 MB MSR 100% OSD If I disable the step for BIOS Upgrade and Configure I can reinstall an computer without problems. <![LOG[Process completed with exit code 1]LOG]!><time="14:10:08.323-120" date="05-10-2017" component="TSManager" context="" type="1" thread="1320" file="commandline.cpp:1124"> <![LOG[TSUEFIDrive: ]LOG]!><time="14:10:08.323-120" date="05-10-2017" component="TSManager" context="" type="1" thread="1320" file="bootimage.cpp:774"> <![LOG[Staging boot image CM1000AA]LOG]!><time="14:10:08.323-120" date="05-10-2017" component="TSManager" context="" type="1" thread="1320" file="bootimage.cpp:781"> <![LOG[Mounting \Device\HarddiskVolume6 at Z:]LOG]!><time="14:10:08.338-120" date="05-10-2017" component="TSManager" context="" type="1" thread="1320" file="mountpoint.cpp:49"> <![LOG[Unmounting volume Z:\]LOG]!><time="14:10:08.338-120" date="05-10-2017" component="TSManager" context="" type="1" thread="1320" file="mountpoint.cpp:104"> <![LOG[0, HRESULT=80004005 (e:\nts_sccm_release\sms\framework\tscore\encryptablevolume.cpp,437)]LOG]!><time="14:10:08.354-120" date="05-10-2017" component="TSManager" context="" type="0" thread="1320" file="encryptablevolume.cpp:437"> <![LOG[Checking to see if the data path is on a bootable volume]LOG]!><time="14:10:08.354-120" date="05-10-2017" component="TSManager" context="" type="1" thread="1320" file="bootimage.cpp:1104"> <![LOG[ Volume S:\ is not NTFS]LOG]!><time="14:10:09.249-120" date="05-10-2017" component="TSManager" context="" type="1" thread="1320" file="bootimage.cpp:362"> <![LOG[Searching for a volume to stage the boot image]LOG]!><time="14:10:09.249-120" date="05-10-2017" component="TSManager" context="" type="1" thread="1320" file="bootimage.cpp:1128"> <![LOG[ Volume S:\ is not NTFS]LOG]!><time="14:10:09.264-120" date="05-10-2017" component="TSManager" context="" type="1" thread="1320" file="bootimage.cpp:362"> <![LOG[ Volume X:\ is not on a fixed disk]LOG]!><time="14:10:09.264-120" date="05-10-2017" component="TSManager" context="" type="1" thread="1320" file="bootimage.cpp:342"> <![LOG[BootImage::FindBootableVolume( NULL, sPath), HRESULT=80070490 (e:\nts_sccm_release\sms\framework\tscore\bootimage.cpp,1135)]LOG]!><time="14:10:09.264-120" date="05-10-2017" component="TSManager" context="" type="0" thread="1320" file="bootimage.cpp:1135"> <![LOG[Unable to find a volume that is suitable for staging the boot image. Element not found. (Error: 80070490; Source: Windows)]LOG]!><time="14:10:09.264-120" date="05-10-2017" component="TSManager" context="" type="3" thread="1320" file="bootimage.cpp:1135"> <![LOG[BootImage::PrepareForStaging(sLocalDataPath), HRESULT=80070490 (e:\nts_sccm_release\sms\framework\tscore\bootimage.cpp,783)]LOG]!><time="14:10:09.264-120" date="05-10-2017" component="TSManager" context="" type="0" thread="1320" file="bootimage.cpp:783"> <![LOG[Failed to validate for boot image staging]LOG]!><time="14:10:09.264-120" date="05-10-2017" component="TSManager" context="" type="3" thread="1320" file="bootimage.cpp:783"> <![LOG[StageBootImage() failed. 0x80070490.]LOG]!><time="14:10:09.264-120" date="05-10-2017" component="TSManager" context="" type="3" thread="1320" file="bootimage.cpp:889"> <![LOG[TS::Boot::BootImage::StageBootImage(sBootImageID, StageBootImageProgressCallback, (LPVOID) m_sStageBootImageMessage.c_str()), HRESULT=80070490 (e:\nts_sccm_release\sms\client\tasksequence\executionengine\engine.cxx,972)]LOG]!><time="14:10:09.264-120" date="05-10-2017" component="TSManager" context="" type="0" thread="1320" file="engine.cxx:972"> <![LOG[Failed to stage a boot image CM1000AA. Element not found. (Error: 80070490; Source: Windows)]LOG]!><time="14:10:09.264-120" date="05-10-2017" component="TSManager" context="" type="3" thread="1320" file="engine.cxx:972"> <![LOG[Failed to reboot the system. Error 0x80070490)]LOG]!><time="14:10:09.264-120" date="05-10-2017" component="TSManager" context="" type="3" thread="1320" file="engine.cxx:1140"> <![LOG[RebootSystem(pwszRebootMessage, dwRebootTimeout, dwRebootReason, bRebootWinPE), HRESULT=80070490 (e:\nts_sccm_release\sms\client\tasksequence\executionengine\engine.cxx,622)]LOG]!><time="14:10:09.264-120" date="05-10-2017" component="TSManager" context="" type="0" thread="1320" file="engine.cxx:622"> <![LOG[Failed to initialize a system reboot. Element not found. (Error: 80070490; Source: Windows)]LOG]!><time="14:10:09.264-120" date="05-10-2017" component="TSManager" context="" type="3" thread="1320" file="engine.cxx:622"> <![LOG[CheckForRebootRequest(&bRebootInitiated), HRESULT=80070490 (e:\nts_sccm_release\sms\client\tasksequence\executionengine\engine.cxx,310)]LOG]!><time="14:10:09.264-120" date="05-10-2017" component="TSManager" context="" type="0" thread="1320" file="engine.cxx:310"> <![LOG[Fatal error is returned in check for reboot request of the action (Restart Computer). Element not found. (Error: 80070490; Source: Windows)]LOG]!><time="14:10:09.264-120" date="05-10-2017" component="TSManager" context="" type="3" thread="1320" file="engine.cxx:310"> <![LOG[An error (0x80070490) is encountered in execution of the task sequence]LOG]!><time="14:10:09.264-120" date="05-10-2017" component="TSManager" context="" type="3" thread="1320" file="engine.cxx:390"> <![LOG[MP server http://LKSRVSCCM03.res.ludvika.intra. Ports 80,443. CRL=false.]LOG]!><time="14:10:09.264-120" date="05-10-2017" component="TSManager" context="" type="1" thread="1320" file="utils.cpp:6255"> <![LOG[Setting authenticator]LOG]!><time="14:10:09.280-120" date="05-10-2017" component="TSManager" context="" type="1" thread="1320" file="utils.cpp:6277"> <![LOG[Set authenticator in transport]LOG]!><time="14:10:09.280-120" date="05-10-2017" component="TSManager" context="" type="0" thread="1320" file="libsmsmessaging.cpp:7958"> <![LOG[Sending StatusMessage]LOG]!><time="14:10:09.296-120" date="05-10-2017" component="TSManager" context="" type="1" thread="1320" file="libsmsmessaging.cpp:4114"> <![LOG[Setting message signatures.]LOG]!><time="14:10:09.296-120" date="05-10-2017" component="TSManager" context="" type="0" thread="1320" file="libsmsmessaging.cpp:1383"> <![LOG[Setting the authenticator.]LOG]!><time="14:10:09.296-120" date="05-10-2017" component="TSManager" context="" type="0" thread="1320" file="libsmsmessaging.cpp:1413"> <![LOG[CLibSMSMessageWinHttpTransport::Send: URL: LKSRVSCCM03.res.ludvika.intra:80 CCM_POST /ccm_system/request]LOG]!><time="14:10:09.296-120" date="05-10-2017" component="TSManager" context="" type="1" thread="1320" file="libsmsmessaging.cpp:8828"> <![LOG[Request was successful.]LOG]!><time="14:10:09.327-120" date="05-10-2017" component="TSManager" context="" type="0" thread="1320" file="libsmsmessaging.cpp:9163"> <![LOG[Executing command line: X:\WINDOWS\system32\cmd.exe /k]LOG]!><time="14:10:21.451-120" date="05-10-2017" component="TSBootShell" context="" type="1" thread="1016" file="bootshell.cpp:1011"> <![LOG[The command completed successfully.]LOG]!><time="14:10:21.455-120" date="05-10-2017" component="TSBootShell" context="" type="1" thread="1016" file="bootshell.cpp:1093"> <![LOG[Successfully launched command shell.]LOG]!><time="14:10:21.455-120" date="05-10-2017" component="TSBootShell" context="" type="1" thread="1016" file="bootshell.cpp:444"> <![LOG[m_TSEngine.Execute(& m_eExecutionResult), HRESULT=80070490 (e:\nts_sccm_release\sms\client\tasksequence\tsmanager\tsmanager.cpp,1250)]LOG]!><time="14:25:10.554-120" date="05-10-2017" component="TSManager" context="" type="0" thread="1320" file="tsmanager.cpp:1250"> Thanks in advance, EGGLAS
  3. Hi, I'm having trobule with refreshing Windows 10 computers from WinPE. We need to upgrade BIOS before BIOS Conversion step in CM1610 and set BIOS settings. When reinstalling an computer it fails at staging Boot image. I have tried to size up the disk so it can hold larger WinPE Boot image but it does not work. 2048 MB Recovery 1024 MB EFI 128 MB MSR 100% OSD If I disable the step for BIOS Upgrade and Configure I can reinstall an computer without problems. <![LOG[Process completed with exit code 1]LOG]!><time="14:10:08.323-120" date="05-10-2017" component="TSManager" context="" type="1" thread="1320" file="commandline.cpp:1124"> <![LOG[TSUEFIDrive: ]LOG]!><time="14:10:08.323-120" date="05-10-2017" component="TSManager" context="" type="1" thread="1320" file="bootimage.cpp:774"> <![LOG[Staging boot image CM1000AA]LOG]!><time="14:10:08.323-120" date="05-10-2017" component="TSManager" context="" type="1" thread="1320" file="bootimage.cpp:781"> <![LOG[Mounting \Device\HarddiskVolume6 at Z:]LOG]!><time="14:10:08.338-120" date="05-10-2017" component="TSManager" context="" type="1" thread="1320" file="mountpoint.cpp:49"> <![LOG[Unmounting volume Z:\]LOG]!><time="14:10:08.338-120" date="05-10-2017" component="TSManager" context="" type="1" thread="1320" file="mountpoint.cpp:104"> <![LOG[0, HRESULT=80004005 (e:\nts_sccm_release\sms\framework\tscore\encryptablevolume.cpp,437)]LOG]!><time="14:10:08.354-120" date="05-10-2017" component="TSManager" context="" type="0" thread="1320" file="encryptablevolume.cpp:437"> <![LOG[Checking to see if the data path is on a bootable volume]LOG]!><time="14:10:08.354-120" date="05-10-2017" component="TSManager" context="" type="1" thread="1320" file="bootimage.cpp:1104"> <![LOG[ Volume S:\ is not NTFS]LOG]!><time="14:10:09.249-120" date="05-10-2017" component="TSManager" context="" type="1" thread="1320" file="bootimage.cpp:362"> <![LOG[Searching for a volume to stage the boot image]LOG]!><time="14:10:09.249-120" date="05-10-2017" component="TSManager" context="" type="1" thread="1320" file="bootimage.cpp:1128"> <![LOG[ Volume S:\ is not NTFS]LOG]!><time="14:10:09.264-120" date="05-10-2017" component="TSManager" context="" type="1" thread="1320" file="bootimage.cpp:362"> <![LOG[ Volume X:\ is not on a fixed disk]LOG]!><time="14:10:09.264-120" date="05-10-2017" component="TSManager" context="" type="1" thread="1320" file="bootimage.cpp:342"> <![LOG[BootImage::FindBootableVolume( NULL, sPath), HRESULT=80070490 (e:\nts_sccm_release\sms\framework\tscore\bootimage.cpp,1135)]LOG]!><time="14:10:09.264-120" date="05-10-2017" component="TSManager" context="" type="0" thread="1320" file="bootimage.cpp:1135"> <![LOG[Unable to find a volume that is suitable for staging the boot image. Element not found. (Error: 80070490; Source: Windows)]LOG]!><time="14:10:09.264-120" date="05-10-2017" component="TSManager" context="" type="3" thread="1320" file="bootimage.cpp:1135"> <![LOG[BootImage::PrepareForStaging(sLocalDataPath), HRESULT=80070490 (e:\nts_sccm_release\sms\framework\tscore\bootimage.cpp,783)]LOG]!><time="14:10:09.264-120" date="05-10-2017" component="TSManager" context="" type="0" thread="1320" file="bootimage.cpp:783"> <![LOG[Failed to validate for boot image staging]LOG]!><time="14:10:09.264-120" date="05-10-2017" component="TSManager" context="" type="3" thread="1320" file="bootimage.cpp:783"> <![LOG[StageBootImage() failed. 0x80070490.]LOG]!><time="14:10:09.264-120" date="05-10-2017" component="TSManager" context="" type="3" thread="1320" file="bootimage.cpp:889"> <![LOG[TS::Boot::BootImage::StageBootImage(sBootImageID, StageBootImageProgressCallback, (LPVOID) m_sStageBootImageMessage.c_str()), HRESULT=80070490 (e:\nts_sccm_release\sms\client\tasksequence\executionengine\engine.cxx,972)]LOG]!><time="14:10:09.264-120" date="05-10-2017" component="TSManager" context="" type="0" thread="1320" file="engine.cxx:972"> <![LOG[Failed to stage a boot image CM1000AA. Element not found. (Error: 80070490; Source: Windows)]LOG]!><time="14:10:09.264-120" date="05-10-2017" component="TSManager" context="" type="3" thread="1320" file="engine.cxx:972"> <![LOG[Failed to reboot the system. Error 0x80070490)]LOG]!><time="14:10:09.264-120" date="05-10-2017" component="TSManager" context="" type="3" thread="1320" file="engine.cxx:1140"> <![LOG[RebootSystem(pwszRebootMessage, dwRebootTimeout, dwRebootReason, bRebootWinPE), HRESULT=80070490 (e:\nts_sccm_release\sms\client\tasksequence\executionengine\engine.cxx,622)]LOG]!><time="14:10:09.264-120" date="05-10-2017" component="TSManager" context="" type="0" thread="1320" file="engine.cxx:622"> <![LOG[Failed to initialize a system reboot. Element not found. (Error: 80070490; Source: Windows)]LOG]!><time="14:10:09.264-120" date="05-10-2017" component="TSManager" context="" type="3" thread="1320" file="engine.cxx:622"> <![LOG[CheckForRebootRequest(&bRebootInitiated), HRESULT=80070490 (e:\nts_sccm_release\sms\client\tasksequence\executionengine\engine.cxx,310)]LOG]!><time="14:10:09.264-120" date="05-10-2017" component="TSManager" context="" type="0" thread="1320" file="engine.cxx:310"> <![LOG[Fatal error is returned in check for reboot request of the action (Restart Computer). Element not found. (Error: 80070490; Source: Windows)]LOG]!><time="14:10:09.264-120" date="05-10-2017" component="TSManager" context="" type="3" thread="1320" file="engine.cxx:310"> <![LOG[An error (0x80070490) is encountered in execution of the task sequence]LOG]!><time="14:10:09.264-120" date="05-10-2017" component="TSManager" context="" type="3" thread="1320" file="engine.cxx:390"> <![LOG[MP server http://LKSRVSCCM03.res.ludvika.intra. Ports 80,443. CRL=false.]LOG]!><time="14:10:09.264-120" date="05-10-2017" component="TSManager" context="" type="1" thread="1320" file="utils.cpp:6255"> <![LOG[Setting authenticator]LOG]!><time="14:10:09.280-120" date="05-10-2017" component="TSManager" context="" type="1" thread="1320" file="utils.cpp:6277"> <![LOG[Set authenticator in transport]LOG]!><time="14:10:09.280-120" date="05-10-2017" component="TSManager" context="" type="0" thread="1320" file="libsmsmessaging.cpp:7958"> <![LOG[Sending StatusMessage]LOG]!><time="14:10:09.296-120" date="05-10-2017" component="TSManager" context="" type="1" thread="1320" file="libsmsmessaging.cpp:4114"> <![LOG[Setting message signatures.]LOG]!><time="14:10:09.296-120" date="05-10-2017" component="TSManager" context="" type="0" thread="1320" file="libsmsmessaging.cpp:1383"> <![LOG[Setting the authenticator.]LOG]!><time="14:10:09.296-120" date="05-10-2017" component="TSManager" context="" type="0" thread="1320" file="libsmsmessaging.cpp:1413"> <![LOG[CLibSMSMessageWinHttpTransport::Send: URL: LKSRVSCCM03.res.ludvika.intra:80 CCM_POST /ccm_system/request]LOG]!><time="14:10:09.296-120" date="05-10-2017" component="TSManager" context="" type="1" thread="1320" file="libsmsmessaging.cpp:8828"> <![LOG[Request was successful.]LOG]!><time="14:10:09.327-120" date="05-10-2017" component="TSManager" context="" type="0" thread="1320" file="libsmsmessaging.cpp:9163"> <![LOG[Executing command line: X:\WINDOWS\system32\cmd.exe /k]LOG]!><time="14:10:21.451-120" date="05-10-2017" component="TSBootShell" context="" type="1" thread="1016" file="bootshell.cpp:1011"> <![LOG[The command completed successfully.]LOG]!><time="14:10:21.455-120" date="05-10-2017" component="TSBootShell" context="" type="1" thread="1016" file="bootshell.cpp:1093"> <![LOG[Successfully launched command shell.]LOG]!><time="14:10:21.455-120" date="05-10-2017" component="TSBootShell" context="" type="1" thread="1016" file="bootshell.cpp:444"> <![LOG[m_TSEngine.Execute(& m_eExecutionResult), HRESULT=80070490 (e:\nts_sccm_release\sms\client\tasksequence\tsmanager\tsmanager.cpp,1250)]LOG]!><time="14:25:10.554-120" date="05-10-2017" component="TSManager" context="" type="0" thread="1320" file="tsmanager.cpp:1250"> Thanks in advance, EGGLAS
  4. Consider the following: The BIOS date & time are correct Date & time remain correct up until the Task Sequence selection screen Once a Task Sequence is selected, the date & time are updated to the built-in WinPE timezone, thus making it the incorrect time. Is this normal and expected behavior?
  5. Dear Forum, I have problem deploying HP XW4600 workstation with SCCM. I'm using WinPE 10 x64 from MDT2013. I was following this procedure to find out card driver (I also tried driver from running WIndows 7x64): https://www.niallbrady.com/2011/08/31/missing-nic-driver-in-winpe-boot-image-no-problem/ So my card is definitely: Broadcom NetXtreme Gigabit Ethernet PCI\VEN_14E4&DEV_167B&SUBSYS_1308103C I took driver for x64 Desktop/Mobile/Server (x64) version 17.2.0.2 from: https://www.broadcom.com/support/ethernet-nic-netxtreme-i-desktop-mobile When I load the driver with drvload b57nd60a.inf it says that driver was loaded fine, then I do the: wpeutil initializeNetwork followed by ipconfig but cannot get IP address from the server. I've also tried: HP Client Windows PE 10 x64 Driver Pack from: http://ftp.hp.com/pub/caps-softpaq/cmit/softpaq/WinPE10.html without success... In the past I've been using 32bit WinPE and these XP workstations were installing fine. Could You please help me to detect and insert correct driver ?
  6. Hello Everyone, I am having a problem when trying to re-deploy an OSD task sequence to machines that have already been imaged. The machines are Dell tablets and we are reusing the same NIC dongles to image them via UEFI PXE booting. I have followed the steps from this article in order to reuse the same dongles: https://blogs.technet.microsoft.com/configurationmgr/2015/08/27/reusing-the-same-nic-for-multiple-pxe-initiated-deployments-in-system-center-configuration-manger-osd/ Our OSD task sequence is deployed to the following collections: "All Unknown Computers", "All Systems", and "All Desktop Clients". Deployment settings are made available to "Only media and PXE" and Rerun behavior is set to "Always rerun program". It seem that when the technician takes a new tablet out of the box since it is seen as an unknown device in CM, it gets the available TS and they can image it. The problem occurs when they try to reimage the same machine, SCCM now sees it as a known device. However, whether the device is known or unknown shouldn't it be able to see the task sequence since I have it deployed to the collections mentioned above? Here is a snippet from my SMSPXE.log: Client lookup reply: <ClientIDReply><Identification Unknown="0" ItemKey="16793987" ServerName=""><Machine><ClientID/><NetbiosName/></Machine></Identification></ClientIDReply> 00:50:B6:17:6D:AA, 4C4C4544-0032-4D10-8052-B9C04F474332: device is in the database. Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="16793987" ServerName=""><Machine><ClientID>GUID:62efbe3a-9224-4a5a-a2c5-63d6fb7b1190</ClientID><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="CM12000F" OfferIDTime="6/17/2016 10:46:00 AM" PkgID="CM100009" PackageVersion="" PackagePath="http://XX-XXX-XX.XX.XX/SMS_DP_SMSPKG$/CM100005"BootImageID="CM100005" Mandatory="0"/></ClientIDReply> 00:50:B6:17:6D:AA, 4C4C4544-0032-4D10-8052-B9C04F474332: found optional advertisement CM12000F Looking for bootImage CM100005 Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="16793987" ServerName=""><Machine><ClientID>GUID:62efbe3a-9224-4a5a-a2c5-63d6fb7b1190</ClientID><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="CM12000F" OfferIDTime="6/17/2016 10:46:00 AM" PkgID="CM100009" PackageVersion="" PackagePath="http://XX-XXX-XX.XX.XX/SMS_DP_SMSPKG$/CM100005"BootImageID="CM100005" Mandatory="0"/></ClientIDReply> I noticed that when the machine is unknown the SMSPXE.log looks like this: Client lookup reply: <ClientIDReply><Identification Unknown="0" ItemKey="0" ServerName=""><Machine><ClientID/><NetbiosName/></Machine></Identification></ClientIDReply> 00:50:B6:17:6D:7E, 4C4C4544-004D-3610-8052-CAC04F474332: device is not in the database. Getting boot action for unknown machine: item key: 2046820353 Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="2046820353" ServerName=""><Machine><ClientID>e2b9e21e-4a0f-40d6-94eb-6ebf20a22d59</ClientID><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="CM12000F" OfferIDTime="6/17/2016 10:46:00 AM" PkgID="CM100009" PackageVersion="" PackagePath="http://XX-XXX-XX.XX.XX/SMS_DP_SMSPKG$/CM100005"BootImageID="CM100005" Mandatory="0"/></ClientIDReply> 00:50:B6:17:6D:7E, 4C4C4544-004D-3610-8052-CAC04F474332: found optional advertisement CM12000F Looking for bootImage CM100005 Client lookup reply: <ClientIDReply><Identification Unknown="0" ItemKey="0" ServerName=""><Machine><ClientID/><NetbiosName/></Machine></Identification></ClientIDReply> 00:50:B6:17:6D:75, 4C4C4544-0053-4710-8052-B8C04F474332: device is not in the database. Getting boot action for unknown machine: item key: 2046820353 Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="2046820353" ServerName=""><Machine><ClientID>e2b9e21e-4a0f-40d6-94eb-6ebf20a22d59</ClientID><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="CM12000F" OfferIDTime="6/17/2016 10:46:00 AM" PkgID="CM100009" PackageVersion="" PackagePath="http://XX-XXX-XX.XX.XX/SMS_DP_SMSPKG$/CM100005"BootImageID="CM100005" Mandatory="0"/></ClientIDReply> Any ideas why it wont see the task sequence? Thanks! Joe
  7. Hello, Just wondering if anyone has manage to image the Dell XPS 13 9350? Got SCCM 2012 R2 SP1 CU2 and when using my current TS wtih Dell XPS 13 9350 it came to the first reboot (partitioning, apply wim, check drivers, install client etc...) and then fail... acording to this link that is normal for this model if you set disk opertion to AHCI which I had: https://www.reddit.com/r/SCCM/comments/40t2iv/dell_xps_9350_9550_sccm_imaging_guide/ I switched to RAID ON as suggested in the link, and added the Intel RAID driver to my WInPE. I can boot on WinPE, partition the disk but when apply WIM in SATA RAID ON mode it fails, smsts.log says the following: Expand a string: WinPE TSManager 3/7/2016 5:01:42 PM 1520 (0x05F0) Executing command line: OSDApplyOS.exe /image:P010034A,%OSDImageIndex% "/config:P010005F,%OSDConfigFileName%" /runfromnet:True TSManager 3/7/2016 5:01:42 PM 1520 (0x05F0) Command line for extension .exe is "%1" %* ApplyOperatingSystem 3/7/2016 5:01:42 PM 1980 (0x07BC) Set command line: "OSDApplyOS.exe" /image:P010034A,1 "/config:P010005F,Unattend.xml" /runfromnet:True ApplyOperatingSystem 3/7/2016 5:01:42 PM 1980 (0x07BC) Found run from net option: 1 ApplyOperatingSystem 3/7/2016 5:01:42 PM 1980 (0x07BC) Not a data image ApplyOperatingSystem 3/7/2016 5:01:42 PM 1980 (0x07BC) ApplyOSRetry: ApplyOperatingSystem 3/7/2016 5:01:42 PM 1980 (0x07BC) TSLaunchMode: PXE ApplyOperatingSystem 3/7/2016 5:01:42 PM 1980 (0x07BC) OSDUseAlreadyDeployedImage: FALSE ApplyOperatingSystem 3/7/2016 5:01:42 PM 1980 (0x07BC) 'C:\' not a removable drive ApplyOperatingSystem 3/7/2016 5:01:42 PM 1980 (0x07BC) Searching for next available volume: ApplyOperatingSystem 3/7/2016 5:01:42 PM 1980 (0x07BC) Volume S:\ size is 350MB and less than 750MB ApplyOperatingSystem 3/7/2016 5:01:42 PM 1980 (0x07BC) Volume C:\ is a valid target. ApplyOperatingSystem 3/7/2016 5:01:42 PM 1980 (0x07BC) Found volume C:\ ApplyOperatingSystem 3/7/2016 5:01:42 PM 1980 (0x07BC) Windows target partition is 0-2, driver letter is C:\ ApplyOperatingSystem 3/7/2016 5:01:42 PM 1980 (0x07BC) !sSystemPart.empty(), HRESULT=80004005 (e:\qfe\nts\sms\framework\tscore\diskvolume.cpp,132) ApplyOperatingSystem 3/7/2016 5:01:42 PM 1980 (0x07BC) System partition not set ApplyOperatingSystem 3/7/2016 5:01:42 PM 1980 (0x07BC) Unable to locate a bootable volume. Attempting to make C:\ bootable. ApplyOperatingSystem 3/7/2016 5:01:42 PM 1980 (0x07BC) bBootDiskDefined == true, HRESULT=80004005 (e:\qfe\nts\sms\client\osdeployment\applyos\installcommon.cpp,690) ApplyOperatingSystem 3/7/2016 5:01:42 PM 1980 (0x07BC) Unable to find the system disk ApplyOperatingSystem 3/7/2016 5:01:42 PM 1980 (0x07BC) MakeVolumeBootable( pszVolume ), HRESULT=80004005 (e:\qfe\nts\sms\client\osdeployment\applyos\installcommon.cpp,772) ApplyOperatingSystem 3/7/2016 5:01:42 PM 1980 (0x07BC) Failed to make volume C:\ bootable. Please ensure that you have set an active partition on the boot disk before installing the operating system. Unspecified error (Error: 80004005; Source: Windows) ApplyOperatingSystem 3/7/2016 5:01:42 PM 1980 (0x07BC) ConfigureBootVolume(targetVolume), HRESULT=80004005 (e:\qfe\nts\sms\client\osdeployment\applyos\applyos.cpp,499) ApplyOperatingSystem 3/7/2016 5:01:42 PM 1980 (0x07BC) Process completed with exit code 2147500037 TSManager 3/7/2016 5:01:42 PM 1520 (0x05F0) !--------------------------------------------------------------------------------------------! TSManager 3/7/2016 5:01:42 PM 1520 (0x05F0) Failed to run the action: Apply Win10x64Ent 1511 + Office 2016 WIM. Unspecified error (Error: 80004005; Source: Windows) TSManager 3/7/2016 5:01:42 PM 1520 (0x05F0) Same TS works on vitually all other Dell models and google around it shows quicly that this model is an issue but most seems to have problem to just see the disk, and I do that... if I F8 in WinPe I can in diskpart see the disk.. and the partitioning parts work.. it is apply the WIM that fails. Thankful for help thanks
  8. Is it possible after choosin' the image to create an prompt to let you choose which application want to add in your image. After that comes the OSDComputername.
  9. Hello All, My task is to trigger the HTA during windows installation and showcase the static screens while the installation continues in the background.Now the issue I'm facing is to trigger the HTA to appear on screen. I'm tying to test my sample HTA file but during installation startup, all I'm seeing is "a blank white window". Below is the code of my HTA file: <html> <head> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=utf-8"> <style> .fullbackground{ position:relative; width:100%; /* alternative: right:0; */ height:100%; /* alternative: bottom:0; */ } img.fullbackground{ position:absolute; z-index:-1; top:0; left:0; width:100%; /* alternative: right:0; */ height:100%; /* alternative: bottom:0; */ } .messageSection { position: absolute; width: 100%; } .mainbody, .header, .footer { padding: 5px; } .mainbody { margin-top: 25px; min-height: 150px; max-height: 388px; overflow: auto; } .messagePara { font-family: Calibri; font-size: 16pt; font-weight: bold; color: #FFFFFF; text-align: center; margin-left:20%; margin-right:20%; margin-bottom:20%;} .header { margin: auto; width: 60%; padding: 10px; text-align:left; color: #FFFFFF; font-family: Calibri; font-size: 14pt; font-weight: bold; margin-top:30px; } .footer { height: 40px; font-family: Calibri; font-size: 11pt; font-weight: bold; color: #FFFFFF; text-align: center; position: absolute; width:100%; bottom:0; left:0; } </style> <HTA:APPLICATION ID="oHTA" BORDER="none" CAPTION="no" CONTEXTMENU="no" Icon="autorun.ico" INNERBORDER="no" NAVIGABLE="yes" SCROLL="no"/> <script language="javascript"> var __TITLE_VAR_TEXT = "Sample Title"; var __COPYRIGHT_VAR_TEXT = "Sample Footer"; var __MESSAGE_DISC_VAR_TEXT = "Sample Message"; var __LINKBODYBACKGROUND_VAR_TEXT = "shuttle6b.jpg"; //background image var splashWindowWidth = 637; var splashWindowHeight = 479; if (window.screen) { splashWindowLeft = (window.screen.availWidth - splashWindowWidth) / 2; splashWindowTop = (window.screen.availHeight - splashWindowHeight) / 2; } try { window.moveTo(splashWindowLeft, splashWindowTop); window.resizeTo(splashWindowWidth, splashWindowHeight); } catch(e){} function windowOnLoad() { maxWindow(); document.title = __MESSAGE_DISC_VAR_TEXT; document.getElementById("image").src=__LINKBODYBACKGROUND_VAR_TEXT; window.setTimeout("closeScreen()",5000); } function closeScreen() { self.close(); } function maxWindow() { window.moveTo(0,0); if (document.all) { top.window.resizeTo(screen.availWidth,screen.availHeight); } else if (document.layers||document.getElementById) { if (top.window.outerHeight<screen.availHeight||top.window.outerWidth<screen.availWidth) { top.window.outerHeight = screen.availHeight; top.window.outerWidth = screen.availWidth; } } } </script> </head> <body style="text-align: center; " onload="windowOnLoad()"> <div class="fullbackground"> <img id="image" class="fullbackground" /> <div class="header"> <script language="javascript">document.write(__TITLE_VAR_TEXT);</script></div> <div class="mainbody"> <p id="messagePara" class="messagePara"> <script language="javascript">document.write(__MESSAGE_DISC_VAR_TEXT);</script> </p> </div> <div class="footer"> <script language="javascript">document.write(__COPYRIGHT_VAR_TEXT); </script></div> </div> </body> </html> I've updated the required INI file with the following entries:- [sample] type = command Caption=UI Reboot=No CommandLine="mshta.exe %programfiles%\Folder_1\ Folder_2\Folder_3\Folder_4\Sample.hta" I've referred the below URLs :- http://www.windows-noob.com/forums/topic/5968-hta-blank-screen/ http://blogs.msdn.com/b/joelschoenberg/archive/2008/08/18/maintenance-booting-your-windows-machines.aspx But none of the options worked. I also tried with passing the HTA file in arguments as mentioned below:- CommandLine=mshta.exe Arguments="%programfiles%\Folder_1\Folder_2\Folder_3\Folder_4\Sample.hta" but it didn't worked. NOTE: I've also used the direct path of "Sample.hta" file but it still didn't show up. Before installation, I've tried pressing F8 key and running the HTA using mshta.exe and that works completely fine. Can anyone please share some suggestions of how to execute this "HTA" from INI file and the correct commandLine value ? Thanks in advance.
  10. Hello, The Task Sequence that was deploying W7 with SCCM 2012 SP1 has stopped to deploying the Lenovo X240 laptop. The Laptop must load WinPE on Workgroup & PXE When I get on F8 to get an ipconfig, nothing but the message "configuration IP" is dysplayed, then WinPE reboot. I don't know if the laptop has joined the workgroup The smsts.log show 2 mains errors : Failed to download pxe variable file. Code(0x00000001) TSPxe 24/07/2015 16:09:06 1176 (0x0498) PxeGetPxeData failed with 0x80004005 TSPxe 24/07/2015 16:09:06 1176 (0x0498) RegOpenKeyExW failed for Software\Microsoft\SMS\Task Sequence TSBootShell 24/07/2015 16:09:06 784 (0x0310) GetTsRegValue() failed. 0x80070002. TSBootShell 24/07/2015 16:09:06 784 (0x0310) The driver are the following : http://support.lenovo.com/us/en/downloads/ds038819 Please, Help me.
  11. Hey all, I'm at my wits end here. I'm trying to add support for a new generation of laptops to my SCCM 2012 R2 TS. I have already gone through the trouble of gathering all the required drivers for the new models and created new Driver Packages only to find that the new models all use a newer\different NIC driver than the previous generation. No big deal I think, I'll just create a new boot WIM for testing, get the appropriate drivers for WinPE and I'm good! Well, not so fast. For some reason when I add the new boot WIM to my testing Task Sequence and try to PXE, the machine is unable to pick up the OSD deployment. If a revert back to the original boot WIM in the same TS it picks up, but there are no NIC drivers. I've pretty much narrowed it down to being some sort of issue with my new boot WIM but can't seem to figure out what. I'll be upfront and say that I have not had to create a new boot WIM before so it's possible I FUBAR'd something during this process. I just used the "Add new Boot WIM" function and pointed the wizard at the Win ADK supplied boot WIM. If that's not right, maybe someone can point me in the right direction. I've confirmed the new boot WIM is at my local DP the new boot WIM is the same version as the working one, WinPE 5.0 (6.3 \ Win 8.1) I've confirmed my drivers are the appropriate version and architecture and the correct model I can't even get any logs because when I use the new boot WIM it doesn't get past PXE. Below are the last few lines of the PXE before the machine reboots: Message from Administrator: Configuration Manager is looking for policy Contacting Server: [local DP IP]....... TFTP Download: smsboot\x64\abortpxe.com PXE Boot aborted. Botting to next device... PXE-M0F: Exiting Intel Boot Agent
  12. Hi, Can someone please point me in the right direction so I can set the "IT Organization" name in the Task Sequence progress window. I've set this in the custom client settings which is deployed to the same collection as the task sequence. When I run a task sequence that captures User State (requires task sequence to be launched from Windows) the "IT Organization" works fine and it displays our company name. However, when I PXE boot a task sequence for a task sequence with no USMT capture, it only displays "IT Organization" in the task sequence progress window. This is when I launch from Software Center:
  13. Alright guys I need some insight. I have been asked to come up with a way to clean a drive (using diskpart) during PE before the OSD password is entered. Now the catch is there has to be a way to opt out. Basically the powers that be want a pop-up that says "Do you want to clean the drive" with yes and no buttons. Now I know I can create a custom media hook and edit the boot.wim to run a script that will clean the drive but like I said, it needs it to prompt the end user. I'm really hoping someone out there has something similar or can point me in the right direction. Environment: SCCM 2012 SP1 integrated with MDT 2012 Update 1 PXE is enabled but most of the techs are attached to using USB media.
  14. SCCM 2007 SP2 R3, SQL Server 2008 x64, Windows Server 2008 R2 x64 I am having difficulty with a bare metal install and capture of Win7 on a laptop. I have followed all guides closely and verified correct version of MDT, AIK, WINPE, but I simply cannot inject drivers into my boot image. I keep getting the following message from the wizard. Error: Boot image to update: MDT Custom PE Error: Actions to perform: Add ConfigMgr binaries Enable Windows PE command line support Add drivers Error: Failed to import the following drivers: IntelĀ® 82567LM-3 Gigabit Network Connection - Failed to inject a ConfigMgr driver into the mounted WIM file Error: The wizard detected the following problems when updating the boot image. Failed to inject a ConfigMgr driver into the mounted WIM file Failed to inject a ConfigMgr driver into the mounted WIM file Failed to inject a ConfigMgr driver into the mounted WIM file Failed to inject a ConfigMgr driver into the mounted WIM file The ConfigMgr Provider reported an error.: ConfigMgr Error Object: instance of SMS_ExtendedStatus { Description = "Failed to insert OSD binaries into the WIM file"; ErrorCode = 2152205056; File = "c:\\qfe\\nts_sms_fre\\sms\\siteserver\\sdk_provider\\smsprov\\sspbootimagepackage.cpp"; Line = 4262; ObjectInfo = "CSspBootImagePackage::PreRefreshPkgSrcHook"; Operation = "ExecMethod"; ParameterInfo = "SMS_BootImagePackage.PackageID=\"BWW00015\""; ProviderName = "WinMgmt"; StatusCode = 2147749889; }; I've noted several other posts where user advise using DSIM. Is this a requirement? I like the ability to utilize the driver repository / see the injected drivers in the SCCM console. Thanks!
  15. Has anybody been successuflly able to boot into ConfigMgr via pxe boot on a HP DL380p? Keeps failing at "Apply network connection" Once it reaches that point, it reboots. I've downloaded all the nic drivers from HP's website and injected them into my boot image, but have had no success. Any ideas or help would be greatly appreciated. OSD works with all of our desktops/laptops so it leads me to believe this error has to do with nic drivers? Thank you
  16. Hey Guys / Niall - I've got the strangest issue I've ever seen with SCCM and need suggestions, please. I recently started at a company which already had pretty extensive OSD TS used for all models. They have a single production OSD task sequence for use with all systems. It has a frontend that integrates with the ticketing system as well as AD and is written with AutoIT using code from the SCCM 2012 R2 SDK. The Issue One specific model specific model (Dell E5440) at only one specific site (New York branch) runs extremely slow when running the OSD TS from WinPE to standard use pf the system after imagine. When looking into it today, I ran an extensive report on a machine with the issue and my system which is in Nashville, runs fine, and is also a E5440 imaged with the same TS. I exported the reports (16mb text files each) then compared in WinMerge. What Causes it to be Slow When I reached CPU Type, I found the following difference: My Machine: Intel Core i7-4600U, 3000 MHz (30 x 100) E5440 /w Issue: Intel Core i7-4600U, 800 MHz (8 x 100) As you can see, the multiplier is somehow at 8 instead of 30. how does this happen during OSD - especially - only at a single site which runs the exact same task sequence? I looked through the TS (which I'm still becoming famailer with) but haven't seen anything which would edit the BIOS. I also took a spare 5440 and got into the BIOS myself. There's not even an option to set the multiplier there manually if I wanted to! Other Tests Performed I already mentioned that running the same TS here in Nashville (and 2 other sites) on the same model works fine. We imaged one here in Nashville, tested that it was fine, then shipped it to New York. They then imaged it (using the same task sequence we used here) and it still had the slowness issue from WinPE to standard use afterwards. Any ideas or suggestions as to how to fix and/or what is causing this to happen? Thanks!
  17. Hello everyone, I have been referencing this site for quite a while now and I appreciate all the information here. I hope to give back to it from time to time so I created an account. That being said, has anyone tried to add an on screen keyboard to the WinPE startup? I have a lot of tablets to image and there are a couple places that we need to be able to type in some information. I am working with SCCM 2012 R2 and the latest ADK. I mount the boot image using imagex, add the keyboard exe that I would like, add the line to run it in winpeshl.ini. Then i unmount, commit, and yadda yadda. When booting to this new winpe boot image the keyboard was not coming up on startup. So at this point i plug in a usb keyboard and hit F8 for the command prompt then try to run the keyboard exe from there. It tells me: "the subsystem needed to support the image is not present". I have tried running imagex from c:\program files (x86)\windows kits\8.1\assessment and deployment kit\deployment tools\amd64\dism. Searches via the google have been hit and miss. Thanks in advance for any thoughts you have on this.
  18. I am trying to deploy our windows image to a new group of Lenovo ThinkCentre M72e (4004) when they pxe they would just reboot. I pxe booted again and hit f8 did an ipconfig and no network address. I know the NIC is a relteck so I went to the site download the nic drivers for windows 7 and imported them and updated by boot image. http://support.lenovo.com/en_US/research/hints-or-tips/detail.page?&DocID=HT073565 But I still PXE and get no ip address I am on the same vlan as my server and when I login to another computer on that port I get an IP. So I am pretty sure I have a driver issue. I loaded that driver in windows 7 and it is defiantly the right driver for the model. Can someone help me out thanks.
  19. Hello, I have a ~8 mb bootable iso that contains the Dell diagnostics tools for laptops. Is it possible to somehow use this iso to boot into the diagnostic tool from PXE using SCCM 2007?
  20. Hei all, I am having a truly strange experience with our SCCM2012 server and a OSD to some desktops. Now, if I had just started with them I would have thought that I had the incorrect driver, but thats not the case here. About a month back I started to configure replacement client desktops for the students. These machines would be going to the library, an intense environment for data. So to make things simple for myself, I took some old HP dx2250 Athlon pc's, installed a new PCI Wifi card and imaged them from SCCM with Win7 x32. I have completed all of them, no problem. I then decided to expand on the usable machines and place several more in the common areas. First batch went well. But the second batch hit a hitch. When they were loading the WinPE environment, they repeatedly rebooted when the network drivers were been loaded. The machines are IDENTICAL in every way to the ones that had been imaged before. I tried booting them on different vlans, but the same issue happened on all. Finally I took one of them over to my work office to troubleshoot it and low and behold - it worked. I did no changes, just booted it from a different physical location. The vlans here are the same as in their previous location. And now things go really weird. I brought over the last 3 and two of them did the same as the first. But not the last. No matter what I try, I cannot get the WinPE environment to load past the network driver load. As mentioned before, the machine is identical to all the others that have been successful. Are there any logs that I can check to follow up or do any of you have any tips for me? Cheers & thanks in advance! Anthony
  21. Hello I'm having a bit of trouble deploying Win7 to an OptiPlex 790. I have added the NIC driver to WinPE. It boots into WinPE, starts the TS, applies the OS, applies the the OptiPlex 790 driver package(lates cab imported from Dell). On the next step after applying drivers, "Setup Windows and ConfigMgr" after it reboots it fails with error code 80007002. Pressing F8 reveals that it has no network. After it fails and restart, I can log on to Windows. everything seems OK except that there is no network driver. I can manually load the network driver, the same I use in the driver package, and it installs it just fine.... It's only the 790 that has that problem, the 780 works just fine. Has anyone experienced anything like this?
  22. I've seen a few blogs which have guides to add Remote Control support to Boot Images which I found would be quite useful. Especially if it's in the Boot Image rather than the Task Sequence so I would be able to RDP/VNC/DameWare etc to the client in WinPE. My main goal is for troubleshooting and for support during the build stage. I've seen the following posts but didn't have too much luck with getting it to work: http://www.deploymentresearch.com/Blog/tabid/62/EntryId/36/Software-Assurance-Pays-Off-Remote-Connection-to-WinPE-during-MDT-SCCM-deployments.aspx http://blog.danovich.com.au/2011/12/27/dameware-remote-control-in-winpe/ http://depsharee.blogspot.com.au/2010/06/integrate-vnc-to-windows-pe.html Anyweb - it would be awesome if you could add a Step-by-Step for this topic as I'm sure a lot of admins would benefit from it. Thanks!
  23. Hey, This is the 1st time i post here but I've been a visitor for quite some time, I was wondering if someone here might know something that i couldn't find an answer to over at technet forums, I'm trying to use "unattend.xml" to enable remote control using DART 7 Remote Connection tool during WinPE as demonstrated here: http://www.deploymentresearch.com/Blog/tabid/62/EntryId/36/Software-Assurance-Pays-Off-Remote-Connection-to-WinPE-during-MDT-SCCM-deployments.aspx The "unattend.xml" is residing in the root of the boot.wim - X:\Unattend.xml The first time the machine boots in to WinPE from PXE it uses this Unattend.xml and everything works great. However, if a step to restart the computer to the boot image assigned for the task sequence which is the same boot.wim then after the restart the original "Unattend.xml" will not be used, instead a different xml called "winpeunattend.xml" which is located at "C:\_SMSTaskSequence\WinPE\WinPEUnattend.xml" And that XML is being created "on the fly" or in runtime, when the TS is "Staging boot.wim" and the SMSTS.log will log: "Creating WinPE Answer File" and "Successfully saved ... C:\_SMSTaskSequence\WinPE\WinPEUnattend.xml" The task sequence is from SCCM 2007 R3 with SP2 and the Advertisement is Mandatory and configured as "Access content directly from Distribution Point". Anyone know how can i control this process to use the root located unattend.xml every time when WinPE loads? this is the link for the post on technet forum: http://social.technet.microsoft.com/Forums/en-US/configmgrosd/thread/c3e744a0-c784-46ab-9df1-eae7f8031de5?prof=required any help is much appreciated, Thanks
  24. Hello All! I'm trying to inject NIC drivers for a HP ProBook 6560B, as winpe does not get network access due to no driver I need to inject it so I can do a capture of a reference PC. I mount the .WIM image and use the following command to inject a driver: dism /image:"C:\Temp\mount" /add-driver /driver:"C:\temp\drivers\nic\rt64win7.inf" After doing this I get the following error: C:\Program Files\Windows AIK\Tools\PETools>dism /image:"C:\temp\mount" /add-driv er /driver:"C:\temp\NIC_Driver\E1E6032.inf" Deployment Image Servicing and Management tool Version: 6.1.7600.16385 Image Version: 6.1.7600.16385 Found 1 driver package(s) to install. Installing 1 of 1 - C:\temp\NIC_Driver\E1E6032.inf: Error - An error occurred. T he driver package could not be installed. For more information, check for log files in the <windir>\inf folder of the targ et image. Error: 2 The system cannot find the file specified. The DISM log file can be found at C:\Windows\Logs\DISM\dism.log When I look at the DISM.LOG file I see the following: 2011-09-16 07:23:31, Info DISM DISM.EXE: <----- Starting Dism.exe session -----> 2011-09-16 07:23:31, Info DISM DISM.EXE: 2011-09-16 07:23:31, Info DISM DISM.EXE: Host machine information: OS Version=6.0.6002, Running architecture=x86, Number of processors=2 2011-09-16 07:23:31, Info DISM DISM.EXE: Executing command line: dism /image:"C:\temp\mount" /add-driver /driver:"C:\temp\NIC_Driver\E1E6032.inf" 2011-09-16 07:23:31, Info DISM DISM Provider Store: PID=380 Getting the collection of providers from a local provider store type. - CDISMProviderStore::GetProviderCollection 2011-09-16 07:23:31, Info DISM DISM Provider Store: PID=380 Provider has not previously been encountered. Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider 2011-09-16 07:23:31, Info DISM DISM Provider Store: PID=380 Loading Provider from location C:\Program Files\Windows AIK\Tools\x86\Servicing\WimProvider.dll - CDISMProviderStore::Internal_GetProvider 2011-09-16 07:23:31, Info DISM DISM Provider Store: PID=380 Connecting to the provider located at C:\Program Files\Windows AIK\Tools\x86\Servicing\WimProvider.dll. - CDISMProviderStore::Internal_LoadProvider 2011-09-16 07:23:31, Info DISM DISM Provider Store: PID=380 Provider has not previously been encountered. Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider 2011-09-16 07:23:31, Info DISM DISM Provider Store: PID=380 Loading Provider from location C:\Program Files\Windows AIK\Tools\x86\Servicing\FolderProvider.dll - CDISMProviderStore::Internal_GetProvider 2011-09-16 07:23:31, Info DISM DISM Provider Store: PID=380 Connecting to the provider located at C:\Program Files\Windows AIK\Tools\x86\Servicing\FolderProvider.dll. - CDISMProviderStore::Internal_LoadProvider 2011-09-16 07:23:31, Info DISM DISM Provider Store: PID=380 Provider has not previously been encountered. Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider 2011-09-16 07:23:31, Info DISM DISM Provider Store: PID=380 Loading Provider from location C:\Program Files\Windows AIK\Tools\x86\Servicing\CompatProvider.dll - CDISMProviderStore::Internal_GetProvider 2011-09-16 07:23:31, Info DISM DISM Provider Store: PID=380 Connecting to the provider located at C:\Program Files\Windows AIK\Tools\x86\Servicing\CompatProvider.dll. - CDISMProviderStore::Internal_LoadProvider 2011-09-16 07:23:31, Info DISM DISM.EXE: Got the collection of providers. Now enumerating them to build the command table. 2011-09-16 07:23:31, Info DISM DISM.EXE: Attempting to add the commands from provider: WimManager 2011-09-16 07:23:31, Info DISM DISM.EXE: Succesfully registered commands for the provider: WimManager. 2011-09-16 07:23:31, Info DISM DISM.EXE: Attempting to add the commands from provider: FolderManager 2011-09-16 07:23:31, Info DISM DISM.EXE: Attempting to add the commands from provider: DISM Log Provider 2011-09-16 07:23:31, Info DISM DISM.EXE: Attempting to add the commands from provider: Compatibility Manager 2011-09-16 07:23:31, Info DISM DISM.EXE: Succesfully registered commands for the provider: Compatibility Manager. 2011-09-16 07:23:31, Info DISM DISM Provider Store: PID=380 Getting the collection of providers from a local provider store type. - CDISMProviderStore::GetProviderCollection 2011-09-16 07:23:31, Info DISM DISM Provider Store: PID=380 Getting the collection of providers from a local provider store type. - CDISMProviderStore::GetProviderCollection 2011-09-16 07:23:32, Info DISM DISM Manager: PID=380 Successfully loaded the ImageSession at "C:\Users\TEMPCR~1.005\AppData\Local\Temp\AD2A267E-2130-404B-A462-5A635EF96F50" - CDISMManager::LoadImageSession 2011-09-16 07:23:32, Info DISM DISM Image Session: PID=4980 Instantiating the Provider Store. - CDISMImageSession::get_ProviderStore 2011-09-16 07:23:32, Info DISM DISM Provider Store: PID=4980 Initializing a provider store for the IMAGE session type. - CDISMProviderStore::Final_OnConnect 2011-09-16 07:23:32, Info DISM DISM Provider Store: PID=4980 Provider has not previously been encountered. Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider 2011-09-16 07:23:32, Info DISM DISM Provider Store: PID=4980 Loading Provider from location C:\Users\TEMPCR~1.005\AppData\Local\Temp\AD2A267E-2130-404B-A462-5A635EF96F50\OSProvider.dll - CDISMProviderStore::Internal_GetProvider 2011-09-16 07:23:32, Info DISM DISM Provider Store: PID=4980 Connecting to the provider located at C:\Users\TEMPCR~1.005\AppData\Local\Temp\AD2A267E-2130-404B-A462-5A635EF96F50\OSProvider.dll. - CDISMProviderStore::Internal_LoadProvider 2011-09-16 07:23:32, Info DISM DISM OS Provider: PID=4980 Defaulting SystemPath to C:\temp\mount - CDISMOSServiceManager::Final_OnConnect 2011-09-16 07:23:32, Info DISM DISM OS Provider: PID=4980 Defaulting Windows folder to C:\temp\mount\Windows - CDISMOSServiceManager::Final_OnConnect 2011-09-16 07:23:33, Info DISM DISM Provider Store: PID=4980 Attempting to initialize the logger from the Image Session. - CDISMProviderStore::Final_OnConnect 2011-09-16 07:23:33, Info DISM DISM Provider Store: PID=4980 Provider has not previously been encountered. Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider 2011-09-16 07:23:33, Info DISM DISM Provider Store: PID=4980 Loading Provider from location C:\Users\TEMPCR~1.005\AppData\Local\Temp\AD2A267E-2130-404B-A462-5A635EF96F50\LogProvider.dll - CDISMProviderStore::Internal_GetProvider 2011-09-16 07:23:33, Info DISM DISM Provider Store: PID=4980 Connecting to the provider located at C:\Users\TEMPCR~1.005\AppData\Local\Temp\AD2A267E-2130-404B-A462-5A635EF96F50\LogProvider.dll. - CDISMProviderStore::Internal_LoadProvider 2011-09-16 07:23:33, Info DISM DISM Provider Store: PID=4980 Getting Provider OSServices - CDISMProviderStore::GetProvider 2011-09-16 07:23:33, Info DISM DISM Provider Store: PID=4980 Provider has previously been initialized. Returning the existing instance. - CDISMProviderStore::Internal_GetProvider 2011-09-16 07:23:33, Info DISM DISM Provider Store: PID=4980 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger 2011-09-16 07:23:33, Info DISM DISM Provider Store: PID=4980 Provider has not previously been encountered. Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider 2011-09-16 07:23:33, Info DISM DISM Provider Store: PID=4980 Loading Provider from location C:\Users\TEMPCR~1.005\AppData\Local\Temp\AD2A267E-2130-404B-A462-5A635EF96F50\PEProvider.dll - CDISMProviderStore::Internal_GetProvider 2011-09-16 07:23:33, Info DISM DISM Provider Store: PID=4980 Connecting to the provider located at C:\Users\TEMPCR~1.005\AppData\Local\Temp\AD2A267E-2130-404B-A462-5A635EF96F50\PEProvider.dll. - CDISMProviderStore::Internal_LoadProvider 2011-09-16 07:23:33, Info DISM DISM Provider Store: PID=4980 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider 2011-09-16 07:23:33, Info DISM PE Provider: CPEImg::Attach: Attach requested to offline image 2011-09-16 07:23:33, Info DISM PE Provider: CPEImg::Attach: windir=C:\temp\mount\Windows. 2011-09-16 07:23:33, Info DISM PE Provider: CPEImg::Attach: Attach succeeded. 2011-09-16 07:23:33, Info DISM PE Provider: CPEImg::GetTrimStatus: Image is not trimmed. 2011-09-16 07:23:33, Info DISM PE Provider: CPEImg::GetInstallRoot: Successfully retrieved installroot X:\ 2011-09-16 07:23:33, Info DISM PE Provider: CPEImg::GetInstallRoot: Successfully retrieved installroot X:\ 2011-09-16 07:23:33, Info DISM PE Provider: CPEImg::SetInstallRoot: Old installroot == new installroot; not performing any operation. 2011-09-16 07:23:33, Info DISM DISM Provider Store: PID=4980 Finished initializing the Provider Map. - CDISMProviderStore::Final_OnConnect 2011-09-16 07:23:33, Info DISM DISM Provider Store: PID=4980 Getting Provider DISMLogger - CDISMProviderStore::GetProvider 2011-09-16 07:23:33, Info DISM DISM Provider Store: PID=4980 Provider has previously been initialized. Returning the existing instance. - CDISMProviderStore::Internal_GetProvider 2011-09-16 07:23:33, Info DISM DISM Manager: PID=380 Image session successfully loaded from the temporary location: C:\Users\TEMPCR~1.005\AppData\Local\Temp\AD2A267E-2130-404B-A462-5A635EF96F50 - CDISMManager::CreateImageSession 2011-09-16 07:23:33, Info DISM DISM Provider Store: PID=4980 Getting Provider OSServices - CDISMProviderStore::GetProvider 2011-09-16 07:23:33, Info DISM DISM Provider Store: PID=4980 Provider has previously been initialized. Returning the existing instance. - CDISMProviderStore::Internal_GetProvider 2011-09-16 07:23:33, Info DISM DISM OS Provider: PID=4980 Setting SystemPath to C:\temp\mount - CDISMOSServiceManager::SetSystemPath 2011-09-16 07:23:33, Info CSI 00000001 Shim considered [l:274{137}]"\??\C:\temp\mount\Windows\Servicing\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7600.16385_none_0935b76c289e0fd5\pkgmgr.exe" : got STATUS_OBJECT_PATH_NOT_FOUND 2011-09-16 07:23:33, Info CSI 00000002 Shim considered [l:268{134}]"\??\C:\temp\mount\Windows\WinSxS\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7600.16385_none_0935b76c289e0fd5\pkgmgr.exe" : got STATUS_SUCCESS 2011-09-16 07:23:33, Info DISM DISM.EXE: Target image information: OS Version=6.1.7600.16385, Image architecture=x86 2011-09-16 07:23:33, Info DISM DISM Provider Store: PID=4980 Getting the collection of providers from an image provider store type. - CDISMProviderStore::GetProviderCollection 2011-09-16 07:23:33, Info DISM DISM Provider Store: PID=4980 Provider has not previously been encountered. Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider 2011-09-16 07:23:33, Info DISM DISM Provider Store: PID=4980 Loading Provider from location C:\Users\TEMPCR~1.005\AppData\Local\Temp\AD2A267E-2130-404B-A462-5A635EF96F50\CbsProvider.dll - CDISMProviderStore::Internal_GetProvider 2011-09-16 07:23:33, Info DISM DISM Provider Store: PID=4980 Connecting to the provider located at C:\Users\TEMPCR~1.005\AppData\Local\Temp\AD2A267E-2130-404B-A462-5A635EF96F50\CbsProvider.dll. - CDISMProviderStore::Internal_LoadProvider 2011-09-16 07:23:33, Info DISM DISM Provider Store: PID=4980 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider 2011-09-16 07:23:33, Info CSI 00000001 Shim considered [l:274{137}]"\??\C:\temp\mount\Windows\Servicing\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7600.16385_none_0935b76c289e0fd5\pkgmgr.exe" : got STATUS_OBJECT_PATH_NOT_FOUND 2011-09-16 07:23:33, Info CSI 00000002 Shim considered [l:268{134}]"\??\C:\temp\mount\Windows\WinSxS\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7600.16385_none_0935b76c289e0fd5\pkgmgr.exe" : got STATUS_SUCCESS 2011-09-16 07:23:33, Info DISM DISM Package Manager: PID=4980 Finished initializing the CbsConUI Handler. - CCbsConUIHandler::Initialize 2011-09-16 07:23:33, Info CSI 00000001 Shim considered [l:274{137}]"\??\C:\temp\mount\Windows\Servicing\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7600.16385_none_0935b76c289e0fd5\pkgmgr.exe" : got STATUS_OBJECT_PATH_NOT_FOUND 2011-09-16 07:23:33, Info CSI 00000002 Shim considered [l:268{134}]"\??\C:\temp\mount\Windows\WinSxS\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7600.16385_none_0935b76c289e0fd5\pkgmgr.exe" : got STATUS_SUCCESS 2011-09-16 07:23:33, Info CBS Failed to find a matching version for servicing stack: C:\temp\mount\Windows\WinSxS\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7600.16385_none_0935b76c289e0fd5\ [hrESULT = 0x80070490 - ERROR_NOT_FOUND] 2011-09-16 07:23:33, Info CBS Failed to find servicing stack directory in online store. [hrESULT = 0x80070490 - ERROR_NOT_FOUND] 2011-09-16 07:23:33, Info CBS Must be doing offline servicing, using stack version from: C:\temp\mount\Windows\WinSxS\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7600.16385_none_0935b76c289e0fd5\cbscore.dll 2011-09-16 07:23:33, Info CBS Loaded Servicing Stack v6.1.7600.16385 with Core: C:\temp\mount\Windows\WinSxS\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7600.16385_none_0935b76c289e0fd5\cbscore.dll 2011-09-16 07:23:33, Info CSI 00000001@2011/9/16:13:23:33.391 WcpInitialize (wcp.dll version 0.0.0.6) called (stack @0x5ef4d85e @0x5f3150a4 @0x5f2f1695 @0x5f4a15fd @0x5f4a17c4 @0x5f48331b) 2011-09-16 07:23:33, Info CBS Failed to get proc address for CMP_GetServerSideDeviceInstallFlags [hrESULT = 0x8007007f - ERROR_PROC_NOT_FOUND] 2011-09-16 07:23:33, Info CBS Failed to load CfgMgr32 DLL. [hrESULT = 0x8007007f - ERROR_PROC_NOT_FOUND] 2011-09-16 07:23:33, Info CBS Could not load SrClient DLL from path: SrClient.dll. Continuing without system restore points. 2011-09-16 07:23:33, Info CSI 00000002@2011/9/16:13:23:33.422 WcpInitialize (wcp.dll version 0.0.0.6) called (stack @0x5ef4d85e @0x5f355d11 @0x5f352b9e @0x5f4a15fd @0x5f4a17c4 @0x5f48331b) 2011-09-16 07:23:33, Info DISM DISM Package Manager: PID=4980 Loaded servicing stack for offline use only. - CDISMPackageManager::RefreshInstanceAndLock 2011-09-16 07:23:33, Info CBS Loading offline registry hive: SOFTWARE, into registry key '{bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/temp/mount/Windows/System32/config/SOFTWARE' from path '\\?\C:\temp\mount\Windows\System32\config\SOFTWARE'. 2011-09-16 07:23:33, Info CBS Loading offline registry hive: SYSTEM, into registry key '{bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/temp/mount/Windows/System32/config/SYSTEM' from path '\\?\C:\temp\mount\Windows\System32\config\SYSTEM'. 2011-09-16 07:23:33, Info CBS Loading offline registry hive: SECURITY, into registry key '{bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/temp/mount/Windows/System32/config/SECURITY' from path '\\?\C:\temp\mount\Windows\System32\config\SECURITY'. 2011-09-16 07:23:33, Info CBS Loading offline registry hive: SAM, into registry key '{bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/temp/mount/Windows/System32/config/SAM' from path '\\?\C:\temp\mount\Windows\System32\config\SAM'. 2011-09-16 07:23:33, Info CBS Loading offline registry hive: COMPONENTS, into registry key '{bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/temp/mount/Windows/System32/config/COMPONENTS' from path '\\?\C:\temp\mount\Windows\System32\config\COMPONENTS'. 2011-09-16 07:23:33, Info CBS Loading offline registry hive: DEFAULT, into registry key '{bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/temp/mount/Windows/System32/config/DEFAULT' from path '\\?\C:\temp\mount\Windows\System32\config\DEFAULT'. 2011-09-16 07:23:33, Info CBS Loading offline registry hive: ntuser.dat, into registry key '{bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/temp/mount/Users/default/ntuser.dat' from path '\\?\C:\temp\mount\Users\default\ntuser.dat'. 2011-09-16 07:23:33, Info CBS Loading offline registry hive: schema.dat, into registry key '{bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/temp/mount/Windows/system32/smi/store/Machine/schema.dat' from path '\\?\C:\temp\mount\Windows\system32\smi\store\Machine\schema.dat'. 2011-09-16 07:23:33, Info CBS Offline image is: writeable 2011-09-16 07:23:33, Info CSI 00000003 CSI Store 4317056 (0x0041df80) initialized 2011-09-16 07:23:33, Info CBS Session: 4980_1897913234 initialized by client DISM Package Manager Provider. 2011-09-16 07:23:33, Info DISM DISM Package Manager: PID=4980 Loaded servicing stack for offline use only. - CDISMPackageManager::RefreshInstanceAndLock 2011-09-16 07:23:33, Info DISM DISM Package Manager: PID=4980 Loaded servicing stack for online use only. - CDISMPackageManager::RefreshInstanceAndLock 2011-09-16 07:23:33, Info DISM DISM Provider Store: PID=4980 Provider has not previously been encountered. Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider 2011-09-16 07:23:33, Info DISM DISM Provider Store: PID=4980 Loading Provider from location C:\Users\TEMPCR~1.005\AppData\Local\Temp\AD2A267E-2130-404B-A462-5A635EF96F50\MsiProvider.dll - CDISMProviderStore::Internal_GetProvider 2011-09-16 07:23:33, Warning DISM DISM Provider Store: PID=4980 Failed to Load the provider: C:\Users\TEMPCR~1.005\AppData\Local\Temp\AD2A267E-2130-404B-A462-5A635EF96F50\MsiProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e) 2011-09-16 07:23:33, Info DISM DISM Provider Store: PID=4980 Provider has not previously been encountered. Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider 2011-09-16 07:23:33, Info DISM DISM Provider Store: PID=4980 Loading Provider from location C:\Users\TEMPCR~1.005\AppData\Local\Temp\AD2A267E-2130-404B-A462-5A635EF96F50\IntlProvider.dll - CDISMProviderStore::Internal_GetProvider 2011-09-16 07:23:33, Info DISM DISM Provider Store: PID=4980 Connecting to the provider located at C:\Users\TEMPCR~1.005\AppData\Local\Temp\AD2A267E-2130-404B-A462-5A635EF96F50\IntlProvider.dll. - CDISMProviderStore::Internal_LoadProvider 2011-09-16 07:23:33, Info DISM DISM Provider Store: PID=4980 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider 2011-09-16 07:23:33, Info DISM DISM Provider Store: PID=4980 Provider has not previously been encountered. Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider 2011-09-16 07:23:33, Info DISM DISM Provider Store: PID=4980 Loading Provider from location C:\Users\TEMPCR~1.005\AppData\Local\Temp\AD2A267E-2130-404B-A462-5A635EF96F50\DmiProvider.dll - CDISMProviderStore::Internal_GetProvider 2011-09-16 07:23:33, Info DISM DISM Provider Store: PID=4980 Connecting to the provider located at C:\Users\TEMPCR~1.005\AppData\Local\Temp\AD2A267E-2130-404B-A462-5A635EF96F50\DmiProvider.dll. - CDISMProviderStore::Internal_LoadProvider 2011-09-16 07:23:33, Info DISM DISM Provider Store: PID=4980 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider 2011-09-16 07:23:33, Info CSI 00000001 Shim considered [l:274{137}]"\??\C:\temp\mount\Windows\Servicing\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7600.16385_none_0935b76c289e0fd5\pkgmgr.exe" : got STATUS_OBJECT_PATH_NOT_FOUND 2011-09-16 07:23:33, Info CSI 00000002 Shim considered [l:268{134}]"\??\C:\temp\mount\Windows\WinSxS\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7600.16385_none_0935b76c289e0fd5\pkgmgr.exe" : got STATUS_SUCCESS 2011-09-16 07:23:33, Info DISM DISM OS Provider: PID=4980 Get the registry path to the SOFTWARE hive located at C:\temp\mount\Windows\system32\config\SOFTWARE and determine if it is loaded. - CDISMOSServiceManager::DetermineBootDrive 2011-09-16 07:23:33, Info DISM DISM Driver Manager: PID=4980 Further logs for driver related operations can be found in the target operating system at %WINDIR%\inf\setupapi.offline.log - CDriverManager::Initialize 2011-09-16 07:23:33, Info DISM DISM Provider Store: PID=4980 Provider has not previously been encountered. Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider 2011-09-16 07:23:33, Info DISM DISM Provider Store: PID=4980 Loading Provider from location C:\Users\TEMPCR~1.005\AppData\Local\Temp\AD2A267E-2130-404B-A462-5A635EF96F50\UnattendProvider.dll - CDISMProviderStore::Internal_GetProvider 2011-09-16 07:23:33, Info DISM DISM Provider Store: PID=4980 Connecting to the provider located at C:\Users\TEMPCR~1.005\AppData\Local\Temp\AD2A267E-2130-404B-A462-5A635EF96F50\UnattendProvider.dll. - CDISMProviderStore::Internal_LoadProvider 2011-09-16 07:23:33, Info DISM DISM Provider Store: PID=4980 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider 2011-09-16 07:23:33, Info DISM DISM Provider Store: PID=4980 Provider has not previously been encountered. Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider 2011-09-16 07:23:33, Info DISM DISM Provider Store: PID=4980 Loading Provider from location C:\Users\TEMPCR~1.005\AppData\Local\Temp\AD2A267E-2130-404B-A462-5A635EF96F50\SmiProvider.dll - CDISMProviderStore::Internal_GetProvider 2011-09-16 07:23:33, Info DISM DISM Provider Store: PID=4980 Connecting to the provider located at C:\Users\TEMPCR~1.005\AppData\Local\Temp\AD2A267E-2130-404B-A462-5A635EF96F50\SmiProvider.dll. - CDISMProviderStore::Internal_LoadProvider 2011-09-16 07:23:33, Info DISM DISM Provider Store: PID=4980 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider 2011-09-16 07:23:33, Info DISM DISM Provider Store: PID=4980 Provider has not previously been encountered. Attempting to initialize the provider. - CDISMProviderStore::Internal_GetProvider 2011-09-16 07:23:33, Info DISM DISM Provider Store: PID=4980 Loading Provider from location C:\Users\TEMPCR~1.005\AppData\Local\Temp\AD2A267E-2130-404B-A462-5A635EF96F50\TransmogProvider.dll - CDISMProviderStore::Internal_GetProvider 2011-09-16 07:23:33, Warning DISM DISM Provider Store: PID=4980 Failed to Load the provider: C:\Users\TEMPCR~1.005\AppData\Local\Temp\AD2A267E-2130-404B-A462-5A635EF96F50\TransmogProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e) 2011-09-16 07:23:33, Info DISM DISM.EXE: Got the collection of providers. Now enumerating them to build the command table. 2011-09-16 07:23:33, Info DISM DISM.EXE: Attempting to add the commands from provider: DISM Package Manager 2011-09-16 07:23:33, Info DISM DISM.EXE: Succesfully registered commands for the provider: DISM Package Manager. 2011-09-16 07:23:33, Info DISM DISM.EXE: Attempting to add the commands from provider: OSServices 2011-09-16 07:23:33, Info DISM DISM.EXE: Attempting to add the commands from provider: IntlManager 2011-09-16 07:23:33, Info DISM DISM.EXE: Succesfully registered commands for the provider: IntlManager. 2011-09-16 07:23:33, Info DISM DISM.EXE: Attempting to add the commands from provider: PE Provider 2011-09-16 07:23:33, Info DISM DISM.EXE: Succesfully registered commands for the provider: PE Provider. 2011-09-16 07:23:33, Info DISM DISM.EXE: Attempting to add the commands from provider: DriverManager 2011-09-16 07:23:33, Info DISM DISM.EXE: Succesfully registered commands for the provider: DriverManager. 2011-09-16 07:23:33, Info DISM DISM.EXE: Attempting to add the commands from provider: DISM Unattend Manager 2011-09-16 07:23:33, Info DISM DISM.EXE: Succesfully registered commands for the provider: DISM Unattend Manager. 2011-09-16 07:23:33, Info DISM DISM.EXE: Attempting to add the commands from provider: DISM Log Provider 2011-09-16 07:23:33, Info DISM DISM.EXE: Attempting to add the commands from provider: SmiManager 2011-09-16 07:23:33, Info DISM DISM Provider Store: PID=4980 Getting Provider DriverManager - CDISMProviderStore::GetProvider 2011-09-16 07:23:33, Info DISM DISM Provider Store: PID=4980 Provider has previously been initialized. Returning the existing instance. - CDISMProviderStore::Internal_GetProvider 2011-09-16 07:23:41, Error DISM DISM Driver Manager: PID=4980 Failed to install the driver package 'C:\temp\NIC_Driver\E1E6032.inf'. - CDmiDriverStore::Import(hr:0x80070002) 2011-09-16 07:23:41, Error DISM DISM Driver Manager: PID=4980 Failed to install the driver package 'C:\temp\NIC_Driver\E1E6032.inf'. - CDriverPackage::InternalInstall(hr:0x80070002) 2011-09-16 07:23:41, Error DISM DISM Driver Manager: PID=4980 d:\w7rtm\base\ntsetup\opktools\dism\providers\dmiprovider\dll\driverpackage.cpp:433 - CDriverPackage::Install(hr:0x80070002) 2011-09-16 07:23:41, Info DISM DISM Driver Manager: PID=4980 Driver package C:\temp\NIC_Driver\E1E6032.inf failed to install. (hr:0x80070002). - CDriverManager::AddDriverPackagesFromCollection 2011-09-16 07:23:41, Error DISM DISM Driver Manager: PID=4980 d:\w7rtm\base\ntsetup\opktools\dism\providers\dmiprovider\dll\drivermanager.cpp:1063 - CDriverManager::Internal_DoAddDriverPackage(hr:0x80070002) 2011-09-16 07:23:41, Error DISM DISM Driver Manager: PID=4980 d:\w7rtm\base\ntsetup\opktools\dism\providers\dmiprovider\dll\drivermanager.cpp:519 - CDriverManager::ExecuteCmdLine(hr:0x80070002) 2011-09-16 07:23:41, Info DISM DISM Driver Manager: PID=4980 Further logs for driver related operations can be found in the target operating system at %WINDIR%\inf\setupapi.offline.log - CDriverManager::ExecuteCmdLine 2011-09-16 07:23:41, Error DISM DISM.EXE: DriverManager processed the command line but failed. HRESULT=80070002 2011-09-16 07:23:41, Info DISM DISM Image Session: PID=4980 Disconnecting the provider store - CDISMImageSession::Final_OnDisconnect 2011-09-16 07:23:41, Info DISM DISM Provider Store: PID=4980 Finalizing the servicing provider(DISM Package Manager) - CDISMProviderStore::Internal_DisconnectProvider 2011-09-16 07:23:41, Info CBS Unloading offline registry hive: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/temp/mount/Windows/System32/config/SOFTWARE 2011-09-16 07:23:41, Info CBS Failed to unload offline registry: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/temp/mount/Windows/System32/config/SOFTWARE, the client may still need it open. [hrESULT = 0x80070005 - E_ACCESSDENIED] 2011-09-16 07:23:41, Info CBS Unloading offline registry hive: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/temp/mount/Windows/System32/config/SYSTEM 2011-09-16 07:23:41, Info CBS Failed to unload offline registry: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/temp/mount/Windows/System32/config/SYSTEM, the client may still need it open. [hrESULT = 0x80070005 - E_ACCESSDENIED] 2011-09-16 07:23:41, Info CBS Unloading offline registry hive: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/temp/mount/Windows/System32/config/SECURITY 2011-09-16 07:23:41, Info CBS Failed to unload offline registry: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/temp/mount/Windows/System32/config/SECURITY, the client may still need it open. [hrESULT = 0x80070005 - E_ACCESSDENIED] 2011-09-16 07:23:41, Info CBS Unloading offline registry hive: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/temp/mount/Windows/System32/config/SAM 2011-09-16 07:23:41, Info CBS Failed to unload offline registry: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/temp/mount/Windows/System32/config/SAM, the client may still need it open. [hrESULT = 0x80070005 - E_ACCESSDENIED] 2011-09-16 07:23:41, Info CBS Unloading offline registry hive: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/temp/mount/Windows/System32/config/COMPONENTS 2011-09-16 07:23:41, Info CBS Failed to unload offline registry: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/temp/mount/Windows/System32/config/COMPONENTS, the client may still need it open. [hrESULT = 0x80070005 - E_ACCESSDENIED] 2011-09-16 07:23:41, Info CBS Unloading offline registry hive: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/temp/mount/Windows/System32/config/DEFAULT 2011-09-16 07:23:41, Info CBS Failed to unload offline registry: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/temp/mount/Windows/System32/config/DEFAULT, the client may still need it open. [hrESULT = 0x80070005 - E_ACCESSDENIED] 2011-09-16 07:23:41, Info CBS Unloading offline registry hive: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/temp/mount/Users/default/ntuser.dat 2011-09-16 07:23:41, Info CBS Failed to unload offline registry: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/temp/mount/Users/default/ntuser.dat, the client may still need it open. [hrESULT = 0x80070005 - E_ACCESSDENIED] 2011-09-16 07:23:41, Info CBS Unloading offline registry hive: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/temp/mount/Windows/system32/smi/store/Machine/schema.dat 2011-09-16 07:23:41, Info DISM DISM Package Manager: PID=4980 Finalizing CBS core. - CDISMPackageManager::Finalize 2011-09-16 07:23:41, Info DISM DISM Provider Store: PID=4980 Disconnecting Provider: DISM Package Manager - CDISMProviderStore::Internal_DisconnectProvider 2011-09-16 07:23:41, Info DISM DISM Provider Store: PID=4980 Found the OSServices. Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect 2011-09-16 07:23:41, Info DISM DISM Provider Store: PID=4980 Finalizing the servicing provider(IntlManager) - CDISMProviderStore::Internal_DisconnectProvider 2011-09-16 07:23:41, Info DISM DISM Provider Store: PID=4980 Disconnecting Provider: IntlManager - CDISMProviderStore::Internal_DisconnectProvider 2011-09-16 07:23:41, Info DISM DISM Provider Store: PID=4980 Found the PE Provider. Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect 2011-09-16 07:23:41, Info DISM DISM Provider Store: PID=4980 Finalizing the servicing provider(DriverManager) - CDISMProviderStore::Internal_DisconnectProvider 2011-09-16 07:23:41, Info DISM DISM Provider Store: PID=4980 Disconnecting Provider: DriverManager - CDISMProviderStore::Internal_DisconnectProvider 2011-09-16 07:23:41, Info DISM DISM Provider Store: PID=4980 Finalizing the servicing provider(DISM Unattend Manager) - CDISMProviderStore::Internal_DisconnectProvider 2011-09-16 07:23:41, Info DISM DISM Provider Store: PID=4980 Disconnecting Provider: DISM Unattend Manager - CDISMProviderStore::Internal_DisconnectProvider 2011-09-16 07:23:41, Info DISM DISM Provider Store: PID=4980 Found the OSServices. Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect 2011-09-16 07:23:41, Info DISM DISM Provider Store: PID=4980 Finalizing the servicing provider(SmiManager) - CDISMProviderStore::Internal_DisconnectProvider 2011-09-16 07:23:41, Info DISM DISM Provider Store: PID=4980 Disconnecting Provider: SmiManager - CDISMProviderStore::Internal_DisconnectProvider 2011-09-16 07:23:41, Info DISM DISM Provider Store: PID=4980 Finalizing the servicing provider(PE Provider) - CDISMProviderStore::Internal_DisconnectProvider 2011-09-16 07:23:41, Info DISM PE Provider: CPEImg::GetInstallRoot: Successfully retrieved installroot X:\ 2011-09-16 07:23:41, Info DISM PE Provider: CPEImg::SetInstallRoot: Old installroot == new installroot; not performing any operation. 2011-09-16 07:23:41, Info DISM PE Provider: CPEImg::Detach: Detach succeeded. 2011-09-16 07:23:41, Info DISM DISM Provider Store: PID=4980 Disconnecting Provider: PE Provider - CDISMProviderStore::Internal_DisconnectProvider 2011-09-16 07:23:41, Info DISM DISM Provider Store: PID=4980 Releasing the local reference to OSServices. - CDISMProviderStore::Internal_DisconnectProvider 2011-09-16 07:23:41, Info DISM DISM Provider Store: PID=4980 Disconnecting Provider: OSServices - CDISMProviderStore::Internal_DisconnectProvider 2011-09-16 07:23:41, Info DISM DISM OS Provider: PID=4980 Successfully unloaded all registry hives. - CDISMOSServiceManager::Final_OnDisconnect 2011-09-16 07:23:41, Info DISM DISM Provider Store: PID=4980 Releasing the local reference to DISMLogger. Stop logging. - CDISMProviderStore::Internal_DisconnectProvider 2011-09-16 07:23:41, Info DISM DISM.EXE: Image session has been closed. Reboot required=no. 2011-09-16 07:23:41, Info DISM DISM.EXE: 2011-09-16 07:23:41, Info DISM DISM.EXE: <----- Ending Dism.exe session -----> 2011-09-16 07:23:41, Info DISM DISM.EXE: 2011-09-16 07:23:41, Info DISM DISM Image Session: PID=380 Disconnecting the provider store - CDISMImageSession::Final_OnDisconnect 2011-09-16 07:23:41, Info DISM DISM Provider Store: PID=380 Disconnecting Provider: WimManager - CDISMProviderStore::Internal_DisconnectProvider 2011-09-16 07:23:41, Info DISM DISM Provider Store: PID=380 Disconnecting Provider: FolderManager - CDISMProviderStore::Internal_DisconnectProvider 2011-09-16 07:23:41, Info DISM DISM Provider Store: PID=380 Found the OSServices. Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect 2011-09-16 07:23:41, Info DISM DISM Provider Store: PID=380 Disconnecting Provider: Compatibility Manager - CDISMProviderStore::Internal_DisconnectProvider 2011-09-16 07:23:41, Info DISM DISM Provider Store: PID=380 Releasing the local reference to DISMLogger. Stop logging. - CDISMProviderStore::Internal_DisconnectProvider The following errors I noticed was this: 2011-09-16 07:23:33, Info CBS Failed to find a matching version for servicing stack: C:\temp\mount\Windows\WinSxS\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7600.16385_none_0935b76c289e0fd5\ [hrESULT = 0x80070490 - ERROR_NOT_FOUND] 2011-09-16 07:23:33, Info CBS Failed to find servicing stack directory in online store. [hrESULT = 0x80070490 - ERROR_NOT_FOUND] 2011-09-16 07:23:33, Info CBS Failed to get proc address for CMP_GetServerSideDeviceInstallFlags [hrESULT = 0x8007007f - ERROR_PROC_NOT_FOUND] 2011-09-16 07:23:33, Info CBS Failed to load CfgMgr32 DLL. [hrESULT = 0x8007007f - ERROR_PROC_NOT_FOUND] 2011-09-16 07:23:33, Warning DISM DISM Provider Store: PID=4980 Failed to Load the provider: C:\Users\TEMPCR~1.005\AppData\Local\Temp\AD2A267E-2130-404B-A462-5A635EF96F50\MsiProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e) 2011-09-16 07:23:33, Warning DISM DISM Provider Store: PID=4980 Failed to Load the provider: C:\Users\TEMPCR~1.005\AppData\Local\Temp\AD2A267E-2130-404B-A462-5A635EF96F50\TransmogProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e) 2011-09-16 07:23:41, Error DISM DISM Driver Manager: PID=4980 Failed to install the driver package 'C:\temp\NIC_Driver\E1E6032.inf'. - CDmiDriverStore::Import(hr:0x80070002) 2011-09-16 07:23:41, Error DISM DISM Driver Manager: PID=4980 Failed to install the driver package 'C:\temp\NIC_Driver\E1E6032.inf'. - CDriverPackage::InternalInstall(hr:0x80070002) 2011-09-16 07:23:41, Error DISM DISM Driver Manager: PID=4980 d:\w7rtm\base\ntsetup\opktools\dism\providers\dmiprovider\dll\driverpackage.cpp:433 - CDriverPackage::Install(hr:0x80070002) 2011-09-16 07:23:41, Error DISM DISM Driver Manager: PID=4980 d:\w7rtm\base\ntsetup\opktools\dism\providers\dmiprovider\dll\drivermanager.cpp:1063 - CDriverManager::Internal_DoAddDriverPackage(hr:0x80070002) 2011-09-16 07:23:41, Error DISM DISM Driver Manager: PID=4980 d:\w7rtm\base\ntsetup\opktools\dism\providers\dmiprovider\dll\drivermanager.cpp:519 - CDriverManager::ExecuteCmdLine(hr:0x80070002) 2011-09-16 07:23:41, Error DISM DISM.EXE: DriverManager processed the command line but failed. HRESULT=80070002 I've had luck injecting other drivers but i've read that some Intel NIC drivers have issues being injected into SCCM and WinPE. I'm just unfamiliar with how these logs work to know if something is wrong w/ the Driver or something i'm doing. I've searched online for things and nothing i've researched seems to be like this probelm even the error message I've searched for I don't get really that great results. Any help would be appriciated. Best Regards!
  25. Our company recently approved a new laptop with 2 hard drives as an available standard. When setting it up for OSD we just went thru the normal procedures that we do with all tha approved hardware platforms but we have an issue with how WinPE sees the hard drives. The two hard drives are a smaller one for OS and a bigger one for data. We specified with the manufacture that the smaller drvie is the 1st HDD and the larger is the 2nd. Both are advanced format drives. The OEM install sees the small drive as disk 0, so does DOS, so does Windows, but WinPE sees it as disk 1 and the larger drive as disk 0. Our standard TS specifies Format and Partiion Disk 0 so when we run the TS is formats and parttions the larger drive. If we use the select disk=system command in diskpart it goes to disk 1. Why does WinPE see the disk number different than anything else and do we have to create a new step in the task sequence just for this hardware platform?
×
×
  • Create New...