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

Can I cache offline USB key media to HDD and remove USB after image is applied?

$
0
0

I have created a bootable USB key from offline media I created using MDT 2013, it functions as it should but I would like to be able to remove the USB key after the image is applied and then have the process continue without needing the USB key inserted.

Is there a way to get MDT to cache what it needs (excluding the WIM files) to the primary/OS drive either through a simple setting in the CustomSettings.ini or by editing a script? If this is going to involve scripting, I'd appreciate if I could be told where to start and then I'll research from there.

Thanks




FAILURE ( 5615 ): False: Boot Drive was not found, required?_

$
0
0

<g class="gr_ gr_3 gr-alert gr_spell gr_run_anim ContextualSpelling ins-del multiReplace" data-gr-id="3" id="3">Im</g> trying to deploy an image to a computer that has a 4Tb drive but in has consistently failed. I have tried applying various images and they all fail; however, they work on other computers that have 500GB drives. Initially, <g class="gr_ gr_283 gr-alert gr_tiny gr_spell gr_run_anim ContextualSpelling multiReplace" data-gr-id="283" id="283">i</g> was using a template Task Sequence that worked for all my other machines but it would fail at about 3% saying "Failure (5624: 112: Run DISm/apply-image )". <g class="gr_ gr_522 gr-alert gr_gramm gr_hide gr_run_anim Grammar" data-gr-id="522" id="522">I them</g> modified the TS under Format and Partition Disk (UEFI) --> disk type --> to GPT. Then the installation of the OS would get to 100% and fail with a new error Failure (5615): False: Boot drive was not found, required? Please let me know if you all have any recommendations. 

------  Applying Windows image using DISM.exe ------	LTIApply	1/6/2017 8:29:36 AM	0 (0x0000)
LTI applying image \\x\DeploymentShare$\Operating Systems\Windows-7-x86\PHXTOR004.wim using DISM	LTIApply	1/6/2017 8:29:36 AM	0 (0x0000)
Event 41023 sent: LTI applying image \\x\DeploymentShare$\Operating Systems\Windows-7-x86\PHXTOR004.wim using DISM	LTIApply	1/6/2017 8:29:37 AM	0 (0x0000)
Property SourcePath is now = \\x\DeploymentShare$\Operating Systems\Windows-7-x86	LTIApply	1/6/2017 8:29:37 AM	0 (0x0000)
Cleaning off old operating system	LTIApply	1/6/2017 8:29:37 AM	0 (0x0000)
Skipping C:\Drivers	LTIApply	1/6/2017 8:29:37 AM	0 (0x0000)
Skipping C:\MININT	LTIApply	1/6/2017 8:29:37 AM	0 (0x0000)
Skipping C:\_SMSTaskSequence	LTIApply	1/6/2017 8:29:37 AM	0 (0x0000)
New ZTIDiskPartition : \\MININT-P11R8JE\root\cimv2:Win32_LogicalDisk.DeviceID="C:"    \\MININT-P11R8JE\root\cimv2:Win32_DiskPartition.DeviceID="Disk #0, Partition #1"	LTIApply	1/6/2017 8:29:37 AM	0 (0x0000)
Enabling 8dot3 name support on volume C:	LTIApply	1/6/2017 8:29:37 AM	0 (0x0000)
About to run command: "\\x\DeploymentShare$\Servicing\X86\DISM.exe"  /Apply-Image /ImageFile:"\\x\DeploymentShare$\Operating Systems\Windows-7-x86\PHXTOR004.wim" /Index:1 /ApplyDir:C:	LTIApply	1/6/2017 8:29:37 AM	0 (0x0000)
Command has been started (process ID 1472)	LTIApply	1/6/2017 8:29:37 AM	0 (0x0000)
ZTI Heartbeat: command has been running for 0 minutes (process ID 1472)	LTIApply	1/6/2017 8:29:37 AM	0 (0x0000)
Event 41003 sent: ZTI Heartbeat: command has been running for 0 minutes (process ID 1472)	LTIApply	1/6/2017 8:29:38 AM	0 (0x0000)
  Console > Deployment Image Servicing and Management tool	LTIApply	1/6/2017 8:29:38 AM	0 (0x0000)
  Console > Version: 10.0.14393.0	LTIApply	1/6/2017 8:29:38 AM	0 (0x0000)
  Console > Applying image	LTIApply	1/6/2017 8:29:44 AM	0 (0x0000)
  Console >
[                           1.0%                           ] 	LTIApply	1/6/2017 8:29:45 AM	0 (0x0000)
  Console >
