Has anyone who has incorporated Dell BIOS updates in a task sequence experienced a problem where after the BIOS update you have to enter the BIOS at least once for MDT/WinPE to see the disk drive after the update?

WinPE has the Intel RST drivers as they included in the Out of Box drivers and injected into the boot images.

My steps look like this:

Update BIOS

Change Boot settings with CCTK to boot from NIC next boot (so my techs don't have to manually PXE boot)

Restart laptop

Change Boot settings with CCTK to boot from HD first

When the laptop reboots it does a PXE boot but for some reason it cannot access the hard disk and assumes this is a new deployment.  I hit F8 to get a command prompt and WinPE doesn't see any drive.  If I continue as if it's new deployment MDT fails at the Partition and Format step because, obviously, it can't do that if it doesn't see any drives.

However, if I reboot the machine and go into the BIOS setup once and then reboot again into WinPE after making NO changes it can now magically see the hard disk and continues on with the task sequence.

I cannot figure out what relationship there is between the BIOS update, having to reboot into the BIOS setup once after the update and WinPE no longer seeing the hard disk unless I do that step first.

I know this is a commonly asked question. I believe I've followed all the steps within this guide.

"https://social.technet.microsoft.com/Forums/en-US/3e083173-f5db-48e9-b744-f71b9ca6541c/how-to-debug-missing-drivers-in-mdt?forum=mdt"

The machine I'm trying to build is a Dell OptiPlex 7040, I've downloaded the cab file from the Dell Support page, and I've updated the Deployment Share, and then replaced the .wim file. 

I beg any help!!

Hello,

I am using MDT to deploy a Windows 10 image to a test device. After the imaging process the machine logs into the Administrator account where usually the Deployment Wizard should launch and complete the MDT deployment, following a successful message or errors. However, after the device auto logs into the Administrator account to complete MDT, I am presented with a blank Wizard.hta screen. I followed the path to where the Wizard.hta is launching from and the folder is empty.

Folder = C:\Users\ADMINI~1\AppData\Local\Temp\DeploymentScripts\Wizard.hta

I also located the log file and found this: (Wizard.log)

<![LOG[Property LogPath is now = C:\MININT\SMSOSD\OSDLOGS]LOG]!><time="15:39:25.000+000" date="03-14-2016" component="Wizard" context="" type="1" thread="" file="Wizard"><![LOG[Microsoft Deployment Toolkit version: 6.3.8330.1000]LOG]!><time="15:39:25.000+000" date="03-14-2016" component="Wizard" context="" type="1" thread="" file="Wizard"><![LOG[Property Debug is now = FALSE]LOG]!><time="15:39:25.000+000" date="03-14-2016" component="Wizard" context="" type="1" thread="" file="Wizard"><![LOG[Not Wizard = False]LOG]!><time="15:39:25.000+000" date="03-14-2016" component="Wizard" context="" type="1" thread="" file="Wizard"><![LOG[FAILURE ( 20001 ): Definition file not defined. Please call with /Defintion:<file>   CommandLine:"\\myimages\mymdt\Scripts\Wizard.hta"]LOG]!><time="15:39:25.000+000" date="03-14-2016" component="Wizard" context="" type="3" thread="" file="Wizard"><![LOG[Microsoft Deployment Toolkit version: 6.3.8330.1000]LOG]!><time="15:40:01.000+000" date="03-14-2016" component="Wizard" context="" type="1" thread="" file="Wizard"><![LOG[Not Wizard = False]LOG]!><time="15:40:01.000+000" date="03-14-2016" component="Wizard" context="" type="1" thread="" file="Wizard"><![LOG[FAILURE ( 20001 ): Definition file not defined. Please call with /Defintion:<file>   CommandLine:"\\myimages\mymdt\Scripts\Wizard.hta"]LOG]!><time="15:40:01.000+000" date="03-14-2016" component="Wizard" context="" type="3" thread="" file="Wizard">

Would anyone know why the Wizard.hta is not properly launching and why MDT is not completing on Windows 10? 

Thank-you,

AP

Hey Guys,

I created a custom Pane with Wizard Studio. How do I pass the variable to my TS?

Thanks

Hello,

Just to clarify usually the error is an unattend error on reboot of the system while applying changes on one of the reboots during setup. After the error I am pretty much hosed and have to start all over by going back to the base OS initial source files and begin from beginning

Here is my Environment Setup:

My MDTSERVER is my personal PC: Win 10 Pro, x64, latest Win Updates. I'm using MDT 2013 update 2, ADK 10, VMware Workstation 12. I have Firefox, xml viewer, cmtrace and a few other tools. It is pretty much a testing machine, not a play machine.

I'm using Win 10 Ent Eval x64

I'm using a Standard Sequence - No copying sysprep or doing Capture

In the Standard Sequence I am installing the OS, C++, Java, MS Office, .Net

* If I run the sequence it will install all apps as expected and log into the desktop

** I am using a step I found online for installing RDP into the install so it will be deployed and enabled on every machine. This step requires me to edit the unattend file. This appears to work properly because when checking the Remote Desktop Settings it is enabled in the Win 10 Ent Eval install in VMware.

My understanding from reading is that on the First Standard Task Sequence Run I would :

1) Install OS, Windows Updates

