Announcement

Collapse
No announcement yet.

Deploying Windows 10 Using WDS\MDT

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Deploying Windows 10 Using WDS\MDT

    Hi,

    Im trying to push out Windows 10 images from our WDS using MDT 8443 (also using AIK 10.1.16299)

    I can deploy windows 7 images fine everything works. If I try and deploy a Windows 10 image (vanilla OR custom) using a brand new task sequence it errors trying to apply the unattended.xml - Failure below is the error from LTIApply.log

    <![LOG[Command has been started (process ID 1676)]LOG]!><time="03:33:32.000+000" date="10-27-2017" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[ Console > Target volumes will be updated with BOOTMGR compatible bootcode.]LOG]!><time="03:33:33.000+000" date="10-27-2017" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[ Console > C: (\\?\Volume{d6723c6b-bb09-11e7-958f-782bcb9ce202})]LOG]!><time="03:33:34.000+000" date="10-27-2017" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[ Console > Successfully updated NTFS filesystem bootcode.]LOG]!><time="03:33:34.000+000" date="10-27-2017" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[ Console > Bootcode was successfully updated on all targeted volumes.]LOG]!><time="03:33:34.000+000" date="10-27-2017" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[Return code from command = 0]LOG]!><time="03:33:34.000+000" date="10-27-2017" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[Find the boot drive (if any) [True] [10.0.15063.0] [False]]LOG]!><time="03:33:34.000+000" date="10-27-2017" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[New ZTIDiskPartition : \\MININT-Q21S553\root\cimv2:Win32_DiskPartition.DeviceID="D isk #0, Partition #0" \\MININT-Q21S553\root\cimv2:Win32_LogicalDisk.DeviceID="V:"]LOG]!><time="03:33:34.000+000" date="10-27-2017" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[New ZTIDisk : \\MININT-Q21S553\root\cimv2:Win32_DiskDrive.DeviceID="\\\\. \\PHYSICALDRIVE0"]LOG]!><time="03:33:34.000+000" date="10-27-2017" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[Found bootable drive (No Boot File Test) [ V: ]: \\MININT-Q21S553\root\cimv2:Win32_LogicalDisk.DeviceID="V:"]LOG]!><time="03:33:35.000+000" date="10-27-2017" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[Ready to Prepare boot partition: V:]LOG]!><time="03:33:35.000+000" date="10-27-2017" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[Property UILanguage is now = en-US]LOG]!><time="03:33:35.000+000" date="10-27-2017" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[About to run command: cscript.exe //nologo "\\server\DeploymentShare$\Scripts\ztiRunComma ndHi dden.wsf" ""\\server\DeploymentShare$\Tools\X64\BCDBoot. exe" C:\windows /l en-US /s V:"]LOG]!><time="03:33:35.000+000" date="10-27-2017" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[Command has returned: 0]LOG]!><time="03:33:35.000+000" date="10-27-2017" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[Run Command: X:\WINDOWS\SYSTEM32\bcdedit.exe /Store "V:\boot\bcd" /timeout 0]LOG]!><time="03:33:35.000+000" date="10-27-2017" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[BCD> The operation completed successfully.]LOG]!><time="03:33:36.000+000" date="10-27-2017" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[BCDEdit returned ErrorLevel = 0]LOG]!><time="03:33:36.000+000" date="10-27-2017" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[Created scratch folder.]LOG]!><time="03:33:36.000+000" date="10-27-2017" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[Copy File: C:\MININT\unattend.xml to C:\Windows\Panther\Unattend.xml]LOG]!><time="03:33:36.000+000" date="10-27-2017" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[Copied unattend.xml to C:\Windows\Panther for image apply.]LOG]!><time="03:33:36.000+000" date="10-27-2017" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[About to run command: dism.exe /Image:C:\ /Apply-Unattend:C:\Windows\Panther\Unattend.xml /ScratchDir:C:\MININT\Scratch]LOG]!><time="03:33:36.000+000" date="10-27-2017" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[Command has been started (process ID 1716)]LOG]!><time="03:33:36.000+000" date="10-27-2017" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[ Console > Deployment Image Servicing and Management tool]LOG]!><time="03:33:36.000+000" date="10-27-2017" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[ Console > Version: 6.1.7600.16385]LOG]!><time="03:33:36.000+000" date="10-27-2017" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[ZTI Heartbeat: command has been running for 2 minutes (process ID 1716)]LOG]!><time="03:35:39.000+000" date="10-27-2017" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[ Console > Error: 0xc0000135]LOG]!><time="03:35:39.000+000" date="10-27-2017" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[ Console > An error occurred while attempting to start the servicing process for the image located at C:\. ]LOG]!><time="03:35:39.000+000" date="10-27-2017" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[ Console > For more information, review the log file.]LOG]!><time="03:35:39.000+000" date="10-27-2017" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[ Console > The DISM log file can be found at X:\WINDOWS\Logs\DISM\dism.log]LOG]!><time="03:35:39.000+000" date="10-27-2017" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[Return code from command = -1073741515]LOG]!><time="03:35:40.000+000" date="10-27-2017" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[FAILURE ( 5627 ): -1073741515 0xC0000135: Run DISM.exe]LOG]!><time="03:35:40.000+000" date="10-27-2017" component="LTIApply" context="" type="3" thread="" file="LTIApply">

    I cant seem to see the issue apart from the LTI failure? Which doesn't really tell me a lot.

    I updated from a previous release of MDT to 2013 installing the Win 10 AIK and upgraded the boot images.
    Last edited by 5habbaranks; 27th October 2017, 12:01.

  • #2
    Seems like you ain't the only one have issues. You just may have found another Windows 10 "feature". MDT 8443 Windows 10 Issues
    1 1 was a racehorse.
    2 2 was 1 2.
    1 1 1 1 race 1 day,
    2 2 1 1 2

    Comment


    • #3
      Are you loading the correct drivers?

      Have you updated your boot images?

      Comment


      • #4
        Hey,

        The only drivers Im loading are the NIC drivers and yep all boot images have been updated.

        With W10 you have to use specific images with AIK - any ideas where you download the different images from (we're not using volume licensing) I would assume the windows media tool would download the latest release - but that's a guess...

        Feel a bit of an idiot but hey ho - I forgot to add the w10 lite touch boot to WDS, all works now
        Last edited by 5habbaranks; 30th October 2017, 12:55.

        Comment


        • #5
          Originally posted by 5habbaranks
          Feel a bit of an idiot but hey ho -
          Don't feel bad, I was looking at a mapped drive on a Server that was mapped to a SHARE on the Server and I was sitting there wondering how the hell they did that. No clues in GPO. Imagine how stupid I felt when it clicked in the cavernous gap between my ears how it was done. Done it hundreds if not thousands of times and had drawn a really big blank. I guess the Older Age Club does that.
          1 1 was a racehorse.
          2 2 was 1 2.
          1 1 1 1 race 1 day,
          2 2 1 1 2

          Comment


          • #6
            That's the thing, I think sometimes your expected to know everything about everything and retain that info.... I struggle so I keep cheat sheets or good old Google

            Comment


            • #7
              Originally posted by 5habbaranks View Post
              Hey,

              The only drivers Im loading are the NIC drivers and yep all boot images have been updated.

              With W10 you have to use specific images with AIK - any ideas where you download the different images from (we're not using volume licensing) I would assume the windows media tool would download the latest release - but that's a guess...

              Feel a bit of an idiot but hey ho - I forgot to add the w10 lite touch boot to WDS, all works now
              Why are you only loading the NIC drivers?

              Erm no that's incorrect. I've used multiple different versions of Windows 10, using the media creation tool as well as the volume licencing ISO files. Do you have some documentation to backup this statement?

              Just an FYI once you update the boot images using the latest version of WinPE in the ADK it will boot most systems.

              Comment


              • #8
                Originally posted by wullieb1 View Post

                Why are you only loading the NIC drivers?

                All I need to do is boot the image - once the image is loaded I manually install the latest drivers. I know I can inject them into the image but its not something Ive got around to yet

                Erm no that's incorrect. I've used multiple different versions of Windows 10, using the media creation tool as well as the volume licencing ISO files. Do you have some documentation to backup this statement? - if you look at the link it states that you should use win 10 1703 with adk 1703 etc

                Just an FYI once you update the boot images using the latest version of WinPE in the ADK it will boot most systems - this is the step I missed. Once sorted deployment worked a treat

                Comment


                • #9
                  Also (not sure if this requires a separate post) how do you stop those bleeping apps from installing themselves. I removed them from the image AND I thought I removed them from any new user profiles being created but they keep coming back - candy crush, minecraft etc?

                  Comment


                  • #10
                    Not sure what the first link is supposed to do. I know where to get the ADK and how to install it, i have done so numerous times, and that link doesn't really give me any information that i need to have that pertains to this issue. In fact i'm just spooling up a home environment now so i can test that the installation files work as i would expect them too.

                    WHy are you removeing the inbuilt apps? I have read of issues with the removal.

                    How are you removing them? https://gallery.technet.microsoft.co...ew/Discussions

                    IMHO leave the apps as is as there are dependencies built in that require these, i'm trying now to find links but when i had a few courses at ignite this was the general consensus. If you really want to have them removed then use this powershell script to remove

                    https://gallery.technet.microsoft.co...ew/Discussions

                    Comment


                    • #11
                      I'm only referring to the mention of the ADK version must match the Win10 version (in my link) not patronising on how to install it.

                      Why am I removing the inbuilt apps such as Candy Crush, Facebook Minecraft etc - I would be surprised if any business thought it to be a good practice to leave this rubbish on their builds. The problems arise when you start to remove the store which I don't plan on doing, just disabling it within GPO.

                      Also we're using professional rather than enterprise so my hands are tied (Professional contains an esd which has various builds of W10 in it Enterprise has a wim).

                      As said please don't feel that I'm patronising you, my W10 frustrations seem to be quite common looking around the net

                      Comment


                      • #12
                        Ahh ok. It doesn't need to match the build but you will run into issues if it doesn't so yeah keep it at the same level or above

                        Don't remove the store. As you mention disable it and remove the stupid taskbar shortcut. There are other apps that you shouldn't remove as they are dependencies for things.

                        We use professional here so please don't feel like your alone. FYI the professional installs that i have used have all been WIM based but if you need to convert it is generally pretty simple. Have a read though here as its done better than i could https://community.spiceworks.com/how...nge-esd-to-wim

                        Comment


                        • #13
                          Yeah I did that to extract the WIM and deployed it to initiate my build, as far as the build goes Im happy with it just needs a little tweeking al la facebook and minecraft. I still think M$ need to rethink their strategy with regards to what they are trying to achieve. Keep consumer ideas away from business\enterprise products and people will be happy

                          Comment


                          • #14
                            Facebook and MineCraft should be easy enough to remove.

                            Code:
                            get-appxpackage | Select name
                            Will give you a list of all the installed packages.

                            Then
                            Code:
                            remove-appxpackage
                            and the name will remove it.

                            *** EDIT ***

                            Before i forget i don't actually think these apps are installed on a default Windows build, i will need to check this however. You may find that it is just a tile which is easily remedied.

                            Candy Crush et all is installed and can be removed.

                            Last edited by wullieb1; 2nd November 2017, 12:43.

                            Comment


                            • #15
                              The problem is I removed them (from the image) and they came back

                              Seems a possible solution is powershell script on boot\login - we shall see. Shouldn't have to go through all these hoops though

                              Comment

                              Working...
                              X