I suddenly started getting this error on all my task sequences. I created a new vanilla sequence and got the error on it as well. It doesn't matter if I select a x86 image task or x64. This is across multiple pieces of hardware as well. Please Help!

I'm using MDT 2013u2 stand alone to build and capture a Windows 10 1511 image in a Hyper-V environment.  During the task sequence, sometimes when the TS process reboots, the client will appear to hang at the windows logon screen, waiting for the administrator password.  The task sequence is taking place behind the logon windo, and I can put in the password and watch the TS process working, but if I don't enter the Admin password, the logon screen just suts there with the TS going on behind it.

Is that normal or is there some way for me to avoid this?  I like to watch.

I have not tried using physical hardware to do my build and capture.  It "feels" like this might be caused by the way Hyper-V is more like an RDP session into the clientOS.  This does not happen when I use the same VM to build and capture Windows 7.

Hi all,

I am currently using MDT 2013 to deploy Windows 10 on several systems. In the task sequence is a custom task to remove the default Windows apps.

All default apps are uninstalled after deployment, but the icons/names still appear in the start menu and seem to be broken. Clicking these apps does nothing and in most cases the icon image is blank.

Is this a known issue and is there a solution?

The custom task contains the following script:

# ***************************************************************************
#
# File:      RemoveApps.ps1
#
# Version:   1.2
#
# Author:    Michael Niehaus
#
# Purpose:   Removes some or all of the in-box apps on Windows 8, Windows 8.1,
#            or Windows 10 systems.  The script supports both offline and
#            online removal.  By default it will remove all apps, but you can
#            provide a separate RemoveApps.xml file with a list of apps that
#            you want to instead remove.  If this file doesn't exist, the
#            script will recreate one in the log or temp folder, so you can
#            run the script once, grab the file, make whatever changes you
#            want, then put the file alongside the script and it will remove
#            only the apps you specified.
#
# Usage:     This script can be added into any MDT or ConfigMgr task sequences.
#            It has a few dependencies:
#              1.  For offline use in Windows PE, the .NET Framework,
#                  PowerShell, DISM Cmdlets, and Storage cmdlets must be
#                  included in the boot image.
#              2.  Script execution must be enabled, e.g. "Set-ExecutionPolicy
#                  Bypass".  This can be done via a separate task sequence
#                  step if needed, see http://blogs.technet.com/mniehaus for
#                  more information.
#
# ------------- DISCLAIMER -------------------------------------------------
# This script code is provided as is with no guarantee or waranty concerning
# the usability or impact on systems and may be used, distributed, and
# modified in any way provided the parties agree and acknowledge the
# Microsoft or Microsoft Partners have neither accountabilty or
# responsibility for results produced by use of this script.
#
# Microsoft will not provide any support through any means.
# ------------- DISCLAIMER -------------------------------------------------
#
# ***************************************************************************


# ---------------------------------------------------------------------------
# Initialization
# ---------------------------------------------------------------------------

