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

Task Sequence Wizard displays after OS install

January 18, 2018, 11:08 am
$
0
0

I just updated MDT and the ADK for Windows 10 1709. I've noticed that when I run a task sequence to install an image (intiated via WDS), after the OS install and reboot, the Windows Deployment Wizard displays again and asks which task sequence I would like to run. The first time I noticed this, it was on a task sequence that I had made a copy of by copying the xml files, so I thought it was a result of that. I created a new task sequence without any copying and it does the same thing. In both cases, if I click through the wizard, it keeps going and finishes the sequence, but it shouldn't be displaying that wizard twice like this. In the second task sequence that I created, I used the Standard Client Task sequence template and the only thing I changed was the OS image to install and removed application installation. Anyone have ideas on how to fix this? 

Windows Deployment Wizard

MDT 6.3.8450.1000

Server 2012 R2 with Windows Deployment Services


↧
Search

MDT 2013 - 30+ Minute Hang during deployment

July 11, 2018, 2:02 pm
$
0
0

Working to get a Windows 10 (1803) deployment working with MDT2013.  Everything is technically working, but there is a very long 30-40 minute hangup at the "Getting Ready" screen.  Have tested on multiple systems, and VMs with the same result.  The log just shows a black hole during this time (from 8:35 - 9:13 in the attached log).   Any help?

Last line before the hangup is :

<![LOG[LTI initiating task sequence-requested reboot.]LOG]!><time="08:35:16.000+000" date="07-09-2018" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">

Next line is :

<![LOG[Property start is now = ]LOG]!><time="09:13:03.000+000" date="07-09-2018" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">

BDD.log : https://1drv.ms/u/s!Ap960AZ887lnbvz3dmovgQuwqaM

↧
↧

conexant audio driver issue when creating image in mdt

June 15, 2018, 10:15 am
$
0
0
every time I try to create an image on a computer that has conexant audio; the process always hangs on sysprep.  I have to uninstall the conexant audio driver for it to go through; and that process is very painful due to the driver trying to reinstall automatically; it takes several tries for me to finally get the image created.  has anyone else encountered this issue and found  solution.  I'm using using microsoft deployment workbench version 6.3.8443.1000.  thanks in advance
↧

Deploying Office 365 (2016) using MDT to a Windows 10 Task Sequence

May 22, 2017, 9:30 am
$
0
0

Having some problems trying to deploy Office 365 ProPlus using MDT (8443) on Server 2016. The batch file and config.xml I have setup work ok if I run them on a computer manually, but when I put it into MDT to run, it errors out during deployment. I'm basically having it run the command below.

\\server\deploymentshare$\applications\Microsoft Office\setup.exe /configure \\server\deploymentshare$\applications\Microsoft Office\config.xml

Below is a copy of the config.xml.

<Configuration>

  <Add OfficeClientEdition="64" Channel="Current">
    <Product ID="O365ProPlusRetail">
      <Language ID="en-us" />
    </Product>
  </Add>

  <Property Name="PinIconsToTaskbar" Value="FALSE" /> 
  
  <Property Name="FORCEAPPSHUTDOWN" Value="TRUE"/>
 
  <Updates Enabled="TRUE" Channel="Current" /> 

  <Display Level="None" AcceptEULA="TRUE" />

  <Property Name="AUTOACTIVATE" Value="1" />

</Configuration>
↧

Error capturing image

July 12, 2018, 3:57 am
$
0
0

Hello Everybody, 

