Quantcast
Channel: Microsoft Deployment Toolkit forum
Viewing all 11297 articles
Browse latest View live

MDT 2012: Force MININT and _SMSTaskSequence on C Drive

$
0
0
Hi,

I'm deploying Windows 7 X64 using MDT 2012, I format 3 partitions at the beginning of the task sequence and I assign them specific drive letters during the state restore phase.
I had no problem with MDT 2010 but since I'm using MDT 2012 MININT and _SMSTaskSequence folders are created on partition 2 so when I assign my drive letters deployment fails.
I tried to force SMSTSLocalDataDrive in cs.ini but it seems that MDT doesn't care, I can see in the variables.dat that the C drive is selected but folders are still in my second partition.
Any help?

My Blog: DeployXP [Under Construction]| Viadeo:Mathieu Ait Azzouzene | Linkedin:Mathieu Ait Azzouzene



How to Rename username n users folder name default set "Administrator"

$
0
0

How to Rename username n users folder name default set "Administrator"..

i trying use wmic command line .. but only rename username.. folder users still administrator.. how to change it ... thanks

MDT8456 Comes up to Task Sequence Wizard instead of continuing

$
0
0

We just updated MDT to 8456 and updated our ADK to support Windows 10 1809. I created a custom wim using MDT and everything went through without error. I imported it into our production deployment share and created a task sequence based off that image. When running the task sequence, it applies the image, but when Windows sets itself up and logs into the administrator account, the task sequence does not continue. Instead, it just brings up the task sequence wizard. If you click through, it picks up where it left off, and continues the task sequence. You can also manually reboot the computer and get the existing deployment message, and it continues without error if you select to not start a new deployment. The odd thing is, this behavior does not happen with our deployment share that we use to create our custom wims.

Configure MDT and WDS to install different version of windows 10

$
0
0

I am having a difficult time configuring MDT and WDS to boot two different versions of windows. What I want to do is whenever a device PXE boots is to offer two options one for windows 10 1803 and one for windows 10 1809. 

What are the best options to accomplish this? 

Modify MDT wizard to automate computer naming

$
0
0
Situation:

I am imaging new systems using MDT Lite-Touch. I am trying to customize the wizard to automate the naming of new systems so that they include a prefix "AG-", a department code which is selected from a drop-down box in the wizard page (eg. "COMM"), and finally the serial number of the computer being imaged, so that my result in this case would be "AG-COMM-1234567"

Status:

I have banged away at this for a while but my Google searches have not turned up answers, my trial-and-error is not producing useful error messages and I think I am missing some fundamentals of how to get variables from the wizard page into the variables used by the lite-touch wizard.

Progress:

1. I first created the HTML page which I will include below and added a script to the page to concatenate the pieces into a variable called OSDComputername which, for testing, I could output in a msgbox and get to display correctly.

* The problem with this is I don't know how to trigger the script then assign it to the OSDComputername variable that is used throughout the rest of the Light-Touch process.
2. I changed the script to a function and added it to DeployWiz_Initization.vbs then used the Initialization field in WDS to call it. I'll include the function below.


* The problem with this is I would get "Undefined Variable" for OSDComputername and I am not sure it is pulling the data from the HTML correctly.

3 . I tried adding variables to "Properties=" (eg.DepartmentName) in the customsettings.ini, pulling thier value from the HTML Form and setting that value to the variable in my function in DeployWiz_Initization.vbs and calling them after "OSDComputername=" in the fashion "OSDComputername="AG-" & %DepartmentName%" in customsettings.ini

* This resulted in errors from my script which did not correctly access the new variables

4. I now have my code working. It is pulling the data from the HTML and setting the OSDComputername environment variable. I have updated the code below to match the working code. It is firing correctly and setting my computer name and description exactly as I wanted it to.

* Issue Resolved!

The HTML page:

<H1>Configure the computer name.</H1>
<p>Please answer the following questions.  Your answers will be used to formulate the computer's name and description.</p>

<FORM NAME="SetComputerNameForm">
    <p>
        <LABEL class="Larger"><u class="Larger">D</u>epartmental Prefix:</LABEL><br />
        <SELECT NAME="DepartmentalPrefix_Edit" ID="DepartmentalPrefix_Edit" language=vbscript onpropertychange=ValidateSetComputerName AccessKey=D>
            <option value="FOO">FOO</option>
            <option value="DOE">DOE</option>                
        </SELECT>
    </p>

    <p>
        <LABEL class="Larger"><u class="Larger">C</u>lient's ID:</LABEL>
        <br />
        <INPUT NAME="ClientID" ID="ClientID" TYPE="text" ID="ClientID" SIZE="15" language=vbscript onpropertychange=ValidateSetComputerName AccessKey=C />
        <label class=ErrMsg for=ClientID>* Required (MISSING)</label>


    </p>

    <p>
        <LABEL class="Larger"><u class="Larger">B</u>uilding:</LABEL><br />
        <SELECT NAME="Building_Edit" ID="Building_Edit" language=vbscript onpropertychange=ValidateSetComputerName  AccessKey=B>
                <option value="ASA">ASA</option>
                <option value="ASB">ASB</option>
        </SELECT>
    </p>

    <p>         
        <LABEL class="Larger"><u class="Larger">R</u>oom Number:</span></LABEL>
        <br />
        <INPUT NAME="RoomNumber" ID="RoomNumber" TYPE="text" ID="RoomNumber" size="15" language=vbscript onpropertychange=ValidateSetComputerName AccessKey=R>
        <label class=ErrMsg for=RoomNumber>* Required (MISSING)</label>
    </p>

