Wanted to bring something to the attention of everyone who may be using the "branding" scripts in MDT 2012 (Latest version) during OS Deployment.  It appears that these scripts take the username and password of the account used to join the domain and adds them to the branding keys in plain text.

If you're not familiar, the key is HKLM\Software\Microsoft\MPSD\OSD

The reg keys are:

OSDJoinAccount

OSDJoinPassword

Man am I glad I caught this prior to a major rollout.  I will be promptly reviewing and modifying these scripts to exclude this information in the registry for obvious security reasons!

The title that I typed for this post

"can I create TS that will include another TS with preselected Apps for  post install"

reflects the need for the following request:

Currently:

LiteTouch GUI displays available images for existing computers models. Next screen provides the list of available applications.

The request is:

to provide one click selection option that will allow to install OS with different post install application.

Ex. select: HP8300-profile 1 will deploy Windows 7 with post install Office, Antivirus, Adobe.

                HP8300-profile 2 will deploy Windows 7 with Firefox, CustomApp1, CustomApp2

I asked TS in TS just because I know that actually TS could be displayed for OSD in MDT.

Are there any option to accomplish the required ? Would SCCM be the answer?

Thanks.

"When you hit a wrong note it's the next note that makes it good or bad". Miles Davis

I tweaked O2013 in OCT and placed it to Applications in MDT..

Didn't note, but users complain about missing Dictionary. O2013 is French .

The only components enabled are: Word, Excel, PP.

Where to enable ?

Thx.

"When you hit a wrong note it's the next note that makes it good or bad". Miles Davis

When changes are made to the Checksum offloads, the NICs reset themselves and I'm losing connectivity to the deployment share during the deployment process (LiteTouch).  It happens during a custom PowerShell script I'm running in the Task Sequence after "Tattoo".

PowerShell Script:

Disable-NetAdapterChecksumOffload -Name * -IpIPv4
Disable-NetAdapterChecksumOffload -Name * -TcpIPv4
Disable-NetAdapterChecksumOffload -Name * -UdpIPv4
Disable-NetAdapterChecksumOffload -Name * -TcpIPv6
Disable-NetAdapterChecksumOffload -Name * -UdpIPv6
Disable-NetAdapterLso -Name * -IPv4
Disable-NetAdapterLso -Name * -IPv6
Disable-NetAdapterRss -Name *

