HII Quick Start Guide

Hardware Independent Imaging is a new process that LANDesk Management Suite version 9. his process a!!ows "ou to use one image across a!! hardware p!at#orms #or a sing!e $perating S"stem image. his process re%uires certain steps #or it to work correct!". his %uick start guide is designed to graphica!!" assist "ou in the set up process. A simp!i#ied description o# the HII process is as #o!!ows. Detai!s a&out the speci#ic steps "ou'!! need to #o!!ow and considerations #or di##erent t"pes o# images are #ound in the LDMS9()sers guide. *hen "ou dep!o" an image created using HII+ the imaging script &oots the device to the *indows pre&oot environment. In the pre&oot environment+ the HII too! wi!! se!ect the appropriate HAL .d!! #i!e and !oad it. he $S is insta!!ed on the device+ &ut &e#ore the $S &oots+ the HII imaging script determines which drivers are re%uired &" the device and copies the driver #i!es to the device's hard disk. he drivers are added to the device's registr"+ so that when the $S &oots the *indows setup detects the new drivers+ insta!!s them+ and con#igures the device with the drivers. *indows then restarts with the drivers running+ and the Management Suite agent is insta!!ed.

Getting Started With HII Set-up

,. Attain the needed drivers -Audio+ .ideo+ Network+ Mass Storage Devices+ and other drivers/ #or the Hardware that "ou wi!! &e dep!o"ing to and the correct $S. Drivers can &e attained &" whatever means "ou see #it+ ie. Driver capture too!+ vendor+ or manu#acturer. *e strong!" recommend getting the drivers #rom the manu#acturer or the vendor+ as driver capture too!s ma" not gra& a!! the #i!es needed+ thus causing #ai!ures. A!wa"s veri#" that the drivers "ou are going to use are tested and va!idated prior to using them with HII. 0. In the LANDesk Management Suite conso!e+ go to the too! &ar and c!ick on 1 oo!s 2 Distri&ution 2 $S Dep!o"ment3.

4. Se!ect the 1Manage driver !i&rar" #or hardware5independent imaging3 as shown a&ove. his wi!! a!!ow "ou to !oad the proper drivers #or each o# the speci#ic hardware t"pes "ou wi!! &e working with.

6. Se!ect the 1Add3 &utton 7reate a !i&rar" o# drivers that wi!! &e avai!a&!e to the imaging too!. hese drivers are used on the hardware "ou want to image+ and are divided into severa! categories. he 1Hardware5independent driver !i&rar"3 a!!ows "ou to add Audio+ .ideo+ Network+ Mass Storage Devices+ and $ther drivers that wi!! &e needed on the di##erent hardware p!at#orms. 8ou wi!! need to set up speci#ic drivers #or each hardware t"pe. I# "ou high!ight the di##erent categories "ou wi!! &e a&!e to see what drivers have a!read" &een added. Associate speci#ic device mode!s with drivers in "our !i&rar". *hen the hardware5 independent imaging too! runs it wi!! detect the device manu#acturer and mode!+ and then down!oad the associated drivers and insta!! them on the device during the imaging process.

9. Se!ect the t"pe o# driver "ou want to add+ then give the driver a uni%ue name+ as each hardware p!at#orm wi!! re%uire a uni%ue driver name

:. Ne;t+ se!ect the $S p!at#orm-s/ that the driver is designed to work with. -Driver detai!s are optiona!./

<. =rowse to the !ocation where the drivers are !ocated. =" de#au!t+ when the driver is !oaded into the HII setup+ it wi!! cop" those #i!es into a repositor" on the core server in 7>?@rogram Ai!es -;B:/?LANDesk?ManagementSuite?!andesk?#i!es?drivers?Cdriver t"pe2. B. Se!ect Ne;t I# the driver #i!es are va!id+ "ou wi!! see a success message. 7!ick Ainish to c!ose the dia!og &o;. I# "ou see an error icon+ "ou'!! need to #ind the correct driver #i!es #or the driver "ou have named.