</FORM>

The Function:

Function ValidateSetComputerName
    ParseAllWarningLabels

    If Len(Document.SetComputerNameForm.ClientNetID.Value) < 1 OR Len(Document.SetComputerNameForm.RoomNumber.Value) < 1 THEN
        ButtonNext.disabled = true
    Else
        Dim Department
        Dim SerialNumber
        Dim CID
        Dim RoomNumber
        Dim BuildingName
        Dim Make
        Dim Model
        Department = Document.SetComputerNameForm.DepartmentalPrefix_Edit.Value
        SerialNumber = oEnvironment.Item("SerialNumber")
        CID = Document.SetComputerNameForm.ClientID.Value
        RoomNumber = Document.SetComputerNameForm.RoomNumber.Value
        BuildingName = Document.SetComputerNameForm.Building_Edit.Value
        Make = oEnvironment.Item("Make")
        Model = oEnvironment.Item("Model")

        oEnvironment.Item("OSDComputerName") = "AG-" & Department & "-" & Right(SerialNumber,7)
        oEnvironment.Item("ComputerDescription") = Department & ", " & CID & ", " & RoomNumber & " " & BuildingName & ", " & Make & " " & Model
        ButtonNext.disabled = false
    End If

End Function

Time in step Applying image

$
0
0

Hello everyone,

I'm starting with MDT and I think I have a problem, the deployments take 1 hour. Only the process of applying image lasts 35 minutes. The equipment is a newly purchased HP Elitebook 850 G5.

I dont have WDS yet, I boot from usb with winpe and I take the image of network or the own usb, in both cases it takes similar.

The .wim image has only 7 Gb.

Can someone who uses MDT tell me if these times are normal?

Thank you!!!

Command has been started (process ID 2268)LTIApply15/02/2019 13:22:370 (0x0000)
ZTI Heartbeat: command has been running for 0 minutes (process ID 2268)LTIApply15/02/2019 13:22:370 (0x0000)
Event 41003 sent: ZTI Heartbeat: command has been running for 0 minutes (process ID 2268)LTIApply15/02/2019 13:22:370 (0x0000)
  Console > Deployment Image Servicing and Management toolLTIApply15/02/2019 13:22:370 (0x0000)
  Console > Version: 10.0.17134.1LTIApply15/02/2019 13:22:370 (0x0000)
  Console > Applying imageLTIApply15/02/2019 13:22:570 (0x0000)
  Console > 
[                           1.0%                           ]LTIApply 15/02/2019 13:22:570 (0x0000)
  Console > 
[=                          2.0%                           ]LTIApply 15/02/2019 13:23:430 (0x0000)
  Console > 
[=                          3.0%                           ]LTIApply 15/02/2019 13:24:040 (0x0000)
  Console > 
[==                         4.0%                           ]LTIApply 15/02/2019 13:24:260 (0x0000)
  Console > 
[==                         5.0%                           ]LTIApply 15/02/2019 13:24:440 (0x0000)
  Console > 
[===                        6.0%                           ]LTIApply 15/02/2019 13:24:580 (0x0000)
  Console > 
[====                       7.0%                           ]LTIApply 15/02/2019 13:25:150 (0x0000)
  Console > 
[====                       8.0%                           ]LTIApply 15/02/2019 13:25:260 (0x0000)
  Console > 
[=====                      9.0%                           ]LTIApply 15/02/2019 13:25:390 (0x0000)
  Console > 
[=====                      10.0%                          ]LTIApply 15/02/2019 13:25:520 (0x0000)
  Console > 
[======                     11.0%                          ]LTIApply 15/02/2019 13:26:040 (0x0000)
  Console > 
[======                     12.0%                          ]LTIApply 15/02/2019 13:26:150 (0x0000)
  Console > 
[=======                    13.0%                          ]LTIApply 15/02/2019 13:26:300 (0x0000)
  Console > 
[========                   14.0%                          ]LTIApply 15/02/2019 13:26:410 (0x0000)
  Console > 
[========                   15.0%                          ]LTIApply 15/02/2019 13:27:040 (0x0000)
ZTI Heartbeat: command has been running for 5 minutes (process ID 2268)LTIApply15/02/2019 13:27:040 (0x0000)
Event 41003 sent: ZTI Heartbeat: command has been running for 5 minutes (process ID 2268)LTIApply15/02/2019 13:27:040 (0x0000)
  Console > 
[=========                  16.0%                          ]LTIApply 15/02/2019 13:27:330 (0x0000)
  Console > 
[=========                  17.0%                          ]LTIApply 15/02/2019 13:27:590 (0x0000)
  Console > 
[==========                 18.0%                          ]LTIApply 15/02/2019 13:28:240 (0x0000)
  Console > 
[===========                19.0%                          ]LTIApply 15/02/2019 13:29:020 (0x0000)
  Console > 
[===========                20.0%                          ]LTIApply 15/02/2019 13:29:320 (0x0000)
  Console > 
[============               21.0%                          ]LTIApply 15/02/2019 13:30:080 (0x0000)
  Console > 
[============               22.0%                          ]LTIApply 15/02/2019 13:30:310 (0x0000)
  Console > 
[=============              23.0%                          ]LTIApply 15/02/2019 13:30:590 (0x0000)
  Console > 
[=============              24.0%                          ]LTIApply 15/02/2019 13:31:250 (0x0000)
  Console > 
