Hey guys,

I want to run a batch script, that gives some information to the user. It should appear before the BDDWelcome-screen appears!

Does anybody know how to do this?

Another possibility would be adding a point at the BDDWelcome-screen between the start-button and the Exit to commandline button. By clicking it the batch script should appear, but the BDDWelcome-screen should stay open.

Who can help me? 

I'm Working on MDT 2012 since 2 weeks (learning) and i found a trick which could be interesting.

I'm using the database to store every settings to automate completely a deployment on a reference computer and capture, and i use multiple role on one computer :

An example :

First role "General settings" which apply to every computer

Second role "OS Installation" which could change (OS type, task sequence....)

Third role "Debugging" to store advanced logs if needed

In the CS.ini, if in priority section "RSettings, RPackages, RApps, RAdmins," are placed before "CSettings, CPackages, CApps, CAdmins, CRoles", only one role is parsed, and in a best case automation is interrupted by displaying a wizard page, in a worse case you've got an error (driver mismatch in my case) which takes you to the wrong way for debugging.

The trick :

CRoles must be parsed before RSettings to populate assigned roles (due by script design) and retrieves all settings from all roles (and merged for deployment)

I keep getting "The package (patch) GUID {7fe1f303-a528-4154-904b-ee10f4d79068} does not exist" at the end of the deployment. I'm testing in a Hyper-V VM, OS is Windows 7 SP1 Enterprise which was fully patched before sysprep (could this be the error, that no patches are available?).

I opened up BDD.log found in C:\Windows\Temp\DeploymentLogs with SMS Trace and this is the output (around this error):

ZTIPatches Entered PREINSTALL state. Deployment Method = UNC ZTIPatches 29.7.2012 23:06:09 0 (0x0000)
Operating system being deployed requires amd64 updates. ZTIPatches 29.7.2012 23:06:09 0 (0x0000)
Pre-Install setup installation state. ZTIPatches 29.7.2012 23:06:09 0 (0x0000)
Load XML.... ZTIPatches 29.7.2012 23:06:09 0 (0x0000)
Unable to find the Packages.xml file, assuming there are no packages to inject. ZTIPatches 29.7.2012 23:06:09 0 (0x0000)
Adding non-language pack entries to unattend.xml ZTIPatches 29.7.2012 23:06:09 0 (0x0000)
Open Control File: Packages ZTIPatches 29.7.2012 23:06:09 0 (0x0000)
Adding language pack entries to unattend.xml ZTIPatches 29.7.2012 23:06:09 0 (0x0000)
Add package {7fe1f303-a528-4154-904b-ee10f4d79068} ZTIPatches 29.7.2012 23:06:09 0 (0x0000)
The package (patch) GUID {7fe1f303-a528-4154-904b-ee10f4d79068} does not exist. ZTIPatches 29.7.2012 23:06:09 0 (0x0000)
Nothing to save, exit. ZTIPatches 29.7.2012 23:06:09 0 (0x0000)
Language pack entries added to unattend.xml successfully ZTIPatches 29.7.2012 23:06:09 0 (0x0000)
ZTIPatches processing completed successfully. ZTIPatches 29.7.2012 23:06:09 0 (0x0000)
Microsoft Deployment Toolkit version: 6.0.2223.0 ZTINextPhase 29.7.2012 23:06:09 0 (0x0000)
The task sequencer log is located at X:\WINDOWS\TEMP\SMSTSLog\SMSTS.LOG.  For task sequence failures, please consult this log. ZTINextPhase 29.7.2012 23:06:09 0 (0x0000)

Can anyone explain what the error is and how I'm able to resolve it. BTW I can't find the SMSTS.LOG at that location.

Hello Guys,

We created Winodows XP Images thorugh Symantec Ghost. As now we are moving to Windows 7, so are creating Windows 7 Image thorugh MDT 2012(Creating Media). For windows 7 Deployment, we don't have any environment set at our client side. So we need to create some bootable external media through which engineer can deploy the images on workstations.

But here we have only one External HDD assigned to engineer and they need to deploy Ghost Images as well as Windows 7 images thorugh the same.