if ($env:SYSTEMDRIVE -eq "X:")
{
  $script:Offline = $true

  # Find Windows
  $drives = get-volume | ? {-not [String]::IsNullOrWhiteSpace($_.DriveLetter) } | ? {$_.DriveType -eq 'Fixed'} | ? {$_.DriveLetter -ne 'X'}
  $drives | ? { Test-Path "$($_.DriveLetter):\Windows\System32"} | % { $script:OfflinePath = "$($_.DriveLetter):\" }
  Write-Verbose "Eligible offline drive found: $script:OfflinePath"
}
else
{
  Write-Verbose "Running in the full OS."
  $script:Offline = $false
}


# ---------------------------------------------------------------------------
# Get-LogDir:  Return the location for logs and output files
# ---------------------------------------------------------------------------

function Get-LogDir
{
  try
  {
    $ts = New-Object -ComObject Microsoft.SMS.TSEnvironment -ErrorAction Stop
    if ($ts.Value("LogPath") -ne "")
    {
      $logDir = $ts.Value("LogPath")
    }
    else
    {
      $logDir = $ts.Value("_SMSTSLogPath")
    }
  }
  catch
  {
    $logDir = $env:TEMP
  }
  return $logDir
}

# ---------------------------------------------------------------------------
# Get-AppList:  Return the list of apps to be removed
# ---------------------------------------------------------------------------

function Get-AppList
{
  begin
  {
    # Look for a config file.
    $configFile = "$PSScriptRoot\RemoveApps.xml"
    if (Test-Path -Path $configFile)
    {
      # Read the list
      Write-Verbose "Reading list of apps from $configFile"
      $list = Get-Content $configFile
    }
    else
    {
      # No list? Build one with all apps.
      Write-Verbose "Building list of provisioned apps"
      $list = @()
      if ($script:Offline)
      {
        Get-AppxProvisionedPackage -Path $script:OfflinePath | % { $list += $_.DisplayName }
      }
      else
      {
        Get-AppxProvisionedPackage -Online | % { $list += $_.DisplayName }
      }

      # Write the list to the log path
      $logDir = Get-LogDir
      $configFile = "$logDir\RemoveApps.xml"
      $list | Set-Content $configFile
      Write-Information "Wrote list of apps to $logDir\RemoveApps.xml, edit and place in the same folder as the script to use that list for future script executions"
    }

    Write-Information "Apps selected for removal: $list.Count"
  }

  process
  {
    $list
  }

}

# ---------------------------------------------------------------------------
# Remove-App:  Remove the specified app (online or offline)
# ---------------------------------------------------------------------------

function Remove-App
{
  [CmdletBinding()]
  param (
        [parameter(Mandatory=$true,ValueFromPipeline=$true)]
        [string] $appName
  )

  begin
  {
    # Determine offline or online
    if ($script:Offline)
    {
      $script:Provisioned = Get-AppxProvisionedPackage -Path $script:OfflinePath
    }
    else
    {
      $script:Provisioned = Get-AppxProvisionedPackage -Online
      $script:AppxPackages = Get-AppxPackage
    }
  }

  process
  {
    $app = $_

    # Remove the provisioned package
    Write-Information "Removing provisioned package $_"
    $current = $script:Provisioned | ? { $_.DisplayName -eq $app }
    if ($current)
    {
      if ($script:Offline)
      {
        $a = Remove-AppxProvisionedPackage -Path $script:OfflinePath -PackageName $current.PackageName
      }
      else
      {
        $a = Remove-AppxProvisionedPackage -Online -PackageName $current.PackageName
      }
    }
    else
    {
      Write-Warning "Unable to find provisioned package $_"
    }

    # If online, remove installed apps too
    if (-not $script:Offline)
    {
      Write-Information "Removing installed package $_"
      $current = $script:AppxPackages | ? {$_.Name -eq $app }
      if ($current)
      {
        $current | Remove-AppxPackage
      }
      else
      {
        Write-Warning "Unable to find installed app $_"
      }
    }

  }
}


# ---------------------------------------------------------------------------
# Main logic
# ---------------------------------------------------------------------------

$logDir = Get-LogDir
Start-Transcript "$logDir\RemoveApps.log"

Get-AppList | Remove-App

Stop-Transcript

Orange County District Attorney

Hi,

I am using WADK 1607 and MDT update 2. I am having issue with deployment process. I have created a simple bare metal task quence and on deployment of windows 10 1607 from baremetal task sequence edge browser automatically launches after log on. Due to this deployment get paused, as it is running from local admin account it throws a warning message that edge browser can not be open through local admin and here task sequence pauses. The task sequence continue after clicking OK button.

The machine is on Workgroup, so there is no gpo is doing the launching of edge.

The edge launches automatically at each logon. this is very basic task sequence and we did not make any customisation which launches edge.

Abhishek

Hi,

I have to implement show hidden file and show file extension for all user. This can be done using registry setting. But problem is that it is in HKCU setting and we want to implement for all user.

We have a situation where we can not implement GPO for this, so is there any way to do this using unattended or with MDT.

i have tried to add synchronous command in OOBE phase to show hidden file and set copy profile true. This did work for the user in which deployment finish, but it did not replicated the setting for other user.

I also tried to run synchronous command at specialize phase but this also did not work for any user even for which deployment completed.

Thanks

Abhishek

Domain Admin credentials provided to all tasks in task sequence and Domain Admin group has Full Control on Images volume where DeploymentShare$ is located.

After enabling this, all the workstations show status of "waiting" in MDT and never start applying the OS.  I had to manually switch them all to unicast to get them to image.

When I deployed a single system, it successfully deployed with multicast enabled, but the OS installed very, very slowly (maybe 5 times slower than normal).  When I tried to do multiple at the same time, it never even started deploying the OS.

I looked in the MDT deployment documentation and saw this:

"MDT supports only the multicast transfer of images stored in the LTI$ distribution share. Images stored in Windows Deployment Services cannot be deployed using multicast transfer"

I don't see any share on the deployment server named "LTI$."  How does that get created?  Do I have to manually rename a share to LTI$ to make this work? 

I've recently noticed an issue with Our MDT System. Sometimes while deploying PCs right when the task sequence gets to the State Restore Step it will skip about 30 steps in that sequence and go straight to the last 4 steps of my task sequence. it does not record any errors at all when this happens and the Toolkit Monitoring says it has complete all 119 Steps of my TS which it has not I have to Reimage again and hope that it doesn't do it again.  does anyone else have an issue similar to this? or any advice. I am on the Latest toolkit 6.3.8330.1000.

Edit: My Task sequence keeping failing randomly in the same spots or the next step after that

I have an in-house application that I have the task sequence install it will skip this one and go to the end of the sequence sometimes it works other times.  Other times it will install the in-house application and move on to the next step which is installing elo touch screen drivers but after the setup.exe for the touch screen drivers extracts I get a dirty environment prompt if I select no the entire task sequence fails and says the task sequencer is already running and then I have to start the reimage all over again. I really need help with this as I cant get any of my PCs to image now.  Nothing has been changed in the Toolkit or on the server as I'm the only one with access to it I was able to deploy fine earlier but after I deployed any now all my PCs are failing at the same spots

Edit2: I went through my log and found the following Errors:

<![LOG[Failed to run the action: Install Latest Java x64.
Incorrect function. (Error: 00000001; Source: Windows)]LOG]!><time="13:31:01.589+240" date="04-02-2016" component="TSManager" context="" type="3" thread="4464" file="instruction.cxx:911">

<![LOG[Failed to run the action: Install Silverlight.
Incorrect function. (Error: 00000001; Source: Windows)]LOG]!><time="13:31:01.635+240" date="04-02-2016"

<![LOG[Failed to run the action: Install Gate Central Terminal.
Incorrect function. (Error: 00000001; Source: Windows)]LOG]!><time="13:31:01.714+240" date="04-02-2016" component="TSManager" context="" type="3" thread="4464" file="instruction.cxx:911">

Hello

Im looking at others ways to deploy our images, we currently have setup a standard MDT image which works across the network say 8 out of 10 times.

Then sometimes the same image would fail, im feedup with trying to battle with the network team other this so im thinking of using something other than network to do this.

I know you can place the whole image on a usb but the image itsself gets updated quite frequently so i dont want to have to keep on updating the usb for say when i make a change like adding or changing an application to the image.

Ideally i would like something where i have say a MDT replica thats physically on a build desk and the we can image computers over say a USB connection.

any other ideas or or help on the above would be greatly appreciated

Thanks

Been looking around for a solution for this and have yet to come up w/ something.  We have (3) identical MDT servers, and I would like to load balancing incoming requests (our organization performs a LOT of imaging), but do not have the budget for a HW load balancer.

Ideally, I would like to round robin incoming PXE requests among the (3) servers but have not come up w/ a supported mechanism to do so - any ideas?

Considered using DFS to host the deployment shares, and having a single PXE/WDS box, but I do not believe this would force the client to pull the NIC from the DFS member it attaches to, am I wrong?

Any help, or ideas would greatly be appreciated!

Hi,

I have MDT2013Update 2. I have created one media using deployment workbench.

Now i want to update the path to another drive as the WIM file size is big and the drive has not the enough space to accommodate the changes when i will update the media.

So i want to change the media path. I dont want to create a new media. Just want to update the existing one.

Any help would be appreciated.

Hi All,

  I have a Windows Server 2012 R2 with MDT 2013 UPDATE 2 installed.  I can deploy OS with MDT solution successfully (All the clients in my company are Windows 7). I have a question about recovery paitition:

 Can I create a recovery partition during the deployment? After the OS is deployed and it will auto create a recovery image in this partition. If the computer has any problem. End uses can repair the computer by the following steps:

1. Press F8 to enter "Repair your computer" mode;
2. Select "System image recovery" or other opinions to load the image we created before.
3. Recover the computer automatically.

Any suggestion is appreciated.

Hi,

I'm starting to loose my sanity over MDT 2012 and language settings. Hopefully someone can help me :)

I'm Running SCCM 2012 with MDT 2012 Update 1.

I'm deplying Windows 7 through the UDI wizard used by our helpdesk around the globe. This requires different language and regional settings to be applied.

As a company we decided to make the OS languge english at all times, so the ONLY thing that changes is the regional settings on the US based image. Like keyboard, currency, timezone etc.

So out of the box this does not work at all. When our helpdesk in Denmark chose the settings below nothing worked. Still en-US settings applied:

I

I googled this and found out, that you need to modify the unattend.xml to change this.

I need to use the variable selected in the the UDI wizard, not some hardcoded settings. This is what most people suggest to change in the unattend.xml (In the settings package):

<InputLocale>%Keyboardlocale%</InputLocale>
<SystemLocale>%InputLocale%</SystemLocale>
<UILanguage>%UILanguage%</UILanguage>
<UserLocale>%Inputlocale%</UserLocale>

However this does not work at all (I applied it all 3 places in the unattend.xml, even some are for the PE....just to be sure)

I'm also very sure that I use the correct settings for amd64 and x86 in the unattend.xml so that is not the reason either.

Every time I image a machine I end up with the regional settings being en-US. No matter what is selected in the UDI.

Please someone help :)

