specialk44

Hi Benzini, We have finally got our deployment working the way we would like, skipping the keyboard locale wizards at the beginning but setting the final locale to UK settings. Unfortunately we do not have a PXE server which works with BDD yet so we are booting from a USB key but the only manual step for us is to enter the password for connecting to the distribution share (which we could also put into the bootstrap.ini file if we wanted to) and the rest is zero-touch, even adding the machine to the required OU as this has been specified within the role on the BDD database. Here are the relevant settings from our bootstrap.ini and customsettings.ini files. Bootstrap.ini file [settings] Priority=Default [Default] SkipBDDWelcome=YES KeyboardLocale=0409:00000809 userID=%user id used to connect to share% userDomain=%your domain% DeployRoot=%path to deployment share% Customsettings.ini - [Default] OSInstall=YES SkipWizard=YES UserDataLocation=NONE SkipAppsOnUpgrade=YES SkipCapture=NO SkipAdminPassword=YES SkipProductKey=YES SkipLocaleSelection=YES BuildID=VISTA-32-CUSTOM TimeZone=85 TimeZoneName=GMT Standard Time UILanguage=en-US UILanguagefallback=en-GB InputLocale=en-GB SystemLocale=en-GB UserLocale=en-GB KeyboardLocale=en-GB Not sure if you really need the fallback option but we put this in during testing and have left it in there. I think as long as you set the UILanguage to en-US it should skip past the initial Vista wizard but by setting the other locales to en-GB the final build should have the appropriate settings. Works for us anyway. Hope this helps.

Benzini, I am experiencing many of the issues you have mentioned, nice to know I am not the only one! Unfortunately I do not have many answers but here is what I have so far: - When I apply a base Vista image (based on the Enterprise DVD) the wizard gets skipped no problem at the start but as soon as I try and use a custom build based on a custom image I get the Windows Install step asking about the Language, Time/Currency and keyboard locale at the start of the deployment process. I think the bootstrap.ini settings just apply to the earlier step when it first boots to WinPE, prior to connecting to your BDD share. I've tried stripping all the settings out of my custom build/image but the only way I can see to get rid of this wizard appearing is to use a ZTI process (through SMS) which we do not have implemented at present. - For the Nvidia driver reg fix you could try amending your unattend.xml file of the build and inserting a run syncronous command into the specialize part of the file. You may need to try out a few commands for this but I have something in here which just puts an entry in the registry with the build ID e.g. cmd /c reg add HKLM\SYSTEM /v BuildVersion /t REG_SZ /d BG-VISTA-32-CUSTOM-BUILDv1. - I am also getting the runtime errors during the office install. I have some general Vista updates being applied (about to add more as now out of date) but have not yet added any office updates. The ones being applied are - KB905866 KB925528 KB925902 KB928089 KB929685 KB929735 KB929777 KB930178 KB930857 KB931099 KB931213 KB931573 KB931768 KB932246 KB933566 KB936824 KB936825 - I am also trying to customize office on the build, particulalrly Word and Outlook settings, so that the default settings are more sutied to our organisation and that when users are re-imaged they have all the necessary settings captured (through USMT). There are a load of settings that can be done through Group Policy but I cant find any to set the reading pane on Outlook. I also haven't found any other way to set a default font up without amending the normal.dotm template. It would also be nice if the default template had more quick access toolbar commands on by default. - Does anyone know how to disable TCP IPv6 as part of the build? I've found a few suggestions here but not been able to get this to work, guessing it might be due to every NIC being different. Karen