[=                          2.0%                           ] 	LTIApply	1/6/2017 8:29:56 AM	0 (0x0000)
  Console >
[=                          3.0%                           ] 	LTIApply	1/6/2017 8:30:00 AM	0 (0x0000)
  Console >
[==                         4.0%                           ] 	LTIApply	1/6/2017 8:30:04 AM	0 (0x0000)
  Console >
[==                         5.0%                           ] 	LTIApply	1/6/2017 8:30:09 AM	0 (0x0000)
  Console >
[===                        6.0%                           ] 	LTIApply	1/6/2017 8:30:17 AM	0 (0x0000)
  Console >
[====                       7.0%                           ] 	LTIApply	1/6/2017 8:30:23 AM	0 (0x0000)
  Console >
[====                       8.0%                           ] 	LTIApply	1/6/2017 8:30:28 AM	0 (0x0000)
  Console >
[=====                      9.0%                           ] 	LTIApply	1/6/2017 8:30:33 AM	0 (0x0000)
  Console >
[=====                      10.0%                          ] 	LTIApply	1/6/2017 8:30:39 AM	0 (0x0000)
  Console >
[======                     11.0%                          ] 	LTIApply	1/6/2017 8:30:45 AM	0 (0x0000)
  Console >
[======                     12.0%                          ] 	LTIApply	1/6/2017 8:30:51 AM	0 (0x0000)
  Console >
[=======                    13.0%                          ] 	LTIApply	1/6/2017 8:30:56 AM	0 (0x0000)
  Console >
[========                   14.0%                          ] 	LTIApply	1/6/2017 8:31:02 AM	0 (0x0000)
  Console >
[========                   15.0%                          ] 	LTIApply	1/6/2017 8:31:08 AM	0 (0x0000)
  Console >
[=========                  16.0%                          ] 	LTIApply	1/6/2017 8:31:14 AM	0 (0x0000)
  Console >
[=========                  17.0%                          ] 	LTIApply	1/6/2017 8:31:20 AM	0 (0x0000)
  Console >
[==========                 18.0%                          ] 	LTIApply	1/6/2017 8:31:25 AM	0 (0x0000)
  Console >
[===========                19.0%                          ] 	LTIApply	1/6/2017 8:31:30 AM	0 (0x0000)
  Console >
[===========                20.0%                          ] 	LTIApply	1/6/2017 8:31:33 AM	0 (0x0000)
  Console >
[============               21.0%                          ] 	LTIApply	1/6/2017 8:31:37 AM	0 (0x0000)
  Console >
[============               22.0%                          ] 	LTIApply	1/6/2017 8:31:41 AM	0 (0x0000)
  Console >
[=============              23.0%                          ] 	LTIApply	1/6/2017 8:31:47 AM	0 (0x0000)
  Console >
[=============              24.0%                          ] 	LTIApply	1/6/2017 8:31:51 AM	0 (0x0000)
  Console >
[==============             25.0%                          ] 	LTIApply	1/6/2017 8:31:55 AM	0 (0x0000)
  Console >
[===============            26.0%                          ] 	LTIApply	1/6/2017 8:31:58 AM	0 (0x0000)
  Console >
[===============            27.0%                          ] 	LTIApply	1/6/2017 8:32:02 AM	0 (0x0000)
  Console >
[================           28.0%                          ] 	LTIApply	1/6/2017 8:32:07 AM	0 (0x0000)
  Console >
[================           29.0%                          ] 	LTIApply	1/6/2017 8:32:11 AM	0 (0x0000)
  Console >
[=================          30.0%                          ] 	LTIApply	1/6/2017 8:32:17 AM	0 (0x0000)
  Console >
[=================          31.0%                          ] 	LTIApply	1/6/2017 8:32:21 AM	0 (0x0000)
  Console >
[==================         32.0%                          ] 	LTIApply	1/6/2017 8:32:24 AM	0 (0x0000)
  Console >
[===================        33.0%                          ] 	LTIApply	1/6/2017 8:32:29 AM	0 (0x0000)
  Console >
[===================        34.0%                          ] 	LTIApply	1/6/2017 8:32:34 AM	0 (0x0000)
  Console >
[====================       35.0%                          ] 	LTIApply	1/6/2017 8:32:40 AM	0 (0x0000)
  Console >
[====================       36.0%                          ] 	LTIApply	1/6/2017 8:32:45 AM	0 (0x0000)
  Console >
[=====================      37.0%                          ] 	LTIApply	1/6/2017 8:32:50 AM	0 (0x0000)
  Console >
