You are here:   Research
Register   |  Login
The quickest way to find articles is to use the below search option.

However, if you go to the end of this page, you also find the Blog archive (calendar format) that allows for browsing of older articles.

Search:

Going Production – Deploy Windows 8 using MDT 2012 Update 1

Aug 19

Written by:
8/19/2012 9:53 AM  RssIcon

Windows 8 RTM is now available and so is the deployment solution to deploy it. As of this writing (August 19, 2012) MDT 2012 Update 1 is the only deployment solution by Microsoft that supports deploying the final version of Windows 8. The other deployment solution Microsoft has, System Center 2012 Configuration Manager, will not support Windows 8 until the SP1 update is released later this year.

Note: Yes, I know: Technically you can use plain vanilla Windows Deployment Services (WDS) and ADK to deploy Windows 8, but that's not a deployment solution. WDS and ADK are only plumbing tools for deployment, not a deployment solution, and MDT 2012 Update 1 will use them in the background anyway. Please do not waste your time trying to build a deployment solution on WDS and ADK, Microsoft has already done it for you: It's named MDT 2012 Update 1!

The Scenario

In this guide you learn to setup MDT 2012 Update 1 to deploy Windows 8 to HP 8560w machines, including the needed drivers and one sample application (7-Zip 9.20)

Download Sample Files

Article sample files (Download)

System Requirements

The steps in this guide assumes you have the following

  • A member server named MDT01 running Windows Server 2008 R2 or Windows Server 2012 with the following software installed:
    • Windows Deployment Services
    • ADK
    • .NET Framework 3.5.1
    • MDT 2012 Update 1
  • Two domain user accounts (password set to P@ssw0rd)
    • BuildAccount
    • JoinAccount (with permissions to join machines in AD)
  • D:\Drivers folder with extracted Windows 8 drivers for 8560w (Use the Windows 7 drivers, HP has not yet released specific Windows 8 drivers)
    • Intel Management Engine Interface (MEI) Driver - SP54317
    • JMicron Media Card Reader Driver - SP52659
    • Validity Fingerprint Driver - SP54614
    • HP 3D DriveGuard - SP53795
  • D:\Setup folder containing the following software
    • Windows 8 Enterprise (content of the ISO)
    • 7-Zip 9.20
    • Article sample files

Note: In this guide the domain is corp.viamonstra.com (VIAMONSTRA).

 

The to be installed HP 8560w, and a few other machines :)

 

Using MDT 2012 Update 1

Configuring MDT 2012 Update 1 to deploy Windows 8 for the 8650w machines is done in nine easy steps:

  • Create a deployment share
  • Import the Windows 8 operating system
  • Import the drivers
  • Add the application
  • Create a task sequence
  • Configure the deployment share settings
  • Update the deployment share
  • Add the MDT 2012 Update 1 boot image to WDS
  • Deploy the Windows 8 image

 

Step 1 - Create a deployment share

These steps assume that you downloaded the article sample files (Download) and extracted the file to D:\Setup\Sample Files on MDT01.

  1. On MDT01, using the Deployment Workbench, right-click Deployment Shares and select New Deployment Share. Use the following settings for the New Deployment Share Wizard.
    1. Deployment share path: D:\MDTProduction
    2. Share name: MDTProduction
    3. Deployment share description: MDT Production
    4. Options:
  2. Using Explorer, copy the following scripts from D:\Setup\Sample Files to D:\MDTProduction\Scripts.
    1. ModelAliasExit.vbs
    2. ZTISetScreenResolution.wsf

Note: The ModelAliasExit.vbs script (written by Michael Murgolo and Ben Hunter) helps MDT trim strange model names into valid model names. For example change "HP EliteBook 8560w (LG661EA#AKG)" to "HP EliteBook 8560w". The ZTISetScreenResolution.wsf script (written by me) configures MDT to allow the graphics driver auto detect method to set the screen resolution.

Deployment Workbench after creating the deployment share.

 

Step 2 - Import the Windows 8 operating system

  1. Using the Deployment Workbench, expand the MDT Production node, and select the Operating Systems node.
  2. Right-click on the Operating Systems node, and select Import Operating System. Use the following settings for the Import Operating System Wizard.
    1. Full set of source files D:\Setup\Windows 8 Enterprise x64
    2. Destination directory name: Windows 8 Enterprise x64
  3. After adding the operating system, change the Operating System name to Windows 8 Enterprise x64.