[==============             25.0%                          ]LTIApply 15/02/2019 13:31:450 (0x0000)
  Console > 
[===============            26.0%                          ]LTIApply 15/02/2019 13:32:120 (0x0000)
ZTI Heartbeat: command has been running for 10 minutes (process ID 2268)LTIApply15/02/2019 13:32:120 (0x0000)
Event 41003 sent: ZTI Heartbeat: command has been running for 10 minutes (process ID 2268)LTIApply15/02/2019 13:32:120 (0x0000)
  Console > 
[===============            27.0%                          ]LTIApply 15/02/2019 13:32:420 (0x0000)
  Console > 
[================           28.0%                          ]LTIApply 15/02/2019 13:33:100 (0x0000)
  Console > 
[================           29.0%                          ]LTIApply 15/02/2019 13:33:360 (0x0000)
  Console > 
[=================          30.0%                          ]LTIApply 15/02/2019 13:33:530 (0x0000)
  Console > 
[=================          31.0%                          ]LTIApply 15/02/2019 13:34:160 (0x0000)
  Console > 
[==================         32.0%                          ]LTIApply 15/02/2019 13:34:430 (0x0000)
  Console > 
[===================        33.0%                          ]LTIApply 15/02/2019 13:35:200 (0x0000)
  Console > 
[===================        34.0%                          ]LTIApply 15/02/2019 13:35:360 (0x0000)
  Console > 
[====================       35.0%                          ]LTIApply 15/02/2019 13:36:080 (0x0000)
  Console > 
[====================       36.0%                          ]LTIApply 15/02/2019 13:36:270 (0x0000)
  Console > 
[=====================      37.0%                          ]LTIApply 15/02/2019 13:36:390 (0x0000)
  Console > 
[======================     38.0%                          ]LTIApply 15/02/2019 13:37:090 (0x0000)
ZTI Heartbeat: command has been running for 15 minutes (process ID 2268)LTIApply15/02/2019 13:37:090 (0x0000)
Event 41003 sent: ZTI Heartbeat: command has been running for 15 minutes (process ID 2268)LTIApply15/02/2019 13:37:090 (0x0000)
  Console > 
[======================     39.0%                          ]LTIApply 15/02/2019 13:37:380 (0x0000)
  Console > 
[=======================    40.0%                          ]LTIApply 15/02/2019 13:38:000 (0x0000)
  Console > 
[=======================    41.0%                          ]LTIApply 15/02/2019 13:38:110 (0x0000)
  Console > 
[========================   42.0%                          ]LTIApply 15/02/2019 13:38:280 (0x0000)
  Console > 
[========================   43.0%                          ]LTIApply 15/02/2019 13:38:450 (0x0000)
  Console > 
[=========================  44.0%                          ]LTIApply 15/02/2019 13:39:040 (0x0000)
  Console > 
[========================== 45.0%                          ]LTIApply 15/02/2019 13:39:210 (0x0000)
  Console > 
[========================== 46.0%                          ]LTIApply 15/02/2019 13:39:360 (0x0000)
  Console > 
[===========================47.0%                          ]LTIApply 15/02/2019 13:39:510 (0x0000)
  Console > 
[===========================48.0%                          ]LTIApply 15/02/2019 13:40:060 (0x0000)
  Console > 
[===========================49.0%                          ]LTIApply 15/02/2019 13:40:460 (0x0000)
  Console > 
[===========================50.0%                          ]LTIApply 15/02/2019 13:41:140 (0x0000)
  Console > 
[===========================51.0%                          ]LTIApply 15/02/2019 13:41:250 (0x0000)
  Console > 
[===========================52.0%                          ]LTIApply 15/02/2019 13:41:330 (0x0000)
  Console > 
[===========================53.0%                          ]LTIApply 15/02/2019 13:41:460 (0x0000)
  Console > 
[===========================54.0%                          ]LTIApply 15/02/2019 13:42:000 (0x0000)
ZTI Heartbeat: command has been running for 20 minutes (process ID 2268)LTIApply15/02/2019 13:42:000 (0x0000)
Event 41003 sent: ZTI Heartbeat: command has been running for 20 minutes (process ID 2268)LTIApply15/02/2019 13:42:000 (0x0000)
  Console > 
[===========================55.0%                          ]LTIApply 15/02/2019 13:42:170 (0x0000)
  Console > 
[===========================56.0%                          ]LTIApply 15/02/2019 13:42:340 (0x0000)
  Console > 
[===========================57.0%=                         ]LTIApply 15/02/2019 13:42:510 (0x0000)
  Console > 
[===========================58.0%=                         ]LTIApply 15/02/2019 13:43:050 (0x0000)
  Console > 
[===========================59.0%==                        ]LTIApply 15/02/2019 13:43:210 (0x0000)
  Console > 
[===========================60.0%==                        ]LTIApply 15/02/2019 13:43:350 (0x0000)
  Console > 
[===========================61.0%===                       ]LTIApply 15/02/2019 13:43:490 (0x0000)
  Console > 
[===========================62.0%===                       ]LTIApply 15/02/2019 13:44:040 (0x0000)
  Console > 
[===========================63.0%====                      ]LTIApply 15/02/2019 13:44:240 (0x0000)
  Console > 
[===========================64.0%=====                     ]LTIApply 15/02/2019 13:44:400 (0x0000)
  Console > 
[===========================65.0%=====                     ]LTIApply 15/02/2019 13:44:560 (0x0000)
  Console > 
