Jump to content


pk@ianz

Established Members
 View Profile  See their activity

  • Posts

    7

  • Joined

  • Last visited

 Content Type 

Posts posted by pk@ianz

  1. Drivers not installing during TS deployment

    in Configuration Manager 2012

    Posted

    Hi. I have an issue where the audio drivers are not getting installed during the deployment for Surface Pro 4. I am using MDT for deployments. Below is the ZTI drivers log.

     

        Found Device HDAUDIO\FUNC_01&VEN_8086&DEV_2809&SUBSYS_80860101 with 3rd party drivers! Count = 1  = {a0802322-6c56-4368-89f4-2e487bda60b1}    {b79f53cd-012b-4f25-8f1f-98cfc43a5dfc}    ZTIDrivers    23/09/2017 8:55:40 a.m.    0 (0x0000)
    Found a driver for HDAUDIO\FUNC_01&VEN_8086&DEV_2809&SUBSYS_80860101: {a0802322-6c56-4368-89f4-2e487bda60b1} from \\WDS\UDSept2017$\Out-of-box Drivers\MEDIA\IntcDAud_6.16.00.3197_01C43A3A030C13CEF997CB2AF7E91D687013A484\IntcDAud.inf    ZTIDrivers    23/09/2017 8:55:40 a.m.    0 (0x0000)
    Validating connection to \\WDS\UDSept2017$\Out-of-box Drivers\MEDIA\IntcDAud_6.16.00.3197_01C43A3A030C13CEF997CB2AF7E91D687013A484    ZTIDrivers    23/09/2017 8:55:40 a.m.    0 (0x0000)
    Mapping server share: \\WDS\UDSept2017$    ZTIDrivers    23/09/2017 8:55:40 a.m.    0 (0x0000)
    Already connected to server WDS as that is where this script is running from.    ZTIDrivers    23/09/2017 8:55:40 a.m.    0 (0x0000)
    Copying drivers from "\\WDS\UDSept2017$\Out-of-box Drivers\MEDIA\IntcDAud_6.16.00.3197_01C43A3A030C13CEF997CB2AF7E91D687013A484" to "D:\Drivers\MEDIA\IntcDAud_6.16.00.3197_01C43A3A030C13CEF997CB2AF7E91D687013A484"    ZTIDrivers    23/09/2017 8:55:40 a.m.    0 (0x0000)
    About to run command: cmd.exe /c xcopy /seihycd "\\WDS\UDSept2017$\Out-of-box Drivers\MEDIA\IntcDAud_6.16.00.3197_01C43A3A030C13CEF997CB2AF7E91D687013A484" "D:\Drivers\MEDIA\IntcDAud_6.16.00.3197_01C43A3A030C13CEF997CB2AF7E91D687013A484" 1> NUL 2>NUL    ZTIDrivers    23/09/2017 8:55:40 a.m.    0 (0x0000)
    Command has been started (process ID 2728)    ZTIDrivers    23/09/2017 8:55:40 a.m.    0 (0x0000)
    Return code from command = 0    ZTIDrivers    23/09/2017 8:55:41 a.m.    0 (0x0000)
    Found a driver for HDAUDIO\FUNC_01&VEN_8086&DEV_2809&SUBSYS_80860101: {b79f53cd-012b-4f25-8f1f-98cfc43a5dfc} from \\WDS\UDSept2017$\Out-of-box Drivers\MEDIA\IntcDAud_8.20.00.922_873C24BAA5D9C4A29EC79A93511F80F7BF0C9763\IntcDAud.inf    ZTIDrivers    23/09/2017 8:55:41 a.m.    0 (0x0000)
    Validating connection to \\WDS\UDSept2017$\Out-of-box Drivers\MEDIA\IntcDAud_8.20.00.922_873C24BAA5D9C4A29EC79A93511F80F7BF0C9763    ZTIDrivers    23/09/2017 8:55:41 a.m.    0 (0x0000)
    Mapping server share: \\WDS\UDSept2017$    ZTIDrivers    23/09/2017 8:55:41 a.m.    0 (0x0000)
    Already connected to server WDS as that is where this script is running from.    ZTIDrivers    23/09/2017 8:55:41 a.m.    0 (0x0000)
    Copying drivers from "\\WDS\UDSept2017$\Out-of-box Drivers\MEDIA\IntcDAud_8.20.00.922_873C24BAA5D9C4A29EC79A93511F80F7BF0C9763" to "D:\Drivers\MEDIA\IntcDAud_8.20.00.922_873C24BAA5D9C4A29EC79A93511F80F7BF0C9763"    ZTIDrivers    23/09/2017 8:55:41 a.m.    0 (0x0000)
    About to run command: cmd.exe /c xcopy /seihycd "\\WDS\UDSept2017$\Out-of-box Drivers\MEDIA\IntcDAud_8.20.00.922_873C24BAA5D9C4A29EC79A93511F80F7BF0C9763" "D:\Drivers\MEDIA\IntcDAud_8.20.00.922_873C24BAA5D9C4A29EC79A93511F80F7BF0C9763" 1> NUL 2>NUL    ZTIDrivers    23/09/2017 8:55:41 a.m.    0 (0x0000)
    Command has been started (process ID 2760)    ZTIDrivers    23/09/2017 8:55:41 a.m.    0 (0x0000)
    Return code from command = 0    ZTIDrivers    23/09/2017 8:55:42 a.m.    0 (0x0000)
        Found Device HDAUDIO\FUNC_01&VEN_8086&DEV_2809 with 3rd party drivers! Count = 1  = {a0802322-6c56-4368-89f4-2e487bda60b1}    {b79f53cd-012b-4f25-8f1f-98cfc43a5dfc}    ZTIDrivers    23/09/2017 8:55:42 a.m.    0 (0x0000)
    Found a driver for HDAUDIO\FUNC_01&VEN_8086&DEV_2809: {a0802322-6c56-4368-89f4-2e487bda60b1} from \\WDS\UDSept2017$\Out-of-box Drivers\MEDIA\IntcDAud_6.16.00.3197_01C43A3A030C13CEF997CB2AF7E91D687013A484\IntcDAud.inf    ZTIDrivers    23/09/2017 8:55:42 a.m.    0 (0x0000)
    Validating connection to \\WDS\UDSept2017$\Out-of-box Drivers\MEDIA\IntcDAud_6.16.00.3197_01C43A3A030C13CEF997CB2AF7E91D687013A484    ZTIDrivers    23/09/2017 8:55:42 a.m.    0 (0x0000)
    Mapping server share: \\WDS\UDSept2017$    ZTIDrivers    23/09/2017 8:55:42 a.m.    0 (0x0000)
    Already connected to server WDS as that is where this script is running from.    ZTIDrivers    23/09/2017 8:55:42 a.m.    0 (0x0000)
    Copying drivers from "\\WDS\UDSept2017$\Out-of-box Drivers\MEDIA\IntcDAud_6.16.00.3197_01C43A3A030C13CEF997CB2AF7E91D687013A484" to "D:\Drivers\MEDIA\IntcDAud_6.16.00.3197_01C43A3A030C13CEF997CB2AF7E91D687013A484"    ZTIDrivers    23/09/2017 8:55:42 a.m.    0 (0x0000)
    About to run command: cmd.exe /c xcopy /seihycd "\\WDS\UDSept2017$\Out-of-box Drivers\MEDIA\IntcDAud_6.16.00.3197_01C43A3A030C13CEF997CB2AF7E91D687013A484" "D:\Drivers\MEDIA\IntcDAud_6.16.00.3197_01C43A3A030C13CEF997CB2AF7E91D687013A484" 1> NUL 2>NUL    ZTIDrivers    23/09/2017 8:55:42 a.m.    0 (0x0000)
    Command has been started (process ID 2796)    ZTIDrivers    23/09/2017 8:55:42 a.m.    0 (0x0000)
    Return code from command = 0    ZTIDrivers    23/09/2017 8:55:43 a.m.    0 (0x0000)
    Found a driver for HDAUDIO\FUNC_01&VEN_8086&DEV_2809: {b79f53cd-012b-4f25-8f1f-98cfc43a5dfc} from \\WDS\UDSept2017$\Out-of-box Drivers\MEDIA\IntcDAud_8.20.00.922_873C24BAA5D9C4A29EC79A93511F80F7BF0C9763\IntcDAud.inf    ZTIDrivers    23/09/2017 8:55:43 a.m.    0 (0x0000)
    Validating connection to \\WDS\UDSept2017$\Out-of-box Drivers\MEDIA\IntcDAud_8.20.00.922_873C24BAA5D9C4A29EC79A93511F80F7BF0C9763    ZTIDrivers    23/09/2017 8:55:43 a.m.    0 (0x0000)
    Mapping server share: \\WDS\UDSept2017$    ZTIDrivers    23/09/2017 8:55:43 a.m.    0 (0x0000)
    Already connected to server WDS as that is where this script is running from.    ZTIDrivers    23/09/2017 8:55:43 a.m.    0 (0x0000)
    Copying drivers from "\\WDS\UDSept2017$\Out-of-box Drivers\MEDIA\IntcDAud_8.20.00.922_873C24BAA5D9C4A29EC79A93511F80F7BF0C9763" to "D:\Drivers\MEDIA\IntcDAud_8.20.00.922_873C24BAA5D9C4A29EC79A93511F80F7BF0C9763"    ZTIDrivers    23/09/2017 8:55:43 a.m.    0 (0x0000)
    About to run command: cmd.exe /c xcopy /seihycd "\\WDS\UDSept2017$\Out-of-box Drivers\MEDIA\IntcDAud_8.20.00.922_873C24BAA5D9C4A29EC79A93511F80F7BF0C9763" "D:\Drivers\MEDIA\IntcDAud_8.20.00.922_873C24BAA5D9C4A29EC79A93511F80F7BF0C9763" 1> NUL 2>NUL    ZTIDrivers    23/09/2017 8:55:43 a.m.    0 (0x0000)
    Command has been started (process ID 2828)    ZTIDrivers    23/09/2017 8:55:43 a.m.    0 (0x0000)
     

  2. MDT Win 10 Deployment using OEM product key

    in Microsoft Deployment Toolkit (MDT)

    Posted

    Hi. I can deploy Windows 10 via MDT. How i can automate the OEM product key activation ? I understand the below powershell script can get the key from the BIOS. Where in the task sequence should I run this script ? Thanks.

    $ProductKey = (Get-WmiObject -Class SoftwareLicensingService).OA3xOriginalProductKey
    iex "cscript /b C:\Windows\System32\slmgr.vbs -ipk $Productkey"
    Start-Sleep 5
    iex "cscript /b C:\Windows\System32\slmgr.vbs -ato"

  3. How can I deploy Windows 10 x64 to the Microsoft Surface Pro 4 using MDT 2013 Update 1

    in Microsoft Deployment Toolkit (MDT)

    Posted

    Hi Niall,

     

    I am tryign to deploy an captured OS image to SP4 via MDT 2013 (Update 1). I am getting the below error:

     

    FAILURE ( 5624 ): 1392: Run DISM: /Apply-Image /ImageFile:"\\WDS\SP4Sept2016$\Operating Systems\WIN10Ver1607x64\WIN10Ver1607x64.wim" /Index:1 /ApplyDir:E: LTIApply 28/09/2016 2:06:04 p.m. 0 (0x0000)
    Event 41002 sent: FAILURE ( 5624 ): 1392: Run DISM: /Apply-Image /ImageFile:"    \\WDS\SP4Sept2016$\Operating Systems\WIN10Ver1607x64\WIN10Ver1607x64.wim" /Index:1 /ApplyDir:E: LTIApply 28/09/2016 2:06:04 p.m. 0 (0x0000)
    Command completed, return code = -2147467259 LiteTouch 28/09/2016 2:06:05 p.m. 0 (0x0000)
    Litetouch deployment failed, Return Code = -2147467259 0x80004005 LiteTouch 28/09/2016 2:06:05 p.m. 0 (0x0000)
    Event 41014 sent: Litetouch deployment failed, Return Code = -2147467259 0x80004005 LiteTouch 28/09/2016 2:06:05 p.m. 0 (0x0000)

     

    I can deploy Surface Pro 3 without any issues but only get the above error for Surface Pro 4. Any idea ?

     

  4. How can I deploy Windows 8.1 x64 to the Microsoft Surface Pro 3 using MDT 2013 ?

    in Microsoft Deployment Toolkit (MDT)

    Posted

    I found out the issue. I was not injecting the ethernet drivers and that was causing the deployment to fail. Although the surface was connected to wi-fi and I was able to access the deployment share but the deployment process needed Ethernet connection to go forward.

     

    The error message regarding the invalid credentials is a bit misleading. But it's all sorted now. Thanks.

  5. How can I deploy Windows 8.1 x64 to the Microsoft Surface Pro 3 using MDT 2013 ?

    in Microsoft Deployment Toolkit (MDT)

    Posted

    Hi Niall,

     

    I used the IP address this time but I got the same error.

     

    Here is how the BootStrap.ini looks like.

     

    [settings]
    Priority=Default

    [Default]
    DeployRoot=\\192.168.1.232\MDTDeploy$
    UserID=MDT
    UserDomain=192.168.1.232
    UserPassword=********

     

    The surface is getting a valid IP address from the DHCP server. Are there logs stored somewhere which can shed some light regarding this issue ?

  7. How can I deploy Windows 8.1 x64 to the Microsoft Surface Pro 3 using MDT 2013 ?

    in Microsoft Deployment Toolkit (MDT)

    Posted

    Hi Niall,

     

    My Surface Pro deployment does not finish and I get the below error:

     

    "A connection to the deployment share (\\192.168.1.***\MDTDEploy$) could not be made. Connection OK. Possible cause invalid credentials."

     

    My Bootstrap.ini looks like this. I am using a local admin account on the deployment server.

     

    [settings]
    Priority=Default

    [Default]
    DeployRoot=\\192.168.1.***\MDTDeploy$
    UserID=MDT
    UserDomain=WDS
    UserPassword=******

     

    I have tried a local admin account, a domin account in bootstrap.ini but everytime I get the same error. The deploy share has the appropriate permissions for the local user and domain user account.

     

    The server is Windows 2012 R2 Datacenter. It has the WDS role installed. This server is in part of our domain.

     

    Any ideas ? Thanks.

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.