i have created an Task Sequence in MDT that installs windows 10 pro and suspend the TS so i can change a couple of settings.
When i resume the TS it crashes on Applying windows PE, i have collected the logs from it and i think i have found the section from that error but i don't know why it crashes. Can you please take a look and help me to solve this error? thanks alot.

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.LTIApply12-7-2018 12:50:070 (0x0000)
Will boot into Windows PE architecture x64 to match OS being deployed.LTIApply12-7-2018 12:50:080 (0x0000)
TargetOS is the current SystemDriveLTIApply12-7-2018 12:50:080 (0x0000)
Get the Boot Drive.LTIApply12-7-2018 12:50:080 (0x0000)
The current autorun setting is - 145LTIApply12-7-2018 12:50:080 (0x0000)
Disabling AutorunLTIApply12-7-2018 12:50:080 (0x0000)
Find the boot drive (if any) [Waar] [10.0.17134.1] [Onwaar]LTIApply12-7-2018 12:50:080 (0x0000)
New ZTIDisk : \\PC-01\root\cimv2:Win32_DiskDrive.DeviceID="\\\\.\\PHYSICALDRIVE0"LTIApply12-7-2018 12:50:080 (0x0000)
DISKPART + Select Disk 0LTIApply12-7-2018 12:50:080 (0x0000)
DISKPART + Select Partition 1LTIApply12-7-2018 12:50:080 (0x0000)
DISKPART + AssignLTIApply12-7-2018 12:50:080 (0x0000)
DISKPART + ExitLTIApply12-7-2018 12:50:080 (0x0000)
About to run command: cscript.exe //nologo "\\WDS01\DeploymentShare$\Scripts\ztiRunCommandHidden.wsf" "DiskPart.exe /s C:\Users\ADMINI~1\AppData\Local\Temp\radC69C6.tmp"LTIApply12-7-2018 12:50:080 (0x0000)
Microsoft Deployment Toolkit version: 6.3.8450.1000ztiRunCommandHidden12-7-2018 12:50:080 (0x0000)
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.ztiRunCommandHidden12-7-2018 12:50:080 (0x0000)
About to run command: DiskPart.exe /s C:\Users\ADMINI~1\AppData\Local\Temp\radC69C6.tmpztiRunCommandHidden12-7-2018 12:50:080 (0x0000)
Command has been started (process ID 7784)ztiRunCommandHidden12-7-2018 12:50:080 (0x0000)
  Console > Microsoft DiskPart version 10.0.17134.1ztiRunCommandHidden12-7-2018 12:50:090 (0x0000)
  Console > Copyright (C) Microsoft Corporation.ztiRunCommandHidden12-7-2018 12:50:090 (0x0000)
  Console > On computer: PC-01ztiRunCommandHidden12-7-2018 12:50:090 (0x0000)
  Console > DiskPart has encountered an error: Er is geen toewijzing uitgevoerd tussen accountnamen en beveiligings-id's.ztiRunCommandHidden12-7-2018 12:50:090 (0x0000)
  Console > See the System Event Log for more information.ztiRunCommandHidden12-7-2018 12:50:090 (0x0000)
Return code from command = -2147023564ztiRunCommandHidden12-7-2018 12:50:090 (0x0000)
Command has returned: -2147023564LTIApply12-7-2018 12:50:090 (0x0000)
No boot drives found. None.LTIApply12-7-2018 12:51:140 (0x0000)
Reverting autorun setting to - 145LTIApply12-7-2018 12:51:140 (0x0000)
Boot Drive not found, attempting recovery option (Win8+Sysprep scenario)...LTIApply12-7-2018 12:51:140 (0x0000)
Found Recovery option: MBR011 Primary499 \\?\Volume{2d6a04e8-0000-0000-0000-100000000000}System Reserved464LTIApply12-7-2018 12:51:140 (0x0000)
ZTI ERROR - Unhandled error returned by LTIApply: Ongeldige procedureaanroep of ongeldig argument (5)LTIApply12-7-2018 12:51:140 (0x0000)
Command completed, return code = -2147467259 LiteTouch12-7-2018 12:51:150 (0x0000)
Litetouch deployment failed, Return Code = -2147467259  0x80004005LiteTouch12-7-2018 12:51:150 (0x0000)

↧
↧

MDT Deployment

July 12, 2018, 4:00 am
$
0
0

Hi;

I'm a newbie on MDT and WDS and trying to implement a sequence task for out of box experience for laptops.

I have a Windows 10 custom image, syspreped and capture it on MDT.

But, when i deploy it on MDT with Standard Client Install it deploys, but de client machine restarts and starts to configure the Windows.

