Start to Finish Project > Deployment Forum Community Forums

Unanswered Active Topics

Forums Search

Forums > Deployment Solutions > Lite Touch

Subject: Start to Finish Project

Prev Next

You are not authorized to post a reply.

Author

Messages

ClintonTull User is Offline

Posts:27

12/31/2007 9:57 AM
I was hired here at Ameren UE in St. Louis and was (Just me) assigned the task of creating one image for multiple types of hardware, Laptops, Desktops, Dell, Panasonic you name it its here. So at my previous Job Pfizer we had this setup but wasn’t familiar with it. I was the techie that noticed if drivers weren’t there or new hardware had the horrible 7b error. Also, can i take a base unattended in xp build it out as a standard and use image x to convert it and use as a deployment? Or do i have to go through the whole process in bdd?? Well on with the story. I have just recently read the article (after hours and hours of reading pprwork on how to deploy this process) of how you setup BDD. Well. My scripting is intermediate but usually can muddle through it. I am wanting to create an image with customizations to the registry, permissions on the registry, permissions on folders, and so forth plus we do not use SMS here at Ameren. (Radia) so a lot of my apps are not MSI or such so I will end up having to package most of my base applications for the build. Like Radia client, and Norton AV software. All patches are pulled down via Radia and so forth. But customizing our builds is a tedious 4-8 hr process once un-attended has completed. Yes it sucks. So where im stuck is after pulling down source files from winxp disk. Have db setup and just a couple apps in place for testing. I get the bsod 7b error at deployment. How do I Inject drivers at this stage before it starts up?? Next questions. With the amount of hardware we have how do I setup a drivers store of all drivers needed for each computer and it know which ones to install by model. We have an arbitrary naming convention which is given out by Radia which is manage by me as well. I assume that will be a prompt for the end user once LTI is ran. ZTI is only used via SMS right???? (not sure)….. I saw at Pfizer we had driver setup with a models.ini with all models in it with variables for machine names generated by wmi and then Im lost again on how it puts it in place before mini setup runs and shows it to have the drivers for that chassis. So whole lot of stuff going on here for me aside from my main duties. This is a “back burner” project for now. Currently we outsource all builds via a ghost with mini setup running at startup, I wish to have easy streamline builds as I did a Pfizer. Also, a web interface was used to setup the pc prior to build. Entered in info such as pc name, sms software to install (don’t have that option here) who and when it is built by and USMT and ghosting all in one. That’s a whole other monster “Backups and Migrations” Which I wish to implement in the future. For one person this is going to take much time. For Pfizer it took over 1 year and 15 guys to setup. Feeling the weight of this project is coming out while expressing my thoughts on this email. WHEWW a lot to bite off for a first project on a new job. Lot to grasp. I do appreciate any help or documents you may have on implementing this. If you wish or need further information to how im doing things here please ask and ill explain the best I can to help resolve and implement BDD.

Mike Dzikowski User is Offline

Deployment Forum MVP

Posts:122

01/01/2008 11:23 PM
Here is how I inject drivers. One things to note, you have to add all of your mass storage drivers before sysprep is ran. But here is how I do the injection of drivers. This is helpful if you have more than 5-10 hardware types. I think this is what you were talking about: I usually grab all of my hardware models from an SMS report. However, you may have to script this with an WMI query or something. Create a Drivers$ share on your DP Create directories for each model of hardware under a Drivers$ share on your distribution point For instance: D:\Drivers\Latitude D410 Create a folder for each type of driver (audio, network, etc) and add the drivers to the folder In the Deployment Workbench add to your rules section Under [Default] DriverPaths1=\\YOURSERVER\Drivers$\%Model% Under [Settings] Priority = Model, Default (default must come after Model) The drivers will now load based on Model during the deployment Note - Only add NIC drivers to the workbench that are needed by WinPE If drivers needs to be removed, updated, deleted simply remove the directory and make your changes. The reason I like this method is because its easier to manage all my drivers for many builds. On the flip side, you'll have to download all the drivers etc. When using this method I only put the needed NIC drivers in the Out of Box drivers in my workbench. Your 7B stop error is most likely due to a HAL issue or a mass storage driver issue. So make sure you have all the correct drivers injected. Are you building your images on a Virtual Machine or Physical Box? Here are some really good resources: deployvista.com myitforum.com http://blogs.technet.com/mniehaus/ http://blogs.technet.com/benhunter/

Mike Dzikowski, MCP

Mike Dzikowski User is Offline

Deployment Forum MVP

Posts:122

01/01/2008 11:43 PM
Here is a front end. You could tweak this to create a web page probably...I have not really used this yet though... http://www.deployvista.com/Blog/tabid/70/EntryID/46/Default.aspx

Mike Dzikowski, MCP

ClintonTull User is Offline

Posts:27