2) Install Java, C++, .Net

3) Edit unattend file for RDP

*** I thought that this is done as a step to create a standard baseline image able to be used for almost any Win 10 x64 install without adding unnecessary programs but optimizing the OS by installing updates, C++, etc... to also speed up deployment a bit.?

4) Do capture of that image

SECOND Run of WIM File

1) Install WIM ( OS based on captured WIM File)

2) Use LTISuspend - Make config changes: Background, Start Layout

3) Capture Image

THIRD Run of Second Captured Image ( Deployment Sequence Install )

1) Install WIM

2) Install Office

3) A few custom things I have run: Copy a tools folder to system32, a batch file creating a few local accounts

4) Use the Copy Profile steps from a video from Johan has online

The main error I am getting is an unattended error during the process and I cannot figure out if it is the RDP unattended changes or the copy profile changes, or if there is something with Company User, Company Name settings.

What I want to complete successfully:

1)I want to make sure of getting RDP enabled somehow during my run

2) I want to do a Suspend and make custom changes

3) I want to modify a few group policy settings, Not many but a few

4) I want all my custom settings, changes, group policy settings set and saved and copied into the default user profile so the setting are saved so each profile created the profiles are congruent with each other.

I am re-running my setup and if and when I get the errors again I can also upload log files. I currently do not have any older run log files to upload.

Thank You,

Wayne

Our company is trying to decide which version of Windows 10 we want to update to from Windows 7 enterprise.  I have creating update task sequences in MDT for 4 versions of Windows 10:

Windows 10 Enterprise x64

Windows 10 Enterprise LTSB x64

Windows 10 Enterprise N x64

Windows 10 Enterprise N LTSB x64

I've created the 4 update task sequences the same way, just pointing to different source media.  When updating a Windows 7 PC the first two task sequences work fine.  The second 2 do not.  After the OS install they seem to get stuck. Does anyone know why this would be?  the N versions do supports updates, I can do them manually.

Why do you need to have both x64 and x86 LiteTouch isos if it is only booting the system so it can connect to the deployment share and run task sequences?

Why can't you use the x86 boot file and deploy both 32-bit and 64-bit OS once the MDT interface loads or use the x64 boot iso and deploy an x86 image (assuming the system you are installing the 32-bit image on is also x64 capable)?

Hi. I'm trying to add a user to admins by command line during install of OS, but it's always time a fail. The reason why I didn't do it via CS.ini is that first this user removes from local admins and then adds. It's due language settings which this user somehow didn't got right language settings. The command is:

cmd.exe /c net localgroup Administrators sys_eng /add

And at the end of install I getting this:

Any ideas why it so? Thanks in advance.

Hi All,

We are working on a migration. Our requirement is as follows:

 -Migrate user profile of User1 of DomainA.com to User2 in DomainB.Com domain.

 -Make sure only settings (User profile settings are migrated). Basically, we don't want to copy user profiles.

Can this be done using USMT tool?

Thank you for your help.

Nick R.

Hello,

I have an issue using MDT 2013 U1. First I capture and sysprep using MDT. The filesystem is fine before this. After deployment the screen is purple when restarting, and when I run "sfc /scannow" it always finds integrity violations, which means these errors have occured during the deployment of Windows 10.

I have tried recreating both task sequences. Recreating the image to capture several times. But nothing seem to work for me.

How can I proceed?

Dear All,

I'm hoping someone can help me.

I'm trying to image a Dell E7450 using MDT. I've created a x86 Litetouch bootable usb stick which works with other models of laptops. However, when using this same stick to boot on the Dell E7450 it loads a black screen with a flashing cursor.

I've tried updating WinPE drivers, removing drivers and just using the NIC drivers but no luck.

Any suggestions will be much appreciated.

Cheers

Hi guys,

I am trying to install some applications during OS deployment with Task Sequence and getting a pop-up during the application installation phase that the environment is dirty. 

It looks like the problem goes away if I clean the drive using Diskpart utility before OS deployment but it's not really practical to do this everytime we image a PC. 

Could you guys please give me any suggestions how to fix this or any logs I can look at for troubleshooting?

Thank you!!

Steve

I loaded the base image from my deployment share then ran windows updates, installed office 2013, AXWAY desktop validator then was going to capture the image back up. With windows 7 i could do this with no issues but I havent gotten it to work yet with this new toolkit. Below is the setupact.log errors that was referenced in the failure dialog box. Any ideas?