I want is to deploy the image and shutdown client machine. Just like "OEM" machines…

Can anyone give some ideias how i can get this working?


↧

USMT - Roaming Profiles Windows 7 to Windows 10

July 2, 2018, 3:14 am
$
0
0

Hello,

I'm looking for some advice in regards to my customers migration from Windows 7 to 10 (new computers, no in-place upgrades), the client uses roaming profiles, I understand that you cannot use USMT with this, the client would like to switch to local profiles once on Windows 10, what would be the best approach for this? I don't think you can use the same roaming profile between operating systems can you? 

From my understanding, the best approach would be:

  1. On Windows 7 device - copy user(s) files (desktop, documents, music, pictures etc)
  2. Build Windows 10 device via MDT
  3. Remove roaming profile from Active Directory users and computers
  4. User logs onto Windows 10 with a new local profile
  5. Copy user files to Windows 10 device

Is this correct? Can USMT be used in anyway here?

Thanks,

Alex.

↧

MDT Running action which has since been removed from the TS

July 13, 2018, 2:55 am
$
0
0

Hi All,

Currently I am testing setting a wallpaper during deployment to display a message stating not to touch the device while the an upgrade is in process. We have had several deployments fail due to users attempting to log on or start using the machine.

My question is, I had created a TS step to initially create a temporary directory in which to store the image to be used however, I could not get this to work for some bizarre reason. Since then I have removed the TS step and decided to copy it to an already created directory. For some reason the task sequence is still running the action which has been removed. I have updated the deployment share and everything else. So i am at a loss to why this is occurring. 

If anyone can enlighten me that would be appreciated.

Many thanks,

Liam 

↧
Search

Setting Keyboard to UK before username and password box

July 13, 2018, 5:05 am
$
0
0

Hi 

is there a way to auto set the keyboard to UK before the Username/Password box.  

After the authenticated its fine, just cant make it default to UK before....

here are my custom files

[Settings]
Priority=Default
Properties=MyCustomProperty
[Default]
_SMSTSOrgName=Name
OSInstall=Y
SkipCapture=NO
SkipAdminPassword=YES
SkipProductKey=YES
SkipUserData=YES
SkipComputerBackup=YES
SkipBitLocker=YES
SkipLocaleSelection=YES
SkipTimeZone=YES
KeyboardLocale=en-GB
UserLocale=en-GB
UILanguage=en-US
TimeZoneName=GMT Standard Time
WSUSServer=http://ipaddress
EventService=http://ipaddress

bootstrap

[Settings]
Priority=Default
[Default]
DeployRoot=\\ipaddress\mdt$
KeyboardLocale=en-GB
SkipBDDWelcome=YES

↧
↧

Win10 Sysprep & Capture hung at 3%

July 13, 2018, 8:18 am
$
0
0

Anyone know a reason why a physical pc would hand at 3% of Capture WIM?

I'm not sure what all is on it but I was asked to create a WIM of the pc. So far it is at 3% and not moving.


Also, if this isn't going to go any further, how do I exit this situation without losing the OS/image on the physical pc? I'd like to reboot and restart the capture if possible.
↧

Losing customizations during deploy with SCCM

July 13, 2018, 9:14 am
$
0
0
The company I'm with is using Microsoft SCCM 2012 [System Center Configuration Manager] for deploying new desktop images, applications and updates to new and existing workstations/ VMs throughout the organization.   In order to create a standard base reference desktop image or 'golden image', they were previously  building a VM using Oracle VirtualBox and then using Symantec Ghost to capture / convert images to WIM files to be used by SCCM.  As it currently stands, they aren't happy with the whole process to create images and would like to get rid of the existing image creation process altogether.   It was taking too long to build [the tech was in Iowa and took 1-2 weeks to build], deliver and deploy to new network nodes / VMs [2+hrs via PXE - yikes].  So to recap - keep SCCM, get rid of the Symantec Ghost process.

That's where I come into the picture!  

They have tasked me with developing a new process to deliver a new image creation process that works with SCCM for deployment to 1000s users in the organization.   They have basically given me 'carte blanche' to seek out anything that with work.   

