Jump to content
MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. ×


  • Content Count

  • Joined

  • Last visited

  • Donations


Community Reputation

0 Neutral

About dandirk

  1. 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
  2. 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
  3. 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 deg
  4. 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...
  5. 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...
  6. Like this?: http://www.guidebookgallery.org/pics/gui/s.../win2000pro.png Honestly I am not sure... About the title of the tweaks you found or how to get win2000 search exactly. I generally use reg monitors to find my reg settings, its generally faster then searching the net. I also can see what other changes are being make (HKLM vs HKCU etc) The XP advanced search screen is pretty darn close to the old Win2k version, so sorry I didn't look any further... EDIT OK I looked and tested the "Use Search Asst" reg and it does work, and provides the search window that I linked to above. Only this o
  7. Try this to get rid of the dog and to enable advanced search by default. Windows Registry Editor Version 5.00 [HKEY_CURRENT_USER\Software\Microsoft\Search Assistant] "UseAdvancedSearchAlways"=dword:00000001 REM Sets the option to always use the advanced files and folder search config 0 = Disable 1 = Enable "SocialUI"=dword:00000000 REM - Sets the option to use the search assistant (dog) 0 = Disable 1 = Enable
  8. Possibly in this extreme case... Maybe people didn't know how to edit the registry. Maybe people know how but would rather purchase an easy and fast tool to do it for them? There are many tweak applications out there that charge a fee yet do not provide a magic tweak but rather a collection of reg/script tweaks that are easy to set/unset? I can tell you if I had to do 20 tweaks, I would pay for a tool to do it.
  9. There are many reasons people would want to do this... presetup for end users via image or script are just 2... This is the reg I use to enable the advanced search... Windows Registry Editor Version 5.00 [HKEY_CURRENT_USER\Software\Microsoft\Search Assistant] "UseAdvancedSearchAlways"=dword:00000001 REM Sets the option to always use the advanced files and folder search config 0 = Disable 1 = Enable "SocialUI"=dword:00000000 REM - Sets the option to use the search assistant (dog) 0 = Disable 1 = Enable
  10. I assume you are using sysprep???? sysprep version before SP3 automatically copies the Administrator profile to the default users profile for you. The SP3 version of sysprep doesn't unless you use the UpdateServerProfileDirectory=1 line in sysprep.ini. If you are using the pre-SP3 version and DON'T want it to copy the admin profile to default users, then you will have to install a MS patch (sorry can't remember it). Then you can create another profile from scratch and copy it over to the default profile... No you don't need to create the default profile from administrator, just remember to c
  11. HAL issues are becoming less and less of an issue if you have a fairly modern environment (4-5 years life cycle). Having sysprep switch between ACPI Multi and ACPI Uni processor HALs is fairly simple I have found. If you have non-acpi HAL machines then yes hal issues will be tougher for a single universal image. We have a 4 year life cycle on our PC/laptops. Currently all 12 models we support are ACPI, most run Multiprocessor HALs. We have 1 Uniprocessor HAL machine (our oldest supported laptop model HP NC6220). For our image, I create the master image on our oldest desktop PC, which happ
  12. hmmm interesting... On my sysprep image the windows driver signing option is NOT set back to prompt and stays at ignore... Maybe you have a default profile issue or something. I only use the reseal/mini setup options when running sysprep, I do not use the -pnp switch. (I actually run sysprep from the GUI). My sysprep ini looks like this (this is SP3 version): [unattended] OemSkipEula=Yes InstallFilesPath=C:\sysprep\i386 DriverSigningPolicy=Ignore UpdateInstalledDrivers=Yes KeepPageFile=0 UpdateServerProfileDirectory=1 NonDriverSigningPolicy=Ignore UpdateUPHAL=
  13. This is a pretty open ended question, much depends on the method of imaging/deployment is used and also the policies of device setup. IcemanND's quotes are pretty much in line with our time frames (his imaging methods are probably close to ours). Ours probably would be a bit longer though closer to 16 hours if there are no "catches". The huge determining factor like IcemanND said would be the type of model. If your shop is a dell/hp only type shop things will be faster because most of the time the hardware/drivers are very similar between models. Bugs/oddities are generally known already.
  14. How can I handle 2 different intel mass storage drivers with the same file names? Sysprep seems to be copying the files to somewhere and prompts me to overwrite during the reseal process... I am creating an image that requires massstorage drivers for an HP 6710b and a HP TC4400. Both have intel chipsets which use the exact same driver file naming scheme. Each of their iastor.inf files and iaahci.inf files are missing the proper deviceID for each other... The .sys files are fairly different in size, the older iastor.sys file is much larger. I downloaded a newer mass storage manager install fr
  • Create New...