Going Production – Deploy Windows 8 using MDT 2012 Update 1

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=VIAMONSTRAJoinAccount
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
  1. Right-click the MDT Production Deployment Share and select Properties.
  2. In the Windows PE tab, in the Platform dropdown list, make sure x86 is selected.
  3. 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.
  4. In the Windows PE tab, in the Platform dropdown list, select x64.
  5. 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.
  6. In the Monitoring tab, select the Enable monitoring for this deployment share check box.
  7. 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

About the author

Johan Arwidmark

0 0 votes
Article Rating
Subscribe
Notify of
guest
49 Comments
Newest
Oldest Most Voted
Inline Feedbacks
View all comments
Admin
Admin
8 years ago

You can use the Final Configuration script on my blog to run commands after the task sequence is completed. For example removing any mapped network drives.

/ Johan

v_2ask
v_2ask
8 years ago

Hello Johan,

I am experiencing a weird issue, after deploying Windows 8.1 using MDT 2012, I get this error "Could not reconnect all network drives" when we login to the desktop after imaging. Is this an issue or a Bug, and how can it be fixed as end users will raise it as a concern.

many thanks in advance

/Ashish

asim_badar
asim_badar
9 years ago

Can you please help my out!!!!!!i have configured my MDT server name MDT-Server , this server has 2 drives C and D drive, c drive has deployment share folder which is also shared with every one having full rights, and D drive has data like ISO files and operating system setup files and other application folders, after installing i am facing some issues, while i boot my client to install windows from MDT server, there is no task list which has already been configured and task sequence has been created, nothing is shown there, after that when windows loading screen… Read more »

Admin
Admin
9 years ago

Check the setupact.log file, it will tell you why it fail… Note that MDT 2012 Update 1 does not support Windows 8.1. You need to update to MDT 2013.

/ Johan

jhiltabidel
jhiltabidel
9 years ago

Upon deployment, after the unattend.xml is applied and the system reboots, I get:

Getting Devices Ready…100%
Getting Ready…

"Windows could not parse or process unattend answer file [C:windowsPantherunattend.xml] for pass [specialize]. A component or setting specified in the answer file does not exist"

I used to get this with Windows 7 if IE10 was in the base OS. With it removed, deployment was fine and we could install IE10 post OS deployment. Anyone else getting this with Windows 8.1?

Admin
Admin
9 years ago

If you are using MDT 2012 Update 1 Lite Touch on the same server as SCCM 2012 SP1 you need to update the deployment share after installing the new ADK (select to regenerate the boot images).

Also make sure that WAIK was uninstalled.

/ Johan

mitchelw
mitchelw
9 years ago

Johan and Forum Members
i have been beating my head against the desk trying to figure out why i cant build my reference image after upgrading to SCCM 2012sp1. i assume it may be related to the ADK8.0. i was using mdt2012u1 before and can still use the boot images that were previously created but need to try to build a wim for windows 8. i was using vmworkstation 4 and used to pxe fine, i tried vmworkstation 10 still no go. Any suggestions?

mitchelw
mitchelw
9 years ago

Johan and Forum Members
i have been beating my head against the desk trying to figure out why i cant build my reference image after upgrading to SCCM 2012sp1. i assume it may be related to the ADK8.0. i was using mdt2012u1 before and can still use the boot images that were previously created but need to try to build a wim for windows 8. i was using vmworkstation 4 and used to pxe fine, i tried vmworkstation 10 still no go. Any suggestions?

Admin
Admin
10 years ago

UEFI is most likely enabled on the machine, change to legacy mode and you should be good.

/ Johan

galicea
galicea
10 years ago

Hello Johan / Forum Posts Members, I am seeking to deploy Windows 8 using our existing WDS server. To date, we have not made use of MDT or SCCM 2007 though both exist in the environment. We have used WDS to boot into a custom boot image which launches a custom HTA which uses a mapped drive to a network share which houses our install.wim files. Once the drive is mapped ImageX is used to drop the image on a target workstation. This is a crude and rudimentary method but It is what I have inherited and am hoping to… Read more »

galicea
galicea
10 years ago

Johan – Thank you for the insight. I have purchased the two SSDs and am working through the lab setup. Thanks again!

Admin
Admin
10 years ago

Hi Gabe.

Replacing the 500 GB SATA III drive with a 480 GB SSD is enough to have a decent lab environment. 128 or 240 GB is just too small…. (sorry)

/ Johan

galicea
galicea
10 years ago

Hello Johan, First – Thank you for all of your efforts! It is awesome to read your material as well as the material produced by your colleagues. My question may have an answer I do not want to hear but here goes… 1) What is the minimum hardware requirements I can use to create a very very simplistic MDT / Windows 8 deployment scenario? My Configuration:I currently have an HP 8470p which is has 16 GB of RAM and a 500 GB SATA III drive as well as an additional 128GB SSD inserted via HDD Caddy in place of the… Read more »

Admin
Admin
10 years ago

Its sounds like you have downloaded and added the wrong version of the updates.

You are much better of by using a local WSUS server, and have the task sequence use it for updates. Downloading updates manually is just a royal pain.

/ Johan

derekod
derekod
10 years ago

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 sequenceI the add in "Install updates Offline"Position it in "Post Install" between "Add… Read more »

trmfp
trmfp
10 years ago

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… Read more »

trmfp
trmfp
10 years ago

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… Read more »

Admin
Admin
10 years ago

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

korp
korp
10 years ago

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?

krozgrov
krozgrov
10 years ago

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…

Admin
Admin
10 years ago

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

/ Johan

krozgrov
krozgrov
10 years ago

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.

krozgrov
krozgrov
10 years ago

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.

krozgrov
krozgrov
10 years ago

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.

Admin
Admin
10 years ago

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

derek2012
derek2012
10 years ago

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 supplementWinPE created by MDT2012 is version 3.1The Windows 8 custom wim task sequence can run sysprep and cannot reboot to the WinPE for creation of… Read more »

derek2012
derek2012
10 years ago

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 supplementWinPE created by MDT2012 is version 3.1The Windows 8 custom wim task sequence can run sysprep and cannot reboot to the WinPE for creation of… Read more »

Admin
Admin
10 years ago

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

chemdawg
chemdawg
10 years ago

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

stanc
stanc
10 years ago

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

m.carterrix@Wlv.ac.uk
m.carterrix@Wlv.ac.uk
11 years ago

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… Read more »

fraigoza
fraigoza
11 years ago

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

Admin
Admin
11 years ago

Most likely it's a corrupt wim file…

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

/ Johan

fraigoza
fraigoza
11 years ago

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:… Read more »

ervi
ervi
11 years ago

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

ervi
ervi
11 years ago

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=

Admin
Admin
11 years ago

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

/ Johan

chemdawg
chemdawg
11 years ago

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.)

tbartley
tbartley
11 years ago

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.

tbartley
tbartley
11 years ago

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… Read more »

Admin
Admin
11 years ago

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… Read more »

mathew
mathew
11 years ago

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.

fraigoza
fraigoza
11 years ago

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?

Technomyke
Technomyke
11 years ago

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.

Admin
Admin
11 years ago

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

tomcollins
tomcollins
11 years ago

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?

Admin
Admin
11 years ago

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

Max3
Max3
11 years ago

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?


>