I have made progress in the last few weeks using MDT 2013 [Microsoft Deployment Toolkit] to create new images using task sequences to build images on VirtualBox.   Trials have been encouraging as I built a working base reference image of Windows 10 Enterprise using the current build [1803].   Deployment time was about 36 mins with no apps installed [PXE to desktop icons].  Currently, with 90-95% of the required apps [Office 365, Adobe Reader, Cisco AnyConnect,  etc] its  about 40-45min and they are happy with that.

However, here's where I need help.   My customizations are getting removed when the reference image is deployed to a new unit/workstation.   Using PowerShell scripting, these tweaks include simplifying the Start Menu / Desktop icons and deleting built-in Win10 apps.  When the image is deployed via SCCM, my customizations are 'lost' and the built-in Win10 apps  keep returning [like the Xbox app].  I have been researching this but haven't found a suitable resolution.   

So, with all that said, I was curious what methods most  SCCM / Systems Deployment teams are currently [and successfully] using to:

a) create the golden reference image to be used by SCCM.  MDT or other?
b) overcome any Win10 customization issue, especially with the built-in apps?
↧

Customizing MDT: reading variables from the form and using later in deployment

July 13, 2018, 2:09 pm
$
0
0

I have inherited an MDT deployment implementation, and decided to build a new server and then get fancy with the Deployment wizard and add my own pane for getting information.

I've been using the MDT Wizard Studio, quite an amazing tool, and I've made my own form that looks something like this:

What I want to do is take the values that the analyst sets in the drop-downs and supply them as parameters in a later task that runs a powershell script:

Here is what is supposed to happen when the values change in either of the dropdowns:

And finally here is my HTML for the page:

<H1>OS Customization</H1><td width=50><img src="sla.png"></td><td><p>Service Level: </br><select id=ServiceLevelList language=VBScript onchange="SetServiceLevel" class=wideedit><option value="2">Gold</option><option value="3">Silver</option><option value="4">Bronze</option></select><input type=hidden Name=ServiceLevelList /></p></td><td width=50><img src="patch.png"></td><p>Patching Group: </br><select id=WSUSGroupList language=VBScript onchange="SetWSUSGroup" class=wideedit><option value="PCM_BigFix_Sunday_A_2200">PCM_BigFix_Sunday_A_2200</option><option value="PCM_BigFix_Daily_A_1700">PCM_BigFix_Daily_A_1700</option><option value="PCM_BigFix_Manual">PCM_BigFix_Manual</option><option value="PCM_BigFix_Saturday_A_0000">PCM_BigFix_Saturday_A_0000</option><option value="PCM_BigFix_Saturday_A_0200">PCM_BigFix_Saturday_A_0200</option><option value="PCM_BigFix_Saturday_A_0800">PCM_BigFix_Saturday_A_0800</option><option value="PCM_BigFix_Saturday_A_2000">PCM_BigFix_Saturday_A_2000</option><option value="PCM_BigFix_Sunday_A_1000">PCM_BigFix_Sunday_A_1000</option><option value="PCM_BigFix_Sunday_A_1100">PCM_BigFix_Sunday_A_1100</option><option value="PCM_BigFix_Sunday_A_1200">PCM_BigFix_Sunday_A_1200</option><option value="PCM_BigFix_Sunday_A_1300">PCM_BigFix_Sunday_A_1300</option><option value="PCM_BigFix_Sunday_A_1500">PCM_BigFix_Sunday_A_1500</option><option value="PCM_BigFix_Sunday_A_1600">PCM_BigFix_Sunday_A_1600</option><option value="PCM_BigFix_Sunday_A_1800">PCM_BigFix_Sunday_A_1800</option><option value="PCM_BigFix_Sunday_A_1900">PCM_BigFix_Sunday_A_1900</option><option value="PCM_BigFix_Sunday_A_2000">PCM_BigFix_Sunday_A_2000</option><option value="PCM_BigFix_Sunday_A_2100">PCM_BigFix_Sunday_A_2100</option><option value="PCM_BigFix_Sunday_A_2300">PCM_BigFix_Sunday_A_2300</option><option value="PCM_BigFix_Tuesday_A_0700">PCM_BigFix_Tuesday_A_0700</option><option value="PCM_BigFix_Tuesday_A_1700">PCM_BigFix_Tuesday_A_1700</option><option value="PCM_BigFix_Tuesday_A_1800">PCM_BigFix_Tuesday_A_1800</option><option value="PCM_BigFix_Tuesday_A_2300">PCM_BigFix_Tuesday_A_2300</option><option value="PCM_BigFix_Wednesday_A_0500">PCM_BigFix_Wednesday_A_0500</option></select><input type=hidden Name=WSUSGroupListName /></p></td>