The imported, and renamed, Windows 8 operating system.

 

Step 3 - Import the drivers

  1. Using the Deployment Workbench, in the MDT Production node, select the Out-Of-Box Drivers node, and create a folder named Windows 8 x64. Then, in the Windows 8 x64 folder, create a subfolder named HP EliteBook 8560w.
  2. Right-click the HP EliteBook 8560w folder and select Import Drivers, use the following settings for the Import Driver wizard:
    1. Driver source directory: D:\Drivers\Windows 8 x64\HP EliteBook 8560w

Imported drivers for the HP 8560w model.

 

Step 4 - Add the application

  1. Using the Deployment Workbench, in the MDT Production node, select the Applications node.
  2. Right-click the Applications node, and select New Application, Use the following settings for the New Application Wizard.
    1. Application with source files
    2. Application name: 7-Zip
    3. Version: 9.20
    4. Source Directory: D:\Setup\7-Zip 9.20
    5. Specify the name of the directory that should be created: 7-Zip 9.20
    6. Command Line: msiexec /i 7z920-x64.msi /q INSTALLDIR="C:\Program Files\7-Zip"
    7. Working directory: .\Applications\7-Zip 9.20

 

Deployment Workbench with the 7-Zip 9.20 application added.

Step 5 - Create a task sequence

  1. Using the Deployment Workbench, in the MDT Production deployment share, select the Task Sequences node.
  2. Right-click on the Task Sequences node, and select New Task Sequence. Use the following settings for the New Task Sequence Wizard.
    1. Task sequence ID: W8-X64-001
    2. Task sequence name: Windows 8 Enterprise x64
    3. Task sequence comments: Production Deployment
    4. Template: Standard Client Task Sequence
    5. Select OS: Windows 8 Enterprise x64
    6. Do not specify a product key at this time
    7. FullName: ViaMonstra
    8. Organization: ViaMonstra
    9. Internet Explorer home page: about:blank
    10. Do not specify an Administrator password at this time
  3. Double-click the new Windows 8 Enterprise x64 task sequence.
  4. In the Task Sequence tab, in the Preinstall group, after the Configure action, add a Run Command Line action with the following settings:
    1. Name: Enable Screen Resolution Auto Detect
    2. Command line: cscript.exe "%SCRIPTROOT%\ZTISetScreenResolution.wsf"
  5. In the Task Sequence tab, in the State Restore group, after the Tattoo action, add an Install Roles and Features action.
  6. In the Select the operating system for which roles are to be installed drop down list, select Windows 8
  7. Click OK.

Note: If you don't add the Install Roles and Features action, the deployment wizard will not prompt you for roles and features.

 

The edited task sequence, now including the "Enable Screen Resolution Auto Detect" and "Install Roles and Features" actions.

 

Step 6 - Configure the deployment share settings

  1. Using Explorer, copy the following files in D:\Setup\Sample Files to D:\MDTProduction\Control. Replace the existing files.
    1. bootstrap.ini
    2. CustomSettings.ini
  2. The CustomSettings.ini file has the following content (controlling the MDT deployment wizard behavior and other deployment settings):

    [Settings]
    Priority=SetModelAlias, Default
    Properties=ModelAlias

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

    [Default]
    _SMSTSORGNAME=%OSDComputerName% to be installed...
    OSInstall=Y
    UserDataLocation=AUTO
    TimeZoneName=Pacific Standard Time
    AdminPassword=P@ssw0rd
    JoinDomain=corp.viamonstra.com
    DomainAdmin=VIAMONSTRA\JoinAccount
    DomainAdminPassword=P@ssw0rd
    MachineObjectOU=ou=Workstations,ou=viamonstra,dc=corp,dc=viamonstra,dc=com
    HideShell=YES
    DriverSelectionProfile=Nothing
    DriverInjectionMode=ALL
    DriverGroup001=Windows 8 x64\%ModelAlias%

    SkipAppsOnUpgrade=NO
    SkipAdminPassword=YES
    SkipProductKey=YES
    SkipComputerName=NO
    SkipDomainMembership=YES
    SkipUserData=YES
    SkipLocaleSelection=YES
    SkipTaskSequence=NO
    SkipTimeZone=YES
    SkipApplications=NO
    SkipBitLocker=YES
    SkipSummary=YES
    SkipCapture=YES
    SkipFinalSummary=NO
    SkipRoles=NO

  3. Right-click the MDT Production Deployment Share and select Properties.
  4. In the Windows PE tab, in the Platform dropdown list, make sure x86 is selected.
  5. In the General sub tab, configure the following settings:
    1. In the Lite Touch Boot Image Settings area.
      1. image description: MDT Production x86
      2. Clear the Generate a Lite Touch bootable ISO image check box
    2. In the Windows PE Customizations area, set the Scratch space size to 128.
  6. In the Windows PE tab, in the Platform dropdown list, select x64.
  7. In the General sub tab, configure the following settings:
    1. In the Lite Touch Boot Image Settings area.
      1. image description: MDT Production x64
      2. Clear the Generate a Lite Touch bootable ISO image check box
    2. In the Windows PE Customizations area, set the Scratch space size to 128.
  8. In the Monitoring tab, select the Enable monitoring for this deployment share check box.
  9. Click OK.