I@> Demove an" !arge #i!es not needed #or the driver insta!!ation #rom the #o!der such as se!#5e;tracting e;e #i!es used to o&tain the drivers.

9. Se!ect 1Ainish3+ to comp!ete the driver up!oad process. Once the different drivers packages have been created, we need to set up the Manufacturer types of systems that you wi be imaging, ie! "e "#$$, H% "&'($$, etc) *his information wi be pu ed from the +,-"esk database for devices that have sent in inventory scans.

,(. In the $perating S"stem Dep!o"ment se!ect the 1Manage manu#acturer and mode! #or hardware5independent imaging3.

,,. Now "ou wi!! have the opportunit" to add the Manu#acturer and Mode! o# the s"stems that "ou wi!! &e imaging.

,0. Airst c!ick on Manu#acturer drop down and se!ect the one "ou want to work with.

,4. Ne;t+ under 1Mode!3+ use the drop down !ist to se!ect the Mode! "ou are wanting to add drivers to. Make sure that "ou know the mode! num&er -i.e. 04<4B7) etcE/+ as it wi!! most !ike!" not &e !isted as with the norma! -i.e. Latitude D:((+ Lenovo 6( etcE/. Note> he LDMS inventor" wi!! popu!ate the dropdowns &ased on the machine records in the data&ase.

,6. Ne;t se!ect the driver t"pe "ou want to add

,9. Ne;t p!ace the check &o; #or the correct driver

,:. $nce a!! the drivers are added+ "ou wi!! see the !ist o# assigned drivers #or that device. N$ F. *ith this so!ution+ there is no need to create a driver store #or each Make and Mode! as !ong as the driver is the same. *hen "ou get the drivers #or "ou device+ "ou can use a sing!e driver across mu!ti&!e p!at#orms as !ong as the drivers are the same. So when "ou are creating

driver stores and "ou are going to share drivers+ make sure "ou are use a more generic driver name when creating the driver store.

.sing Hardware-Independent Imaging With OS "ep oyment Scripts

8ou can incorporate hardware5independent imaging into an $S dep!o"ment script #or *indows devices+ i# the script meets these re%uirements> G It must &e &ased on the *indows @F &oot environment G It must use *indows S"sprep to con#igure the $S image o incorporate hardware5independent imaging+ "ou need to se!ect the HII option in the script wiHard so the HII too! runs a#ter the operating s"stem is insta!!ed. A!so+ "ou need to se!ect one o# the #o!!owing options> G 8ou can have the HII too! automatica!!" se!ect the manu#acturer and mode! o# the device "ou are imaging+ &ased on the strings in the device's =I$S. Se!ect this option i# "ou want to use the script #or devices #rom mu!tip!e manu#acturers. G 8ou can speci#" one manu#acturer and mode!. Se!ect this option on!" i# "ou wi!! use the script on the same device mode! ever" time. To include hardware-independent imaging in an OS deployment script, set up your script as you would normally for an OS Deployment, but for HII you need the following settings checked in the script. ,. 7!ick oo!s 2 Distri&ution 2 $S Dep!o"ment. 0. )nder $S images+ se!ect a script. Dight5c!ick the script and se!ect Fdit+ or to create a new script+ right5c!ick A!! $SD Scripts and se!ect New *indows @F con#iguration.

4. 7!ick Methods and credentia!s. Se!ect the 1Images uses S"sprep3 and 1)se Hardware5 independent imaging3 check &o;es.

6. 7!ick 1S"sprep options3 2 1Hardware5independent imaging3. o have the HII too! automatica!!" se!ect the manu#acturer and mode! o# the device to &e imaged+ c!ick Auto detect. he too! wi!! read the settings in the device =I$S to #ind strings that match the manu#acturer and mode! strings "ou have de#ined when "ou associated device mode!s with drivers. I# "ou want to speci#" a manu#acturer and mode! #or the script+ c!ick Se!ect manu#acturer and mode!. Se!ect a manu#acturer and then a mode! #rom the !ists. he device drivers associated with that mode! are !isted #or "our re#erence.

De#ine a!! other script options "ou want+ and c!ick Save to save the script.