Hi!

We want to make use of the upgrade scenario to deploy Windows 10 on our Windows 8.1 clients. I downloaded the official Windows 10 media from Volume licensing center and imported it correctly into MDT.

When we try to start the upgrade, it fails with following in the BCD.log

4699421/09/2015 13:42:18LTIApplySetup failed to upgrade OS from  \\<our MDT server>\DeploymentShare$\Operating Systems\Windows 10 Enterprise x64\setup.exe, rc = -1047526908
4699721/09/2015 13:42:19LTIApplyZTI ERROR - Non-zero return code by LTIApply, rc = -1047526908  0xC1900204

So I've tried to start the ISO manually, wich gives a bit more explanation when we have to choose wich kind of upgrade we want:

"you can't keep windows settings, personal files, and apps because you've chosen to install windows 10using a different language than you're currently using."

That explains a lot. We are using Windows 8.1 client machines with the native en-US language, but have chosen to make nl-NL the default language for our users.

When I run "DISM /online /get-intl" we see clearly: Default system UI language : nl-NL.

When I change this to en-US the upgrade will succeed without a problem. But if we want to change it, we need to restart the machine and boot in a pre Windows environment. If we need to do that on every machine in our company the upgrade will take a lot longer than it should be.

I also tried to import the language pack into the ISO without success :-s

Anyone has an idea? Or a solution to bring the default system UI language to en-US? (like gpo?)

Currently I'm trying to deploy Windows 10 x64 for some of our workstations. In our task sequence we have a bunch of Applications to be installed. However I noticed something when testing.

If I force an Application (in this case the "Application" calls a Batch script which will just return with Exit /B 3) to fail, I see that ZTIApplications.wsf will Log the Error properly in BDD.log. However, immediately after it states that it states that "ZTIApplications processing completed successfully. " and  "Command completed, return code = 0".

What this means, is that my deployment will firstly continue on to the next task thinking it was successful. And then the end result is that a Final Summary page is shown saying "SUCCESS" but also stating "During the deployment process, 1 errors and 0 warnings were reported...", which is obviously a false positive.

So my question is:
-Is this expected behaviour?
-If this is expected behaviour, is this documented anywhere? I don't see anything related to this
-Are there any workarounds? Currently I'm thinking of running my Applications as Command Line tasks instead, since these seem to properly detect errors