Here our problem is that we are not able to create bootable(dual boot) media through which we can get option to deploy both Ghost Images as well as Windows 7 Images(Created through MDT(Media).

Please help us if anyone has done this..

Thanks,

Dinesh Kashyap

I am trying to use UpdateExit.vbs to run a command against the mounted litetouch WIM when it is being created/updated in MDT 2012.  I had this working in MDT 2010.

I added the command to the If oEnv("STAGE") = "WIM" section of the UpdateExit.vbs and I added a WScript.Quit 1 to the end so that the output would be listed in the MDT console.  The issue I am having is that it appears that STAGE is never set to WIM so that section is never processed and my command is never run.

I see stages called POSTWIM, ISO and POSTISO, but not one called WIM.

Here is the output from my console:

=== Making sure the deployment share has the latest x86 tools ===

=== Processing LiteTouchPE (x86) boot image ===

Building requested boot image profile.
Determining if any changes have been made in the boot image configuration.
No existing boot image profile found for platform x86 so a new image will be created.
Calculating hashes for requested content.
Changes have been made, boot image will be updated.
Windows PE WIM D:\Program Files\Windows AIK\Tools\PETools\x86\winpe.wim will be used.
WIM file mounted.
Set Windows PE system root.
Set Windows PE scratch space.
Added component winpe-hta
Added component winpe-scripting
Added component winpe-wmi
Added component winpe-securestartup
Added component winpe-mdac
Added component dart
<the part where it injects drivers>
<the part where it copies files>
Copying WIM to the deployment share.

Microsoft (R) Windows Script Host Version 5.6
Copyright (C) Microsoft Corporation 1996-2001. All rights reserved.

INSTALLDIR = C:\Program Files\Microsoft Deployment Toolkit
DEPLOYROOT = D:\DeploymentPoints\Workstation
PLATFORM = x86
ARCHITECTURE = x86
TEMPLATE = LiteTouchPE
STAGE = POSTWIM
CONTENT = C:\DOCUME~1\user\LOCALS~1\Temp\1\MDTUpdate.4860\LiteTouchPE_x86.wim

Exit code = 1

Creating an ISO.
Microsoft (R) Windows Script Host Version 5.6
Copyright (C) Microsoft Corporation 1996-2001. All rights reserved.

INSTALLDIR = C:\Program Files\Microsoft Deployment Toolkit
DEPLOYROOT = D:\DeploymentPoints\Workstation
PLATFORM = x86
ARCHITECTURE = x86
TEMPLATE = LiteTouchPE
STAGE = ISO
CONTENT = C:\DOCUME~1\user\LOCALS~1\Temp\1\MDTUpdate.4860\ISO

Exit code = 1

Copying ISO to the deployment share.
Microsoft (R) Windows Script Host Version 5.6
Copyright (C) Microsoft Corporation 1996-2001. All rights reserved.

INSTALLDIR = C:\Program Files\Microsoft Deployment Toolkit
DEPLOYROOT = D:\DeploymentPoints\Workstation
PLATFORM = x86
ARCHITECTURE = x86
TEMPLATE = LiteTouchPE
STAGE = POSTISO
CONTENT = C:\DOCUME~1\user\LOCALS~1\Temp\1\MDTUpdate.4860\LiteTouchPE_x86.iso

Exit code = 1

=== Completed processing platform x86 ===

=== Making sure the deployment share has the latest x64 tools ===

=== Processing LiteTouchPE (x64) boot image ===

Building requested boot image profile.
Determining if any changes have been made in the boot image configuration.
No existing boot image profile found for platform x64 so a new image will be created.
Calculating hashes for requested content.
Changes have been made, boot image will be updated.
Windows PE WIM D:\Program Files\Windows AIK\Tools\PETools\amd64\winpe.wim will be used.
WIM file mounted.
Set Windows PE system root.
Set Windows PE scratch space.
Added component winpe-hta
Added component winpe-scripting
Added component winpe-wmi
Added component winpe-securestartup
Added component winpe-mdac
Added component dart
<the part where it injects drivers>
<the part where it copies files>
Copying WIM to the deployment share.
Microsoft (R) Windows Script Host Version 5.6
Copyright (C) Microsoft Corporation 1996-2001. All rights reserved.

INSTALLDIR = C:\Program Files\Microsoft Deployment Toolkit
DEPLOYROOT = D:\DeploymentPoints\Workstation
PLATFORM = x64
ARCHITECTURE = amd64
TEMPLATE = LiteTouchPE
STAGE = POSTWIM
CONTENT = C:\DOCUME~1\user\LOCALS~1\Temp\1\MDTUpdate.4860\LiteTouchPE_x64.wim

Exit code = 1

Creating an ISO.
Microsoft (R) Windows Script Host Version 5.6
Copyright (C) Microsoft Corporation 1996-2001. All rights reserved.

INSTALLDIR = C:\Program Files\Microsoft Deployment Toolkit
DEPLOYROOT = D:\DeploymentPoints\Workstation
PLATFORM = x64
ARCHITECTURE = amd64
TEMPLATE = LiteTouchPE
STAGE = ISO
CONTENT = C:\DOCUME~1\user\LOCALS~1\Temp\1\MDTUpdate.4860\ISO

Exit code = 1

Copying ISO to the deployment share.
Microsoft (R) Windows Script Host Version 5.6
Copyright (C) Microsoft Corporation 1996-2001. All rights reserved.

INSTALLDIR = C:\Program Files\Microsoft Deployment Toolkit
DEPLOYROOT = D:\DeploymentPoints\Workstation
PLATFORM = x64
ARCHITECTURE = amd64
TEMPLATE = LiteTouchPE
STAGE = POSTISO
CONTENT = C:\DOCUME~1\user\LOCALS~1\Temp\1\MDTUpdate.4860\LiteTouchPE_x64.iso

Exit code = 1

=== Completed processing platform x64 ===

=== Processing complete ===

Refresh scenario

I have a machine which currently runs Windows 7 Professional x86, I try to do a refresh scenario to get Windows 7 enterprise x86 and it throws up an error during the initial windows setup phase (something about a configuration problem, I can’t remember the text and I’m not bothered about the error because that isn’t my question), my question is:

Is it possible that using the refresh scenario I can redeploy a different edition of windows 7 (even an x64 edition) or do I need to use the new computer or upgrade scenario for this?

Thanks

Steve

I seem to be having an issue with performing a refresh deployment going from windows 7 professional x64 to windows 7 enterprise x64. when the enterprise OS is going through the setting up the system phase (black screen, windows logo in the middle, white text at the bottom). a windows message appears in the middle of the screen stating the following:

windows could not configure one or more system components. to install windows, restart the computer and then restart the installation

restarting the computer will bring it back to this message, or one similar stating that the system restarted unexpectedly and that i need to restart the installation. why does this error occur, how can i get round it?

thanks

Steve

When i start a deployment using MDT by using the boot media, all my screens are answered for me and it's completley automated - i started off by using customsettings.ini but then found the database is more powerful - either way its automated, great!

However, when i execute the litetouch.vbs script while already booted into an OS the screens presented are not automated. is there a way to automate these screens, obviously the boot media must do something differently from the vbs script. all i want is to simply execute the script and let it get on with it (my DB records are based on location, make/model, and serial numbers so everything is already pre-designed.

thanks

Steve

I have some xml files written for me for our deploy. All I did was take those files, drop them in the x86 and amd64 folders, edit the customsettings.ini file, and was able to capture data.

When it gets to the Restore, it fails stating "the specified disk or diskette cannot be accessed." I'm only using MDT TS to capture and restore the data. The xml files do work as they are using them in LanDesk Migration.
I do not know how (or even if I need to) assign the x86 xml files for the capture and the amd64 files for the restore, as they suggest I do. They perform a working capture/restore this way with LanDesk.

I have nothing but limited exposure to USMT 4 and how to restore the data, which I see, because its right there where I told it to go! Just don't know how to get it back. I've given wide-open access to the folder.
Thanks!

When deploying a task sequence using winpe & MDT 2010 everything seems to work fine untill the stage 'restart computer' stage because after this, it does not automatically log back on as the administrator. When manually trying to log on as the administrator I recieve the error 'Administrator account has been disabled'.

I have worked a way around this by booting into safe mode & enabling the account but this way the task sequence cannot continue with the state restore part of the task sequence. I have done some reading and apparently sysprep is causing this problem.

We have many other WIM files and task sequences which all work OK so I don't know why this problem is happening on this particular WIM file.

Any help/advice would be greatly appreciate, thank you.

When setting up the task sequence to deploy Windows XP, I specified the OEM CD Key I use to use with MDT 2010.  I am using Dell OEM media on Dell Hardware with a Dell OEM Key.  I can enter the key when prompted during the deployment, but it will not automatically be used during the deployment.

Mark

Hi Guys ,

I cath a

Hi guys

I have raised a Win XP SP3 image to the MDT 2010 with out Applications
After that I have created a task sequence related to this SO and making rule to perform installation of 13 applications
I have created a image to peform deployment

When I perform the SO and Applications deployment the application are not installed
I have checked the bdd log and I can see the following message: " <![LOG[Application List is empty, exiting ZTIApplications.wsf]LOG]!"

In the same mdt 2010 , when I perform this deployment using a unattend mode from original source Win XP SP3, the applications are installed successfull

Why the applications are not installed ?
Why the task sequence are stopped before installing applications on reference machine ( dell optiplex 380 )

Your reply will be highly appreciated

Rgds

Paul

Hello everyone,

I have successfully configured a new MDT 2012 environment from Release-To-Web versions of MDT. (Clean environment, no remnants of MDT 2010, etc.)

1 - I have copied the DaRT 7.0 Tools.cab file from both an x86 and x64 installation of Windows 7 Enterprise from the tutorial posted here:

http://blogs.technet.com/b/mniehaus/archive/2011/11/28/mdt-2012-new-feature-dart-integration.aspx

I enabled DaRT, updated my boot WIMs, and tried PXE booting to my deployment share. I connect to my deployment share with no issues.

I then open the DaRT toolset from the intro menu.

Problem: The Standalone System Sweeper fails to run. Clicking on it displays "The tool failed to run. Try choosing another tool." The only option is to click OK and takes you back to the main DaRT menu selection.

Tests I have performed so far: For kicks and giggles, I have also rebuilt the boot WIMs with all of the contents from (Admin PC's hard drive) C:\Program Files\Microsoft DaRT 7\v7\ folder into the X:\DeploymentShare\Tools\(x64 or x86)\ . I thought "Sweeper.cab" might do it, but no success.

Also, I know DaRT is partially working. Remote Connection starts automatically when the PC is booted to WinPE. I also know my DaRT media is not corrupted because I was able to generate a DaRT.iso image on my admin PC, extract the .WIM from the ISO and PXE boot that with NO issues. (Everything in that DaRT media works without issues, which leads me to believe it is something in MDT 2012.)

FYI, if it helps any, the "Version.txt" file from the DaRT 7.0 installation says: 7.0.291.0

I have my scratch space on my WinPE media set to "128"

My WAIK version is 7.1 (7.0 with SP1 Supplement)

Also to the MDT 2012 team: Thanks, this version is much more polished out-of-box versus the 2010 initial release. I don't have to use extra scripts to clean up the "dirty" environment at the end of a Task Sequence anymore (it just works now), and I don't get the odd partitioning scheme that 2010 used (BitLocker reasons). So, thumbs up!!!

Thanks,
stealthfield

Cory | Find me: Wordpress | Twitter: @stealthfield

What may be issue for this ?

Please provide the solution.

Hi,

I have installed MDT 2012 Update1 Beta1 from MDT 2012 and updated my existing deployment share. I have skipped everything in winpe phase and after the upgrade I can see MDT OS Roles and Features prompting for input. Is there any parameter so that I can skip it. I have also specified SkipOSRoles and SkipOSFeatures in Customsettings.ini but no luck.

Thanks inadvance

Cheers

Hari Rama K

Hello,

i have a little problem with the Deployment of a customized wim-file with MDT 2010.
Following situation: I use a Standard Windows 7 Enterprise 64bit Installation, where the latest Windows updates are installed. After Sysprep I captured a wim-file using imagex, imported in Operating Systems of MDT 2010, created a task sequence and then deployed. 

After the boot sequence you select the OS, the language packs and the software to install. The installation of the OS works fine until the point where the installation should start the software.right after the reboot. 

More specifically LiteTouch starts on the Windows desktop no longer automatic. But when I change to the directory C:\MININT\ and i start the file „LiteTouch.wsf“ manually, the installation of the pre-selected applications and the deployment runs through to the final report.  Why does the installation not run completely through automatically as with the ordinary standard install.wim?

Good Afternoon All!

I'm trying to create an OSD TS that does a few specific things and for the past 2 days have been using the UDI Wizard to try to get it to work.  The problem is, that UDI task sequences are more more complex than standard ones.  Most of the steps seem to deal with USMT which I'm not even that interested in.

Anyways, does anyone know of a good resource for training for this sort of specific thing?  I've found MDT training video and material, but none pertaining to UDI task sequences or MDT & SCCM.  I've already gone through Niall's SCCM Guide pages 16+, but need more info.

Thanks!

Ben K.

hi all.

Running MDT2012 and have setup a 'Run Powershell' Task. This seems to run some Microsoft.BDD.TaskSequncePSHost.exe process but its returning an error and not running:

ZTI ERROR - Non-zero return code by ZTIPowershell, rc = -532459699 0xE0434F4D

I've tested a simple PS script that simply says write-host "testing' and get the same error. Any ideas?

hello,

it is my understanding that the uninstall registry key name allows the application install process to detect if an application already exists by way of this registry key, if it does exist then it skips it. i am trying to utlise this key but there doesnt seem to be much information on how to use it. in my office 2010 application in MDT i added "MicrosoftOffice2010ProPlus" as my registry key name, but when installing office 2010 it doesnt seem to add this to the registry. so then i ad it manually myself but even if i do this and re run my task sequence the installation still tries to go ahead and install office 2010, it just seems to get stuck though.

can anyone provide some insight into how i could utilise this? what i want to achive is not reinstall an app that already exists.

Steve