Windows 10 MININT folder not being cleaned up

May 4, 2016, 4:35 pm

≫ Next: deployment works over the network but not on standalone usb

≪ Previous: Error when capturing

I'm coming to the end of my Windows 10 Deployment testing and almost ready to roll out to a bunch of Venue Tablets.

One thing I am noticing is that the MININT folder does not get cleaned up.

Anyone else having this problem?

↧

deployment works over the network but not on standalone usb

May 4, 2016, 3:07 pm

≫ Next: MDT update 2 offline media fails UEFI secureboot authentication

≪ Previous: Windows 10 MININT folder not being cleaned up

Currently working on Deploying Windows 10 via MDT. It works fine via the normal method of using the litetouch iso but when i try and create the standalone usb iso and build from that, the deployment finishes but it doesnt install half of the software.

Here is the log. Can anyone advise what i can do to ensure it all installs? I have copied and pasted the first app that doesnt actually install even though from the log it says it does.

This all works fine from a network deployment so i am bit puzzled.

<![LOG[Name: Microsoft Office Communicator 2007]LOG]!><time="15:28:25.000+000" date="05-04-2016" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
<![LOG[################]LOG]!><time="15:28:25.000+000" date="05-04-2016" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
<![LOG[Using a local or mapped drive, no connection is required.]LOG]!><time="15:28:25.000+000" date="05-04-2016" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
<![LOG[Change directory: D:\Deploy\Applications\Microsoft Office Communicator 2007]LOG]!><time="15:28:25.000+000" date="05-04-2016" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
<![LOG[Run Command: D:\Deploy\Tools\X64\bddrun.exe OfficeCommunicator2007_Build1.2.EXE /S]LOG]!><time="15:28:25.000+000" date="05-04-2016" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
<![LOG[ZTI installing application ]LOG]!><time="15:28:25.000+000" date="05-04-2016" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
<![LOG[About to run command: D:\Deploy\Tools\X64\bddrun.exe OfficeCommunicator2007_Build1.2.EXE /S]LOG]!><time="15:28:25.000+000" date="05-04-2016" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
<![LOG[Command has been started (process ID 1932)]LOG]!><time="15:28:25.000+000" date="05-04-2016" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
<![LOG[ZTI Heartbeat: command has been running for 0 minutes (process ID 1932)]LOG]!><time="15:28:26.000+000" date="05-04-2016" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
<![LOG[Return code from command = 0]LOG]!><time="15:28:39.000+000" date="05-04-2016" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
<![LOG[Application Microsoft Office Communicator 2007 installed successfully]LOG]!><time="15:28:39.000+000" date="05-04-2016" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
<![LOG[Property InstalledApplications001 is now = {b74a0bab-595b-4a17-a506-7c4146bd873e}]LOG]!><time="15:28:39.000+000" date="05-04-2016" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
<![LOG[Property InstalledApplications002 is now = {34961d5a-a3a6-4a00-9955-9e3ce347d6a5}]LOG]!><time="15:28:39.000+000" date="05-04-2016" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
<![LOG[Property InstalledApplications003 is now = {31b4c4a5-d304-4d72-8a57-ce7275d7df2d}]LOG]!><time="15:28:39.000+000" date="05-04-2016" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
<![LOG[Property InstalledApplications004 is now = {04e18cd9-b22d-4dbf-aab2-ef7a9bb7d389}]LOG]!><time="15:28:39.000+000" date="05-04-2016" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
<![LOG[Property InstalledApplications005 is now = {e6db8353-61dc-4874-be7d-cfc5d4e0d2d5}]LOG]!><time="15:28:39.000+000" date="05-04-2016" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
<![LOG[Property InstalledApplications006 is now = {ba5f4307-22cc-4133-b77f-825d30919604}]LOG]!><time="15:28:39.000+000" date="05-04-2016" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
<![LOG[Property InstalledApplications007 is now = {31036353-9f97-4d0d-9324-14157bf27f7b}]LOG]!><time="15:28:39.000+000" date="05-04-2016" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
<![LOG[Property InstalledApplications008 is now = {45a06686-e2e2-42c0-b4a4-d4a93b44b75d}]LOG]!><time="15:28:39.000+000" date="05-04-2016" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
<![LOG[Property InstalledApplications009 is now = {85e53573-fc92-4967-a475-216b9ed6459a}]LOG]!><time="15:28:39.000+000" date="05-04-2016" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
<![LOG[ZTIApplications processing completed successfully.]LOG]!><time="15:28:39.000+000" date="05-04-2016" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
<![LOG[Microsoft Deployment Toolkit version: 6.3.8298.1000]LOG]!><time="15:28:40.000+000" date="05-04-2016" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
<![LOG[The task sequencer log is located at C:\Users\ADMINI~1\AppData\Local\Temp\SMSTSLog\SMSTS.LOG. For task sequence failures, please consult this log.]LOG]!><time="15:28:40.000+000" date="05-04-2016" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
<![LOG[Language/Locale Identified (in order of precedence): 3081,0C09,0x0C09,9,0009,0x0009]LOG]!><time="15:28:40.000+000" date="05-04-2016" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
<![LOG[Mandatory Single Application install indicated. Guid: {a326a6d6-c74b-471d-9cde-273ad14d374c}]LOG]!><time="15:28:40.000+000" date="05-04-2016" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
<![LOG[################]LOG]!><time="15:28:40.000+000" date="05-04-2016" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
<![LOG[Entry: {a326a6d6-c74b-471d-9cde-273ad14d374c}]LOG]!><time="15:28:40.000+000" date="05-04-2016" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
<![LOG[Name: LiveMeeting 8.0.6362.249]LOG]!><time="15:28:40.000+000" date="05-04-2016" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
<![LOG[################]LOG]!><time="15:28:40.000+000" date="05-04-2016" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
<![LOG[Using a local or mapped drive, no connection is required.]LOG]!><time="15:28:40.000+000" date="05-04-2016" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
<![LOG[Change directory: D:\Deploy\Applications\LiveMeeting 8.0.6362.249]LOG]!><time="15:28:40.000+000" date="05-04-2016" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
<![LOG[Run Command: D:\Deploy\Tools\X64\bddrun.exe Install.bat]LOG]!><time="15:28:40.000+000" date="05-04-2016" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
<![LOG[ZTI installing application ]LOG]!><time="15:28:40.000+000" date="05-04-2016" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
<![LOG[About to run command: D:\Deploy\Tools\X64\bddrun.exe Install.bat]LOG]!><time="15:28:40.000+000" date="05-04-2016" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
<![LOG[Command has been started (process ID 4700)]LOG]!><time="15:28:40.000+000" date="05-04-2016" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
<![LOG[ZTI Heartbeat: command has been running for 0 minutes (process ID 4700)]LOG]!><time="15:28:40.000+000" date="05-04-2016" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
<![LOG[Return code from command = 1618]LOG]!><time="15:28:44.000+000" date="05-04-2016" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
<![LOG[Application LiveMeeting 8.0.6362.249 returned an unexpected return code: 1618]LOG]!><time="15:28:44.000+000" date="05-04-2016" component="ZTIApplications" context="" type="3" thread="" file="ZTIApplications">
<![LOG[Property InstalledApplications001 is now = {b74a0bab-595b-4a17-a506-7c4146bd873e}]LOG]!><time="15:28:44.000+000" date="05-04-2016" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
<![LOG[Property InstalledApplications002 is now = {34961d5a-a3a6-4a00-9955-9e3ce347d6a5}]LOG]!><time="15:28:44.000+000" date="05-04-2016" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
<![LOG[Property InstalledApplications003 is now = {31b4c4a5-d304-4d72-8a57-ce7275d7df2d}]LOG]!><time="15:28:44.000+000" date="05-04-2016" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
<![LOG[Property InstalledApplications004 is now = {04e18cd9-b22d-4dbf-aab2-ef7a9bb7d389}]LOG]!><time="15:28:44.000+000" date="05-04-2016" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
<![LOG[Property InstalledApplications005 is now = {e6db8353-61dc-4874-be7d-cfc5d4e0d2d5}]LOG]!><time="15:28:44.000+000" date="05-04-2016" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
<![LOG[Property InstalledApplications006 is now = {ba5f4307-22cc-4133-b77f-825d30919604}]LOG]!><time="15:28:44.000+000" date="05-04-2016" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
<![LOG[Property InstalledApplications007 is now = {31036353-9f97-4d0d-9324-14157bf27f7b}]LOG]!><time="15:28:44.000+000" date="05-04-2016" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
<![LOG[Property InstalledApplications008 is now = {45a06686-e2e2-42c0-b4a4-d4a93b44b75d}]LOG]!><time="15:28:44.000+000" date="05-04-2016" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
<![LOG[Property InstalledApplications009 is now = {85e53573-fc92-4967-a475-216b9ed6459a}]LOG]!><time="15:28:44.000+000" date="05-04-2016" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
<![LOG[Property InstalledApplications010 is now = {a326a6d6-c74b-471d-9cde-273ad14d374c}]LOG]!><time="15:28:44.000+000" date="05-04-2016" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
<![LOG[ZTIApplications processing completed successfully.]LOG]!><time="15:28:44.000+000" date="05-04-2016" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
<![LOG[Microsoft Deployment Toolkit version: 6.3.8298.1000]LOG]!><time="15:28:45.000+000" date="05-04-2016" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
<![LOG[The task sequencer log is located at C:\Users\ADMINI~1\AppData\Local\Temp\SMSTSLog\SMSTS.LOG. For task sequence failures, please consult this log.]LOG]!><time="15:28:45.000+000" date="05-04-2016" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
<![LOG[Language/Locale Identified (in order of precedence): 3081,0C09,0x0C09,9,0009,0x0009]LOG]!><time="15:28:45.000+000" date="05-04-2016" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
<![LOG[Mandatory Single Application install indicated. Guid: {40110360-5c6a-4cf3-a048-9ddd45912808}]LOG]!><time="15:28:45.000+000" date="05-04-2016" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
<![LOG[################]LOG]!><time="15:28:45.000+000" date="05-04-2016" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
<![LOG[Entry: {40110360-5c6a-4cf3-a048-9ddd45912808}]LOG]!><time="15:28:45.000+000" date="05-04-2016" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
<![LOG[Name: Outlook Add-in 8.0.6362.249]LOG]!><time="15:28:45.000+000" date="05-04-2016" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
<![LOG[################]LOG]!><time="15:28:45.000+000" date="05-04-2016" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
<![LOG[Using a local or mapped drive, no connection is required.]LOG]!><time="15:28:45.000+000" date="05-04-2016" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
<![LOG[Change directory: D:\Deploy\Applications\Outlook Add-in 8.0.6362.249]LOG]!><time="15:28:45.000+000" date="05-04-2016" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
<![LOG[Run Command: D:\Deploy\Tools\X64\bddrun.exe Install.bat]LOG]!><time="15:28:45.000+000" date="05-04-2016" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
<![LOG[ZTI installing application ]LOG]!><time="15:28:45.000+000" date="05-04-2016" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
<![LOG[About to run command: D:\Deploy\Tools\X64\bddrun.exe Install.bat]LOG]!><time="15:28:45.000+000" date="05-04-2016" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">

↧

MDT update 2 offline media fails UEFI secureboot authentication

May 1, 2016, 7:58 am

≫ Next: How to deploy Win 10 + Legacy Software + Capture

≪ Previous: deployment works over the network but not on standalone usb

I am currently the head of a project where I need to deploy Windows 10 to 100 tablets a week. For some retarded reason which I can still not accept, I am unable to gain access to or permission to set up a WDS instance, despite being a member of a domain network. Anyway, this has left me few options, so I have chosen to create offline bootable MDT media on external disks and deploy operating systems this way. I am able to create the content easily enough, but when I attempt to boot from the external device, I get an error message saying that secureboot failed to authenticate the bootable image, "ACCESS DENIED". When I go into the bios and disable secure boot, it works like a dream, but as I have to do this for every single one of the 100 devices a week I have to image, this can take a good bit of time. Am I doing something wrong that would cause this issue? If not, is there a solution? What is the root cause?

↧

How to deploy Win 10 + Legacy Software + Capture

May 5, 2016, 4:49 am

≫ Next: Task Sequence doesn't start on new WDS Server 2012 (Video)

≪ Previous: MDT update 2 offline media fails UEFI secureboot authentication

Hi All...

I'm currently using MDT 2013 U2. I'd like to create a task sequence where it will push out Windows 10 to a Dell OptiPlex and before capturing it, that it will give me enough time to install 3 legacy software programs I have that I don't believe I'm able to deploy as a package / application.

Is this possible to do with MDT 2013 U2? What is the best way for me to be able to do this?

Thanks!

Thanks... Frank

↧

Task Sequence doesn't start on new WDS Server 2012 (Video)

May 5, 2016, 3:54 am

≫ Next: Problem Installing .NET 3.5 on Windows 8.1 with MDT 2013

≪ Previous: How to deploy Win 10 + Legacy Software + Capture

Just built a new 2012 server and included WDS. Any have any idea why this is happening? I've never had a problem before!

Video of Issue

All the settings are the same as on our previous server.

Here's the CustomSettings.ini, I've removed Sensitive information.

[Settings]
Priority=Default

[Default]
OSInstall=Y
SkipFinalSummary=YES
SkipProductKey=YES
SkipComputerBackup=YES
SkipUserData=YES
SkipDomainMembership=YES
SkipApplications=NO
SkipAdminPassword=YES
SkipComputerName=YES
SkipTaskSequence=NO
SkipBitLocker=YES
FinishAction=LOGOFF

KeyboardLocalePE=0809:00000809
KeyboardLocale=0809:00000809

OSDComputerName=%SERIALNUMBER%
MachineObjectOU=OU=New Computers,DC=zincahead,DC=local

TimeZoneName=GMT Standard Time
UserLocale=en-GB
UILanguage=en-US

WSUSServer=http://syd-dc-01
EventService=http://syd-dc-01:9800

And the BootStrap.ini

[Settings]
Priority=Default

[Default]
DeployRoot=\\SYD-DC-01\DeploymentShare$

SkipBDDWelcome=YES
KeyboardLocalePE=0809:00000809
KeyboardLocale=0809:00000809

↧

Problem Installing .NET 3.5 on Windows 8.1 with MDT 2013

June 25, 2015, 7:02 am

≫ Next: MDT 2013 & Windows 8.1: Installing .NET Framework 3.5 from Task Sequence

≪ Previous: Task Sequence doesn't start on new WDS Server 2012 (Video)

I have been attempting to get .NET 3.5 installed in our 8.1 Enterprise builds and I continue to receive DISM errors. I have added a TS step that installs the 3.5 feature but continue to get errors. This worked in the past but I have modified the task sequence slightly to add windows update roll-up packages in the Apply Patches step.

I also tried running an application using the DISM commands to install this directly from the source path, but it always fails. What am I missing here? Is it possible that adding the update packages will make this fail?

↧

MDT 2013 & Windows 8.1: Installing .NET Framework 3.5 from Task Sequence

January 7, 2014, 8:48 am

≫ Next: How to require an administrator password to allow MDT deployment to start

≪ Previous: Problem Installing .NET 3.5 on Windows 8.1 with MDT 2013

Hello, I'm having issues with MDT 2013 and installed .NET Framework 3.5 on Windows 8.1 Enterprise x64 via the Standard Client Task Sequence. I been able to get it to process and MDT says that it installed but when I check the machine it is not.

CustomSettings.ini includes:

WindowsSource=%DEPLOYROOT%\Operating Systems\Windows 8.1 Enterprise x64\sources\sxs
SkipRoles=YES

Standard Client Task Sequence

Install Roles and Features in the State Restore (right before Post Application Windows Update)
Windows 8.1 is selected as the Operating System and .NET Framework 3.5 is checked (along with sub checkboxes)

Again, it doesn't give me an error it says it installs but when I check the machine it is not installed......

I also have Windows Updates enabled in the State Restore Task Sequence section.

↧

How to require an administrator password to allow MDT deployment to start

May 5, 2016, 6:58 pm

≫ Next: MDT 2013 Update 2 - Failed to save environment to (80070057)_ Error during deployment

≪ Previous: MDT 2013 & Windows 8.1: Installing .NET Framework 3.5 from Task Sequence

Hi everyone,

I'm looking for a way to require that users who request an MDT deployment be obligated to provide their credentials to be able to proceed with the MDT deployment request.

We used to have WDS ask for confirmation through the "pending devices" tab in the snap-in, but this required the IT techs to either have the WDS snap-in installed on their computer, or to remote login on the deployment server, which isn't very practical.

Thanks in advance for the help :)

↧

MDT 2013 Update 2 - Failed to save environment to (80070057)_ Error during deployment

May 5, 2016, 10:24 am

≫ Next: Windows 10 - Surface Pro 4 - Drivers

≪ Previous: How to require an administrator password to allow MDT deployment to start

Hello,

I am currently experiencing an issue with deploying a custom WIM using MDT 2013 Update 2. The same task and WIM successfully deployed out to this set of PCs before upgrading to Update 2.

My WIM is Windows 7 Enterprise x64 - created virtually using VMware. Successfully deployed and is still deploying to one set of machines - Dell laptops. But having an issue with Fuji Siemens PCs. Below is the error I am seeing. This is right after the operating system has finished applying and the unattend task has ran and is about to reboot to run the sysprep but this error appears.

Taking a closer look at the SMSTS.log seems to have lots of errors here is a sample.

D:\_SMSTaskSequence does not exist TSManager 05/05/2016 13:55:15 1212 (0x04BC) Failed to create D:\_SMSTaskSequence (3) TSManager 05/05/2016 13:55:15 1212 (0x04BC) Failed to create user-specified local data path D:\_SMSTaskSequence. Error 0x80070003 TSManager 05/05/2016 13:55:15 1212 (0x04BC) We do not find an available volume to store the local data path TSManager 05/05/2016 13:55:15 1212 (0x04BC) Set a global environment variable _SMSTSNextInstructionPointer=54 TSManager 05/05/2016 13:55:15 1212 (0x04BC) Set a TS execution environment variable _SMSTSNextInstructionPointer=54 TSManager 05/05/2016 13:55:15 1212 (0x04BC) Set a global environment variable _SMSTSInstructionStackString=47 TSManager 05/05/2016 13:55:15 1212 (0x04BC) Set a TS execution environment variable _SMSTSInstructionStackString=47 TSManager 05/05/2016 13:55:15 1212 (0x04BC) Save the current environment block TSManager 05/05/2016 13:55:15 1212 (0x04BC) Failed to save environment to (80070057) TSManager 05/05/2016 13:55:15 1212 (0x04BC) Failed to save the current environment block. This is usually caused by a problem with the program. Please check the Microsoft Knowledge Base to determine if this is a known issue or contact Microsoft Support Services for further assistance. The parameter is incorrect. (Error: 80070057; Source: Windows) TSManager 05/05/2016 13:55:15 1212 (0x04BC) Failed to persist execution state. Error 0x(80070057) TSManager 05/05/2016 13:55:15 1212 (0x04BC) Failed to save execution state and environment to local hard disk TSManager 05/05/2016 13:55:15 1212 (0x04BC) The task sequence execution engine can not reboot the machine because we failed to persist execution environment TSManager 05/05/2016 13:55:15 1212 (0x04BC) Fatal error is returned in check for reboot request of the action (Restart computer). Unspecified error (Error: 80004005; Source: Windows) TSManager 05/05/2016 13:55:15 1212 (0x04BC) An error (0x80004005) is encountered in execution of the task sequence TSManager 05/05/2016 13:55:15 1212 (0x04BC) Executing in non SMS standalone mode. Ignoring send a task execution status message request TSManager 05/05/2016 13:55:15 1212 (0x04BC) Task Sequence Engine failed! Code: 80004005 TSManager 05/05/2016 13:55:15 1212 (0x04BC) **************************************************************************** TSManager 05/05/2016 13:55:15 1212 (0x04BC) Task sequence execution failed with error code 80004005 TSManager 05/05/2016 13:55:15 1212 (0x04BC)

I can't post any images so am unable to show the exact error during deployment.

Any ideas? Am totally stuck and out of ideas. I have tested running the TS without it injecting any drivers to see if it was a driver issue but that brings up the same issue.

Thanks.

↧

Windows 10 - Surface Pro 4 - Drivers

May 6, 2016, 12:17 am

≫ Next: Tagerdrive is dirty - how to fix?

≪ Previous: MDT 2013 Update 2 - Failed to save environment to (80070057)_ Error during deployment

Hey,

I'm testing deployment of Windows 10 (Pro x64) on a Surface Pro 4 tablet. I have imported the entire April driver pack (https://www.microsoft.com/en-us/download/details.aspx?id=49498) for the Surface. Deployment in general is fine, except there are some drivers missing post-deployment.

Interestingly, if I manually update the drivers, using the MDT Out-Of-Box-Drivers folder as the source, it picks up all the missing drivers.

So why are they not being injected/picked up by the initial deployment. As I say, some of the drivers are being picked up fine, so selection profiles etc. seem to be OK.

Thanks.

↧

Tagerdrive is dirty - how to fix?

May 6, 2016, 2:32 am

≫ Next: Override path to CustomSettings.ini in Bootstrap.ini

≪ Previous: Windows 10 - Surface Pro 4 - Drivers

Hi,

I am trying to troubleshoot why my Windows 10 x64 deployment of a captured image is hanging for approx. 15 minutes in the Staterestore phase. I guess it hangs while repairing the dirty targetdrive, but how can I fix this? Filesystem is fine before sysprep and capture.

Thse are the lines from BDD.log where it hangs:

Property PHASE is now = STATERESTORE	ZTINextPhase	06-05-2016 09:50:24	0 (0x0000)
ZTINextPhase COMPLETED.  Return Value = 0	ZTINextPhase	06-05-2016 09:50:24	0 (0x0000)
ZTINextPhase processing completed successfully.	ZTINextPhase	06-05-2016 09:50:24	0 (0x0000)
Command completed, return code = -2147021886	LiteTouch	06-05-2016 09:50:24	0 (0x0000)
Property LTIDirty is now = FALSE	LiteTouch	06-05-2016 09:50:24	0 (0x0000)
If there is a drive letter defined, make sure we clear it now so we can *force* recalcutation.	LiteTouch	06-05-2016 09:50:24	0 (0x0000)
Property OSDTargetDriveCache is now = DIRTY	LiteTouch	06-05-2016 09:50:24	0 (0x0000)
LTI initiating task sequence-requested reboot.	LiteTouch	06-05-2016 09:50:24	0 (0x0000)
Property start is now = 	LiteTouch	06-05-2016 10:08:37	0 (0x0000)
Microsoft Deployment Toolkit version: 6.3.8330.1000	LiteTouch	06-05-2016 10:08:37	0 (0x0000)
ZTIUtility!GetAllFixedDrives (False)	LiteTouch	06-05-2016 10:08:38	0 (0x0000)
New ZTIDisk : \\MININT-FU2S8LH\root\cimv2:Win32_DiskDrive.DeviceID="\\\\.\\PHYSICALDRIVE0"	LiteTouch	06-05-2016 10:08:38	0 (0x0000)
New ZTIDiskPartition : \\MININT-FU2S8LH\root\cimv2:Win32_DiskPartition.DeviceID="Disk #0, Partition #1"    \\MININT-FU2S8LH\root\cimv2:Win32_LogicalDisk.DeviceID="C:"	LiteTouch	06-05-2016 10:08:38	0 (0x0000)
New ZTIDisk : \\MININT-FU2S8LH\root\cimv2:Win32_DiskDrive.DeviceID="\\\\.\\PHYSICALDRIVE0"	LiteTouch	06-05-2016 10:08:38	0 (0x0000)
New ZTIDisk : \\MININT-FU2S8LH\root\cimv2:Win32_DiskDrive.DeviceID="\\\\.\\PHYSICALDRIVE0"	LiteTouch	06-05-2016 10:08:38	0 (0x0000)
ZTIUtility!GetAllFixedDrives =   C: 	LiteTouch	06-05-2016 10:08:38	0 (0x0000)
Found existing task sequence state information in C:\_SMSTaskSequence, will continue	LiteTouch	06-05-2016 10:08:38	0 (0x0000)
Property LTIDirtyOS is now = FALSE	LiteTouch	06-05-2016 10:08:38	0 (0x0000)

↧

Override path to CustomSettings.ini in Bootstrap.ini

May 6, 2016, 2:45 am

≫ Next: MDT - DomainOU.XML display friendly names

≪ Previous: Tagerdrive is dirty - how to fix?

Hi!

Is it possible to override path to the CustomSettings.ini through the Bootstrap.ini? So, I'm having a script that creates a VM, inserts an LTI ISO and I need the VM to process the proper customsettings.ini (that's pre-created by the script as well). The closest I could get is to hardcode a TS ID into the default customsettings and have the Gather step to process rules from a a pre-created 'CustomSettings_<MAC ADDRESS>.ini' file, but I'd prefer bootstrap.ini to launch 'CustomSettings_<MAC ADDRESS>.ini' directly to have greater flexibility. I know that this flexibility can be achieved with SQL Database, but in my case this option is not available.

Any ideas?

Thanks,

Ivan

Ivan Seriavin

↧

MDT - DomainOU.XML display friendly names

May 6, 2016, 3:08 am

≫ Next: Sysprep and Capture of Windows 7 SP1 x64 VMware VM Failing to Boot into WinPE 10

≪ Previous: Override path to CustomSettings.ini in Bootstrap.ini

Hello,

I am wondering if it's possible to display friendly names in MDT winpe instead of the full LDAP name?

So, for example, display "Encrypted Laptops" instead of "OU=x3,OU=x2,OU=x1,DC=x,DC=x,DC=x"

Hope this makes sense!

↧

Sysprep and Capture of Windows 7 SP1 x64 VMware VM Failing to Boot into WinPE 10

May 5, 2016, 4:06 pm

≫ Next: MDT Wizard Studio

≪ Previous: MDT - DomainOU.XML display friendly names

I have a process to build my custom images using MDT 2013 on a series of VMware Workstation VMs. I'm not sure what has changed, but when I try to run my standard build/sysprep/capture task sequence for a Windows 7 SP1 x64 system, the systems gets to the point where it applies PE on the system, runs sysprep, then modifies the BCD so that the system will boot into PE.

The system reboots, PE starts, and when it gets to the point where the Windows logo appears on screen, it fails with a 0xc000000e error.The same VM successfully boots into PE via PXE to start the process.

I'm using MDT 2013 U2 with WinPE 10. Everything has been working fine for ages, but something has apparently changed. The same build/capture works as expected for Windows 10 on VMware, and also with Windows 7 SP1 x64 on Hyper-V. Whatever the issue is, it is specific to VMware Workjstation (v12 loaded on my build system).

Been digging around, but at the point now where I'm out of things to try and not sure what to look at next.

Scott Ladewig http://www.ladewig.com

↧

MDT Wizard Studio

May 6, 2016, 5:16 am

≫ Next: Remove application from Deployment Share

≪ Previous: Sysprep and Capture of Windows 7 SP1 x64 VMware VM Failing to Boot into WinPE 10

Hey Guys,

I am a rookie when it comes to HTML and Wizard Studio. I need help with disabling the "Next" button on the pane until a selection is made (like the TS pane).

I created a very simple pane with a drop down to select a country. I want the pane to open without a country selected and with the Next button disabled until one is selected.

I included my xml and screen shot of pane.

Thanks for any help you can provide.
Dave

<Wizard><Global></Global><Pane id="MyCountryCode" title="Country"><Body><![CDATA[<H1>Select your Country:</H1><table style="width: 100%;"><tr><td width="80px"><img src="DeployWiz_Language.png"></td><td align="left"><select name="MYCountryCode" class=WideEdit" language=vbscript ><option value="AF">Afghanistan</option><option value="AX">Åland Islands</option><option value="AL">Albania</option><option value="DZ">Algeria</option><option value="AS">American Samoa</option><option value="AD">Andorra</option><option value="AO">Angola</option><option value="AI">Anguilla</option><option value="AQ">Antarctica</option><option value="AG">Antigua and Barbuda</option><option value="AR">Argentina</option><option value="AM">Armenia</option><option value="AW">Aruba</option><option value="AU">Australia</option><option value="AT">Austria</option><option value="AZ">Azerbaijan</option><option value="BS">Bahamas</option><option value="BH">Bahrain</option><option value="BD">Bangladesh</option><option value="BB">Barbados</option><option value="BY">Belarus</option><option value="BE">Belgium</option><option value="BZ">Belize</option><option value="BJ">Benin</option><option value="BM">Bermuda</option><option value="BT">Bhutan</option><option value="BO">Bolivia</option><option value="BA">Bosnia and Herzegovina</option><option value="BW">Botswana</option><option value="BV">Bouvet Island</option><option value="BR">Brazil</option><option value="IO">British Indian Ocean Territory</option><option value="BN">Brunei Darussalam</option><option value="BG">Bulgaria</option><option value="BF">Burkina Faso</option><option value="BI">Burundi</option><option value="KH">Cambodia</option><option value="CM">Cameroon</option><option value="CA">Canada</option><option value="CV">Cape Verde</option><option value="BQ">Caribbean Netherlands </option><option value="KY">Cayman Islands</option><option value="CF">Central African Republic</option><option value="TD">Chad</option><option value="CL">Chile</option><option value="CN">China</option><option value="CX">Christmas Island</option><option value="CC">Cocos (Keeling) Islands</option><option value="CO">Colombia</option><option value="KM">Comoros</option><option value="CG">Congo</option><option value="CD">Congo, Democratic Republic of</option><option value="CK">Cook Islands</option><option value="CR">Costa Rica</option><option value="CI">Côte d'Ivoire</option><option value="HR">Croatia</option><option value="CU">Cuba</option><option value="CW">Curaçao</option><option value="CY">Cyprus</option><option value="CZ">Czech Republic</option><option value="DK">Denmark</option><option value="DJ">Djibouti</option><option value="DM">Dominica</option><option value="DO">Dominican Republic</option><option value="EC">Ecuador</option><option value="EG">Egypt</option><option value="SV">El Salvador</option><option value="GQ">Equatorial Guinea</option><option value="ER">Eritrea</option><option value="EE">Estonia</option><option value="ET">Ethiopia</option><option value="FK">Falkland Islands</option><option value="FO">Faroe Islands</option><option value="FJ">Fiji</option><option value="FI">Finland</option><option value="FR">France</option><option value="GF">French Guiana</option><option value="PF">French Polynesia</option><option value="TF">French Southern Territories</option><option value="GA">Gabon</option><option value="GM">Gambia</option><option value="GE">Georgia</option><option value="DE">Germany</option><option value="GH">Ghana</option><option value="GI">Gibraltar</option><option value="GR">Greece</option><option value="GL">Greenland</option><option value="GD">Grenada</option><option value="GP">Guadeloupe</option><option value="GU">Guam</option><option value="GT">Guatemala</option><option value="GG">Guernsey</option><option value="GN">Guinea</option><option value="GW">Guinea-Bissau</option><option value="GY">Guyana</option><option value="HT">Haiti</option><option value="HM">Heard and McDonald Islands</option><option value="HN">Honduras</option><option value="HK">Hong Kong</option><option value="HU">Hungary</option><option value="IS">Iceland</option><option value="IN">India</option><option value="ID">Indonesia</option><option value="IR">Iran</option><option value="IQ">Iraq</option><option value="IE">Ireland</option><option value="IM">Isle of Man</option><option value="IL">Israel</option><option value="IT">Italy</option><option value="JM">Jamaica</option><option value="JP">Japan</option><option value="JE">Jersey</option><option value="JO">Jordan</option><option value="KZ">Kazakhstan</option><option value="KE">Kenya</option><option value="KI">Kiribati</option><option value="KW">Kuwait</option><option value="KG">Kyrgyzstan</option><option value="LA">Lao People's Democratic Republic</option><option value="LV">Latvia</option><option value="LB">Lebanon</option><option value="LS">Lesotho</option><option value="LR">Liberia</option><option value="LY">Libya</option><option value="LI">Liechtenstein</option><option value="LT">Lithuania</option><option value="LU">Luxembourg</option><option value="MO">Macau</option><option value="MK">Macedonia</option><option value="MG">Madagascar</option><option value="MW">Malawi</option><option value="MY">Malaysia</option><option value="MV">Maldives</option><option value="ML">Mali</option><option value="MT">Malta</option><option value="MH">Marshall Islands</option><option value="MQ">Martinique</option><option value="MR">Mauritania</option><option value="MU">Mauritius</option><option value="YT">Mayotte</option><option value="MX">Mexico</option><option value="FM">Micronesia, Federated States of</option><option value="MD">Moldova</option><option value="MC">Monaco</option><option value="MN">Mongolia</option><option value="ME">Montenegro</option><option value="MS">Montserrat</option><option value="MA">Morocco</option><option value="MZ">Mozambique</option><option value="MM">Myanmar</option><option value="NA">Namibia</option><option value="NR">Nauru</option><option value="NP">Nepal</option><option value="NC">New Caledonia</option><option value="NZ">New Zealand</option><option value="NI">Nicaragua</option><option value="NE">Niger</option><option value="NG">Nigeria</option><option value="NU">Niue</option><option value="NF">Norfolk Island</option><option value="KP">North Korea</option><option value="MP">Northern Mariana Islands</option><option value="NO">Norway</option><option value="OM">Oman</option><option value="PK">Pakistan</option><option value="PW">Palau</option><option value="PS">Palestine, State of</option><option value="PA">Panama</option><option value="PG">Papua New Guinea</option><option value="PY">Paraguay</option><option value="PE">Peru</option><option value="PH">Philippines</option><option value="PN">Pitcairn</option><option value="PL">Poland</option><option value="PT">Portugal</option><option value="PR">Puerto Rico</option><option value="QA">Qatar</option><option value="RE">Réunion</option><option value="RO">Romania</option><option value="RU">Russian Federation</option><option value="RW">Rwanda</option><option value="BL">Saint Barthélemy</option><option value="SH">Saint Helena</option><option value="KN">Saint Kitts and Nevis</option><option value="LC">Saint Lucia</option><option value="VC">Saint Vincent and the Grenadines</option><option value="MF">Saint-Martin (France)</option><option value="WS">Samoa</option><option value="SM">San Marino</option><option value="ST">Sao Tome and Principe</option><option value="SA">Saudi Arabia</option><option value="SN">Senegal</option><option value="RS">Serbia</option><option value="SC">Seychelles</option><option value="SL">Sierra Leone</option><option value="SG">Singapore</option><option value="SX">Sint Maarten (Dutch part)</option><option value="SK">Slovakia</option><option value="SI">Slovenia</option><option value="SB">Solomon Islands</option><option value="SO">Somalia</option><option value="ZA">South Africa</option><option value="GS">South Georgia and the South Sandwich Islands</option><option value="KR">South Korea</option><option value="SS">South Sudan</option><option value="ES">Spain</option><option value="LK">Sri Lanka</option><option value="PM">St. Pierre and Miquelon</option><option value="SD">Sudan</option><option value="SR">Suriname</option><option value="SJ">Svalbard and Jan Mayen Islands</option><option value="SZ">Swaziland</option><option value="SE">Sweden</option><option value="CH">Switzerland</option><option value="SY">Syria</option><option value="TW">Taiwan</option><option value="TJ">Tajikistan</option><option value="TZ">Tanzania</option><option value="TH">Thailand</option><option value="NL">The Netherlands</option><option value="TL">Timor-Leste</option><option value="TG">Togo</option><option value="TK">Tokelau</option><option value="TO">Tonga</option><option value="TT">Trinidad and Tobago</option><option value="TN">Tunisia</option><option value="TR">Turkey</option><option value="TM">Turkmenistan</option><option value="TC">Turks and Caicos Islands</option><option value="TV">Tuvalu</option><option value="UG">Uganda</option><option value="UA">Ukraine</option><option value="AE">United Arab Emirates</option><option value="GB">United Kingdom</option><option value="US">United States</option><option value="UM">United States Minor Outlying Islands</option><option value="UY">Uruguay</option><option value="UZ">Uzbekistan</option><option value="VU">Vanuatu</option><option value="VA">Vatican</option><option value="VE">Venezuela</option><option value="VN">Vietnam</option><option value="VG">Virgin Islands (British)</option><option value="VI">Virgin Islands (U.S.)</option><option value="WF">Wallis and Futuna Islands</option><option value="EH">Western Sahara</option><option value="YE">Yemen</option><option value="ZM">Zambia</option><option value="ZW">Zimbabwe</option></select></td></tr></table>

]]></Body></Pane></Wizard>

↧

Remove application from Deployment Share

April 27, 2016, 2:27 pm

≫ Next: Windows boot looping after upgrading from 7 to 10

≪ Previous: MDT Wizard Studio

If I remove an application from the deployment share do I need to re-capture the reference image?

↧

Windows boot looping after upgrading from 7 to 10

March 11, 2016, 9:13 am

≫ Next: MDT 2013 Update 2. No copy of DISM in a new deployment share? No \Servicing folder?

≪ Previous: Remove application from Deployment Share

I'm fairly new to MDT. My company has tasked me to use MDT 2013 Update 1 to upgrade our user base (10,000+ machines) from Windows 7 Enterprise 64 to Window 10 Enterprise 64. My tests have gone pretty good so far, I've built a driver collection and selection profiles, I have Applications imported and set in the task sequence, etc. And everything seems to work great. I run the upgrade task sequence on a target machine, I get no errors, and once finished the system is on Windows 10 and I'm able to login.

The problem occurs after the first manual reboot. Once you do a restart, or shutdown and power back up, it gets stuck in a boot loop. I'll see the blue windows 10 logo, with the little spinning circle beneath it, the screen will flicker a couple times, and then it reboots and does the same thing. I've dug through the logs but don't see any errors or warnings. One other strange thing though: I booted one of the boot looping machines from the WIndows 10 install media, with the intention of trying the repair console. Upon booting from the install media the first window that pops up tells me "It looks like you started an upgrade and booted from installation media. If you want to continue with the upgrade, remove the media from your PC and click Yes. If you want to perform a clean installation instead, click No."

So it seems like it still thinks its in the upgrade process. But MDT says it has finished. I have no idea whats happening here.

Thanks for any help or guidance anyone can give.

↧

MDT 2013 Update 2. No copy of DISM in a new deployment share? No \Servicing folder?

May 6, 2016, 8:40 am

≫ Next: Unable to Find CustomSettings.ini (Video)

≪ Previous: Windows boot looping after upgrading from 7 to 10

I'm trying to troubleshoot a failed deployment, and I've come across an inconsistency that I would like some clarification on.

Last week we upgraded from MDT 2013 to MDT 2013 Update 2. On SOME deployments, we're getting the following error:

FAILURE ( 5624 ): 1: Run DISM: /Apply-Image /ImageFile:"\\[SERVER]\Deploy$\Operating Systems\Win7x64-Office-2016-02-18\Sources\install.wim" /Index:1 /ApplyDir:C:

In troubleshooting this, I noticed that there is no DISM.EXE anywhere in our Deploy$ share. This share was upgraded from 2013 to 2013 U2.

So I created a new deployment share, 'Test$', and noticed that it had a different amount of files and folders in it compared to the Deploy$ share.

Deploy$:

$OEM$
Applications
Boot
Captures
Control
Drivers
Logs
Operating Systems
Out-of-Box Drivers
Packages
Scripts
Servicing
Templates
Tools
Audit.log

Test$

$OEM$
Applications
Boot
Captures
Control
Operating Systems
Out-of-Box Drivers
Packages
Scripts
Templates
Tools
Audit.log

Is there supposed to a \Servicing folder in my shares? Shouldn't there be a copy of DISM in the \Tools folder on the shares? Is my installation of MDT jacked?

↧

Unable to Find CustomSettings.ini (Video)

May 5, 2016, 3:54 am

≫ Next: "System.Management.Automation.CmdletInvocationException: Index was out of range" when trying to import drivers.

≪ Previous: MDT 2013 Update 2. No copy of DISM in a new deployment share? No \Servicing folder?

Just built a new 2012 server and included WDS. Any have any idea why this is happening? I've never had a problem before!

Video of Issue

All the settings are the same as on our previous server.

Here's the CustomSettings.ini, I've removed Sensitive information.

And the BootStrap.ini

[Settings]
Priority=Default

[Default]
DeployRoot=\\SYD-DC-01\DeploymentShare$

SkipBDDWelcome=YES
KeyboardLocalePE=0809:00000809
KeyboardLocale=0809:00000809

↧

"System.Management.Automation.CmdletInvocationException: Index was out of range" when trying to import drivers.

May 6, 2016, 3:10 pm

≫ Next: Unsupported 16-bit application - smsboot.exe

≪ Previous: Unable to Find CustomSettings.ini (Video)

When trying to import Windows 10 x64 drivers for the Dell Precision 5510 laptop, using the cab file here.

Part way through I get this error:

Scanning directories for the count of INFs to import.
Expanding CAB file \\Server\Share\Drivers\DriverSourceFiles-MDT\x64_win10\Precision 5510\chipset\3K80H_A00-00\drivers\stdcfltn.cab
Expanding CAB file \\Server\Share\Drivers\DriverSourceFiles-MDT\x64_win10\Precision 5510\communication\5PMW3_A00-00\Win64\Data1.cab
Expanding CAB file \\Server\Share\Drivers\DriverSourceFiles-MDT\x64_win10\Precision 5510\video\PFWXP_A00-00\Windows10-x64\KT112452.inf\20.19.15.4331\DisplayAudiox64.cab
Performing the operation "import" on target "Out-of-box drivers".
Creating new item named Realtek Semiconductor Corp. MEDIA HDX861A.inf 6.0.1.7628 at DS001:\Out-of-Box Drivers\x64_win10\Precision 5510.
Creating new item named Realtek Semiconductor Corp. MEDIA HDXAMA.inf 6.0.1.7628 at DS001:\Out-of-Box Drivers\x64_win10\Precision 5510.
Creating new item named Realtek Semiconductor Corp. MEDIA HDXAMA3.inf 6.0.1.7628 at DS001:\Out-of-Box Drivers\x64_win10\Precision 5510.
Creating new item named Realtek Semiconductor Corp. MEDIA HDXBPCAI.inf 6.0.1.7628 at DS001:\Out-of-Box Drivers\x64_win10\Precision 5510.
Creating new item named Realtek Semiconductor Corp. MEDIA HDXBPCAS.inf 6.0.1.7628 at DS001:\Out-of-Box Drivers\x64_win10\Precision 5510.
Creating new item named Realtek Semiconductor Corp. MEDIA HDXCONEQ.inf 6.0.1.7628 at DS001:\Out-of-Box Drivers\x64_win10\Precision 5510.
Creating new item named Realtek Semiconductor Corp. MEDIA HDXCPC.inf 6.0.1.7628 at DS001:\Out-of-Box Drivers\x64_win10\Precision 5510.
Creating new item named Realtek Semiconductor Corp. MEDIA HDXCR.inf 6.0.1.7628 at DS001:\Out-of-Box Drivers\x64_win10\Precision 5510.
Creating new item named Realtek Semiconductor Corp. MEDIA HDXDELL.inf 6.0.1.7628 at DS001:\Out-of-Box Drivers\x64_win10\Precision 5510.
Creating new item named Realtek Semiconductor Corp. MEDIA HDXDMINI.inf 6.0.1.7628 at DS001:\Out-of-Box Drivers\x64_win10\Precision 5510.
Creating new item named Realtek Semiconductor Corp. MEDIA HDXFJ.inf 6.0.1.7628 at DS001:\Out-of-Box Drivers\x64_win10\Precision 5510.
Creating new item named Realtek Semiconductor Corp. MEDIA HDXFJMA.inf 6.0.1.7628 at DS001:\Out-of-Box Drivers\x64_win10\Precision 5510.
Creating new item named Realtek Semiconductor Corp. MEDIA HDXFTS.inf 6.0.1.7628 at DS001:\Out-of-Box Drivers\x64_win10\Precision 5510.
Creating new item named Realtek Semiconductor Corp. MEDIA HDXGW.inf 6.0.1.7628 at DS001:\Out-of-Box Drivers\x64_win10\Precision 5510.
Creating new item named Realtek Semiconductor Corp. MEDIA HDXHPAI1.inf 6.0.1.7628 at DS001:\Out-of-Box Drivers\x64_win10\Precision 5510.
Creating new item named Realtek Semiconductor Corp. MEDIA HDXHPAI2.inf 6.0.1.7628 at DS001:\Out-of-Box Drivers\x64_win10\Precision 5510.
Creating new item named Realtek Semiconductor Corp. MEDIA HDXHPAI3.inf 6.0.1.7628 at DS001:\Out-of-Box Drivers\x64_win10\Precision 5510.
Creating new item named Realtek Semiconductor Corp. MEDIA HDXHPbNB.INF 6.0.1.7628 at DS001:\Out-of-Box Drivers\x64_win10\Precision 5510.
Creating new item named Realtek Semiconductor Corp. MEDIA HDXHPBPC.INF 6.0.1.7628 at DS001:\Out-of-Box Drivers\x64_win10\Precision 5510.
Creating new item named Realtek Semiconductor Corp. MEDIA HDXHPNB.INF 6.0.1.7628 at DS001:\Out-of-Box Drivers\x64_win10\Precision 5510.
Creating new item named Realtek Semiconductor Corp. MEDIA HDXLC.inf 6.0.1.7628 at DS001:\Out-of-Box Drivers\x64_win10\Precision 5510.
Creating new item named Realtek Semiconductor Corp. MEDIA HDXLC2.inf 6.0.1.7628 at DS001:\Out-of-Box Drivers\x64_win10\Precision 5510.
Creating new item named Realtek Semiconductor Corp. MEDIA HDXLC3.inf 6.0.1.7628 at DS001:\Out-of-Box Drivers\x64_win10\Precision 5510.
Creating new item named Realtek Semiconductor Corp. MEDIA HDXLCNB.inf 6.0.1.7628 at DS001:\Out-of-Box Drivers\x64_win10\Precision 5510.
Creating new item named Realtek Semiconductor Corp. MEDIA HDXLVJ.inf 6.0.1.7628 at DS001:\Out-of-Box Drivers\x64_win10\Precision 5510.
Creating new item named Realtek Semiconductor Corp. MEDIA HDXLVTIC.inf 6.0.1.7628 at DS001:\Out-of-Box Drivers\x64_win10\Precision 5510.
Creating new item named Realtek Semiconductor Corp. MEDIA HDXLVW.inf 6.0.1.7628 at DS001:\Out-of-Box Drivers\x64_win10\Precision 5510.
Creating new item named Realtek Semiconductor Corp. MEDIA HDXMATP3.inf 6.0.1.7628 at DS001:\Out-of-Box Drivers\x64_win10\Precision 5510.
Creating new item named Realtek Semiconductor Corp. MEDIA HDXMaxxD.inf 6.0.1.7628 at DS001:\Out-of-Box Drivers\x64_win10\Precision 5510.
Creating new item named Realtek Semiconductor Corp. MEDIA HDXMB2H.inf 6.0.1.7628 at DS001:\Out-of-Box Drivers\x64_win10\Precision 5510.
Creating new item named Realtek Semiconductor Corp. MEDIA HDXMB2O.inf 6.0.1.7628 at DS001:\Out-of-Box Drivers\x64_win10\Precision 5510.
Creating new item named Realtek Semiconductor Corp. MEDIA HDXMB3H.inf 6.0.1.7628 at DS001:\Out-of-Box Drivers\x64_win10\Precision 5510.
Creating new item named Realtek Semiconductor Corp. MEDIA HDXMB3HD.inf 6.0.1.7628 at DS001:\Out-of-Box Drivers\x64_win10\Precision 5510.
Creating new item named Realtek Semiconductor Corp. MEDIA HDXMSS.inf 6.0.1.7628 at DS001:\Out-of-Box Drivers\x64_win10\Precision 5510.
Creating new item named Realtek Semiconductor Corp. MEDIA HDXMSSDS1.inf 6.0.1.7628 at DS001:\Out-of-Box Drivers\x64_win10\Precision 5510.
Creating new item named Realtek Semiconductor Corp. MEDIA HDXMSSExtDsp.inf 6.0.1.7628 at DS001:\Out-of-Box Drivers\x64_win10\Precision 5510.
Creating new item named Realtek Semiconductor Corp. MEDIA HDXNEC.inf 6.0.1.7628 at DS001:\Out-of-Box Drivers\x64_win10\Precision 5510.
Creating new item named Realtek Semiconductor Corp. MEDIA HDXNECMA.inf 6.0.1.7628 at DS001:\Out-of-Box Drivers\x64_win10\Precision 5510.
Creating new item named Realtek Semiconductor Corp. MEDIA HDXPanasonic.inf 6.0.1.7628 at DS001:\Out-of-Box Drivers\x64_win10\Precision 5510.
Creating new item named Realtek Semiconductor Corp. MEDIA HDXPCEE3.inf 6.0.1.7628 at DS001:\Out-of-Box Drivers\x64_win10\Precision 5510.
Creating new item named Realtek Semiconductor Corp. MEDIA HDXPCEE4.inf 6.0.1.7628 at DS001:\Out-of-Box Drivers\x64_win10\Precision 5510.
Creating new item named Realtek Semiconductor Corp. MEDIA HDXPrmAu.inf 6.0.1.7628 at DS001:\Out-of-Box Drivers\x64_win10\Precision 5510.
Creating new item named Realtek Semiconductor Corp. MEDIA HDXRDC.inf 6.0.1.7628 at DS001:\Out-of-Box Drivers\x64_win10\Precision 5510.
Creating new item named Realtek Semiconductor Corp. MEDIA HDXROG.inf 6.0.1.7628 at DS001:\Out-of-Box Drivers\x64_win10\Precision 5510.
Creating new item named Realtek Semiconductor Corp. MEDIA HDXRT.inf 6.0.1.7628 at DS001:\Out-of-Box Drivers\x64_win10\Precision 5510.
Creating new item named Realtek Semiconductor Corp. MEDIA HDXRT4.inf 6.0.1.7628 at DS001:\Out-of-Box Drivers\x64_win10\Precision 5510.
Creating new item named Realtek Semiconductor Corp. MEDIA HDXRtGi.inf 6.0.1.7628 at DS001:\Out-of-Box Drivers\x64_win10\Precision 5510.
Creating new item named Realtek Semiconductor Corp. MEDIA HDXRTNLA.inf 6.0.1.7628 at DS001:\Out-of-Box Drivers\x64_win10\Precision 5510.
Creating new item named Realtek Semiconductor Corp. MEDIA HDXSBCH.inf 6.0.1.7628 at DS001:\Out-of-Box Drivers\x64_win10\Precision 5510.
Creating new item named Realtek Semiconductor Corp. MEDIA HDXSEDS.inf 6.0.1.7628 at DS001:\Out-of-Box Drivers\x64_win10\Precision 5510.
Creating new item named Realtek Semiconductor Corp. MEDIA HDXSF.inf 6.0.1.7628 at DS001:\Out-of-Box Drivers\x64_win10\Precision 5510.
Creating new item named Realtek Semiconductor Corp. MEDIA HDXSF3.inf 6.0.1.7628 at DS001:\Out-of-Box Drivers\x64_win10\Precision 5510.
Creating new item named Realtek Semiconductor Corp. MEDIA HDXSG.inf 6.0.1.7628 at DS001:\Out-of-Box Drivers\x64_win10\Precision 5510.
Creating new item named Realtek Semiconductor Corp. MEDIA HDXSG2.inf 6.0.1.7628 at DS001:\Out-of-Box Drivers\x64_win10\Precision 5510.
Creating new item named Realtek Semiconductor Corp. MEDIA HDXSGAW.inf 6.0.1.7628 at DS001:\Out-of-Box Drivers\x64_win10\Precision 5510.
Creating new item named Realtek Semiconductor Corp. MEDIA HDXSGMA4.inf 6.0.1.7628 at DS001:\Out-of-Box Drivers\x64_win10\Precision 5510.
Creating new item named Realtek Semiconductor Corp. MEDIA HDXSony.inf 6.0.1.7628 at DS001:\Out-of-Box Drivers\x64_win10\Precision 5510.
Creating new item named Realtek Semiconductor Corp. MEDIA HDXSony2.inf 6.0.1.7628 at DS001:\Out-of-Box Drivers\x64_win10\Precision 5510.
Creating new item named Realtek Semiconductor Corp. MEDIA HDXSRSA.inf 6.0.1.7628 at DS001:\Out-of-Box Drivers\x64_win10\Precision 5510.
Creating new item named Realtek Semiconductor Corp. MEDIA HDXSRSD.inf 6.0.1.7628 at DS001:\Out-of-Box Drivers\x64_win10\Precision 5510.
Creating new item named Realtek Semiconductor Corp. MEDIA HDXSRSD2.inf 6.0.1.7628 at DS001:\Out-of-Box Drivers\x64_win10\Precision 5510.
Creating new item named Realtek Semiconductor Corp. MEDIA HDXSRSL.inf 6.0.1.7628 at DS001:\Out-of-Box Drivers\x64_win10\Precision 5510.
Creating new item named Realtek Semiconductor Corp. MEDIA HDXSRSS.inf 6.0.1.7628 at DS001:\Out-of-Box Drivers\x64_win10\Precision 5510.
Creating new item named Realtek Semiconductor Corp. MEDIA HDXSRSSV.inf 6.0.1.7628 at DS001:\Out-of-Box Drivers\x64_win10\Precision 5510.
Creating new item named Realtek Semiconductor Corp. MEDIA HDXSST.inf 6.0.1.7628 at DS001:\Out-of-Box Drivers\x64_win10\Precision 5510.
Creating new item named Realtek Semiconductor Corp. MEDIA HDXSST4.inf 6.0.1.7628 at DS001:\Out-of-Box Drivers\x64_win10\Precision 5510.
Creating new item named Realtek Semiconductor Corp. MEDIA HDXSSTHPAI1.inf 6.0.1.7628 at DS001:\Out-of-Box Drivers\x64_win10\Precision 5510.
Creating new item named Realtek Semiconductor Corp. MEDIA HDXSSTHPNB.inf 6.0.1.7628 at DS001:\Out-of-Box Drivers\x64_win10\Precision 5510.
Creating new item named Realtek Semiconductor Corp. MEDIA HDXSSTP3.inf 6.0.1.7628 at DS001:\Out-of-Box Drivers\x64_win10\Precision 5510.
Creating new item named Realtek Semiconductor Corp. MEDIA HDXTHX.inf 6.0.1.7628 at DS001:\Out-of-Box Drivers\x64_win10\Precision 5510.
Creating new item named Realtek Semiconductor Corp. MEDIA HDXTHX2.inf 6.0.1.7628 at DS001:\Out-of-Box Drivers\x64_win10\Precision 5510.
Creating new item named Realtek Semiconductor Corp. MEDIA HDXTHXD.inf 6.0.1.7628 at DS001:\Out-of-Box Drivers\x64_win10\Precision 5510.
Creating new item named Realtek Semiconductor Corp. MEDIA HDXToshiba.inf 6.0.1.7628 at DS001:\Out-of-Box Drivers\x64_win10\Precision 5510.
Creating new item named Realtek Semiconductor Corp. MEDIA HDXVienna.inf 6.0.1.7628 at DS001:\Out-of-Box Drivers\x64_win10\Precision 5510.
Creating new item named Realtek Semiconductor Corp. MEDIA HDXXFM.inf 6.0.1.7628 at DS001:\Out-of-Box Drivers\x64_win10\Precision 5510.
Copying existing item Intel System heci.inf 11.0.0.1166 from DS001:\Out-of-Box Drivers\x64_Win7\Precision 7710 to DS001:\Out-of-Box Drivers\x64_win10\Precision 5510.
Copying existing item Intel Ports mesrl.inf 11.0.0.1136 from DS001:\Out-of-Box Drivers\x64_Win7\Optiplex 7040 to DS001:\Out-of-Box Drivers\x64_win10\Precision 5510.
Copying existing item ST Microelectronics DiskDrive stdcfltn.inf 1.00.00.12 (1) from DS001:\Out-of-Box Drivers\x64_win81\Precision 7710 to DS001:\Out-of-Box Drivers\x64_win10\Precision 5510.
Creating new item named STMicroelectronics System ST_Accel.inf 2.2.3.7 (3) at DS001:\Out-of-Box Drivers\x64_win10\Precision 5510.
Creating new item named Intel(R) Corporation System tbt81x.inf 15.3.39.1 at DS001:\Out-of-Box Drivers\x64_win10\Precision 5510.
Creating new item named Intel(R) Corporation Net tp2p81x.inf 15.3.39.2 at DS001:\Out-of-Box Drivers\x64_win10\Precision 5510.
Creating new item named Intel(R) HIDClass HidEventFilter.inf 1.1.0.311 at DS001:\Out-of-Box Drivers\x64_win10\Precision 5510.
Creating new item named Realtek Semiconduct Corp. MTD RtsBaStorX.inf 10.0.10130.27054 (3) at DS001:\Out-of-Box Drivers\x64_win10\Precision 5510.
Creating new item named Realtek Semiconduct Corp. MTD RtsP2StorX.inf 10.0.10130.29089 (3) at DS001:\Out-of-Box Drivers\x64_win10\Precision 5510.
Creating new item named Realtek Semiconduct Corp. MTD RtsPerX.inf 10.0.10125.21277 (2) at DS001:\Out-of-Box Drivers\x64_win10\Precision 5510.
Creating new item named Realtek Semiconduct Corp. MTD RtsPStorX.inf 10.0.10130.28157 (3) at DS001:\Out-of-Box Drivers\x64_win10\Precision 5510.
Creating new item named Realtek Semiconduct Corp. USB RtsUerXDisableMMC.inf 10.0.10125.31214 at DS001:\Out-of-Box Drivers\x64_win10\Precision 5510.
Creating new item named Intel DPTF dptf_acpi.inf 8.1.10604.207 at DS001:\Out-of-Box Drivers\x64_win10\Precision 5510.
Creating new item named Intel DPTF dptf_cpu.inf 8.1.10604.207 at DS001:\Out-of-Box Drivers\x64_win10\Precision 5510.
Creating new item named Intel DPTF dptf_pch.inf 8.1.10604.207 at DS001:\Out-of-Box Drivers\x64_win10\Precision 5510.
Creating new item named Intel DPTF esif_manager.inf 8.1.10604.207 at DS001:\Out-of-Box Drivers\x64_win10\Precision 5510.
Copying existing item Intel Corporation System iaLPSS2_GPIO2_SKL.inf 30.63.1519.07 from DS001:\Out-of-Box Drivers\x64_win10\7440 AIO\chipset to DS001:\Out-of-Box Drivers\x64_win10\Precision 5510.
Copying existing item Intel Corporation System iaLPSS2_I2C_SKL.inf 30.63.1519.07 from DS001:\Out-of-Box Drivers\x64_win10\7440 AIO\chipset to DS001:\Out-of-Box Drivers\x64_win10\Precision 5510.
Copying existing item Intel Corporation System iaLPSS2_SPI_SKL.inf 30.63.1519.07 from DS001:\Out-of-Box Drivers\x64_win10\7440 AIO\chipset to DS001:\Out-of-Box Drivers\x64_win10\Precision 5510.
Copying existing item Intel Corporation System iaLPSS2_UART2_SKL.inf 30.63.1519.07 from DS001:\Out-of-Box Drivers\x64_win10\7440 AIO\chipset to DS001:\Out-of-Box Drivers\x64_win10\Precision 5510.
Creating new item named INTEL System baytrail-iSystem.inf 10.1.1.11 (3) at DS001:\Out-of-Box Drivers\x64_win10\Precision 5510.
Creating new item named INTEL System braswellSystem.inf 10.1.1.11 (3) at DS001:\Out-of-Box Drivers\x64_win10\Precision 5510.
Creating new item named INTEL System broadwellSystem.inf 10.1.1.11 (3) at DS001:\Out-of-Box Drivers\x64_win10\Precision 5510.
Creating new item named INTEL System commonSystem.inf 10.1.1.11 (3) at DS001:\Out-of-Box Drivers\x64_win10\Precision 5510.
Creating new item named INTEL System cougarpointSystem.inf 10.1.1.11 (3) at DS001:\Out-of-Box Drivers\x64_win10\Precision 5510.
Creating new item named INTEL USB cougarpointUSB.inf 10.1.1.11 (3) at DS001:\Out-of-Box Drivers\x64_win10\Precision 5510.
Creating new item named INTEL System haswellSystem.inf 10.1.1.11 (3) at DS001:\Out-of-Box Drivers\x64_win10\Precision 5510.
Creating new item named INTEL System ivybridgeSystem.inf 10.1.1.11 (3) at DS001:\Out-of-Box Drivers\x64_win10\Precision 5510.
Creating new item named INTEL System lynxpoint-hrefreshSystem.inf 10.1.1.11 (3) at DS001:\Out-of-Box Drivers\x64_win10\Precision 5510.
Creating new item named INTEL System lynxpointlpSystem.inf 10.1.1.11 (3) at DS001:\Out-of-Box Drivers\x64_win10\Precision 5510.
Creating new item named INTEL System lynxpointSystem.inf 10.1.1.11 (3) at DS001:\Out-of-Box Drivers\x64_win10\Precision 5510.
Creating new item named INTEL System pantherpointSystem.inf 10.1.1.11 (3) at DS001:\Out-of-Box Drivers\x64_win10\Precision 5510.
Creating new item named INTEL System sandybridgeSystem.inf 10.1.1.11 (3) at DS001:\Out-of-Box Drivers\x64_win10\Precision 5510.
Creating new item named INTEL System skylakeSystem.inf 10.1.1.11 (3) at DS001:\Out-of-Box Drivers\x64_win10\Precision 5510.
Creating new item named INTEL System sunrisepoint-hSystem.inf 10.1.1.11 (3) at DS001:\Out-of-Box Drivers\x64_win10\Precision 5510.
Creating new item named INTEL SDHost sunrisepoint-lpSDHost.inf 10.1.1.11 (3) at DS001:\Out-of-Box Drivers\x64_win10\Precision 5510.
Creating new item named INTEL System sunrisepoint-lpSystem.inf 10.1.1.11 (3) at DS001:\Out-of-Box Drivers\x64_win10\Precision 5510.
Creating new item named INTEL System valleyview2System.inf 10.1.1.11 (3) at DS001:\Out-of-Box Drivers\x64_win10\Precision 5510.
Creating new item named INTEL USB valleyview2USB.inf 10.1.1.11 (3) at DS001:\Out-of-Box Drivers\x64_win10\Precision 5510.
Creating new item named INTEL System wildcatpointlpSystem.inf 10.1.1.11 (3) at DS001:\Out-of-Box Drivers\x64_win10\Precision 5510.
Creating new item named INTEL USB wildcatpointlpUSB.inf 10.1.1.11 (3) at DS001:\Out-of-Box Drivers\x64_win10\Precision 5510.
Copying existing item Broadcom Corporation Bluetooth bcbtums-win8x64-brcm.inf 12.0.1.731 from DS001:\Out-of-Box Drivers\x64_win10\Latitude E7270\network to DS001:\Out-of-Box Drivers\x64_win10\Precision 5510.
Copying existing item Broadcom Corporation HIDClass bcmhidnossr.inf 1.0.0.102 (4) from DS001:\Out-of-Box Drivers\x64_win10\Latitude E7270\network to DS001:\Out-of-Box Drivers\x64_win10\Precision 5510.
Copying existing item Broadcom Corp. MEDIA btwaudio.inf 12.0.1.718 from DS001:\Out-of-Box Drivers\x64_win10\Latitude E7270\network to DS001:\Out-of-Box Drivers\x64_win10\Precision 5510.
Copying existing item Broadcom Corp. BluetoothVirtual btwavdt.inf 12.0.1.718 from DS001:\Out-of-Box Drivers\x64_win10\Latitude E7270\network to DS001:\Out-of-Box Drivers\x64_win10\Precision 5510.
Copying existing item Broadcom Corp. BluetoothVirtual btwl2cap.inf 12.0.0.1680 (2) from DS001:\Out-of-Box Drivers\hidden to DS001:\Out-of-Box Drivers\x64_win10\Precision 5510.
Name already exists: 'D:\Share\Out-of-Box Drivers\x64_win10\Precision 5510\Broadcom Corp. BluetoothVirtual btwl2cap.inf 12.0.0.1680 (2)' specified.
Copying existing item Broadcom HIDClass btwrchid.inf 12.0.1.718 from DS001:\Out-of-Box Drivers\x64_win10\Latitude E7270\network to DS001:\Out-of-Box Drivers\x64_win10\Precision 5510.
Copying existing item Broadcom Corporation Bluetooth bcbtumsLD-win7x64.inf 12.0.0.8047 from DS001:\Out-of-Box Drivers\x64_win81\Latitude E7250\_Newest to DS001:\Out-of-Box Drivers\x64_win10\Precision 5510.
Creating new item named Intel Net Netwew00.INF 15.12.0.9 (7) at DS001:\Out-of-Box Drivers\x64_win10\Precision 5510.
Creating new item named Intel Net Netwew01.INF 15.18.0.1 (7) at DS001:\Out-of-Box Drivers\x64_win10\Precision 5510.
Creating new item named Intel Net Netwtw02.INF 18.20.0.9 at DS001:\Out-of-Box Drivers\x64_win10\Precision 5510.
Copying existing item Broadcom Net bcmwdidhdpcie.inf 1.519.0.0 from DS001:\Out-of-Box Drivers\x64_win10\Latitude E7270\network to DS001:\Out-of-Box Drivers\x64_win10\Precision 5510.
Creating new item named Intel Corporation Bluetooth ibtserialbus.inf 8.18.58.740 (2) at DS001:\Out-of-Box Drivers\x64_win10\Precision 5510.
Creating new item named Intel Corporation System ibtuart.inf 21.20.26.316 at DS001:\Out-of-Box Drivers\x64_win10\Precision 5510.
Creating new item named Intel Corporation Bluetooth ibtusb.inf 18.1.1535.1946 at DS001:\Out-of-Box Drivers\x64_win10\Precision 5510.

System.Management.Automation.CmdletInvocationException: Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: index ---> System.ArgumentOutOfRangeException: Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: index
   at System.ThrowHelper.ThrowArgumentOutOfRangeException(ExceptionArgument argument, ExceptionResource resource)
   at System.Collections.Generic.List`1.get_Item(Int32 index)
   at Microsoft.BDD.PSSnapIn.Verifier.AddDriver(String theInfFile)
   at Microsoft.BDD.PSSnapIn.ImportDriver.ImportDrivers(String thePath)
   at Microsoft.BDD.PSSnapIn.ImportDriver.ImportDrivers(String thePath)
   at Microsoft.BDD.PSSnapIn.ImportDriver.ImportDrivers(String thePath)
   at Microsoft.BDD.PSSnapIn.ImportDriver.ImportDrivers(String thePath)
   at Microsoft.BDD.PSSnapIn.ImportDriver.ProcessRecord()
   at System.Management.Automation.CommandProcessor.ProcessRecord()
   --- End of inner exception stack trace ---
   at System.Management.Automation.Runspaces.PipelineBase.Invoke(IEnumerable input)
   at Microsoft.BDD.Wizards.DriverProgress.WizardProcessing()
   at Microsoft.BDD.Wizards.WizardProgress.InitiateWizardProcessing()

↧

Latest Images