Note : It will take a while for the Deployment Workbench to create the monitoring database and web service. The console even appears to hang, but no worries, just give a little time :)

Editing the deployment share properties.

 

Step 7 - Update the deployment share

  1. Right-click the MDT Production Deployment Share and select Update Deployment Share. Use the default Options.

Note: The update process will take 5 – 10 minutes.

 

Step 8 - Add the MDT 2012 Update 1 boot image to WDS

  1. In the WDS Console, expand MDT01.corp.viamonstra.com, right-click Boot Images and select Add Boot Image
  2. Browse to the D:\MDTProduction\Boot\LiteTouchPE_x64.wim file and add the image with the default settings.

 

Step 9 - Deploy the Windows 8 Image

  1. Start your HP 8560w machine, press F12 for PXE boot, and complete the Deployment Wizard using the below settings:
    1. Password: P@ssw0rd
    2. Select a task sequence to execute on this computer: Windows 8 Enterprise x64
    3. Computer Name: PC0001
    4. Roles and Features: .NET Framework 3.5 (includes .NET 2.0 and 3.0)
    5. Select one or more applications to install:
      1. 7-Zip 9.20
      2. HP Hotkey Support 4.5.9.1
  2. On MDT01, using the Deployment Workbench, use the Monitoring node to view the deployment process.
  3. Done, have some well-deserved coffee, and enjoy the show!

 

Selecting roles and features to install in MDT 2012 Update.


 

Windows 8 UI guidance during deployment.


 

MDT 2012 Update 1 installing applications in the background.


 

Windows 8 Deployed :)

 

/ Johan

Trackback Print
Tags:
Categories:
Location: Blogs Parent Separator Deployment Research - Johan Arwidmark

34 comment(s) so far...


Gravatar

Re: Going Production – Deploy Windows 8 using MDT 2012 Update 1

Johan, I'm trying to think of a way to demo MDT deployment setting up WDS/MDT + 1 DC in a VM environment on a laptop but with the ability to deploy to real clients. Would this be possible using a single onboard nic + a simple switch?

By Max3 on   8/19/2012 1:09 PM
Gravatar

Re: Going Production – Deploy Windows 8 using MDT 2012 Update 1

Absolutely, that's how i deploy classroom myself when I teach deployment classes... I have a laptop with a SSD drive, gigabit nic, and two vm's running on it (one DC and one Deployment Server). I can easily deploy 30 machines at the same time (using multicast).

/ Johan

By Arwidmark on   8/19/2012 3:01 PM
Gravatar

AIK vs ADK

Since the AIK can deploy Win8, should we still upgrade to the ADK? We're using the AIK for upgrading from XP to 7, will the ADK cause problems or require recoding that process? Or, is it best to maintain 2 seperate environments?

By tomcollins on   8/21/2012 7:31 AM
Gravatar

Re: Going Production – Deploy Windows 8 using MDT 2012 Update 1

Both WAIK and ADK can be used to deploy all supported operating systems. That being said, WinPE 4.0 (part of ADK) is faster, and has more deployment options (like offline bitlocker). If you want to use ADK you need to update to MDT 2012 Update 1.