[===========================66.0%======                    ]LTIApply 15/02/2019 13:45:110 (0x0000)
  Console > 
[===========================67.0%======                    ]LTIApply 15/02/2019 13:45:260 (0x0000)
  Console > 
[===========================68.0%=======                   ]LTIApply 15/02/2019 13:45:400 (0x0000)
  Console > 
[===========================69.0%========                  ]LTIApply 15/02/2019 13:45:540 (0x0000)
  Console > 
[===========================70.0%========                  ]LTIApply 15/02/2019 13:46:080 (0x0000)
  Console > 
[===========================71.0%=========                 ]LTIApply 15/02/2019 13:46:240 (0x0000)
  Console > 
[===========================72.0%=========                 ]LTIApply 15/02/2019 13:46:410 (0x0000)
  Console > 
[===========================73.0%==========                ]LTIApply 15/02/2019 13:46:540 (0x0000)
  Console > 
[===========================74.0%==========                ]LTIApply 15/02/2019 13:47:100 (0x0000)
ZTI Heartbeat: command has been running for 25 minutes (process ID 2268)LTIApply15/02/2019 13:47:100 (0x0000)
Event 41003 sent: ZTI Heartbeat: command has been running for 25 minutes (process ID 2268)LTIApply15/02/2019 13:47:100 (0x0000)
  Console > 
[===========================75.0%===========               ]LTIApply 15/02/2019 13:47:220 (0x0000)
  Console > 
[===========================76.0%============              ]LTIApply 15/02/2019 13:47:480 (0x0000)
  Console > 
[===========================77.0%============              ]LTIApply 15/02/2019 13:48:520 (0x0000)
  Console > 
[===========================78.0%=============             ]LTIApply 15/02/2019 13:49:130 (0x0000)
  Console > 
[===========================79.0%=============             ]LTIApply 15/02/2019 13:49:300 (0x0000)
  Console > 
[===========================80.0%==============            ]LTIApply 15/02/2019 13:49:440 (0x0000)
  Console > 
[===========================81.0%==============            ]LTIApply 15/02/2019 13:50:010 (0x0000)
  Console > 
[===========================82.0%===============           ]LTIApply 15/02/2019 13:50:160 (0x0000)
  Console > 
[===========================83.0%================          ]LTIApply 15/02/2019 13:50:320 (0x0000)
  Console > 
[===========================84.0%================          ]LTIApply 15/02/2019 13:50:490 (0x0000)
  Console > 
[===========================85.0%=================         ]LTIApply 15/02/2019 13:51:030 (0x0000)
  Console > 
[===========================86.0%=================         ]LTIApply 15/02/2019 13:51:190 (0x0000)
  Console > 
[===========================87.0%==================        ] LTIApply15/02/2019 13:51:340 (0x0000)
  Console > 
[===========================88.0%===================       ] LTIApply15/02/2019 13:51:500 (0x0000)
  Console > 
[===========================89.0%===================       ] LTIApply15/02/2019 13:52:040 (0x0000)
ZTI Heartbeat: command has been running for 30 minutes (process ID 2268)LTIApply15/02/2019 13:52:040 (0x0000)
Event 41003 sent: ZTI Heartbeat: command has been running for 30 minutes (process ID 2268)LTIApply15/02/2019 13:52:040 (0x0000)
  Console > 
[===========================90.0%====================      ] LTIApply15/02/2019 13:52:190 (0x0000)
  Console > 
[===========================91.0%====================      ] LTIApply15/02/2019 13:53:140 (0x0000)
  Console > 
[===========================92.0%=====================     ] LTIApply15/02/2019 13:54:260 (0x0000)
  Console > 
[===========================93.0%=====================     ] LTIApply15/02/2019 13:54:570 (0x0000)
  Console > 
[===========================94.0%======================    ] LTIApply15/02/2019 13:55:210 (0x0000)
  Console > 
[===========================95.0%=======================   ] LTIApply15/02/2019 13:55:570 (0x0000)
  Console > 
[==========================100.0%==========================] LTIApply15/02/2019 13:56:190 (0x0000)
  Console > The operation completed successfully.LTIApply15/02/2019 13:56:190 (0x0000)
Return code from command = 0LTIApply15/02/2019 13:56:190 (0x0000)
Property LTIDirtyOS is now = TRUELTIApply15/02/2019 13:56:190 (0x0000)

"Can not find script file "C:\MININT\Scripts\LiteTouch.wsf".

$
0
0
every time I turn on my pc this this pops up "Can not find script file "C:\MININT\Scripts\LiteTouch.wsf". and my Microsoft apps crash need help much appreciated 

MDT 2013 build 4856: 1- ZTIapplication list is empty, 2- Captureing image reboots into winpe wizard

$
0
0

Hello Iahe upgraded from bild 4843 to build 4356 along with adk 1809.

I am experinencing 2 issues:

1- none of my applications install any more. here is the ztilapplication log:

2- when I resume my ref image to continue on capturing the image, it will reboot into winPe wizard.

I did not have any issue prior to upgrade.

please help

thanks


MDT 2013 build 8456: 1- ZTIapplication list is empty, 2- Captureing image reboots into winpe wizard

$
0
0

Hello Iahe upgraded from bild 4843 to build 4356 along with adk 1809.

I am experinencing 2 issues:

1- none of my applications install any more. here is the ztilapplication log:

2- when I resume my ref image to continue on capturing the image, it will reboot into winPe wizard.