[======================     38.0%                          ] 	LTIApply	1/6/2017 8:32:54 AM	0 (0x0000)
  Console >
[======================     39.0%                          ] 	LTIApply	1/6/2017 8:32:58 AM	0 (0x0000)
  Console >
[=======================    40.0%                          ] 	LTIApply	1/6/2017 8:33:01 AM	0 (0x0000)
  Console >
[=======================    41.0%                          ] 	LTIApply	1/6/2017 8:33:05 AM	0 (0x0000)
  Console >
[========================   42.0%                          ] 	LTIApply	1/6/2017 8:33:08 AM	0 (0x0000)
  Console >
[========================   43.0%                          ] 	LTIApply	1/6/2017 8:33:12 AM	0 (0x0000)
  Console >
[=========================  44.0%                          ] 	LTIApply	1/6/2017 8:33:17 AM	0 (0x0000)
  Console >
[========================== 45.0%                          ] 	LTIApply	1/6/2017 8:33:21 AM	0 (0x0000)
  Console >
[========================== 46.0%                          ] 	LTIApply	1/6/2017 8:33:26 AM	0 (0x0000)
  Console >
[===========================47.0%                          ] 	LTIApply	1/6/2017 8:33:33 AM	0 (0x0000)
  Console >
[===========================48.0%                          ] 	LTIApply	1/6/2017 8:33:38 AM	0 (0x0000)
  Console >
[===========================49.0%                          ] 	LTIApply	1/6/2017 8:33:44 AM	0 (0x0000)
  Console >
[===========================50.0%                          ] 	LTIApply	1/6/2017 8:33:47 AM	0 (0x0000)
  Console >
[===========================51.0%                          ] 	LTIApply	1/6/2017 8:33:55 AM	0 (0x0000)
  Console >
[===========================52.0%                          ] 	LTIApply	1/6/2017 8:33:59 AM	0 (0x0000)
ZTI Heartbeat: command has been running for 5 minutes (process ID 1472)	LTIApply	1/6/2017 8:34:00 AM	0 (0x0000)
Event 41003 sent: ZTI Heartbeat: command has been running for 5 minutes (process ID 1472)	LTIApply	1/6/2017 8:34:01 AM	0 (0x0000)
  Console >
[===========================53.0%                          ] 	LTIApply	1/6/2017 8:34:02 AM	0 (0x0000)
  Console >
[===========================54.0%                          ] 	LTIApply	1/6/2017 8:34:06 AM	0 (0x0000)
  Console >
[===========================55.0%                          ] 	LTIApply	1/6/2017 8:34:11 AM	0 (0x0000)
  Console >
[===========================56.0%                          ] 	LTIApply	1/6/2017 8:34:16 AM	0 (0x0000)
  Console >
[===========================57.0%=                         ] 	LTIApply	1/6/2017 8:34:20 AM	0 (0x0000)
  Console >
[===========================58.0%=                         ] 	LTIApply	1/6/2017 8:34:22 AM	0 (0x0000)
  Console >
[===========================59.0%==                        ] 	LTIApply	1/6/2017 8:34:26 AM	0 (0x0000)
  Console >
[===========================60.0%==                        ] 	LTIApply	1/6/2017 8:34:29 AM	0 (0x0000)
  Console >
[===========================61.0%===                       ] 	LTIApply	1/6/2017 8:34:33 AM	0 (0x0000)
  Console >
[===========================62.0%===                       ] 	LTIApply	1/6/2017 8:34:37 AM	0 (0x0000)
  Console >
[===========================63.0%====                      ] 	LTIApply	1/6/2017 8:34:40 AM	0 (0x0000)
  Console >
[===========================64.0%=====                     ] 	LTIApply	1/6/2017 8:34:44 AM	0 (0x0000)
  Console >
[===========================65.0%=====                     ] 	LTIApply	1/6/2017 8:34:48 AM	0 (0x0000)
  Console >
[===========================66.0%======                    ] 	LTIApply	1/6/2017 8:34:52 AM	0 (0x0000)
  Console >
[===========================67.0%======                    ] 	LTIApply	1/6/2017 8:34:55 AM	0 (0x0000)
  Console >
[===========================68.0%=======                   ] 	LTIApply	1/6/2017 8:34:58 AM	0 (0x0000)
  Console >
[===========================69.0%========                  ] 	LTIApply	1/6/2017 8:35:01 AM	0 (0x0000)
  Console >
[===========================70.0%========                  ] 	LTIApply	1/6/2017 8:35:03 AM	0 (0x0000)
  Console >