For our updates to MDT 2012 Update 1 so far, I have used separate servers.

/ Johan

By Arwidmark on   8/21/2012 1:12 PM
Gravatar

Re: Going Production – Deploy Windows 8 using MDT 2012 Update 1

How do you remove the first login prompt windows 8 requests when it firsts boots. right now if i put in a temp account it will then auto login with the administrator account and continue the OSD.

By Technomyke on   8/24/2012 7:42 AM
Gravatar

Re: Going Production – Deploy Windows 8 using MDT 2012 Update 1

We primarily still use Windows XP. I noticed that the ADK for Windows 8 does not list Windows XP as a supported OS; Any potential issues that you can think of that we could encounter if we use the ADK for Windows 8 to continue to deploy Windows XP, at least untill we upgrade off XP?

By fraigoza on   8/24/2012 10:32 AM
Gravatar

Re: Going Production – Deploy Windows 8 using MDT 2012 Update 1

Hi Johan

I'm very interested to build my own SCCM Environment where I can setup several machine etc. Can you tell what OS you are using on your laptop?
How many RAM are you using and which Model. I would like to build my own lab like how you do in your training class. Saw your picture and thought to do it like you.

By mathew on   8/25/2012 12:41 PM
Gravatar

Re: Going Production – Deploy Windows 8 using MDT 2012 Update 1

Hi Mathew,

These days any laptop with a Core i7, 4 memory slots and a local SSD (SATA-III) will outperform most servers running with 10k or 15k disks...

I have a mix of laptops available for demos and lab. The one I use the most is a HP 8540w with 16 GB RAM and 1.2 TB SSD (I removed the Blu-Ray and added a second 600 GB SSD), and secondly a HP 8560w with 32 GB RAM and a single 480 GB SSD. I even have a simple Lenovo ThinkPad T420 Core i5 with a 480 GB SSD and 16 GB RAM and it performs pretty OK.

I'm currently running Windows Server 2012 and Hyper-V on those machines, but I also have another HP 8540w with 16 GB RAM where I use VMware workstation 8 (soon to be upgraded to 9).

/ Johan

By Arwidmark on   8/26/2012 4:53 AM
Gravatar

Re: Going Production – Deploy Windows 8 using MDT 2012 Update 1

Hi Johan

I'm looking at Windows 8 imaging so have set up a test lab using the Windows 8 Hyper V Client and MDT 2012 Update 1. Its just a non-domain joined server holding the deployment share, but for the life of me i cannot get the imaging VM to contact the deployment share. I get the" Connection OK: Possible cause: invalid credentials" error. However if i hit F8 to get the command prompt and net use to the deployment share with the exact details from the bootstrap.ini file, i can connect fine. I also tried hitting F8 before the wizard starts, and mapping the drive first, then manually running litetouch.vbs, but still get the error.

I cant work out what im missing. I may have to set up a domain in my lab and follow your guide!

Thanks
Tony

By tbartley on   9/2/2012 2:50 AM
Gravatar

Re: Going Production – Deploy Windows 8 using MDT 2012 Update 1

ok, after spending 2 days on this and posting the above, i figured it out. I was using 2 vm's with APIPA IP addressing. Although i could manually connect between the two vm's, and the connection said OK, it obviously wasnt. Once i brought up a DHCP server it started working.

By tbartley on   9/2/2012 3:56 AM
Gravatar

Re: Going Production – Deploy Windows 8 using MDT 2012 Update 1

Hi Johan - would really be interested in seeing a post about "Windows To Go", especially when it comes to customizations (applying custom images, automating domain joins, leveraging MDT, etc.)

By chemdawg on   9/5/2012 10:25 AM
Gravatar

Re: Going Production – Deploy Windows 8 using MDT 2012 Update 1

Will be covered in our upcoming Deploying Windows 8 and Office 2013 book :) ETA: 6 weeks

/ Johan

By Arwidmark on   9/5/2012 3:43 PM
Gravatar

Re: Going Production – Deploy Windows 8 using MDT 2012 Update 1

Another thing to ask about %OSDComputerName% variable that is used in _SMSTSORGNAME= ..how does it get set?
I dont see that its set anywhere? Does that ModelAlias.vbs do that trick. Is it possible to get an prestaged computeraccount name to show together with _SMSTSORGNAME=