01/02/2008 12:30 PM
ok, now im running winxp as my distribution server so i may not have bdd 2007, just the mmc snap it for it. I followed the guide from http://www.deployvista.com/Repository/BDD2007/tabid/74/EntryId/25/DMXModule/400/ctl/EntryDetails/mid/400/Default.aspx setup permissions for "Everyone" Wide open then imported the OS then setup a task sequence then ran the .iso litetouch.iso x86 in Virtual Machine to boot it up and see if it will show the menu. It fails to bring up the second cmd window. NO menu. Earlier had the menu come up but was blank white. Any ideas??

ClintonTull User is Offline

Posts:27

01/03/2008 12:55 PM
Ok, got the sql remote connection issue worked out.... permissions granted on the system for the distribution... permissions and named pipes and tcip setup on the sql server.... now it gets 3/4 the way through installing in Lite touch and it hangs on the install. Anyone know why this is happening?? This is in a virtual machine install using the litetouch.iso to boot up with.

ClintonTull User is Offline

Posts:27

01/03/2008 3:28 PM
ok, setup completely bombs out after copying over the setup files in LTI. here is the log from the VM Install sesion. see attached for lite touch and bdd logs.
Attachment: BDD.log Attachment: LiteTouch.log

ClintonTull User is Offline

Posts:27

01/03/2008 3:35 PM
Also, 60KB is all that can be uploaded the BDD log file is naturally 71kb....... Possibly get that changed maybe to 120 or so?

Mike Dzikowski User is Offline

Deployment Forum MVP

Posts:122

01/03/2008 3:51 PM
Have you ever tried deploying a machine on this VM before? Sometimes left over junk from a previous failed deployment will make BDD hiccup. Try formatting that drive from within WinPE, reboot, and try the deployment again. Also, I noticed in the logs BDD is complaining about a SLShare not being found. Try adding that to your CS.ini - Just create a Share and add that to the CS.ini (see the link below for an example). FYI -- BDD likes all shares to be named as Share$ (with the dollar sign). http://www.microsoft.com/technet/desktopdeployment/bdd/enterprise/ZTIDFTGuide_12.mspx Let me know how that works, Mike Dzikowski

Mike Dzikowski, MCP

ClintonTull User is Offline

Posts:27

01/04/2008 10:32 AM
Well here is my customsettings.ini. all being ran on my own system d19473 Still having same errors. Xp bombs out at starting unattended installation. Loosing faith i can get an unattend to work!!!!!! Pulilng Hair! [Settings] Priority= Default CustomKeysUserData=UDShare,UDDir,UDProfiles,SLShare=\\D19473\distribution$\Logs,OSInstall,Packages(),Administrators(),DriverPaths(c:\Drivers),PowerUsers() CustomKeysSysprep=ComputerName,TimeZone ************* is syntax for drivers above (c:\driver) correct?? [Default] OSDINSTALLSILENT=1 TimeZone=020 JoinDomain= ComputerName=Dxxxxx OSInstall=Y SkipAppsOnUpgrade=NO SkipCapture=YES SkipAdminPassword=YES SkipProductKey=YES --------------------------------------------------------------------------------------------------- BootStrap: [Settings] Priority=Default [Default] DeployRoot=\\D19473\Distribution$ Database.xml - - BDDAdminDB D19473 BDD 6988 DBMSSOCN BDD \\d19473\Distribution$

ClintonTull User is Offline

Posts:27

01/08/2008 12:30 PM
Ok, I have an image from start to finish ran from VMware and configured upon completion i did the "Do not run sysprep but copy over the files so I can configure our image to a BASE Standard for our company. Ill try the drivers situation next and test on the machines that i know have issues with mass storage drivers. How is it others are using the DB to do this same process correct? How do I do it while using the DB as well?

ClintonTull User is Offline

Posts:27

01/15/2008 1:06 PM
I have the image completed. Now if i have 7b errors on bootup and the drivers setup correctly stated above, how do i Inject the drivers? Is that done as is the sysprep injection? When I saw the previous company they had a folder in the drivers storage area called inject, then oem$, inf, system32 blah blah blah. how is this specified or will bdd just pick up those files and put them where they need to be for Hal issues?? or mass storage??? Wil the 7b error be a mass storage error or a hal error?

ClintonTull User is Offline

Posts:27

01/15/2008 1:17 PM
Also, anyone have a problem with the mouse not working in VM after the system is installed. I have to delete the mouse driver unhook the mouse from pc then reboot the vm ware session and then it reinstalls the mouse and it works. Go figure...

Mike Dzikowski User is Offline

Deployment Forum MVP

Posts:122

01/15/2008 1:48 PM
You could install the VMWare tools and extract the VMWare mouse driver and add that to the Out of Box Drivers.

Mike Dzikowski, MCP

ClintonTull User is Offline

Posts:27