[===========================71.0%=========                 ] 	LTIApply	1/6/2017 8:35:07 AM	0 (0x0000)
  Console >
[===========================72.0%=========                 ] 	LTIApply	1/6/2017 8:35:12 AM	0 (0x0000)
  Console >
[===========================73.0%==========                ] 	LTIApply	1/6/2017 8:35:16 AM	0 (0x0000)
  Console >
[===========================74.0%==========                ] 	LTIApply	1/6/2017 8:35:21 AM	0 (0x0000)
  Console >
[===========================75.0%===========               ] 	LTIApply	1/6/2017 8:35:26 AM	0 (0x0000)
  Console >
[===========================76.0%============              ] 	LTIApply	1/6/2017 8:35:30 AM	0 (0x0000)
  Console >
[===========================77.0%============              ] 	LTIApply	1/6/2017 8:35:44 AM	0 (0x0000)
  Console >
[===========================78.0%=============             ] 	LTIApply	1/6/2017 8:35:50 AM	0 (0x0000)
  Console >
[===========================79.0%=============             ] 	LTIApply	1/6/2017 8:35:58 AM	0 (0x0000)
  Console >
[===========================80.0%==============            ] 	LTIApply	1/6/2017 8:36:04 AM	0 (0x0000)
  Console >
[===========================81.0%==============            ] 	LTIApply	1/6/2017 8:36:11 AM	0 (0x0000)
  Console >
[===========================82.0%===============           ] 	LTIApply	1/6/2017 8:36:18 AM	0 (0x0000)
  Console >
[===========================83.0%================          ] 	LTIApply	1/6/2017 8:36:24 AM	0 (0x0000)
  Console >
[===========================84.0%================          ] 	LTIApply	1/6/2017 8:36:31 AM	0 (0x0000)
  Console >
[===========================85.0%=================         ] 	LTIApply	1/6/2017 8:36:38 AM	0 (0x0000)
  Console >
[===========================86.0%=================         ] 	LTIApply	1/6/2017 8:36:44 AM	0 (0x0000)
  Console >
[==========================100.0%==========================] 	LTIApply	1/6/2017 8:36:50 AM	0 (0x0000)
  Console > The operation completed successfully.	LTIApply	1/6/2017 8:36:52 AM	0 (0x0000)
Return code from command = 0	LTIApply	1/6/2017 8:36:52 AM	0 (0x0000)
Property LTIDirtyOS is now = TRUE	LTIApply	1/6/2017 8:36:53 AM	0 (0x0000)
The image \\x\DeploymentShare$\Operating Systems\Windows-7-x86\PHXTOR004.wim was applied successfully.	LTIApply	1/6/2017 8:36:53 AM	0 (0x0000)
Event 5625 sent: The image \\x\DeploymentShare$\Operating Systems\Windows-7-x86\PHXTOR004.wim was applied successfully.	LTIApply	1/6/2017 8:36:53 AM	0 (0x0000)
About to run command: "\\x\DeploymentShare$\Tools\X86\bootsect.exe"  /nt60 C:	LTIApply	1/6/2017 8:36:53 AM	0 (0x0000)
Command has been started (process ID 1580)	LTIApply	1/6/2017 8:36:53 AM	0 (0x0000)
  Console > Target volumes will be updated with BOOTMGR compatible bootcode.	LTIApply	1/6/2017 8:36:54 AM	0 (0x0000)
  Console > C: (\\?\Volume{f566e94f-f585-4c0e-9d29-e244ae8d8caa})	LTIApply	1/6/2017 8:36:55 AM	0 (0x0000)
  Console >     Updated NTFS filesystem bootcode.  The update may be unreliable since the	LTIApply	1/6/2017 8:36:55 AM	0 (0x0000)
  Console >     volume could not be locked during the update:	LTIApply	1/6/2017 8:36:55 AM	0 (0x0000)
  Console >         Access is denied.	LTIApply	1/6/2017 8:36:55 AM	0 (0x0000)
  Console > Bootcode was successfully updated on all targeted volumes.	LTIApply	1/6/2017 8:36:55 AM	0 (0x0000)