By ervi on   9/9/2012 9:47 PM
Gravatar

Re: Going Production – Deploy Windows 8 using MDT 2012 Update 1

Uh..oh just realized that computername is set manually during installation :P
Again my fingers were faster than anything else...

By ervi on   9/10/2012 9:11 AM
Gravatar

Re: Going Production – Deploy Windows 8 using MDT 2012 Update 1

Hi Johan,

I want to thank you very much for having such a wonderful guide. Like your two books, it is very concise and easy to follow. I was able to very quickly create a task sequence to deploy windows 8 64 bit. However, when I did the same for Windows 8 32 bit, the deployment keeps failing. Always in the same spot. It gets to 38% done, when installing the wim. I am hoping you can help me figure out what’s going on. I would greatly appreciate it. The error that I get is as follows:

Failure (5624): 2: Run ImageX: /apply
“server\deploymentshare$\Operating System\Windows 8 32 bit\sources\install.wim” 1 c:
Lifetouch deployment failed, Return code = -2147467259 0x800004005
Failed to run the action: install operating system
Unknown error (error: 000015f8; source: unknown)
The execution of the group (install) has failed and the execution has been aborted. An action failed.
Operation aborted (error: 800004004; source: windows)
Failed to run the last action: install operating system. Execution of task sequence failed.
Unknown error (error: 000015f8; source : unknown)
Task sequence engine failed! Code: enExecutionFail
Task sequence execution failed with error code 800004005
Error Task sequence manager failed to execute take sequence. Code 0X800004005

This happens every time. I am truly at a lost. Any help would be greatly appricated.

By fraigoza on   9/11/2012 4:31 PM
Gravatar

Re: Going Production – Deploy Windows 8 using MDT 2012 Update 1

Most likely it's a corrupt wim file...

If you boot into WinPE and run ImageX manually, can you apply the image?

/ Johan

By Arwidmark on   9/12/2012 11:58 AM
Gravatar

Re: Going Production – Deploy Windows 8 using MDT 2012 Update 1

Johan,

You are awesome!!! After re-downloading the Windows 8 source again and re-importing it all worked fine. The only weird thing was that I had to change the MDT OS directory name to something different. MDT appears to have cached the old directory structure. Thank you very much your assistance.

Francisco

By fraigoza on   9/17/2012 12:25 PM
Gravatar

Re: Going Production – Deploy Windows 8 using MDT 2012 Update 1

Hi Johan,

We are planning on upgrading our existing MDT infrastructure to MDT 2012 Update 1 and I was wandering if you could provide me with some tips/guidance on the upgrade process?.

Our current deployment servers are running WindowsServer 2008 R2, WDS, WAIK and MDT 2010 Update 1 including the MDT Database. I was told at one of the sessions at Techhed that you cannot run the WAIK and ADK on the same machine. Do I need to Uninstall the WAIK and MDT 2010, and then Install the ADK and MDT2012 Update 1? Will my existing deployment shares, TS's, rules boot images etc work with MDT2012 update 1 and the new ADK.

Thanks in advance,

Matt

By m.carterrix@Wlv.ac.uk on   9/20/2012 2:19 AM
Gravatar

Re: Going Production – Deploy Windows 8 using MDT 2012 Update 1

Hi Johan

Thanks for all your work! It has been a major help.

When using the "standard task sequence", to create a reference image for Win8 - the image boots up in this blue screen with options to troubleshoot after it executes sysprep.

Is there another way to run sysprep for Win8 prior to capturing the reference image.

Thanks,

Stan

By stanc on   10/16/2012 1:56 PM
Gravatar

Re: Going Production – Deploy Windows 8 using MDT 2012 Update 1

What is the latest news on your upcoming "Deploying Windows 8 and Office 2013" book? Anxiously awaiting...

By chemdawg on   10/26/2012 11:15 AM
Gravatar

Re: Going Production – Deploy Windows 8 using MDT 2012 Update 1

chemdawg: The books is on its way, but delayed about a month...

Stan: If you get a BSOD during a ref image build you are most likely having a hardware issue on your hyper-v or vmware host. If you are building ref images on physical hardware you are doing it wrong :) Use a virtual machine