Thanks!

Hello all,

i have this new Dell's laptop (Latitude E7470) that I'm trying to deploy. when deploy starts, right after I click on "Run the depoyment wizard to install a new computer deployment",  it immediately shout on missing drivers (PCI\VEN_8086&DEV_156F&SUBSYS_06DC1028&REV_21 which is the Intel(R) Ethernet Connection I219-LM device).

i followed this forum guide (http://en.community.dell.com/support-forums/laptop/f/3518/p/19676051/20898909?rfsh=1460360493687) which basically direct me to download the Intel driver from there site and extract it, and added all of the 32 and 64-bit drivers to their respective driver management locations (both their regular install folders and the winpe folder for the boot images).

For that i follow this guy guide (http://deploymentresearch.com/Research/Post/325/MDT-2013-Lite-Touch-Driver-Management) which basically tell me to create 1 folder under out of the box drivers for windows 7 drivers and 2 additional folders for WinPE 64 and WinPE 86. then make 2 selection profiles, 1 for the x64 and 1 for x86 and direct them to their designated folders under out of the box...

then i went to MDT Deployment share properties and at the Windows PE tab go to the Drivers and Patches and there configure for each platform which selection profile to use.

when booting for deployment i still have the same error.

under MDT Deployment share properties i went to Windows PE and under General tab i changed the background bitmap. when boot again i still getting the default bitmap and not what i choose. So i start thinking whether my new setup is working or not.

the strange thing is that i'm using VM to mount my basic windows installation and to patch it with new microsoft updates and then recapture it, for this I disjoin from the domain, and net use to the deploymentshare$ folder and run the litetouch.vbs.when doing this i do see the bitmap file I configured.

can any1 help pls? why when booting from WinPE and do not pull the MDT Deployment share properties and when running the litetouch.vbs it does.

Thanks a lot for your help.

While attempting to image some desktops today, we press F12 to PXE boot and after a minute, but before the menu appears where we'd normally choose the sequence we get a msg that says:

The task sequence has been suspended.
LiteTouch is trying to perform NIC configuration.
This cannot be performed in Windows PE.
If booting from a USB Flash Disk, please remove all drives before restarting.
Otherwise, ensure the hard disk is selected first in the boot order of the BIOS.
Reboot WinPE (Close all windows) to resume

I've found other posts online about this and it appears the solution is to wipe the existing partitions from the machine using diskpart.  I tried this on a couple and it did allow me to image again but this is not feasible on 1000+ desktops.  Can someone please help me determine the cause?

We're using MDT 2013 U2 (6.3.8330.1000), the last time we imaged was the start of May, no changes have been made to the MDT/WDS server since as far as I'm aware and I'm the one who would normally administer this server.  Also, this problem has started at several of our locations location, all using their own MDT/WDS server.  These servers do automatically install Windows updates (security and critical).

I have looked in D:\Minint\smsosd\osdlogs\bdd.log with cmtrace64.exe and the first red line says to check X:\Windows\Temp\smtslog\smts.log, this line actually appears 5 times in bdd.log so maybe it's expected. I've opened that and there are no red lines but there is a single yellow line that says: "Execution engine result code: 2"

I would include the logs here but I'm not sure how to get them off the desktop while in WinPE.  Any help would be greatly appreciated!

Hello All,

I'm trying to build my offline media however i'm getting the two errors as show below. Can someone please help?

The process completed with 2 errors.
Stating MDT Media Update
Access to the path 'D:\FinalImage\Content\Deploy\Control\Settings.xml' is denied.
The specified Drive Path does not exist.

Running MDT 2013 Update 2 on Server 2012 R2.