Return code from command = 0	LTIApply	1/6/2017 8:36:55 AM	0 (0x0000)
Find the boot drive (if any) [True] [6.1.7601.23392] [False]	LTIApply	1/6/2017 8:36:55 AM	0 (0x0000)
No boot drives found. None.	LTIApply	1/6/2017 8:36:55 AM	0 (0x0000)
FAILURE ( 5615 ): False: Boot Drive was not found, required?	LTIApply	1/6/2017 8:36:55 AM	0 (0x0000)
Event 41002 sent: FAILURE ( 5615 ): False: Boot Drive was not found, required?	LTIApply	1/6/2017 8:36:55 AM	0 (0x0000)
Removing AutoAdminLogon registry entries	LTICleanup	1/6/2017 8:36:57 AM	0 (0x0000)
Re-enabling UAC for built-in Administrator account	LTICleanup	1/6/2017 8:36:57 AM	0 (0x0000)
Re-enabling asynchronous RunOnce	LTICleanup	1/6/2017 8:36:57 AM	0 (0x0000)
VSSMaxSize not specified using 5% of volume.	LTICleanup	1/6/2017 8:36:57 AM	0 (0x0000)
Logs contained 10 errors and 2 warnings.	LTICleanup	1/6/2017 8:36:58 AM	0 (0x0000)
No Windows PE image to delete.	LTICleanup	1/6/2017 8:36:58 AM	0 (0x0000)
Checking mapped network drive.	LTICleanup	1/6/2017 8:36:58 AM	0 (0x0000)
testing drive Z: mapped to \\x\DeploymentShare$	LTICleanup	1/6/2017 8:36:58 AM	0 (0x0000)
Disconnecting drive Z: mapped to \\x\DeploymentShare$	LTICleanup	1/6/2017 8:36:58 AM	0 (0x0000)
Cleaning up C:\MININT directory.	LTICleanup	1/6/2017 8:36:58 AM	0 (0x0000)
Cleaning up TOOLS, SCRIPTS, and PACKAGES directories.	LTICleanup	1/6/2017 8:36:58 AM	0 (0x0000)
Removing C:\MININT folder (final log entry)	LTICleanup	1/6/2017 8:36:58 AM	0 (0x0000)


Why is OS deployment so slow via MDT?

$
0
0

Happy New Year!

I am testing MDT in my local LAN environment and have been able to successfully deploy several Windows 10 test instances both to VMs and to actual physical hardware on the network.

But I do want to understand why the process of PXE boot to WDS server and the subsequent install of a selected system is so slow? Is it just the fact that everything has to come over the network or is there something else I am missing?

In my testing - the last being to physical hardware - I am estimating this deployment took 50 minutes to deploy. The same via USB key at the machine takes no more that 7 or 8 minutes tops.

Just wondering what the point of this if it takes so long? Is there some optimization that I have missed - or is this just the way it is?

I did have WSUS inline as part of a few of the tests but removed it as it seemed to take forever for an install to actually install updates from the server. But even after removal - it seems like my MDT script is doing nothing for 20 minutes after the OS looks like it is deployed.

Appreciate an insights on your install times or other things that I need to be looking at.

Cheers!

B

mdt 8443 sysprep and capture windows 10 1607 issue

$
0
0

Hello,
I'm having an awful time trying to capture an image of a Windows 10 machine running 1607 build. I updated my MDT server to the latest build, 63.8443.1000.  I updated ADK to latest version 10.  I updated deployment share and used the "completely regenerate boot images". I set up a simple test sysprep and capture sequence.  After I run litetouch.vbs on the Windows machine to be imaged, first screen comes up where I can choose my task sequence.  I choose my test capture, click next, answer no to the backup file question, click next.  I don't get the option to give the image a name.  A status screen regard PXE comes up for less than a minute.  While the machine reboots, it says it finished with zero errors but no image is created. I get the success message with 0 errors and no details.  The minint folder with logs is not always there but doesn't appear to show any errors.  It's just skipping the capture process.  Thoughts?

Thank you

Aaron

Help troubleshooting deployment please...

$
0
0

I recently updated our MDT server from 2013 U2 6.3.8330.1000 to 6.3.8443.1000 and I also updated the ADK to v1607, I updated the boot images and imported them in WDS for PXE booting.   I did this so we could get started with Windows 10.  I've created a new build and capture sequence and also a deploy sequence, both for Windows 10, which are working well.  

However, when I tried to image a hyper-v vm using our old Windwos 7 ts it would throw a pink screen and error 6524 while still in WinPE every time, if I imaged a desktop using this ts it would intermittently fail, I can't say for sure whether it was also error 6524 or not.

Anyway, I recreated this Windows 7 ts thinking that was the problem.  When I image the vm I still get the same 6524 error. When I image a desktop I get error 5627 but it's intermittent like before.  The failure screen is:

Something is making me think this is related to our previous habit of fiddling with the partition structure in the image to make a C:, D: and NOT the 500MB utility partition but I don't understand it enough to fix it.  We will not be doing this with Windows 10. If someone can please, please help I would greatly appreciate it, just tell me what you need.

