how can I setup Zero Touch Installation ?


Recommended Posts

The most up to date version of this Guide will always be here. Reproduction of this guide is allowed as long as it links back to here

Verify that you have the correct infrastructure in place

Zero Touch Installation (ZTI) requires the following products to be installed in your network infrastructure:-

* SMS 2003

* SMS 2003 OSD Feature Pack Update

* Windows Deployment Services in Windows Server 2003

* Microsoft SQL Server 2000

Note: If you want a Microsoft checklist of the steps required to get ZTI working, see this page on Technet.

Prepare the deployment environment.

For the purpose of this article, I'm assuming that you have already installed and configured SMS 2003 and SQL.

Install BDD 2007 and then install USMT either manually by downloading the msi package or by installing it using the Components section of DeploymentWorkbench (the MMC console for BDD 2007). USMT captures desktop, and application settings, as well as user accounts and user files, and then migrates them to a new Windows installation. Next, install the SMS 2003 OSD Feature Pack. Click here to download and install the SMS 2003 OSD Feature Pack Update, once downloaded, double click the exe to extract it somewhere, I extracted it to c:\sms and then ran the OSDeployment_Setup.EXE file from within that folder to install the OSD Feature Pack. Once the feature pack is installed, it's safe to delete the setup folder (c:\sms if you did the same as me).

Once installed, you can start up the SMS Administrator Console and you'll see a new setting in the left pane called Image Packages. You are now ready to setup Zero Touch using the 18 Step guide below.

Zero Touch in 18 Steps

Create an OSD capture CD.

Capture a Vista image (wim).

Import the captured Vista WIM image into BDD.

Import WinPE2004/2005 & required OS files into BDD.

Create a new build in BDD for the captured WIM image.

Create and update the BDD Deployment point (OSD/ZTI).

Update SMS WinPE from the BDD/ZTi deployment point.

Import the captured Vista WIM image into SMS.

Create an OS deploy program.

Update the distribution point for the OS deploy program.

The following four steps in the process are not specific to Zero Touch Installation, but make the distribution of resources easier and more scalable in an enterprise environment.

Copy driver resources for SMS packaging.

Create a package from the driver resources.

Add the driver resources to a distribution point.

Update the SMS distribution point.

Update customsettings.ini and bootstrap.ini in BDD.

Update each OSD phase with BDD ZTI files and scripts.

Copy osdshell.lab.exe to osdshell.exe.

Create an install CD.

That's it, you are done !

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Why should simply opening the Action Center ... require any significant amount of CPU cycles? Too many are ignoring the elephant in the room: today's CPUs may have similar clock frequencies to CPUs from a decade ago (~4 to 5 GHz), but they run with far higher performance per clock, even on the smallest E-cores. The Action Center is a static, minor desktop element. It ought to open instantly on any CPU made in the past 2.5 decades at even low clocks. Opening a program? Boost away. Unzipping a file? Boost to your heart's content. Right-clicking the notification area? This should be an ultra-efficient, low-impact event that opens instantly. Compare today's UI elements to Windows 7 UI elements. Today's UI elements hardly do anything more substantial or important or critical, yet now require modern-day processors to jump half a GHz to reduce their latency.
    • This is not an option lmao: it is part of the KB5094126 update, pushed to all users. There is no GUI to configure it. Reading the article should be required for commenting.
    • Can you recommend me a good Pixel 7 on eBay? Because some are saying Gen 1, and I don't think that's what I want, right?
    • Close, but it is for any application starting, not just during boot time. In fact, it probably will not improve boot time at all because during a boot, the CPU is already boosting, so a pre-boost wouldn't change anything. I agree that it isn't exciting (especially considering every other OS already does it), but it is a good thing, even if they are just playing catch up.
    • Any so called performance increase will be in milliseconds, which nobody will actually notice in real world usage.
  • Recent Achievements

    • One Year In
      slackerzz earned a badge
      One Year In
    • One Year In
      highriskpaym earned a badge
      One Year In
    • One Month Later
      highriskpaym earned a badge
      One Month Later
    • Week One Done
      highriskpaym earned a badge
      Week One Done
    • Week One Done
      FBSPL earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      501
    2. 2
      PsYcHoKiLLa
      198
    3. 3
      +Edouard
      156
    4. 4
      Steven P.
      84
    5. 5
      ATLien_0
      71
  • Tell a friend

    Love Neowin? Tell a friend!