Below is a log snippet for example. I made a custom task sequence which only runs my one Application, which is forced to be a failure (trimmed out time stamps, and thread so it's easier to read). Currently we were using MDT 2013 Update 1. However during this investigation I installed MDT 2013 Update 2. I see the issue in both cases:

Logs:

Microsoft Deployment Toolkit version: 6.3.8330.1000	ZTIApplications
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.	ZTIApplications
Language/Locale Identified (in order of precedence): 1033,0409,0x0409,9,0009,0x0009	ZTIApplications
Mandatory Single Application install indicated. Guid: {fb6ae709-9e4d-40b7-9f3a-f1a5a6f64274}	ZTIApplications
################	ZTIApplications
Entry: {fb6ae709-9e4d-40b7-9f3a-f1a5a6f64274}	ZTIApplications
Name:  Pason Core Applications	ZTIApplications
################	ZTIApplications
Using a local or mapped drive, no connection is required.	ZTIApplications


ZTI installing application 	ZTIApplications
About to run command: E:\Deploy\Tools\X64\bddrun.exe Install-Applications.bat	ZTIApplications
Command has been started (process ID 8980)	ZTIApplications
ZTI Heartbeat: command has been running for 0 minutes (process ID 8980)	ZTIApplications
Return code from command = 3	ZTIApplications
Application Pason Core Applications returned an unexpected return code: 3	ZTIApplications
Property InstalledApplications001 is now = {fb6ae709-9e4d-40b7-9f3a-f1a5a6f64274}	ZTIApplicationsZTIApplications processing completed successfully.	ZTIApplications
Command completed, return code = 0	LiteTouch
LTI deployment completed successfully	LiteTouch
Property RetVal is now = 0	LiteTouch

Starting this morning when trying to launch MDT I get an error message that says "a connection to the deployment share could not be made possible cause invalid credentials".

When I press F8 and open a command prompt and try to connect to the deployment share I get a message that access is denied. However, if I do net use I can map a drive using the credentials that are in the Custom.ini file.  

I haven't made any changes to the share permissions.  Everything was working OK until this AM.

Any help would be greatly appreciated.

Andrew Churchill

I'm trying to upgrade to Windows 10 in Microsoft Deployment Toolkit , but to start the process on the client with Windows 7 shows some errors , the process was followed like this tutorial:

https://technet.microsoft.com/en-us/library/mt426643(v=vs.85).aspx?f=255&mspperror=-2147217396

There are the errors:

Deployment Summary
Failure
Setup failed to upgrade OS from \\fwks014\mdtproductionS\Operating Systems\Windows 10
Pro Technical Preview x64X\setup.exe, rc -2147024809
ZTI ERROR - Non-zero return code by LTIApply, rc 1
Litetouch deployment failed, Return Code z -2147467259 Ox80004005
Failed to run the action: upgrade Windows.
unknown error (Error: 00000001; Source: unknown)
The execution of the group (Upgrade the Operating System) has failed and the execution has
been aborted. An action failed.
unknown error (Error: 80004004. Source: Unknown)
Failed to run the last action: upgrade Windows. Execution of task sequence failed.
unknown error (Error: 00000001; Source: Unknown)
Task Sequence Engine failed! Code: enExecutionFail
Task sequence execution failed with error code 80004005
SetNamedSecurityInf00 failed.
setobjectownero failed. ox80070005.
RegQueryValueExW is unsuccessful for SoftwareXMicrosoftXSMSXTask Sequence
SMSTSEndProgram
GetTsRegValue0 is unsuccessful. Ox80070002.
Error Task Sequence Manager failed to execute task sequence. Code Ox80004005

I'm using MDT Update 2 , tried upgrading to a desktop using Windows 7 Pro and a virtual machine using Windows 7 Pro .

I upload log in:

https://onedrive.live.com/redir?resid=83D67A22DCE62137!2292&authkey=!AMxJ3oFmE_i2Bqc&ithint=file%2clog

Hi. Is there anyway to password protect a bootable usb for Windows MDT? in the event a USB gets lost i don't want anyone to be bale to find it and utilize the USB, or see the settings of the customesettings.ini file. 

If i can even go as far as encrypting and still somehow booting would be even better. 

We need to upgrade some already in use Enterprise 10240 systems to Enterprise 1511.  Each workstation has a unique Administrator password.

How and when do we configure an administrator password that will work during the upgrade process?

Do we have to match the existing administrator password or will the task sequence change the password to the one specified for the task sequence?

I realize this is not an MDT related question but i have a golden image i am deploying where i use the CopyProfile unattended option. The admin profile has a Start Menu i have customized and that has the IE icon on it.

When i deploy and create a new user profile the place where the icon is supposed to be is just empty

<LayoutModificationTemplate Version="1" xmlns="http://schemas.microsoft.com/Start/2014/LayoutModification"><LayoutOptions StartTileGroupCellWidth="6" /><DefaultLayoutOverride><StartLayoutCollection><defaultlayout:StartLayout GroupCellWidth="6" xmlns:defaultlayout="http://schemas.microsoft.com/Start/2014/FullDefaultLayout"><start:Group Name="Browsers" xmlns:start="http://schemas.microsoft.com/Start/2014/StartLayout"><start:Tile Size="2x2" Column="2" Row="0" AppUserModelID="Microsoft.MicrosoftEdge_8wekyb3d8bbwe!MicrosoftEdge" /><start:DesktopApplicationTile Size="2x2" Column="4" Row="0" DesktopApplicationID="Chrome" /><start:DesktopApplicationTile Size="2x2" Column="0" Row="0" DesktopApplicationID="Microsoft.InternetExplorer.Default" /></start:Group><start:Group Name="Microsoft Office Communications" xmlns:start="http://schemas.microsoft.com/Start/2014/StartLayout"><start:DesktopApplicationTile Size="2x2" Column="0" Row="0" DesktopApplicationID="Microsoft.Office.OUTLOOK.EXE.16" /><start:DesktopApplicationTile Size="2x2" Column="2" Row="0" DesktopApplicationID="{7C5A40EF-A0FB-4BFC-874A-C0F2E0B9FA8E}\Microsoft Office\Office16\lync.exe" /></start:Group><start:Group Name="Microsoft Office Productivity" xmlns:start="http://schemas.microsoft.com/Start/2014/StartLayout"><start:DesktopApplicationTile Size="2x2" Column="2" Row="0" DesktopApplicationID="{7C5A40EF-A0FB-4BFC-874A-C0F2E0B9FA8E}\Microsoft Office\Office16\EXCEL.EXE" /><start:DesktopApplicationTile Size="2x2" Column="0" Row="0" DesktopApplicationID="{7C5A40EF-A0FB-4BFC-874A-C0F2E0B9FA8E}\Microsoft Office\Office16\WINWORD.EXE" /><start:DesktopApplicationTile Size="2x2" Column="4" Row="0" DesktopApplicationID="{7C5A40EF-A0FB-4BFC-874A-C0F2E0B9FA8E}\Microsoft Office\Office16\POWERPNT.EXE" /><start:DesktopApplicationTile Size="2x2" Column="4" Row="2" DesktopApplicationID="{7C5A40EF-A0FB-4BFC-874A-C0F2E0B9FA8E}\Microsoft Office\Office16\MSPUB.EXE" /><start:DesktopApplicationTile Size="2x2" Column="2" Row="2" DesktopApplicationID="{7C5A40EF-A0FB-4BFC-874A-C0F2E0B9FA8E}\Microsoft Office\Office16\ONENOTE.EXE" /><start:DesktopApplicationTile Size="2x2" Column="0" Row="2" DesktopApplicationID="{7C5A40EF-A0FB-4BFC-874A-C0F2E0B9FA8E}\Microsoft Office\Office16\MSACCESS.EXE" /></start:Group><start:Group Name="Microsoft Cloud" xmlns:start="http://schemas.microsoft.com/Start/2014/StartLayout"><start:DesktopApplicationTile Size="2x2" Column="0" Row="0" DesktopApplicationID="{7C5A40EF-A0FB-4BFC-874A-C0F2E0B9FA8E}\Microsoft Office\Office16\GROOVE.EXE" /></start:Group></defaultlayout:StartLayout></StartLayoutCollection></DefaultLayoutOverride></LayoutModificationTemplate>

Hello. Has anyone else noticed that clicking the UDI Wizard preview does not do anything ?

I have tried on several systems with the same result, nothing happens.

I monitored the activity with process monitor, but the processes it fires seems to exit normally.

eshe

Hi everybody

I just set up my first MDT environment and played around with bulk adding computers to the MDT database. There I recognized something strange. The computer ID didn't start at 1, it started at 2000 and I don't know why and how I can change this. I guess it's something in the database. I deleted all computers from the database and want to start with ID 1. Does anybody know how I can achieve this?

Thanks for the help.

I'm using MDT 2013 and WDS.  I want to be able to have custom settings based on the Task Sequence chosen.  For example, if Task Sequence ID 01 is chosen, the PC will join domain A.  If Task Sequence ID 02 is chosen, it will join domain B.  Currently my CustomSettings.ini file starts with:

[Settings]

Priority=TaskSequenceID, Default

[01]

<Stuff I want to happen during Task Sequence ID 01>

[Default]

<Default actions I want to occur for other tasks>

This is being ignored unless once I choose the task during deployment I open a command prompt, rerun ZTIGather.wsf, then click Back and choose the task again.  I've tried adding ZTIGather.wsf as the first action in the task sequence, but it's not working. What's the easiest/best way to customize actions based on the task?

I am working with MDT 2010, and I am getting the error, "Invalid Credentials:  The Network location cannot be reached." When I run the LiteTouch 64 bit, I don't think the network is working.  It's like there is not driver for the network card in the LiteTouch 64 bit to make the network connection.  When I hit F8 key, it brings a DOS box up for testing, and I found out these things.

 - I can ping the loop back address 127.0.0.1.

 - Cannot use the net use command to connect to the server share \\server01\DeploymentSahre$.

 - I can not ping by name or IP address the server that is holding my Deployment Share.

This is the first time I am working with this technology, and I was following a guide off the Technet library.  It almost like I am missing the driver for the network card.  I have Windows Deployment installed on server01, the server will answer, and I am able to put in my user name and password,  it accepts and starts loading. 

I did figure out how to inject the network drivers into Windows Deployment for the Motherboard I was using, do I have to do the same thing here again? MDT is using the Windows Deployment Images on the server01; MDT is setup on server01.   I would have thought that since the driver was already injected into the Image MDT would use that as well.  So, do I need to put a driver into the LiteTouch 64bit image and if I do how do I do that?

thanks very much for your help,

Rick Arnold

ArnoldConsult

Rick Arnold Arnoldconsult, MCP

I have read other posts where users are getting this same error after they have removed an application from MDT, yet the GUID is still referenced in the Applications.xml file....however I am getting the error after importing an application into MDT.

I have confirmed that the application matching the GUID is present in the Applications.xml file that is in the Control folder of my deployment share, but when I check the Applications.xml file that is in the Deploy\Control folder on the USB media it is not listed, yet the same driver (with a separate GUID) for another model that was imported at the same time is there.

I have verified that the WMI query statement for the TS group for the model is correct.  Can anyone shed some light on my this may be occurring?

Thank you

Hi all!

I'm trying to deploy Windows 10 Enterprise using MDT 2013 SP1. During the deployment I'm trying to have Bitlocker auto-configured and enabled. However I keep getting error: FAILURE ( 6767 ): -2144272340  0x8031002C: Enable BDE Protectors.

I've searched the interwebs but every post I see is about people who are using Configuration Manager. Since I'm not, the solutions provided there don't apply to me.

My bitlocker settings:

BDEInstallSuppress=NO
BDEDriveLetter=Q:
BDEDriveSize=2000
BDEInstall=TPMKey
BDERecoveryKey=AD
BDEKeyLocation=C:\windows\BDEKey
BDEBitLockerWaitForEncryption=TRUE

I've configured AD for Bitlocker backup, and after the deployment finishes I can manually enable bitlocker and it will save the key to AD. However I'd very much like this to be automatic since I'm trying to make it ZTI as much as possible.

I have followed the steps in this article: Configuring Bitlocker for MDT except for the part where you use a script to check if the TPM chip is already enabled. The reason I'm not doing this (yet) is because for now I only have to configure Surface 3 (not pro) tablets and I know that the chip is enabled. So from the task sequence screenshot in the article, I have only got the Enable Bitlocker step.

Thanks in advance for any suggestions!

Kind regards,

Elke

I am new to using the MDT.  I have installed and configured it on my deployment server per Microsoft's guidelines.  I am attempting to upgrade domain joined Windows 7 x64 Pro machines, but the process eventually hangs on the client and closes. Using the monitoring tool within the workbench, I can see that the process always fails at the "Upgrade Windows" step (8 of 23.)  I'm using Windows 10 Pro x64 media obtained from the Volume Licensing site, and I've setup my task sequence per the guidelines.  Here's a quick snapshot of the log from the point at which the process fails:

It looks like the process is calling for a reboot after the initial failure, but that never happens.

I'm able to browse out to the OS folder on the production share from the client machine, and initiate the upgrade manually without any issue.  I've seen similar posts with the same errors caused by language variations with the chosen media, but all of my media is the same version as the client OS.  Just for the sake of  troubleshooting, I added WindowsUpgradeAdditionalOptions=/compat IgnoreWarning to the CustomSettings.ini, but that doesn't work either.  I'm at a bit of a loss.  Any info or ideas would be most appreciated.

Hi,

I'm trying to connect to an MDT 2013 deployment share over the network via PXE, and about 50% of the time it doesn't happen. The client does get an IP address, but the connection process times out with an error indicating that "\\192.168.0.1\DeploymentShare$ cannot be contacted, possible invalid credentials." The credentials are good. If I press F8 and connect to the deployment share manually, the same credentials get me in. I specified the IP address in BootStrap.ini because maybe there is a DNS/WINS issue on the network. If there is, I cannot fix it as I'm not part of that team. The WinPE PXE client does get the correct DNS servers and NetBIOS over TCP/IP is enabled. What more should I need, especially if I'm connecting via IP instead of hostname. Am I doing something wrong?

Thanks

Jason

I created a task sequence to upgrade to Windows 10. It fails with the following info:

Setup failed to upgrade OS from  \\CV-WDT\DeploymentShare$\Operating Systems\Win 10 x64 Patched 2-10-16\setup.exe, rc = -2147024894
ZTI ERROR - Non-zero return code by LTIApply, rc = 1
Litetouch deployment failed, Return Code = -2147467259  0x80004005
Failed to run the action: Run Command Line.
This action is only valid for products that are currently installed. (Error: 00000645; Source: Windows)
The execution of the group (Preparation) has failed and the execution has been aborted. An action failed.
Operation aborted (Error: 80004004; Source: Windows)
Failed to run the last action: Run Command Line. Execution of task sequence failed.
This action is only valid for products that are currently installed. (Error: 00000645; Source: Windows)
Task Sequence Engine failed! Code: enExecutionFail
Task sequence execution failed with error code 80004005
SetNamedSecurityInfo() failed.
SetObjectOwner() failed. 0x80070005.
RegQueryValueExW is unsuccessful for Software\Microsoft\SMS\Task Sequence, SMSTSEndProgram
GetTsRegValue() is unsuccessful. 0x80070002.
Error Task Sequence Manager failed to execute task sequence. Code 0x80004005
Failed to run the action: Upgrade Windows.
Incorrect function. (Error: 00000001; Source: Windows)
The execution of the group (Upgrade the Operating System) has failed and the execution has been aborted. An action failed.
Operation aborted (Error: 80004004; Source: Windows)
Failed to run the last action: Upgrade Windows. 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
SetNamedSecurityInfo() failed.
SetObjectOwner() failed. 0x80070005.
RegQueryValueExW is unsuccessful for Software\Microsoft\SMS\Task Sequence, SMSTSEndProgram
GetTsRegValue() is unsuccessful. 0x80070002.
Error Task Sequence Manager failed to execute task sequence. Code 0x80004005
Failed to run the action: Upgrade Windows.
Incorrect function. (Error: 00000001; Source: Windows)
The execution of the group (Upgrade the Operating System) has failed and the execution has been aborted. An action failed.
Operation aborted (Error: 80004004; Source: Windows)
Failed to run the last action: Upgrade Windows. 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
SetNamedSecurityInfo() failed.
SetObjectOwner() failed. 0x80070005.
RegQueryValueExW is unsuccessful for Software\Microsoft\SMS\Task Sequence, SMSTSEndProgram
GetTsRegValue() is unsuccessful. 0x80070002.
Error Task Sequence Manager failed to execute task sequence. Code 0x80004005
Failed to run the action: Upgrade Windows.
Incorrect function. (Error: 00000001; Source: Windows)
The execution of the group (Upgrade the Operating System) has failed and the execution has been aborted. An action failed.
Operation aborted (Error: 80004004; Source: Windows)
Failed to run the last action: Upgrade Windows. 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
SetNamedSecurityInfo() failed.
SetObjectOwner() failed. 0x80070005.
RegQueryValueExW is unsuccessful for Software\Microsoft\SMS\Task Sequence, SMSTSEndProgram
GetTsRegValue() is unsuccessful. 0x80070002.
Error Task Sequence Manager failed to execute task sequence. Code 0x80004005
Failed to run the action: Upgrade Windows.
Incorrect function. (Error: 00000001; Source: Windows)
The execution of the group (Upgrade the Operating System) has failed and the execution has been aborted. An action failed.
Operation aborted (Error: 80004004; Source: Windows)
Failed to run the last action: Upgrade Windows. 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
SetNamedSecurityInfo() failed.
SetObjectOwner() failed. 0x80070005.
RegQueryValueExW is unsuccessful for Software\Microsoft\SMS\Task Sequence, SMSTSEndProgram
GetTsRegValue() is unsuccessful. 0x80070002.
Error Task Sequence Manager failed to execute task sequence. Code 0x80004005
Failed to run the action: Upgrade Windows.
Incorrect function. (Error: 00000001; Source: Windows)
The execution of the group (Upgrade the Operating System) has failed and the execution has been aborted. An action failed.
Operation aborted (Error: 80004004; Source: Windows)
Failed to run the last action: Upgrade Windows. 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
SetNamedSecurityInfo() failed.
SetObjectOwner() failed. 0x80070005.
RegQueryValueExW is unsuccessful for Software\Microsoft\SMS\Task Sequence, SMSTSEndProgram
GetTsRegValue() is unsuccessful. 0x80070002.
Error Task Sequence Manager failed to execute task sequence. Code 0x80004005
Failed to run the action: Upgrade Windows.
Incorrect function. (Error: 00000001; Source: Windows)
The execution of the group (Upgrade the Operating System) has failed and the execution has been aborted. An action failed.
Operation aborted (Error: 80004004; Source: Windows)
Failed to run the last action: Upgrade Windows. 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
SetNamedSecurityInfo() failed.
SetObjectOwner() failed. 0x80070005.
RegQueryValueExW is unsuccessful for Software\Microsoft\SMS\Task Sequence, SMSTSEndProgram
GetTsRegValue() is unsuccessful. 0x80070002.
Error Task Sequence Manager failed to execute task sequence. Code 0x80004005

This is a default Windows Upgrade task sequence using a WIM file that is confirmed working with a fresh deployment.

Dan Chandler-Klein

I just like to clarify something about updating the custom.ini and bootstrap.ini

I have read that any changes made to the deployment workbench etc.. you need to update the deployment share.  

I was having problems with skipping the BDD welcome and finally came across an article that says after editing the bootstrap you need to  completely regenerate the boot images, and then replace the old win files on wds with the new ones that have been generated.  

I tried this and it seem to have worked and the welcome screen was skipped, is this the process for everytime I updated the bootstrap.   

one last thing can can i update the custom.ini and the bootstrap.ini directly from the control folder ?  If i do update them will i still need to regenerate the images.

thanks I new to MDT and want to understand what happening when editing these files 

I would like to provide a computer name when deploying VMs because my current naming scheme (using the Serial number breaks unattended for VMs)

Updated C:\MININT\Unattend.xml with OSDComputerName=VM-VMware-42 2e cf f6 59 f8 c0 19-16 21 ed 35 6a e1 9a d4 (value was VM-VMware-42 2e cf f6 59 f8 c0 19-16 21 ed 35 6a e1 9a d4)ZTIConfigure 2/29/2016 10:50:29 AM0 (0x0000)

The serial is too long and contains characters not suitable for a computer name.

I have changed my CS.ini to ask for a computer name if a VM is detected but for some reason i never get the computer name pane.

Something is wrong in my settings section i guess:

[Settings]
Priority=DefaultGateway,ByLaptopType, ByDesktopType, ByVMType, ByServerType, HardwareInfo,Model,Default
Properties=Type,MakeAlias,ModelAlias,Mbam,MyCustomProperty

[DefaultGateway]
10.8.255.254=Paris
10.12.20.254=WTC
10.1.255.254=ITVLAN

[WTC]
DeployRoot=\\mdtserver\MDTProduction$
WSUSServer=http://NLWUSSV02:8530
SLSHARE=\\mdtserver\Logs$\%ComputerName%
UDShare=\\mdtserver\MigData$
BackupShare=\\mdtserver\MigData$
EventService=http://mdtserver:9800
SLShareDynamicLogging =\\mdtserver\Logs$\%ComputerName%

[Paris]
DeployRoot=\\mdtserver2\MDTProduction$
WSUSServer=http://mdtserver2:8530
SLSHARE=\\mdtserver2\Logs$\%ComputerName%
UDShare=\\mdtserver2\MigData$
BackupShare=\\mdtserver2\MigData$
EventService=http://mdtserver2:9800
SLShareDynamicLogging =\\mdtserver2\Logs$\%ComputerName%

[ITVLAN]
DeployRoot=\\mdtserver\MDTProduction$
WSUSServer=http://NLWUSSV02:8530
SLSHARE=\\mdtserver\Logs$\%ComputerName%
UDShare=\\mdtserver\MigData$
BackupShare=\\mdtserver\MigData$
EventService=http://mdtserver:9800
SLShareDynamicLogging =\\mdtserver\Logs$\%ComputerName%
BDEInstallSuppress=NO


[HardwareInfo]
UserExit=ModelAliasExit.vbs
MakeAlias=#SetMakeAlias()#
ModelAlias=#SetModelAlias()#


[Default]
_SMSTSOrgName=IT TEAM - Production

UDDIR=%ComputerName%
BackupDir=%ComputerName%

ScanStateArgs=/ue:*\* /ui:Corp\* /uel:30
USMTMigFiles001=MigApp.xml
USMTMigFiles002=MigUser.xml
USMTMigFiles003=MigDocs.xml
USMTMigFiles004=WNB.xml

HideShell=YES
ApplyGPOPack=NO

SkipUserData=NO
UserDataLocation=AUTO
SkipApplications=YES
SkipAppsOnUpgrade=NO
SkipPackageDisplay=NO
SkipAdminPassword=YES
SkipProductKey=YES
SkipComputerName=YES
SkipDomainMembership=YES
SkipLocaleSelection=YES
SkipTaskSequence=NO
SkipTimeZone=YES
SkipBitLocker=YES
SkipSummary=YES
SkipBDDWelcome=YES
SkipCapture=YES
SkipFinalSummary=YES

TimeZoneName=W. Europe Standard Time

JoinDomain=corp.acmegroup.local
DomainAdmin=JoinAccount
DomainAdminDomain=corp.acmegroup.local
DomainAdminPassword=ABC-123
MachineObjectOU=OU=ImagedComputers,DC=corp,DC=acmegroup,DC=local

BitsPerPel=32
VRefresh=60
XResolution=1
YResolution=1


[ByLaptopType]
SkipComputerName=YES
OSDComputerName=%Type%-%SerialNumber%
Subsection=Laptop-%IsLaptop%
MandatoryApplications001={4d6d80f2-e23a-46d4-b9b3-5f10d348adb3}


[ByDesktopType]
SkipComputerName=YES
OSDComputerName=%Type%-%SerialNumber%
Subsection=Desktop-%IsDesktop%


[ByVMType]
Subsection=VM-%IsVM%
SkipComputerName=NO

[ByServerType]
Subsection=Server-%IsServer%
SkipBDDWelcome=NO
SkipComputerName=NO

[Laptop-True]
Type=LT

[Desktop-True]
Type=WK

[VM-True]
Type=VM

[Server-True]
Type=Server