I have shared the logs from the failed desktop imaging here https://1drv.ms/f/s!Apnj5ye_VbzEqA5SA75T6oWRL7gb

1607 boot image causes boot sequence issue

$
0
0

I have updated my boot image from 1511 to 1607. There is only 1 model that i have that has a problem. It is a Dell M4800. It applies the image fine but after the first reboot instead of booting to the drive, it boots back into IPv4 and loads my PXE boot image again. It should boot to the hard drive. When I image with my 1511 boot image it works fine. I did not update anything with the task sequence or any drivers either. If i go to the boot menu, I can manually select the hard drive and it will pick up where it left off in the imaging process but it's not automatically doing that. I am on the latest BIOS.

Is anyone else seeing this on any models or the M4800 specifically? Not quite sure what to try next.

MDT / ADK WIN10 1607 support

$
0
0

Hello:

Happy New Year.

Background first:

Prior to WIN10 1607 (Anniversary update), I used ADK and MDT 2013 SP2.

After WIN10 1607 update was released, in a few places, I read that (to support the WIN10 1607) I needed to install the newly released version of ADK and MDT 2013 to support the 1607.  So I went to install the new ADK / MDT version.  During the initial install, I not only found I could NOT upgrade, but the software told me that I had to uninstall the current ADK. Though, reluctant, I did the ADK uninstall. Then I went to install the ADK 10 1607, the install stated that the folder must be empty to install.

The question:

Each time a new build of Windows 10 comes out, do I need to completely scrap ADK and MDT to install their latest versions (and completely rebuild the imaging process using the Deployment Workbench)????

Thank you, very much.

Unable to Create some applications within MDT 8443

$
0
0

When trying to add the DotNet 4.6.2 Application to MDT 8443 (ADK 1607) I keep getting the following:

Performing the operation "import" on target "Application".
Beginning application import
Copying application source files from D:\Apps\DOTNET462 to D:\DeploymentShare\Applications\DOTNET462
The filename, directory name, or volume label syntax is incorrect
The filename, directory name, or volume label syntax is incorrect
System.ComponentModel.Win32Exception (0x80004005): The filename, directory name, or volume label syntax is incorrect
   at Microsoft.BDD.Core.DirectoryUtility.CopyFile(DEInfo sourceFile, DEInfo destFile, String destFullName)
   at Microsoft.BDD.Core.DirectoryUtility.CopyDirectory(String theSource, String theDest)
   at Microsoft.BDD.Core.DirectoryUtility.CopyDirectory(String theSource, String theDest)
   at Microsoft.BDD.Core.DirectoryUtility.BeginCopy()
   at Microsoft.BDD.PSSnapIn.ImportApplication.ProcessRecord()


I've changed the folder and exe name to something easier like "ABC" and the error still occurs.

The following is a copy of the PowerShell script generated from the "View Script" Button when creating the Application:

Import-Module "C:\Program Files\Microsoft Deployment Toolkit\bin\MicrosoftDeploymentToolkit.psd1"
New-PSDrive -Name "DS003" -PSProvider MDTProvider -Root "D:\DeploymentShare"
import-MDTApplication -path "DS003:\Applications" -enable "True" -Name "DOTNET462" -ShortName "DOTNET462" -Version "" -Publisher "" -Language "" -CommandLine "cscript.exe Install-DOTNET462.wsf" -WorkingDirectory ".\Applications\DOTNET462" -ApplicationSourcePath "D:\Apps\DOTNET462" -DestinationFolder "DOTNET462" -Verbose

I get the same error with other Applications I tried to add, weirdly though some have worked.

I've created two new Servers (Both 2012R2 and 2016 Standard) and am having the same issue on both.

Anyone have any ideas?

Edit: Heres an image of the Error:



No MDT Imported Drivers Loading, Elitebook 840 G1

$
0
0

I am deploying a custom wim of Windows 10 x64 enterprise.  I built the image on VM and now trying out a USB media deployment.  The Deployment goes through till finish with no errors.  After the deployment I checked Device manager and had several bangs for missing drivers.  

I am using the "Total Control" method.


- I verified the name structure of my Out of Box MDT Folder "Windows 10\HP EliteBook 840 G1"

- I verified the WMI name is "HP EliteBook 840 G1"

- I built a CAB file using the HP SDM and imported that CAB into my Deployment Share.

- I verified in the TS that the pre-install "Set Drivergroup" sequence has the value of "Windows 10\%Model%"