/ Johan

By Arwidmark on   10/30/2012 1:27 PM
Gravatar

Re: Going Production – Deploy Windows 8 using MDT 2012 Update 1

Hi, I tried to Deploy Windows 8 with MDT2012 Update 1, but besides the clean install (imported iso), I cannot deploy windows 8 in the same way that i deploy windows 7 (both x86 and x64) (install clean image with mdt2012 -> install apps -> sysprep and capture task sequence -> wim captured and imported as custom wim file for deployment)
Deployment environment:
Windows Server 2008 R2 (SP1)
Windows Automated installation kit (WAIK) for Windows 7 + WAIK supplement
WinPE created by MDT2012 is version 3.1
The Windows 8 custom wim task sequence can run sysprep and cannot reboot to the WinPE for creation of wim file like what i do for windows 7
What I need to do to keep windows pe 3.1 and windows 7 and 8 in the same deployment share?

By derek2012 on   11/12/2012 11:00 PM
Gravatar

Re: Going Production – Deploy Windows 8 using MDT 2012 Update 1

Hi, I tried to Deploy Windows 8 with MDT2012 Update 1, but besides the clean install (imported iso), I cannot deploy windows 8 in the same way that i deploy windows 7 (both x86 and x64) (install clean image with mdt2012 -> install apps -> sysprep and capture task sequence -> wim captured and imported as custom wim file for deployment)
Deployment environment:
Windows Server 2008 R2 (SP1)
Windows Automated installation kit (WAIK) for Windows 7 + WAIK supplement
WinPE created by MDT2012 is version 3.1
The Windows 8 custom wim task sequence can run sysprep and cannot reboot to the WinPE for creation of wim file like what i do for windows 7
What I need to do to keep windows pe 3.1 and windows 7 and 8 in the same deployment share?

By derek2012 on   11/12/2012 11:05 PM
Gravatar

Re: Going Production – Deploy Windows 8 using MDT 2012 Update 1

use the standard client task sequence, and configure the rules for build and capture (DoCapture=YES). Then add a Suspend action (the LTISuspend.wsf script) to allow for your app installs.

/ Johan

By Arwidmark on   11/18/2012 10:10 AM
Gravatar

Re: Going Production – Deploy Windows 8 using MDT 2012 Update 1

I'm curious, is there a way to use the install "Roles and Features" screen when deploying a SCCM2012 MDT OSD Task Sequence? We want to be able to select specific roles during the server build. I have not been able to figure anything out.
Thanks.

By krozgrov on   11/27/2012 8:43 AM
Gravatar

Re: Going Production – Deploy Windows 8 using MDT 2012 Update 1

I'm curious, is there a way to use the install "Roles and Features" screen when deploying a SCCM2012 MDT OSD Task Sequence? We want to be able to select specific roles during the server build. I have not been able to figure anything out.
Thanks.

By krozgrov on   11/27/2012 8:43 AM
Gravatar

Re: Going Production – Deploy Windows 8 using MDT 2012 Update 1

I'm curious, is there a way to use the install "Roles and Features" screen when deploying a SCCM2012 MDT OSD Task Sequence? We want to be able to select specific roles during the server build. I have not been able to figure anything out.
Thanks.

By krozgrov on   11/27/2012 8:52 AM
Gravatar

Re: Going Production – Deploy Windows 8 using MDT 2012 Update 1

You can create a custom pane in UDI, or "steal" the Lite Touch wizard pane, and use together with ConfigMgr (requires some customization)

/ Johan

By Arwidmark on   11/28/2012 12:39 AM
Gravatar

Re: Going Production – Deploy Windows 8 using MDT 2012 Update 1

How would I steal LTI pane to use SCCM? I have tried to run the DeployRoles VBS from a "Run Command Line" step and that's not working. I have tried to buld in UDI not have much luck making it look and behave correctly...

By krozgrov on   11/29/2012 12:41 PM
Gravatar

Re: Going Production – Deploy Windows 8 using MDT 2012 Update 1

Hi!

I've had success using variables/functions between #:s in CustomSettings.ini that I've found in examples around the net, for example;
BackupFile=%TaskSequenceID%-#year(date) & "-" & month(date) & "-" & day(date) & "_" & hour(date) & minute(date)#