I did not have any issue prior to upgrade.

please help

thanks


MDT 2013 Update 2 (8443) - Windows 10 Enterprise Upgrade

$
0
0

I have created an upgrade sequence that appears to work well.  During testing of a successful upgrade, we found that the "Go back to Windows 7" button always produces an error.  "We're sorry, but you can't go back".

I could not locate anything in the setupact.log that would indicate an issue.  During research, I put a pause in immediately following the upgrade step and before the next step (a reboot in my case).  When I remoted into the machine at this point, go back to w7 was still available.

I have now run the upgrade by copying the folder from my MDT server for the OS directly to my test client.  

setup.exe /auto Upgrade /Quiet /NoReboot /DynamicUpdate Disable /ImageIndex 3 /compat IgnoreWarning

This resulted in a successful upgrade and the ability to go back.

This points me to the setupcomplete.cmd causing an issue.  Has anyone seen this before? 

Deploy WIndow 7 and got blue screen (UNEXPECTED KERNEL MODE TRAP) during "applying unattemd.xml with dism.exe"

$
0
0

HI all, 

I am deploying window 7 (32bit) to Lenovo T470 with 2 drive (one SSD and SATA hard disk) via WINPE. I have move the boot order for the SSD to first in the bios and disable the SATA hard disk. On the widow 7 images task sequence I have assign a SCCM driver package for this model. on the MDT Windows PE > Drivers and Patches, I  have injected the WINPE3.1 and intel network adapter driver, when I try to deploy the images, on "applying "applying unattemd.xml with dism.exe" I will get a blue screen and then when I try to boot up the machine, it will be on ablack screen with the message "An operating system wasn't found. try disconnecting any drivers that don't contain an operating system. Press Ctrl+Alt+Del to restart". only until I remove the SCCM driver package and deploy again then I can deploy the images. wonder what did I do wrong? did I missing out anything or do I need to inject additional driver? below is the blue screen and the SSD that my window 7 is using. I didn't inject any SSD driver while deploying as I can't find this SSD driver and do I really need it? 

Fyi: I have select "Install all drivers from selection profile" on the task sequence. to inject all SCCM Driver Package for the model T470

For your information, I have capture the images with the hotfix KB2990941 and KB3087873 before deploying it out. I have no issue to capture the window 7 32bit. but when deploying it.

ADK 1809 hanging command prompt

$
0
0