- I verified in the TS that the pre-install "Inject Drivers" sequence selection profile is set to "Nothing" and "Install all drivers from selection profile."

- I see drivers being injected during the pre-install phase of deployment.

- No network cable is ever plugged in during the deployment or any moment after the deployment finishes (so driver logs can be as clean as possible on client side)

- Checked ZTIDrivers.log and see lots of drivers being copied to C:\Drivers. I do NOT see a C:\Drivers folder after deployment (Should I?)

- BDD.log shows at the beginning "Unable to determine asset tag by WMI"  but a few lines later in the log Property Model information is populated to be correct.

When it was all said and done I was able to verify some network drivers that did load were not the ones I imported (different versions, verified by updating driver and selecting my USB Deployment share Out of Box folder to search, it did load the driver from that search.)  I also updated devices that loaded generic windows drivers with the drivers from the Out of Box Folder.  Also, devices that had missing driver bangs were all able to be updated by manually selecting update driver and pointing the search to my USB Out Of Box Drivers folder.

So it seems my deployment is not loading any of my imported drivers and only loading built Windows drivers and I am not sure why.  I have looked over logs but this is kind of new territory for me and I am sure I am overlooking something.  I have to be, right?

You should be able to find the logs I think someone may need to help at this location:  Logs here

Thank you for any help that could be offered!


MDT 2013 Upd 2 - How to Pre-populate the W10 1607 Reference Image with Languages

$
0
0

Hi there,

Would you be so kind to advise how to pre-populate the Windows 10 (1607) reference image so that user who gets it deploy would have 2 available language sets - English (United States) and another language - like English (United Kingdom) on the following screenshot:

Many thanks, in advance!!!

Unable to mount the WIM, so the update process cannot continue.

$
0
0

Hi , I am getting this error message when I try to update deployment share for AMD x64. I have MDT in a separate server and WDS in separate server. once the WIM is updated , I map the other server and update the boot image to the WDS to deployment.

This  is the error message.

=== Making sure the deployment share has the latest x86 tools ===

=== Processing LiteTouchPE (x86) boot image ===

Building requested boot image profile.
Determining if any changes have been made in the boot image configuration.
Loading the existing boot image profile for platform x86.
Calculating hashes for requested content.
Changes have been made, boot image will be updated.
Windows PE WIM D:\Deployment Shares\AMD\Boot\LiteTouchPE_x86.wim will be used.
Unable to mount the WIM, so the update process cannot continue.

=== Completed processing platform x86 ===

=== Making sure the deployment share has the latest x64 tools ===

=== Processing Generic (x64) boot image ===

Building requested boot image profile.
Determining if any changes have been made in the boot image configuration.
Loading the existing boot image profile for platform x64.
Calculating hashes for requested content.
Changes have been made, boot image will be updated.
Windows PE WIM D:\Deployment Shares\AMD\Boot\Generic_x64.wim will be used.
Unable to mount the WIM, so the update process cannot continue.

=== Processing LiteTouchPE (x64) boot image ===

Building requested boot image profile.
Determining if any changes have been made in the boot image configuration.
Loading the existing boot image profile for platform x64.
Calculating hashes for requested content.
Changes have been made, boot image will be updated.
Windows PE WIM D:\Deployment Shares\AMD\Boot\LiteTouchPE_x64.wim will be used.
Unable to mount the WIM, so the update process cannot continue.

=== Completed processing platform x64 ===


=== Processing complete ===

Please help,

Thanks

c:\minint\script\LightTouch.wsf post deployment remainder

$
0
0
After successful (no errors) deployments I often see a message on logon saying the script c:\minint\script\LightTouch.wsf cannot be found. I can't find where's that coming from. I checked for startup scripts but it's not there. The deployed OS is 2012 R2.

yaro

Litetouch deployment failed, Return Code = -2147024894 0x80070002 with MDT 2010 and Win XP

Pre Selected Applications in MDT-Possible?

$
0
0

Hi Could someone tell me if its possible to have "pre-Selected" applications in MDT?  Basically, that when a task sequence is selected and the user gets to the application part, an App is already pre selected, Say Office.  

And if possible, make it that if Office 32bit is selected and they select 64bit, could the other be unchecked automatically, sort of like an "this or that, but not both" radio button

Hope that makes sense.  Also, I really want to avoid having to add this to the task sequence, we are trying to  reduce our images down to one.

Thanks.

Separate log files during deployment?

$
0
0

Hello!

I have this in my rules so during deployment, MDT is making a log file.