Daniel F. Willingham

I've installed patch 2 for MDT 2013 and started to look into deploying Windows 10 Enterprise. Most of the times the deployment works ok. However, sometimes I do get errors when installing applications:

"WARNING - unable to set working directory: Permission denied (70)"

The files reside on a DFS share and access is set correctly. The same applications do work ok when deploying Windows 7. Nothing has been changed on the DFS side. We install apps from different locations like local MDT share and also two different DFS shares. Access to one of the DFS shares works ok while the second may fail.

I can remember having had a similar issue back in Windows XP times where XP wasn't able to access different network locations. So we had to put in a couple of reboots. Strange to see that behaviour come back.

Interestingly enough sometimes it works without problems. I don't think it is related to the back-end systems as that is occuring at multiple sites and Windows 7 works ok.

Excerpt from the log file below showing both the successful and the failed attempt.

Any ideas ?

Thanks
Thorsten

<![LOG[Name:  Microsoft Skype for Business]LOG]!><time="11:06:32.000+000" date="05-04-2016" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
<![LOG[################]LOG]!><time="11:06:32.000+000" date="05-04-2016" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
<![LOG[Validating connection to \\<domain-dfs>\software$\Deployment\Microsoft\Lync\Skype]LOG]!><time="11:06:32.000+000" date="05-04-2016" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
<![LOG[Mapping server share: \\<domain-dfs>\software$]LOG]!><time="11:06:32.000+000" date="05-04-2016" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
<![LOG[Already connected to server <domain-dfs> as that is where this script is running from.]LOG]!><time="11:06:32.000+000" date="05-04-2016" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
<![LOG[        Change directory: \\<domain-dfs>\software$\Deployment\Microsoft\Lync\Skype]LOG]!><time="11:06:32.000+000" date="05-04-2016" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
<![LOG[WARNING - unable to set working directory: Permission denied (70)]LOG]!><time="11:06:34.000+000" date="05-04-2016" component="ZTIApplications" context="" type="2" thread="" file="ZTIApplications">
<![LOG[        Run Command: \\<domain-dfs>\EMDeployment\UAT\Tools\X64\bddrun.exe lyncmso2013-kb3039779-fullfile-x86-glb.exe /quiet /passive /norestart]LOG]!><time="11:06:34.000+000" date="05-04-2016" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
<![LOG[ZTI installing application ]LOG]!><time="11:06:34.000+000" date="05-04-2016" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
<![LOG[Event 41031 sent: ZTI installing application ]LOG]!><time="11:06:35.000+000" date="05-04-2016" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
<![LOG[About to run command: \\<domain-dfs>\EMDeployment\UAT\Tools\X64\bddrun.exe lyncmso2013-kb3039779-fullfile-x86-glb.exe /quiet /passive /norestart]LOG]!><time="11:06:35.000+000" date="05-04-2016" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
<![LOG[Command has been started (process ID 904)]LOG]!><time="11:06:35.000+000" date="05-04-2016" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
<![LOG[Return code from command = 2]LOG]!><time="11:06:36.000+000" date="05-04-2016" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
<![LOG[Application Microsoft Skype for Business returned an unexpected return code: 2]LOG]!><time="11:06:36.000+000" date="05-04-2016" component="ZTIApplications" context="" type="3" thread="" file="ZTIApplications">
<![LOG[Event 41034 sent: Application Microsoft Skype for Business returned an unexpected return code: 2]LOG]!><time="11:06:37.000+000" date="05-04-2016" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
<![LOG[################]LOG]!><time="11:06:37.000+000" date="05-04-2016" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
<![LOG[Entry: {da2f354a-51ae-47a0-8074-012acbc572f0}]LOG]!><time="11:06:37.000+000" date="05-04-2016" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
<![LOG[Name:  Microsoft Office 2010 Professional Plus 14]LOG]!><time="11:06:37.000+000" date="05-04-2016" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
<![LOG[################]LOG]!><time="11:06:37.000+000" date="05-04-2016" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
<![LOG[Validating connection to \\<domain-dfs>\nancdfsrglobalapps\Apps\Microsoft\Office14\Office14\]LOG]!><time="11:06:37.000+000" date="05-04-2016" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
<![LOG[Mapping server share: \\<domain-dfs>\nancdfsrglobalapps]LOG]!><time="11:06:37.000+000" date="05-04-2016" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
<![LOG[Already connected to server <domain-dfs> as that is where this script is running from.]LOG]!><time="11:06:37.000+000" date="05-04-2016" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
<![LOG[        Change directory: \\<domain-dfs>\nancdfsrglobalapps\Apps\Microsoft\Office14\Office14\]LOG]!><time="11:06:37.000+000" date="05-04-2016" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
<![LOG[        Run Command: \\<domain-dfs>\EMDeployment\UAT\Tools\X64\bddrun.exe Setup.exe /adminfile \\<domain-dfs>\nancdfsrglobalapps\Apps\Microsoft\Office14\MSP\office14-global.msp /config \\<domain-dfs>\nancdfsrglobalapps\Apps\Microsoft\Office14\CONFIG\configInstallEMEA.xml]LOG]!><time="11:06:37.000+000" date="05-04-2016" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
<![LOG[ZTI installing application ]LOG]!><time="11:06:37.000+000" date="05-04-2016" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
<![LOG[Event 41031 sent: ZTI installing application ]LOG]!><time="11:06:39.000+000" date="05-04-2016" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
<![LOG[About to run command: \\<domain-dfs>\EMDeployment\UAT\Tools\X64\bddrun.exe Setup.exe /adminfile \\<domain-dfs>\nancdfsrglobalapps\Apps\Microsoft\Office14\MSP\office14-global.msp /config \\<domain-dfs>\nancdfsrglobalapps\Apps\Microsoft\Office14\CONFIG\configInstallEMEA.xml]LOG]!><time="11:06:39.000+000" date="05-04-2016" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
<![LOG[Command has been started (process ID 4636)]LOG]!><time="11:06:39.000+000" date="05-04-2016" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
<![LOG[ZTI Heartbeat: command has been running for 2 minutes (process ID 4636)]LOG]!><time="11:08:00.000+000" date="05-04-2016" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
<![LOG[Event 41003 sent: ZTI Heartbeat: command has been running for 2 minutes (process ID 4636)]LOG]!><time="11:08:03.000+000" date="05-04-2016" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
<![LOG[ZTI Heartbeat: command has been running for 7 minutes (process ID 4636)]LOG]!><time="11:13:00.000+000" date="05-04-2016" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
<![LOG[Event 41003 sent: ZTI Heartbeat: command has been running for 7 minutes (process ID 4636)]LOG]!><time="11:13:09.000+000" date="05-04-2016" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
<![LOG[Return code from command = 0]LOG]!><time="11:16:20.000+000" date="05-04-2016" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
<![LOG[Application Microsoft Office 2010 Professional Plus 14 installed successfully]LOG]!><time="11:16:20.000+000" date="05-04-2016" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">

Hi,

I want to deploy the Windows 10 using MDT with formatting the existing OS Partition only.

Currently, All system has Windows 7 and 8 and i want to deploy Windows 10 after formatting the existing OS Partition using MDT Task sequence.

Please suggest for MDT TS Configuration.

Shailendra Dev

Hi,

I am looking for MDT Task sequence Configuration to clean/format the Existing OS Partition and then deploy the windows 10 on the same partition...

Shailendra Dev

I am preparing an unattend.xml for an installation of Windows 8.1.

My question stems from a requirement we have for a software installation which requires at least 1 login to the Limited Local Account (set forth by the manufacturer) before it can be executed. As far as I understand, this is required because the installation makes some changes to desktop icons in the Local Account, and therefore requires that it has been initialized through its first login.

I currently have my unattend.xml creating an Admin account, and a Local Account, and autologging in to my Admin account. Is there a way to initialize all of my accounts (as is done when you first login to an account), but before my autologin into the Admin account at the end of the installation?

I was exploring the AutoLogon parameter in the Specialize pass as opposed to the OOBE pass, and was wondering if that could be my solution. The issue there is that in the Specialize pass, the accounts haven't been defined yet. There doesn't seem to be any documentation on how AutoLogon works in the Specialize pass.

Any ideas on how i could do this?

Currently having an issue with our server deployment. What we are seeing is that when we have servers that have large amounts of RAM and we are deploying to a server with smaller drives the initial swap file is filling up the drive and the deployment is failing at the 1st boot after the image is applied. We are unable to restart the deployment and find that the OS drive is full and filled up by the swap file trying to create at 2x RAM amount. Is there a way to get around that? So far we seem to have determined that Sysprep will reset our swap size preferences when we capture the image, and that there is no way to change the swap file during the build. Is this correct? Or am I just not finding the right page to tell me how to correct this issue?

Thanks.

I am creating a reference Image for my company . Everything thus far has gone great . I am ready to capture the image to deploy. When the wizard comes up I am selecting the reference image task and then selecting sysprep and capture as one of the choice asked . Everything seems to go fine , I see sysprep run and I am expecting the machine at this point to create the WIm file in the back ground after sysprep reboots the machine a write it up the captures folder on my deployment share.

What does happen is I get a error after the reboot  from windows script host  " Can not find script file "c:\LTIBootstrap.vbs"

If I click ok the desktop come up and the wim file is never created.

Question one am I doing this correctly ??

If I am How to trouble shoot ??