It works and it's great, but I am looking for more information. I'm coming up short looking for a reference for this. What other variables/functions can be called between ##?
What language/script engine is actually used there?

By korp on   2/13/2013 6:48 AM
Gravatar

Re: Going Production – Deploy Windows 8 using MDT 2012 Update 1

The language is VBScript so anything you can do in vbscript can be used. For more complex scripting you can store the snippets in an external script and call them as userexit's.

As for additional documentation, check out Maik Kosters documentation over ZTIUtility functions: myitforum.com/cs2/blogs/maikkoster/archive/2012/06/24/extending-the-mdt-documentation-some-goodies-from-ztiutility-vbs-string-and-file-handling.aspx

/ Johan

By Arwidmark on   2/13/2013 7:44 AM
Gravatar

Re: Going Production – Deploy Windows 8 using MDT 2012 Update 1

Johan,

I am having a couple of slight issues using MDT 2012 update 1 to deploy Windows 7 and 8. This was working fine for an old deploymentshare that was created with MDT 2010 and then upgraded to 2012 update 1, but the new deployment share I created is not functioning as expected.

First, I have added applications to be installed for specific task sequences in the customsettings.ini file. However, none of the applications install for any of the task sequences and I don't see any failures in the logs.

Second, I am unable to join a domain using the Customsettings.ini file as well. No errors in the logs, it just doesn't do it.

I am including my customsettings.ini file below for your review.

Thanks,

Steve Gear

==============================================================================


Priority=TaskSequenceID, Default

[Default]
OSInstall=Y
WipeDisk=TRUE
SkipAdminPassword=YES
SkipProductKey=YES
SkipBDDWelcome=YES
KeyboardLocale=en-us
SkipDeploymentType=YES
SkipCapture=YES
SkipDomainMembership=YES
SkipUserData=YES
SkipApplications=YES
SkipComputerName=YES
ComputerName=LBI%SerialNumber%
SkipLocaleSelection=Yes
UILanguage=en-us
UserLocale=en-us
KeyboardLocale=en-us
SkipTimeZone=YES
TimeZone=020
TimeZoneName=Central Standard Time
SkipBitLocker=Yes
SkipSummary=Yes
SkipFinalSummary=Yes
WSUSServer=http://SRV1005:8530
FinishAction=Restart

[WIN7_64]
Applications001={cfbc6bfa-d3dc-4135-b939-4031cc371fe8}
Applications002={f703b21e-3137-49b0-af9b-c77a3adfea1c}
Applications003={0dfdba3e-4676-4c36-9b8a-e79c0c3856dc}
Applications004={1e95c3f6-0977-4d45-9ae7-097ea888b926}

[WIN8_64]
Applications001={cfbc6bfa-d3dc-4135-b939-4031cc371fe8}

By trmfp on   5/3/2013 7:24 AM
Gravatar

Re: Going Production – Deploy Windows 8 using MDT 2012 Update 1

Johan,

I am having a couple of slight issues using MDT 2012 update 1 to deploy Windows 7 and 8. This was working fine for an old deploymentshare that was created with MDT 2010 and then upgraded to 2012 update 1, but the new deployment share I created is not functioning as expected.

First, I have added applications to be installed for specific task sequences in the customsettings.ini file. However, none of the applications install for any of the task sequences and I don't see any failures in the logs.

Second, I am unable to join a domain using the Customsettings.ini file as well. No errors in the logs, it just doesn't do it.

I am including my customsettings.ini file below for your review.

Thanks,

Steve Gear

==============================================================================


Priority=TaskSequenceID, Default

[Default]
OSInstall=Y
WipeDisk=TRUE
SkipAdminPassword=YES
SkipProductKey=YES
SkipBDDWelcome=YES
KeyboardLocale=en-us
SkipDeploymentType=YES
SkipCapture=YES
SkipDomainMembership=YES
SkipUserData=YES
SkipApplications=YES
SkipComputerName=YES
ComputerName=LBI%SerialNumber%
SkipLocaleSelection=Yes
UILanguage=en-us
UserLocale=en-us
KeyboardLocale=en-us
SkipTimeZone=YES
TimeZone=020
TimeZoneName=Central Standard Time
SkipBitLocker=Yes
SkipSummary=Yes
SkipFinalSummary=Yes
WSUSServer=http://SRV1005:8530
FinishAction=Restart