SLShareDynamicLogging=%DeployRoot%\Logs

However, I notice that this is dumping everything to a BDD.log during deployment. If I start multiple deployments at once, then all those deployments get thrown into the same log file. At the end of deployment, MDT sorts the log files into the machine name, but this means the BDD.log is filled with lines from other deployments.

Is it possible to change the name of BDD.log during deployment? Something like BDD_%MachineName%.log to avoid multiple deployments logging to the same file?


Cannot connect to deployment share, booted from USB key

$
0
0

Hi,

I'm trying to deploy Windows 7 Enterprise from MDT 2013, running on Windows Server 2012 R2. The boot key that I use will not have Windows PE connect to the deployment share with the following error message.

"A connection to the deployment share (\\ServerIPAddress\DeploymentShare$) could not be made. Connection OK. Possible course: invalid credentials.

Retry: Try again to connect to the deployment share. Cance: Give up, cancelling any in-progress task sequence."

I can connect to the deployment share through Windows from a UNC path, and from a net use command, but not in Windows PE. Pressing F8 in PE shows that I get a valid IP address, and can ping the deployment server by IP address and FQDN. Net use does not work in PE, and times-out with an error 53, network path not found. There is a firewall between the client and the server, but I do not think it is getting in the way. If it was, I wouldn't be able to connect from Windows. I can't see the log files on PE because C:\MININT is not accessible, no such file.

What could it be?

Thanks


Jason

MDT 2013 - Install drivers from Deployment share NOT USB when booting from USB

$
0
0
A lot of our machines do not have PXE available so we are using a USB stick to image machines. My 'Out of Box' driver size is 9 gigs for all of our different models. I have them sorted using %MAKE%\%MODEL% etc. What I am trying to do is ONLY include my 'PE Drivers' on my USB stick then have MDT inject the drivers (PRE-install) from the Deployment Share (like PXE would). The O/S installs perfectly and this is NOT included on my USB stick, (Operating System Folder is empty on the USB). If I use my Selection Profile (under the General Tab, in the Media001 properties) that includes Everything EXCEPT Operating system and Drivers (includes PE Drivers), no drivers install on the O/S, but everything else installs perfectly. If I use my Selection profile: Everything EXCEPT Operating system (Includes ALL drivers), then the correct drivers install on the O/S along with everything else. End point: Operating system drivers DO NOT install unless they are included on the USB stick. Can we modify the script to copy drivers from the Deployment share if they are not found on the USB media (like the script does for the Operating system)? I know it does this because it does not care if the O/S is on my USB or not, it always installs. This would reduce the USB (MEDIA) size down to 2 gigs which is a lot quicker to copy to USB! In addition, I am not creating any ISOs, I am simply copying the 6 items (Boot, Deploy, EFI, autorun.inf, bootmgr, bootmgr.efi) to the root of my bootable USB. These files appear when I update Media content. If I do create an ISO, this appears in the same folder (\\DeploymentShare$\reminst\Production\Content) as the 6 items I just described.

spikiemikie1970

Sysprep limit - some questions

$
0
0

Is there any way to avoid the sysprep limit? Is there an option in the unattend file?

Should I not have registered Windows? I don't think I was able to install (or check) for updates until I validated Windows.

I would like to keep a VM around of my basic build and run updates on that VM periodically, and then peel an image off as needed (rather than, you know, actually using MDT as it was meant). And while I realize that MDT isn't meant to be used like that, I don't see why I couldn't. Or is that the entire point? To prevent people from doing it my way?


~if this were /. this sig would be funny

An item with the same key has already been added.

$
0
0

When trying to add a Selection Profile in MDT 2013, Server 2012 R2, the process errors out saying "An item with the same key has already been added." I wasn't able to find any information about it anywhere. Anyone have any ideas? I tried different names and different settings. The name does not exist anywhere. Thanks!


Brandon Justice Paychex


Adding Windows 10 to deployment

$
0
0

We are running Server 2012 R2 with MDT 2013 and use it to capture and deploy Windows 8.1 installations.

Right now i want to add a Windows 10 deployment, so I've imported the source files and tried to capture an reference machine.
This is not working, after the source files should be applied it stops with the error that it cannot find a Windows installation.

No specific software or modules were installed for the Windows 10 capture / deployment
My goal is to have 2 installations available, one for Windows 8.1 and one for Windows 10.

What is the best way to achieve this?

My idea is to install the ADK for Windows 10, but i do not want to break the Windows 8.1 deployment.

Thanks,

Dennis

Viewing all 11297 articles
Browse latest View live


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