dandirk

I thought /audit put windows in audit mode at next boot? Also assume this is when the 2 audit passes are run... From: http://technet.microsoft.com/en-us/library/cc766514(WS.10).aspx "To apply the settings in auditSystem and auditUser, you must boot to Audit mode by using the sysprep/audit command.". I highly doubt I need to automate anything in the audit passes, just read that audit mode is required to do profile edits and add apps. Is this not the case? Could I just enable to admin account, login, install apps, updates etc then run sysprep /generalize /oobe and have my xml copy profile set? I also found a similar process HERE, where they run audit mode right away after install by using ctrl+shift+f3 in step 9. As of right now I don't want to boot to audit when I image PC, just when configuring the image (before image is taken). Am I off base here?

I am using guides on the internet to setup a unattended.xml for use with sysrep. These are great but I really like understanding the process a bit better then just following steps blindly... Currently we install XP, add drivers, apps, config etc then sysprep with mini setup option. Would sort of like to mimic this procedure. We do not have an imaging server etc, we image with ghost, and let mini-setup install drivers, name etc for a fresh PC/config. Been reading up on the AIK and XML passes. Microsoft's description here is what I am basing this process on... This is how I understand my use of sysprep and the unattended.xml process. Please let me know if I an wrong or off base. 1. Install Win7 on reference PC or VM. (install unattended.xml in sysprep folder if needed for audit modes) 2. Run "sysprep.exe /audit" to reboot to audit mode (this will activate the admin account, and run the 2 audit sections of the AIK IF I need them). 3 In audit mode (administrator account), add software, copy drivers folder to %windows%\inf, windows updates, GUI changes etc 4. Run sysprep.exe \generalize \oobe \shutdown \unattend:XXX.xml 5. Take ghost image. 6. Reboot and the mini-setup like will run and go through Generalize, Specialize, and OOBE passes at next boot, NOT running offline and PE????? I will have to tackle the joindomain issue, but I figure I will do that later, when I have everythings else working. I know there are bugs and issues with joindomain. I just want to understand which passes are being used so I can edit/test accordingly. Thank you for your time.

cool thanks - just like mdt...

Question about using DISM to inject out of box drivers for Win7. With XP/sysprep I just copied drivers to the computer and appended hklm\software\microsoft\windows\currentversion DevicePath key with each driver folder. Worked great for pnp drivers even printers etc. Driver Injection with XP had issues with drivers that had the same file names but were distinctly different (inf, sys etc were the same name but different HWids/versions etc). Does injecting with DISM have similar issues with multiple versions of the same driver? I am still playing around with all the robust tools for win7 (nth degree of complexity vs xp lol)... the MDT tool does seem to seperate drivers into individual folders, but I don't think mdt is intended for our needs (single universal image file to be deployed locally aka ghost image) Thanks

Well not really how to slipstream drivers (got that covered:)) But I figured you guys will probably know more so the general XP forums... Running into small quirks with intel graphics drivers after unattended install. Basically it comes down to configuring settings (like display clone, single display etc). Before I start reg monitoring, wondering if you gurus deal with graphics drivers configs. Does instal have some sort of admin profiles or something... Ran some google and didn't find much...

I know this is a really old post but it was helpful to me... The last poster is correct the StartButtonBalloonTip = 2 works for that annoying "Click on the Start Menu..." large Balloon that pops up on new installs/syspreped installs. It will only go away if you click on the start menu while the balloon is up. Not sure about the above notes regarding the runonce locations etc. I used a different approach. I deleted the key from HKCU and then ADDED it to HKLM so it would affect all users... Testing whether the change will hold through sysprep...