We are using MDT 8450 and ADK 1809 to install Win10 build 1803. We had the "not enough memory" error issue(https://support.microsoft.com/en-us/help/4339170/not-enough-memory-resources-error-cmd-winpe-windows-10) when using ADK 1803 and so upgraded to ADK 1809.

Everything was fine for a few weeks until we started getting a hanging command prompt again. No"not enough memory" error this time, though - just a plain prompt. If it is closed, the PC restarts and finishes the task sequence.

The appears when trying to execute a Restart Computer task that comes after a Run Command Line task which runs ZTINextPhase.wsf. The final couple lines in BDD.log are:

LTI initiating task sequence-requested reboot.

Event 41017 sent: LTI initiating task sequence-requested reboot.

Anyone else seeing this?

Skip

MDT UEFI FORMAT ONLY C ,and keep partition d (data)

$
0
0

hi gays ,i hope your are good ,i have i probleme with mdt ,i have two partition C and D (for data ) , and for reinstall i want format only C and keep D for win 10 ,in my task i disable format ,and creat file.txt format with diskpart /S ,and for install system i select disk 0 and partition 1 (all that for BIOS senario ),and it work fine ,but for UEFI senario she cant work !!! i have try format partition 3 or 4 ,and install with logical or availed partition ,but nothings every times i have error unable to detect drive ,plz help me ,thanks 

Windows 10: MDT Sysprep and Capture Task Sequence Failure.

$
0
0

Sysprep and Capture task sequence fails when it tries to capture Windows 10 Professional.

OS: Windows Server 2008 Enterprise 64bit

MDT (6.3.8450.1000)

Windows Assessment and Deployment Kit - Windows 10

Windows Automated Installation Kit

Operating System deployment did not complete successfully.

Please review the log file to determine the cause of the problem.

During the deployment process, 83 errors and 23 warnings were reported.

Unexpected return code while re-arming Office 2010, RC = -1073425657

Unexpected return code while re-arming Office 2013, RC = -1073425657

Unexpected return code while re-arming Office 2016, RC = -1073425657

Expected image state is IMAGE_STATE_GENERALIZE_RESEAL_TO_OOBE, actual image state is

IMAGE_STATE_COMPLETE, sysprep did not succeed.

FAILURE (6192): ERROR - Sysprep did not complete successfully, check

C:\WIN DOWS\system32\sysprep\panther\setupact.log for details

Litetouch deployment failed, Return Code = -2147467259 0x80004005

Failed to run the action: Execute Sysprep.

Unknown error (Error: 00001830; Source: Unknown)

The execution of the group (Capture Image) has failed and the execution has been aborted.

An action failed.

Operation aborted (Error: 80004004; Source: Windows)

Failed to run the last action: Execute Sysprep. Execution of task sequence failed.

Unknown error (Error: 00001830; Source: Unknown)

Task Sequence Engine failed! Code: enExecutionFail

Task sequence execution failed with error code 80004005

SetNamedSecuritylnfoo failed.

SetObjectOwnero failed. 0x80070005.

RegoueryValueExW is unsuccessful for Software\Microsoft\SMS\Task Sequence,

SMSTSEndProgram

GetTsRegValueo is unsuccessful. 0x80070002.

Error Task Sequence Manager failed to execute task sequence. Code 0x80004005

Failed to run the action: Execute Sysprep.

Unknown error (Error: 00001830; Source: Unknown)

The execution of the group (Capture Image) has failed and the execution has been aborted.

An action failed.

Operation aborted (Error: 80004004; Source: Windows)

Failed to run the last action: Execute Sysprep. Execution of task sequence failed.

Unknown error (Error: 00001830; Source: Unknown)

Task Sequence Engine failed! Code: enExecutionFail

Task sequence execution failed with error code 80004005

SetNamedSecuritylnfoo failed.

SetObjectOwnerO failed. 0x80070005.

RegCìueryValueExW is unsuccessful for Software\Microsoft\SMS\Task Sequence,

SMSTSEndProgram

GetTsRegValueo is unsuccessful. 0x80070002.

Error Task Sequence Manager failed to execute task sequence. Code 0x80004005

Failed to run the action: Execute Sysprep.

Unknown error (Error: 00001830; Source: Unknown)

The execution of the group (Capture Image) has failed and the execution has been aborted.

An action failed.

Operation aborted (Error: 80004004; Source: Windows)

Failed to run the last action: Execute Sysprep. Execution of task sequence failed.

Unknown error (Error: 00001830; Source: Unknown)

Task Sequence Engine failed! Code: enExecutionFail

Task sequence execution failed with error code 80004005

SetNamedSecuritylnfoo failed.

SetObjectOwnero failed. 0x80070005.

RegQueryValueExW is unsuccessful for Software\Microsoft\SMS\Task Sequence,

SMSTSEndProgram

GetTsRegValueo is unsuccessful. 0x80070002.

Error Task Sequence Manager failed to execute task sequence. Code 0x80004005

Failed to run the action: Execute Sysprep.

Unknown error (Error: 00001830; Source: Unknown)

The execution of the group (Capture Image) has failed and the execution has been aborted.

An action failed.

Operation aborted (Error: 80004004; Source: Windows)

Failed to run the last action: Execute Sysprep. Execution of task sequence failed.

Unknown error (Error: 00001830; Source: Unknown)

Task Sequence Engine failed! Code: enExecutionFail

Task sequence execution failed with error code 80004005

SetNamedSecuritylnfo() failed.

SetObjectOwnero failed. 0x80070005.

RegCìueryValueExW is unsuccessful for Software\Microsoft\SMS\Task Sequence,

SMSTSEndProgram

GetTsRegValueo is unsuccessful. 0x80070002.

Error Task Sequence Manager failed to execute task sequence. Code 0x80004005

Failed to run the action: Execute Sysprep.

Unknown error (Error: 00001830; Source: Unknown)

The execution of the group (Capture Image) has failed and the execution has been aborted.

An action failed.

Operation aborted (Error: 80004004; Source: Windows)

Failed to run the last action: Execute Sysprep. Execution of task sequence failed.

Unknown error (Error: 00001830; Source: Unknown)

Task Sequence Engine failed! Code: enExecutionFail

Task sequence execution failed with error code 80004005

SetNamedSecuritylnfoQ failed.

SetObjectOwnero failed. 0x80070005.

RegQueryValueExW is unsuccessful for Software\Microsoft\SMS\Task Sequence,

SMSTSEndProgram

GetTsReg Val ue0 is unsuccessful. 0x80070002.

Error Task Sequence Manager failed to execute task sequence. Code 0x80004005

Failed to run the action: Execute Sysprep.

Unknown error (Error: 00001830; Source: Unknown)

The execution of the group (Capture Image) has failed and the execution has been aborted.

An action failed.

Operation aborted (Error: 80004004; Source: Windows)

Failed to run the last action: Execute Sysprep. Execution of task sequence failed.

Unknown error (Error: 00001830; Source: Unknown)

Task Sequence Engine failed! Code: enExecutionFail

Task sequence execution failed with error code 80004005

SetNamedSecuritylnfoo failed.

SetObjectOwnero failed. 0x80070005.

RegCìueryValueExW is unsuccessful for Software\Microsoft\SMS\Task Sequence,

SMSTSEndProgram

GetTsRegValueo is unsuccessful. 0x80070002.

Error Task Sequence Manager failed to execute task sequence. Code 0x80004005

Failed to run the action: Execute Sysprep.

Unknown error (Error: 00001830; Source: Unknown)

The execution of the group (Capture Image) has failed and the execution has been aborted.

An action failed.

Operation aborted (Error: 80004004; Source: Windows)

Failed to run the last action: Execute Sysprep. Execution of task sequence failed.

Unknown error (Error: 00001830; Source: Unknown)

Task Sequence Engine failed! Code: enExecutionFail

Task sequence execution failed with error code 80004005

SetNamedSecuritylnfoo failed.

SetObjectOwnero failed. 0x80070005.

RegCìueryValueExW is unsuccessful for Software\Microsoft\SMS\Task Sequence,

SMSTSEndProgram

GetTs RegValueo is unsuccessful. 0x80070002.

Error Task Sequence Manager failed to execute task sequence. Code 0x80004005

Failed to run the action: Execute Sysprep.

Unknown error (Error: 00001830; Source: Unknown)

The execution of the group (Capture Image) has failed and the execution has been aborted.

An action failed.

Operation aborted (Error: 80004004; Source: Windows)

Failed to run the last action: Execute Sysprep. Execution of task sequence failed.

Unknown error (Error: 00001830; Source: Unknown)

Task Sequence Engine failed! Code: enExecutionFail

Task sequence execution failed with error code 80004005

SetNamedSecuritylnfoQ failed.

SetObjectOwnero failed. 0x80070005.

RegCìueryValueExW is unsuccessful for Software\Microsoft\SMS\Task Sequence,

SMSTSEndProgram

GetTsRegValueo is unsuccessful. 0x80070002.

Error Task Sequence Manager failed to execute task sequence. Code 0x80004005

Failed to run the action: Execute Sysprep.

Unknown error (Error: 00001830; Source: Unknown)

The execution of the group (Capture Image) has failed and the execution has been aborted.

An action failed.

Operation aborted (Error: 80004004; Source: Windows)

Failed to run the last action: Execute Sysprep. Execution of task sequence failed.

Unknown error (Error: 00001830; Source: Unknown)

Task Sequence Engine failed! Code: enExecutionFail

Task sequence execution failed with error code 80004005

SetNamedSecuritylnfo0 failed.

SetObjectOwner() failed. 0x80070005.

RegCìueryValueExW is unsuccessful for Software\Microsoft\SMS\Task Sequence,

SMSTSEndProgram

GetTsRegValueo is unsuccessful. 0x80070002.

Error Task Sequence Manager failed to execute task sequence. Code 0x80004005

DFS and Joining OU's

$
0
0

So I know this might sounds like two separate issues but they will relate, I promise. haha

I am implementing WDS/MDT for the 2nd time in my career for a company who did not have a proper imaging solution. Long story short, the previous company only had one site and the current one I'm working for has a total of 24 locations under one domain.

Each site has it's own DC, Computer Workstation OU for that site and site code and a utility server that hosts WDS/MDT 
For example Our New Jersey site code is called HINJ.
Our WDS/MDT server is located on an utility server which local to that location.

I want to use DFS NameSpace and Replication to sync all my sites with the same deployment share. All the sites have matching task sequences, software, OS and etc... with the exception of the following two lines in the rules tab: OSDComputername=
and
MachineObjectOU=OU= 
Example rule for naming New Jersey, Kentucky and Corp Computers:
(In New Jersey's rules) OSDComputername=HINJ-%SerialNumber%
(In Kentucky's rules) OSDComputername=HFDH-%SerialNumber%
(In Corp's rules) OSDComputername=CORP-%SerialNumber%

When join computer to the domain rule:
(In New Jersey's rules) MachineObjectOU=OU=Win-10-Workstations,OU=HINJ,DC=MYDOMAIN,DC=com
(In Kentucky's rules) MachineObjectOU=OU=Win-10-Workstations,OU=HFDH,DC=MYDOMAIN,DC=com
(In Corp's rules) MachineObjectOU=OU=Win-10-Workstations,OU=CORP,DC=MYDOMAIN,DC=com

From my understanding with DFS Replication, if all the site's reference Corp's Deployment share, then the rules for each site are always going to get changed to whatever is set as the  DFS Primary Member (Corp's Deployment Share) folder which tells me that I will have manually change the rules back to the site's specific information each time replication happens.

Is there a better way to manage all 24 shares? Am I over thinking or under thinking this? 

Hopefully I wrote this out clear enough to understand my issue. Thanks in advance.


MDT Zero Touch deployment of Windows 10 with Bitlocker TPM chip & PIN

$
0
0

Hi  -

I'd like to know if what I am trying to do is possible. We are upgrading to Windows 10 using our MDT system (No SCCM or MBAM) and we pre-populate the MDT database with a laptop serial no. and other specifics. We have custom fields in the MDT database for BIOS passwords so each machine has a unique BIOS password and admin password. This works fine on our present build which uses encrypted disk drives and Windows 7.

What I want to do is pre-populate a the database with a unique PIN for each machine to be used with Bitlocker, so as well as installing Windows 10 it installs bitlocker and encrypts the drive unattended- so that when the machine is issued to the user they are given the PIN. This needs to be Zero touch.

I've yet to get this to work at all even without a PIN - due to the way the machines are built the solution has to be zero-touch.

I have the necessary BIOS tools and can enable the TPM chip

The standard MDT task sequence installs bit locker - and the settings for PIN, Store recovery key in AD etc all seem to be accepted (enabled the bitlocker config screen in MDT to see the popluated values)

But it never works. Had one instance where a key was stored in the computer object in AD, but the disk never encrypts

Do I need to set anything in GPO? We tend to block GPO's as they break the task sequence (login message, renaming Admin account etc) so I've set up a staging OU to create the computer object which works, but the final bitlocker encryption and setting the PIN never works.

Am I missing something very obvious - or is what I'm trying to do not possible? Do I need MBAM or anything else to accomplish what I need?

Any pointers would be very much appreciated. Thanks in advance.

R

SkipAdminPassword rule doesn't work

$
0
0

Hey everyone,

do you know how skip this step (picture 1)?

The rule customsettings.ini rule "SkipAdminPassword=YES" doesn't work

Picture 1 - WDT-SkipAdminPassword

thanks a lot :)

MDT 2013 build 8456: ZTIapplication list is empty

$
0
0

Hello I have upgraded from build 8443 to build 8456 along with adk 1809.

I am experiencing following issue:

- none of my mandatory applications install any more. here is the ztilapplication log:

single application in TS install ok though.


I did not have any issue prior to upgrade.


thanks




MDT - Windows 10 imaging and initial default browsers

$
0
0

Hello!

I have been creating images for several years now and still have not found a suitable solution to changing the default browser for all new users from Edge to Internet Explorer.  Up until Windows 10 1803 this hasn't seemed to cause a pressing need to get this changed.  From what I have noticed, the Edge browser starting with 1803 causes issues with our state testing app.  There are several background services that start up and prevent the testing app to run.

I have tried to accomplish this 3 different ways.  I have applied a group policy that uses the xml file I exported from a computer I set all the defaults on.  I have used the same xml file and applied it in an MDT task sequence using the ZTIDefaultAssociations.wsf that copies the OEMDefaultAssociations.xml file to the system32 folder as well as writes the path in registry.  Both of these options have successfully changed the default browser to IE, but if you change the default to something else it is reverted back to IE every time you restart. 

I have also tried using dism to load these defaults.

I need to get the default changed from Edge to Internet Explorer for every new user that logs into the computer, but allows the user to pick their own browser and have it stick.

MDT 8456 Monitoring Service

$
0
0

After upgrading multiple servers to MDT 8456, some of them no longer have the MDT monitoring service. It's completely missing from services.msc. Did anyone else experience this issue or have the resolution? The monitoring service was working in 8450 prior to the upgrade.

Full error:

Assembly: mscorlib  Assembly Version: 4.0.0.0  File Version: 4.7.3324.0 built by: NET472REL1LAST_C
Assembly: Microsoft.ManagementConsole  Assembly Version: 3.0.0.0  File Version: 6.3.9600.16384
Assembly: System  Assembly Version: 4.0.0.0  File Version: 4.7.3353.0 built by: NET472REL1LAST_B
Assembly: MMCFxCommon  Assembly Version: 3.0.0.0  File Version: 6.3.9600.16384
Assembly: System.Configuration  Assembly Version: 4.0.0.0  File Version: 4.7.3324.0 built by: NET472REL1LAST_C
Assembly: System.Core  Assembly Version: 4.0.0.0  File Version: 4.7.3324.0 built by: NET472REL1LAST_C
Assembly: System.Xml  Assembly Version: 4.0.0.0  File Version: 4.7.3062.0 built by: NET472REL1
Assembly: System.Windows.Forms  Assembly Version: 4.0.0.0  File Version: 4.7.3324.0 built by: NET472REL1LAST_C
Assembly: System.Drawing  Assembly Version: 4.0.0.0  File Version: 4.7.3062.0 built by: NET472REL1
Assembly: Microsoft.BDD.Workbench  Assembly Version: 6.3.8456.1000  File Version: 6.3.8456.1000
Assembly: Microsoft.BDD.Core  Assembly Version: 6.3.8456.1000  File Version: 6.3.8456.1000
Assembly: Microsoft.BDD.PSSnapIn  Assembly Version: 6.3.8456.1000  File Version: 6.3.8456.1000
Assembly: System.Management.Automation  Assembly Version: 3.0.0.0  File Version: 6.3.9600.19170
Assembly: System.Numerics  Assembly Version: 4.0.0.0  File Version: 4.7.3062.0 built by: NET472REL1
Assembly: System.DirectoryServices  Assembly Version: 4.0.0.0  File Version: 4.7.3062.0 built by: NET472REL1
Assembly: System.Management  Assembly Version: 4.0.0.0  File Version: 4.7.3062.0 built by: NET472REL1
Assembly: Microsoft.Management.Infrastructure  Assembly Version: 1.0.0.0  File Version: 6.3.9600.16384
Assembly: Anonymously Hosted DynamicMethods Assembly  Assembly Version: 0.0.0.0
Assembly: Microsoft.PowerShell.Commands.Diagnostics  Assembly Version: 3.0.0.0  File Version: 6.3.9600.16384
Assembly: System.Configuration.Install  Assembly Version: 4.0.0.0  File Version: 4.7.3062.0 built by: NET472REL1
Assembly: System.Transactions  Assembly Version: 4.0.0.0  File Version: 4.7.3221.0 built by: NET472REL1LAST_C
Assembly: Microsoft.PowerShell.Commands.Utility  Assembly Version: 3.0.0.0  File Version: 6.3.9600.19170
Assembly: Microsoft.PowerShell.ConsoleHost  Assembly Version: 3.0.0.0  File Version: 6.3.9600.17399
Assembly: Microsoft.PowerShell.Commands.Management  Assembly Version: 3.0.0.0  File Version: 6.3.9600.17399
Assembly: Microsoft.PowerShell.Security  Assembly Version: 3.0.0.0  File Version: 6.3.9600.17399
Assembly: Microsoft.WSMan.Management  Assembly Version: 3.0.0.0  File Version: 6.3.9600.16384
Assembly: System.Data  Assembly Version: 4.0.0.0  File Version: 4.7.3260.0 built by: NET472REL1LAST_C
Assembly: System.Data.Services.Client  Assembly Version: 4.0.0.0  File Version: 4.7.3062.0 built by: NET472REL1
 
System.InvalidOperationException: Unable to access the monitoring data service at http://Hostname-of-server:9801/MDTMonitorData.  Make sure the MDT monitoring service is running.

   at Microsoft.BDD.Workbench.Utility.RunPSCommand(String commandString, Dictionary`2 parameters)
   at Microsoft.BDD.Workbench.MonitoringListView.Refresh()

Viewing all 11297 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>