Here are the errors from the BDD.log (sorry couldn't get the _SMSTaskSequence.log)

ZTIPowerShell processing completed successfully. ZTIPowerShell 8/25/2014 2:27:28 PM 0 (0x0000)
Command completed, return code = -2147467259 LiteTouch 8/25/2014 2:27:29 PM 0 (0x0000)
Litetouch deployment failed, Return Code = -2147467259  0x80004005 LiteTouch 8/25/2014 2:27:29 PM 0 (0x0000)
For more information, consult the task sequencer log ...\SMSTS.LOG. LiteTouch 8/25/2014 2:27:29 PM 0 (0x0000)
Property RetVal is now = -2147467259 LiteTouch 8/25/2014 2:27:29 PM 0 (0x0000)
Unable to copy log to the network as no SLShare value was specified. LiteTouch 8/25/2014 2:27:29 PM 0 (0x0000)

What I was thinking about trying was adding a few lines to the end of my script:

1. PING 1.1.1.1 -n 1 -w 30000 >NUL

    This would give the server 30 seconds to right itself after resetting the NICs

2. net use command to remap the share.

Two questions regarding re-mapping the share.

   1. I'm assuming this will run as Administrator token.  Will this be an issue for continued deployment?

   2. At the beginning of the deployment process the Tech has to enter his/her credentials to access the deployment share to begin the deployment process.  Are those the credentials I need to continue using, or does MDT use some other credentials to access the deployment share that far into the deployment process (during state restore phase)?

Thank you for taking time to read my post.

-Cheers!

Hi,

Please advise howto build and capture a task sequence in MDT. So not a capture from an existing ts but a build, then capture ts in MDT 2013. Iow, what are the final steps to use after a general built in order to properly capture to a wim-file.
A screenshotted step-by-step guide would be usefull.

J.

Jan Hoedt

I have setup a Native VHD system and am having problems moving the Windows Recovery Environment out of the VHD to its' own partition.

I am not having much luck getting REAGENTC.EXE to establish the new /target.

C:\Users\Administrator>reagentc /info
Windows Recovery Environment (Windows RE) and system reset configuration
Information:

    Windows RE status:         Enabled
    Windows RE location:       \\?\GLOBALROOT\device\harddisk2\partition1\Recovery\WindowsRE
    Boot Configuration Data (BCD) identifier: c02b8b67-4993-11e4-b309-0090a9b7bb54
    Recovery image location:
    Recovery image index:      0
    Custom image location:
    Custom image index:        0

REAGENTC.EXE: Operation Successful.

How does one change the BCD identifier and location path shown above for Native Boot VHD systems?

I have messed with this for a few days, and am not finding any solutions.

Hi All,

I`m in the process of creating a single master image for devices in France and Netherlands, I`ve installed all the relevant applications, software and MUI language packs and syspreped and captured the image. The problem is when I attempt to install Windows 7 from the bootable USB it only provides English as the language to install. How do I change this so it allows me to install French and Dutch from the USB?

When I double click the setup.exe file from an existing Windows 7 installation it provides me with the option to install English, French and Dutch but not when I boot from USB. 

Any advice would be hugely appreciated. 
Thank you,

Scott Evans

acronis image that I use to resore for making changes before capture with MDT2012.

Used this image during last 3 weeks.

Restored it applied some MS patches and trying to capture with MDT as usually.

Tried few times, restarted server and pc but getting the same error. It fails during Apply WinPE phase.

Could it be that my image became "no good". How to tackle this thing?

BDD:

<![LOG[Property LogPath is now = C:\MININT\SMSOSD\OSDLOGS]LOG]!><time="07:31:22.000+000" date="10-02-2014" component="Wizard" context="" type="1" thread="" file="Wizard">
<![LOG[Property definition is now = Summary_Definition_ENU.xml]LOG]!><time="07:31:22.000+000" date="10-02-2014" component="Wizard" context="" type="1" thread="" file="Wizard">
<![LOG[Microsoft Deployment Toolkit version: 6.1.2373.0]LOG]!><time="07:31:22.000+000" date="10-02-2014" component="Wizard" context="" type="1" thread="" file="Wizard">
<![LOG[Property Debug is now = FALSE]LOG]!><time="07:31:22.000+000" date="10-02-2014" component="Wizard" context="" type="1" thread="" file="Wizard">
<![LOG[Not Wizard = Faux]LOG]!><time="07:31:23.000+000" date="10-02-2014" component="Wizard" context="" type="1" thread="" file="Wizard">
<![LOG[Property WizardComplete is now = N]LOG]!><time="07:31:23.000+000" date="10-02-2014" component="Wizard" context="" type="1" thread="" file="Wizard">

&quot;When you hit a wrong note it's the next note that makes it good or bad&quot;. Miles Davis

I checked for component update.

Found required did install. I strongly believe I had it installed before. And today's reinstallation just change the installation date in Control Panel. How to identify if the appropriate version is installed. Required (in MDT) and installed are have nothing in common. May be it displays the version of x86.

&quot;When you hit a wrong note it's the next note that makes it good or bad&quot;. Miles Davis

I haven’t been able to find much info on this so I thought I would try here and see if anyone can help. We’ve been using MDT 2010 for the last couple of years to install Windows 7 on Macintosh’s running Bootcamp and it’s been working fine. We recently upgraded to MDT 2012 and the same process we used to use for this does not work anymore and I would like to find out how to make it work on 2012. Here’s how the process works: 

First, setup Bootcamp on the Mac.  This creates another partition on the Mac for the Windows OS (partition 3 for MAC OS 10.6 and lower, partition 4 for OS 10.7 Lion because of the recovery partition). Unfortunately Bootcamp cannot create NTFS partitions so it formats it as FAT32.

We then create a standard client task sequence using MDT and the Windows 7 source files (not a custom image) and give it a name to make it obvious it’s for Mac’s – “Windows 7 for Macintosh running Bootcamp”. We edit that task sequence and disable the built in “Format and Partition Disk” step since we don’t need to create the partition, only format it as NTFS. We then create a custom diskpart.txt file called BootCamp_Lion.txt with the following contents:

SELECT DISK 0

SELECT PARTITION 4

FORMAT FS=NTFS QUICK OVERRIDE

We place this file in the “Extra directory to add” location we’ve specified in the Win PE Customization section so it is located on the root of X:\ when it boots into Win PE. We then add a command line to the task sequence:  diskpart.exe /s x:\BootCamp_Lion.txt to format the existing bootcamp partition as NTFS.  Then in the “Install Operating System” step we set it to apply to a specific disk and partition – Disk 0, Partition 4. This installs Windows 7 on the Bootcamp partition and leaves the Mac OS intact and has been working fine in MDT 2010. Now with MDT 2012, the task sequence starts fine, formats the partition, installs Win 7, but when it comes up in the full OS for the first time I get the error “Unable to find the SMS Task Sequencer. The deployment will not proceed.”  And the task sequence stops. I know the partitioning part has changed in 2012 and have read that you can get this error if you deploy to something other than disk 0, partition 1 but I’m wondering if I can accomplish the same thing that I used to have working in 2012. Is there a different way I can do this?  Any help would be appreciated.

Thanks,

Robb

Hello, I have some drivers that may be needed on a deployed computer and may not be, for example, some specific printer drivers.  For that matter, I may not have the printer in question plugged into the machine when I image it with MDT, but would love to already have the driver in place so that after I image it and then plug in the printer, the drivers are present.  So is there a way to force MDT to put drivers in a driver store without actually installing them?

Hi everyone!

Actually my MDT is configured for deploying 3 OS (WIN7x86FR, WIN7x64FR, WIN7x64EN) with 3 "new computer task sequence".

i create an UserExit Script who provide "OSDComputerName" variable value with nslookup resolution and provide "AdminPassword" value with a specific hash. I create a new wizard panel to provide a new "MYDomain" Property for joining different Domain. After OS installation

My customsettings rules is configured to Skipcapture=YES because my properties are not compatible with a capture task sequence.

So my question is :

is it bad practice to capture an image that was deployed from mdt after adjustment?

or there is no any consequences?

&quot;When you hit a wrong note it's the next note that makes it good or bad&quot;. Miles Davis

I followed the official documentation to use locationserver.xml when load balancing, except it's not using the path. It just shows X:\Deploy as the path. If I choose a different server and then choose the first server from the drop down, the path stays stuck on the second server. Is the official documentation missing a UNCPath tag of some sort for the load balanced servers?

Create a LocationServer.xml File to Load Balance Multiple Servers at Different Locations

<?xml version="1.0" encoding="utf-8" ?><servers><QueryDefault></QueryDefault><server><serverid>1</serverid><friendlyname>
          Contoso HQ, Seattle, USA</friendlyname><Server1>\\STLDS01\Deployment$</Server1><Server2>\\STLDS02\Deployment$</Server2><Server3>\\STLDS03\Deployment$</Server3><Server weight=”1”>\\STLDS01\Deployment$</Server><Server weight=”2”>\\STLDS02\Deployment$</Server><Server weight=”4”>\\STLDS03\Deployment$</Server></server><server><serverid>2</serverid><friendlyname>
          Contoso NYC, New York, USA</friendlyname><UNCPath>\\NYCDS01\Deployment$</UNCPath></server> </servers>

If this post is helpful please vote it as Helpful or click Mark for answer.

I run a script in Postinstallation in my Task Sequence. I am trying to copy some files to a location on the destination disk of the OS installation, but receive this error: FAILURE ( 5456 ): Unable to determine Destination Disk, Partition, and/or Drive.

The script is pretty simple, and is intended to customize the App Layout file (Start screen layout), by copying the AppsFolderLayout.bin to the Default profile folder. But it fails at this:

sDestinationDrive = oUtility.GetOSTargetDriveLetter

It has this one included <script language="VBScript" src="ZTIUtility.vbs"/>, from which I see that oUtility should come from.

The Preinstall "Format and Partition Disk" is default (Disk 0, Standard MBR and 100% of disk, Variable:OSDisk). The "Install Operating System" default too (Logical drive letter stored in variable: OSDisk).

Any insight on this error will be appreciated.

I'm using a VirtualBox VM to pilot some changes and I've run into an unusual problem that only seems to affect VirtualBox VM's.  Other machines (VMware VM's, Hyper-V VM's and physical) work fine no matter which setting for the Install OS step.

I discovered that the Install OS step in the TS was set to 'Specific disk and partition Disk 0 Partition 1', for whatever reason, and didn't change it because things were working.  (This is a new organization)  When its setup like this, the VirtualBox VM fails with "Failure ( 5456 ): Unable to determine Destination Disk, Partition and/or Drive. See BDD.LOG for more information."  In the BDD, right above that line it says "DestinationDisk and Partition did not yield a target Partition."

Curious, when I check `diskpart > lis dis` it says "There are no fixed disks to show."  I double checked the VM config & tried again.  As soon as I was in PE I checked diskpart and it shows disk 0 with 45GB free.  Good. Select the TS, it begins then fails again with the same error.  I go back into diskpart and the disk is missing. ??

I change the Install Os step to 'Logical drive letter stored in a variable', set the variable to 'OSDisk'.  I then checked the properties of the Partition under 'Format and Partition' and manually entered 'OSDisk' as the variable since the field was empty.  The rest of the properties look normal: Primary partition, 100%, make this a boot partition, NTFS file system, quick format.


One more try: Boot the VM, check the disks (OK), select the TS stalls on 'Format and Partition Disk Preparing Disk 0 Partitions ...'.  I open BDD and I see several lines that read "Waiting for Drive to Exist: X%"  Finally it fails with "ZTI ERROR - Unhandled error returned by ZTIDiskpart: Object Required (424)".  I check the disks again and its missing.  What the heck?

I created a brand new standard client TS, made zero customizations to it, & tried both the WIM we're deploying and a stock Win7 WIM but they both fail with the Object required error. 

does MDT Team plan a update for Windows 10?

Error's durring Setup - (Import Windows 10 from ISO, Standard tasksequence)

Chris

in my mdt I have 4 images for Desktops and 4 for laptops they contain basic apps.

Then I have Applications for post deployment installation that a tech have to select (Office, Antivirus) other softs are installed manually depending on department requirements.

I have a colleague that never opened a Workbench, but read some MDT reviews and insists that I don't need 8 images (TSs) for Windows 7. But only one with Drivers in Out of the Box. Sure I have some NETWORK drivers without which I couldn't capture images and some video drivers in Out of the Box.

I would like to know if somebody has one Windows 7 or one Windows 8 Image/Task Sequence and just bunch of Drivers in out of the box for multiple computer models (how many?)? I still believe that having an image per model in environment where 1-2 models are added per year is practical.

Also can somebody with more than 5 applications in Applications node share his number of apps and in case that it is more than 10 do you bundle them for providing to a tech one click option to define 5 , 8 and etc apps for post installation.

Thx.

&quot;When you hit a wrong note it's the next note that makes it good or bad&quot;. Miles Davis

I want to load custom vbs script before selecting task sequence to display hardware info like CPU ram ...

What will be the best practice to run *.vbs - do I add that to Lite Touch.wsf

I did try to add:

Dim objShell
Set objShell = Wscript.CreateObject("WScript.Shell")
objShell.Run "msg.vbs"

to Lite Touch.vbs file, byt no msg is displayed

I have three different MDT-installations providing me with one fully automated ref.image i then use in two different systems depending if the computer is in school or in other community service.

i recently updated the ADK to the one released just a few days ago (http://www.microsoft.com/en-US/download/details.aspx?id=39982) and now my ref.image capture process is broken. the capture will not happen and i get this error message: 

Error creating an image of drive C:, rc = 1
ZTI ERROR - Non-zero return code by ZTIBackuo, rc = 1
Litetouch deployment failed, Return Code = -2147467259 0x80004005
Failed to run the action: Create WIM.
Incorrect function. (Error: 00000001; Source: Windows)
The execution of the group (State Restore) has failed and the execution has been aborted. An action failed.
Operation aborted (Error: 80004004; Source: Windows)
Failed to run the last action: Create WIM. Execution of task sequence failed.
Incorrect function. (Error: 00000001; Source: Windows)
Task Sequence Engine failed! Code: enExecutionFail
Task Sequence execution failed with error code 80004005
Error Task Sequence Manager failed to execute task sequence. COde 0x80004005

i also have this issue in one of the other installations which also is used to provide our computer supplier with a correct WIM-file.

so, i did what most people would do i guess... i reinstalled the older version of ADK and now i got it working in both my enviroments used to create WIM-files...

how can i provide information in order to solve this issue?

i would guess i rather have the new ADK installed instead of the old one, but the new one is not working properly.