My issue is that the registry settings are the default values from CS.ini. I am weak with HTML so I'm guessing it's something in there with the names or how I'm assigning them in the vbscript that fires.

Can anyone with experience help point me in the right direction?

↧

Documenting MDT for a customer - What do you include?

July 15, 2018, 2:36 pm
$
0
0

Hello,

I'm wondering, what do you consultants in the marketplace include when tasked with documenting an MDT deployment? What sort of information would you include?

I've just delivered a MDT solution that deploys Windows 10 CBB...

I was thinking the following:

  • List of all applications, location of source files and command line used to install
  • List of supported models (drivers)
  • List the custom \ changed steps within the Windows 10 deployment task sequence
  • General information on the environment, hostname, hardware, software versions etc.

Thanks in advance.

↧
↧

Issues with deploying image

July 16, 2018, 5:53 am
$
0
0

Hi all,

I am creating a deployment image, and after the installation process, it reboots and comes up with a "Windows could not finish configuring the system. To attempt to resume configuration, restart the computer." ... and it keeps on doing this in a loop.

Another issue is that it keeps up asking for credentials to access the network share. I've set up a deployment share with these rules:

[Settings]
Priority=Default
Properties=MyCustomProperty

[Default]
OSInstall=Y
SkipCapture=NO
SkipAdminPassword=YES
AdminPassword=*******
SkipProductKey=YES
SkipComputerBackup=YES
SkipBitLocker=NO
TimeZoneName=W. Europe Standard Time
UILanguage=en-gb
UserLocale=en-gb
KeyboardLocale=en-gb;0809:00000809
JoinDomain=domain.local
MachineObjectOU=OU=xyzetc...
DomainAdminDomain=xyz
EventService=http://MDT01:9800

For the bootstrap.ini:

[Settings]
Priority=Default

[Default]
DeployRoot=\\MDT01\DeploymentShare$
UserID=MDT01\SRV_MDT
UserPassword=***********
UserDomain=MDT01.domain.local
KeyboardLocale=en-gb;0809:00000809

I've created a local user account on the server with access to the deployment share, instead of an AD user.

So at this stage I can see 2 issues, one for the network share access and another with the actual deployment.

Would appreciate your comments! Thanks a lot.

↧

Delaying domain join process

July 16, 2018, 8:21 am
$
0
0

Hi, I have to install an application wich can't be silently installed if the computer is in the domain. So I'd like to delay the domain join process but I have seen something to do in unattend.xml and ZTIDomainJoin.wsf but it doesn't seem to be for MDT 2013.

So do you have a solution?

Thanks

↧
Search

Set Sound Scheme to None or No Sounds for all users

July 4, 2017, 1:37 pm
$
0
0

Looking for advice on how to set the sound scheme to No Sounds or None for all users.  Good practices.

Deploying Windows 10 v1607 vanilla, and NOT using custom reference image and do not wish to go that direction.

I am considering adding a step in MDT to call and load default user hive (ntuser.dat), change the sound scheme, and unload the hive.  Will this work?  Is it good practice?

HKEY_USERS\.DEFAULT\AppEvents\Schemes

Create SZ called Default

Value would be .NONE


Should I be doing this through group policy?

Looking for step by step.

Thank you everyone!

Patrick



↧