[WIN7_64]
Applications001={cfbc6bfa-d3dc-4135-b939-4031cc371fe8}
Applications002={f703b21e-3137-49b0-af9b-c77a3adfea1c}
Applications003={0dfdba3e-4676-4c36-9b8a-e79c0c3856dc}
Applications004={1e95c3f6-0977-4d45-9ae7-097ea888b926}

[WIN8_64]
Applications001={cfbc6bfa-d3dc-4135-b939-4031cc371fe8}

By trmfp on   5/3/2013 7:45 AM
Gravatar

Re: Going Production – Deploy Windows 8 using MDT 2012 Update 1

Johan,

I am tying to get used to MDT 2012 Update, I am just experimenting at the moment in a home lab and I have it installed on Windows 8 Enterprise Eval x64.
I have also installed the ADK.

The problem that I have at the moment is that I want to install offline updates which I have downloaded manually.
Create a folder in packages and install the updates.
I am using the default selection profile "All Packages" which selects the folder with the offline updates.
I create a standard task sequence
I the add in "Install updates Offline"
Position it in "Post Install" between "Add windows recovery" and "Next Phase"
I update the deployment share
I then select to create a new media and update it.

When I install updates this way it fails most of the time,

example of errors I get:

Injected package Package_for_KB2803676 neutral amd64 6.2.1.0
******
Processing 1 of 1 - Adding package Package_for_KB2804584~31bf3856ad364e35~amd64~~6.2.1.1
Error: 0x800f081e

The specified package is not applicable to this image.
Injected package Package_for_KB2804584 neutral amd64 6.2.1.1
******
Processing 1 of 1 - Adding package Package_for_KB2805222~31bf3856ad364e35~amd64~~6.2.1.2
Error: 0x800f081e

The specified package is not applicable to this image.
Injected package Package_for_KB2805222 neutral amd64 6.2.1.2
******
Processing 1 of 1 - Adding package Package_for_KB2805227~31bf3856ad364e35~amd64~~6.2.1.1
Error: 0x800f081e

The specified package is not applicable to this image.
Injected package Package_for_KB2805227 neutral amd64 6.2.1.1
Injected package Package_for_KB2805966 neutral amd64 6.2.3.1
Injected package Package_for_KB2811660 neutral amd64 6.2.1.2
Injected package Package_for_KB2812822 neutral amd64 6.2.1.1
Injected package Package_for_KB2812829 neutral amd64 6.2.1.0
Injected package Package_for_KB2815769 neutral amd64 6.2.1.0
******
Processing 1 of 1 - Adding package Package_for_KB2820197~31bf3856ad364e35~amd64~~6.2.1.1
Error: 0x800f081e

The specified package is not applicable to this image.
Injected package Package_for_KB2820197 neutral amd64 6.2.1.1
Injected package Package_for_KB2820330 neutral amd64 6.2.1.1
Injected package Package_for_KB2822241 neutral amd64 6.2.1.3
******
Processing 1 of 1 - Adding package Package_for_KB2823516~31bf3856ad364e35~amd64~~6.2.1.0
Error: 0x800f081e

The specified package is not applicable to this image.
Injected package Package_for_KB2823516 neutral amd64 6.2.1.0
******
Processing 1 of 1 - Adding package Package_for_KB2829254~31bf3856ad364e35~amd64~~6.2.1.0
Error: 0x800f081e

The specified package is not applicable to this image.
Injected package Package_for_KB2829254 neutral amd64 6.2.1.0
Injected package Package_for_KB2829361 neutral amd64 6.2.1.1
Injected package Package_for_KB2829530 neutral amd64 6.2.1.1
Injected package Package_for_KB2830290 neutral amd64 6.2.1.1
******
Processing 1 of 1 - Adding package Package_for_KB2837385~31bf3856ad364e35~amd64~~6.2.1.0
Error: 0x800f081e

The specified package is not applicable to this image.
Injected package Package_for_KB2837385 neutral amd64 6.2.1.0
******

******************
******************
Failure (5627) :8 Run DISM.exe

******************
******************







By derekod on   5/22/2013 10:36 AM

Blog Archive

Minimize
Home   |   Research   |   Videos   |   Links