01/15/2008 2:03 PM
Create a Drivers$ share on your DP Create directories for each model of hardware under a Drivers$ share on your distribution point For instance: D:\Drivers\Latitude D410 Create a folder for each type of driver (audio, network, etc) and add the drivers to the folder In the Deployment Workbench add to your rules section Under [Default] DriverPaths1=\\YOURSERVER\Drivers$\%Model% Under [Settings] Priority = Model, Default (default must come after Model) I did this and got the dreaded 7b error on reboot. do i have to specify anything anywhere else or will it go through all the folders and subfolders and find the sys inf file appropriatly? DriverPaths1=\\myserver\Distribution$\Drivers\%Model% I put the drivers folder inside of Distribution$ and made the path appropriately in the rules. How is it I do injection now using this method? Here is a models.inf file for a past company but since im new to how they set the old up Im unfamiliar. [Models] DEFAULTW=Default Workstation DEFAULTL=Default Laptop VMware Virtual Platform=VMWARE PORTEGE 3500=PORTEGE 350x PORTEGE 3505=PORTEGE 350x Compaq Tablet PC TC1000=TC1100 Deskpro=Compaq DeskPro Dell Optiplex GX520=Dell Optiplex GX520 OptiPlex GX1 400Mbr+=Dell Optiplex GX1 OptiPlex GX1 500Mbr+=Dell Optiplex GX1 OptiPlex GX1 600Mbr+=Dell Optiplex GX1 OptiPlex GX1 600L=Dell Optiplex GX1 OptiPlex GX1 500MTbr+=Dell Optiplex GX1 OptiPlex GX1 450M+=Dell Optiplex GX1 OptiPlex GX1 400L+=Dell Optiplex GX1 OptiPlex GX1 400MTbr+=Dell Optiplex GX1 OptiPlex GX1 500M+=Dell Optiplex GX1 OptiPlex GX1 600L+=Dell Optiplex GX1 OptiPlex GX1 350Mbr+=Dell Optiplex GX1 OptiPlex GX1 450MTbr+=Dell Optiplex GX1 OptiPlex GX1 550L+=Dell Optiplex GX1 Optiplex GX110=Dell Optiplex GX110 Optiplex GX150=Dell Optiplex GX150 OptiPlex GX240=Dell OptiPlex GX240 Optiplex GX260=Dell Optiplex GX260 Optiplex GX270=Dell Optiplex GX270 Optiplex Gxa 266M EM+=Dell Optiplex Gxa Latitude CPi A366XT=Dell Latitude CPi Latitude CPx J650GT=Dell Latitude CPx Latitude L400=Dell Latitude L400 Latitude C400=Dell Latitude C400 Latitude C600=Dell Latitude C600 Latitude C610=Dell Latitude C610 Latitude D810=Dell Latitude D810 Latitude D820=Dell Latitude D820 Latitude LS=Dell Latitude LS Optiplex SX260=Dell Optiplex SX260 Optiplex SX270=Dell Optiplex SX270 Precision WorkStation 420 MT=Dell Precision 420 MT Precision WorkStation 530 MT=Dell Precision 530 MT HP Tablet PC Tx1100=TC1100 PORTEGE M200=Portege M200 STYLISTIC ST50XX=Stylistic ST5022D I260+=ITRONIX I260+ JLT1502=JLT1502 CF-xxxxxxxxx=Toughbook CF-30 17023xx=ThinkPad X60s 1703Axx=ThinkPad X60s 7666xxx=ThinkPad X61s 7667xxx=Thinkpad X61s 6363xxx=ThinkPad X60 Tablet 6364xxx=ThinkPad X60 Tablet 7763Axx=ThinkPad X61 Tablet 1860BA9=ThinkPad R52 D2004=Fujitsu Siemens RX100 S3 PRIMERGY RX100 S4=Fujitsu Siemens RX100 S4 VX5=LXE VX5 ProLiant DL140=ProLiant DL140 ProLiant DL140 G2=ProLiant DL140 ProLiant DL140 G3=ProLiant DL140

Cody Sloat User is Offline

Posts:1

02/28/2008 5:30 PM
Hello, I was interested in the Drivers folder share method. In our previous method used here we had one share with all the models in it, and then each had sub folders much like you have now. When we moved over to BDD 2007 we initially used pnp but we currently have about 200 different models, so we implemented a make and model script with drivergroups etc. It now takes 5-10 minutes to load workbench and 5-10 per driver INF we have to add. I was searching for a method of speeding up this process and stumbled across your solution. Can you elaborate on the specifics more? Ie, step by step whats needed to be done to implement this method? Or is it just those short steps you listed.

You are not authorized to post a reply.

Forums > Deployment Solutions > Lite Touch > Start to Finish Project

ActiveForums 3.7

I usually grab all of my hardware models from an SMS report. However, you may have to script this with an WMI query or something.