WDS not generating boot files

June 21, 2018, 12:05 pm
$
0
0
I have been fighting with WDS to deploy my MDT generated image for at least a week now. We have been using the MDT image in iso format to deploy to computers locally for a few months now and the task sequence and install works great. The problem is when i add the lite touch wim file to WDS, it wont netboot with UEFI. I am not using DHCP Options as that appears to be deprecated, and all necessary IP Helpers are set. The computers receive and IP and see the server, but fail to boot. Secure boot is turned off. The message presented before it fails is "NBP filename is boot\x64\wdsmgfw.efi filesize is 0 bytes"  sure enough, if i go to my remoteinstall folder on the WDS server, in boot\x64, there is no wdsmgfw.efi file. it has generated several others, but there is nothing named anything even close. I have attempted to set the lite touch wim to the default for both regular x64 and x64 UEFI platforms to no effect. Where are these files supposed to come from? i completely started from scratch with my MDT sequence and regenerated it, uninstalled WDS role and reinstalled it after a reboot, all to no effect. What are the next steps i should take? it seems like such a minor thing but its causing the entire thing to not work
↧
↧

Start Menu borked on Fresh install of Windows 10

June 1, 2018, 3:56 pm
$
0
0

HI all,

I know this may be misleading, but I am having a problem with the start menu coming over on my image after being captured by and deployed with MDT.  I pain painstakingly customize the start menu so that my students have 90% of what they need readily available to them off the start menu.  I updated my image from 1703 (quite stable) to 1803 and, using the CopyProfile command in the unattend.xml file, I copy the admin profile over to the  default profile and making the start menu awesome.  I have used this technique successfully for both Win 7 and Win 10, but 1803 seems to not work with it.

I have tried capturing the image 4 times, and all four times the start menu doesn't apply and half the apps are extremely slow to respond.  Some keep settings, but it's like others are just caught in a strange loop that they can't get out of.  Even the local admin accounts are having problems after deployment.  I made a new image VM to see if I could fix this, and the default start menu came up with the arrows over a bunch of tiles that normally aren't there...just like when I deploy my image...

Has anyone else run into this in 1803 yet?  Please let me know!

PS.  I read this article, but I don't think it's the same problem I am running into.  I had no problems with 1703.

Please remember to click "Mark as Answer" on the post that helps you, and to click "Unmark as Answer" if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

↧

Surface Deployment Accelerators

July 16, 2018, 3:14 pm
$
0
0

Hi All

I am using the latest version of the Surface Deployment Accelerators (v 2.8.136.0) to rollout Windows 10 Enterprise 1803 July 2018 Edition

I have downloaded the ISO image to use as the source OS files for this edition from the MS Volume Licensing Service Centre and also from our MSDN Subscriptions (Business Editions)

When running the SDA wizard, when it prompts me to select the location of the Windows Source Files, I browse and select the Drive where the ISO image is mounted and select the root of the share but a red cross pops up saying "could not find a compatible ISO file in this location"

I know the ISO file is correctly mounted and is there. It happens with Windows 10 1709 edition ISO file as well

Interestingly, it works just fine with Windows 10 1703 Editions when I mount the ISO file downloaded from the VLSC site

Anyone else had this issue and if so what was your resolution step?

We have for now used the Windows 10 1703 Edition ISO and intend to patch up to 1803 edition manually but that is going to be laborious for 60 to 70 Surface devices

Any pointers are much appreciated

Thanks in advance



↧

Seperate driver sets (computer and printer)

July 16, 2018, 5:52 pm
$
0
0

Hi Team,

I need to install two types of drivers, the first being the laptop model drivers and the second being printer drivers.

At the moment, I have:

Out of the Box Drivers

> Windows 10 x64

 >> Dell Inc.

 >>> Model

>> Printer Drivers

 >>> Canon Universal x64

I'm setting Select Driver Group "DriverGroup001" to Windows 10 x64\%Make%\%Model% which is working perfectly.

How can I set it to also install the Canon Printer Drivers?

Thank you

↧
Viewing all 11297 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>