Thank you Mr. Smartepants !!! I´ll give it a try tomorrow at work, this past week I´ve used Network Inventory Advisor v3.7 to audit the entire network, and I have an excel with all drivers needed for my 600+ computers, so I´ll make a pendrive with these and another with all drivers, for when a notebook lands on my workbench...

Mr. Overflow, please don´t refrain yourself !! If there´s anything to read about please point me in the right direction... I´m puzzled about the "marriage" with a machine...

I have all machines logged to my domain (Windows NT Server, yikes !!) but all profiles are stored locally, I think I´ll have SID issues, I never had one but I´m scared as a red shirt ensign, encountering a Borg vessel...

I´ll think I´ll quit this job and search another one... I´m starting to get bored because of the lack of challenges...

Again, a pleasure to hear about you guys !!!

Take care !!!

protools_operator wrote:

Hi, I've been reading this forum for a few years now and this is my first post.

I wonder if I can replace the NTLDR file after using the "2nd Method" to the original XP file and it won't affect the operating system functions.

If anyone tried that I would like to know.
Thank you,
-Noam

If you refer to what I wrote, I think that after the Longhorn NTLDR has successfully identified the HAL and Kernel type AND Windows XP has assigned the proper machine type in device manager (after 1rst reboot) it is safe to revert back to the original. I´ve never felt the need to do so, but I see no harm about it.

Why should I replace the original Windows XP SP3 NTLDR with the original NTLDR from Windows Vista Beta 1 (aka Longhorn) because the longhorn NTLDR has automatic HAL and Kernel type detection, saving the trouble of choosing the correct HAL and Kernel image each time you deploy the image.

I was busy trying to add these driverpacks to my universal image, the last try was about the last week, anyway I managed to make an image that deploys in 7 minutes, has a size of 10.8Gb on disk, on first start, it automagically searches on "C:\D" for 1667 drivers to mach those in device manager, so, the only thing I had to do is wait 10 minutes for the image to "stabilize" itself, then run a batch file to erase the driver database and restore original DriverPath in registry, change computer name, add to domain, and finally put it on the assigned workplace.

As good as it sounds, I felt it a little "strange" mainly because it took about 4 minutes to search the driverpacks, only after that I could use the mouse and the keyboard, I think I´d rather keep my driverpack on a pen drive and write a batch file to do the job, besides, in the long run I think I´ll save more time....

Cheers !!!

PS: I wonder (kinda like the Philosoraptor LOL) what would happen if someone copies an entire user profile folder, and exports the registry keys, to another computer, will it work ?? I´m asking for trouble if I do this on a domain computer ?? If I manage to do this, I can automate backups... that´s another quest in this "one click fix" for my 629-computers-h*ll...

Glad to hear news about you guys !!!

Take care !!!

Well, about the drivers, I´ve never figured out so we just might join forces and resolve this puzzle...

Meanwhile I carry an 8gb pendrive with a bunch of drivers, so I just add them via device manager

Like a year ago I tried S.A.D. and it works, but not flawlessly as I would like to, so I decide to take a break... tongue

Besides they only pay for a "repair guy" the´re not paying me for a full sysadmin.  big_smile

About the key, the only good method I can think of now, would be to replace OOBETimer in registry and run "msoobe /a" at first run

That would pop up a window asking for activation, then you select "via telephone" and "change product key"


I´m getting out of thread I think, so send me a mail if you need anything else !!!

Hi, Intelppm.sys is Intel Processor Power Manager and it will only load itself if you make the "source" image on an Intel based computer, therefore if you make the image with an AMD processor none of this happens, if by change you use a Intel CPU when creating the image then you will have to switch startmode to 3 on that service for the image to boot on an AMD machine.

In several microsoft KBs HAL and Kernel combos are mentioned but I think there where only two KBs that says there are performance issues by using a HAL not tailored to your processor, I`ve been switching HALs like 4 years now and never have BSODs, dunno about performance, but problems have not arisen so far.

If by chance you get your hands on a Longhorn Beta 1 NTLDR that NTLDR has automatic HAL switching, so you extract all HALs and Kernels to their proper locations and use a BOOT.INI switch to tell NTLDR to guess wich one to use, I think this method works better.

Here is some reference to the HAL / Kernel.

http://support.microsoft.com/kb/99588/en-us

http://support.microsoft.com/kb/237556/en-us    - This one is for windows 2000 but it works for XP too, check out the filenames as they are a complete reference.

http://support.microsoft.com/kb/309283/en-us

http://support.microsoft.com/kb/159111/en-us    - This one mentions problems with multiprocessors using uniprocessor HAL.


Please forgive my english grammar, my native regional settings are spanish, Argentina big_smile

Feel free to reply or mail should you want to further discuss this topic.

Best of luck !!!

Sorry for the delay, I´ve also worked at five computer shops before, and I´m currently working on a hospital, we have 547 computers 8 servers and lots of routers switches etc. I repair computers for a living since 21yo now I´m 29 and I´m from Argentina.

I use one single image of Windows XP SP3 for every PC and let windows decide about the HAL, I´ve already know about different HALs, ACPI, NON-ACPI and all the stuff, I´ve read all KBs from MS and yes it can be done in two ways:

Method 1: Use a custom BOOT.INI describing different entries for each HAL + Kernel modes, Basically those are 4 types
                Remember you have to extract all kernels and hals from drivers.cab or sp1.cab or sp2.cab or sp3.cab and place them
                in their proper paths for this method to work correctly. This method requires you to choose the correct HAL + Kernel combo from the
                BOOT.INI menu, also this method works well on Windows 2000 too.

Method 2: Find NTLDR from Windows Vista Beta 1 AKA Longhorn, that NTLDR has automatic detection of HAL, plus, you must add /AUTODETECT
                to the end of the BOOT.INI loader string, for this method you must also uncompress all kernels and HALs into their proper paths.
                this method only works on Windows XP, the Longhorn NTLDR fails to boot on Windows 2000.

I know that both methods are not supported by MS, indeed MS does not support anything but SysPrep under certain conditions and the original installer CD, but I´ve been using it since the last 4 years and never had a problem related to this.

The ONLY thing that I´m cautious about is NEVER join the image to a domain before deploying, that is ONLY join a domain once the machine has been deployed, because of SID replication issue (although I´m pretty sure that SIDs are generated on the PDC the first time you log in) by the way I´ve used method 1 the first year, from the last 3 years until now I´m using the method 2.

Too bad that NTLDR is only available on english ( I use windows in spanish, when you press F8 before log in the menu pops out in english) I´ve tried my best to translate Longhorn NTLDR  to spanish but I was unsuccesful.

So know I´m stalking this forum so I can read again about Devicepath and Windows Plug and play service checking sub folders on a network path, if that is possible or not.

So, to everyone reading this out, feel free to ask any questions via this forum or mail.

Do it once, do it well, never do it again !!!

Thanks !!! I´ll try M2 but since my machines are Pentium III with 128 - 256 RAM it takes ALOT to decompress even small files, I´ll try today at work !!!

Bump !!! I´m using SAD on my win2000 universal image, all works fine, but I have two questions:

Is there any driverpack for modems ??? If there is none, it´s ok if I start making one ???

It takes about 20 minutes SAD + M1, is there any way to make it faster ??? or can I tell windows 2000 to check on subfolders ???

Ok, thanks again for pointing me on the right direction OverFlow !!!! since SAD M1 is working flawlessly as an autostart right after 1rst boot of deployed image, guess I´ll be using that approach for this week, anyway it would be nice to mark some mass storage lines for win2k, so I will do it for my next build wich starts this wednesday !!!

Thanks again buddies !!!!

PS: I wish I had a cold beer dispenser & teleporter, you really deserve a cold one !!!!!

Last night, around 3am local time I`ve put all driverpacks in my pendrive, today I`ve already deployed 3 machines with my universal image, 3 different machines and it works flawlessly !!! Then I plug my pendrive with driverpacks in it, and something kinda weird happened to me, on the first machine driverpacks were applied flawless, on the second machine audio and pci bus got stuck, and third machine also was a flawless run...

I know that my caffeine level on thursday nights is far from ideal, thats why I think that I´ve messed up with directory naming conventions ( F**K folders, again tongue)
I´ve renamed Driverpacks.net to 1 and 2 each made with one of the methods
available (read: the cabber and the 7zipper )

I´ve also noticed that when DPinst finished a line says on the console: bad command or file name... OMG that´s when the DPfinisher should come out and play !!!, I´ll check that out, but I´m a little confused...

I´ve also made a new CD with driverpacks integrated, but fails to install due to an error in a .sys file, but I know it`s because of Windows 2000 limitation with text mode mass storage driver size (read about that here !! wink ) this night I´ll make one without mass storage text mode to see what happens, meanwhile I´m modifying my current image...

Thank you !!! Thanks for your time and your good advices !!

HA! I knew it !!! Now I can go to sleep without feeling dirty about not changing SID on deploy, for me thats priceless !!! thats why I say that you guys rock !!!!

1 day of this forum brainstorming about deployment and configuration approachs and 700 employees of microsoft should be fired !!! just for having twisted ideas.

Thank you sir ! SAD + M1 solved my geek puzzle here !! But I still have some questions to ask... please tell me if it`s ok to ask these here or should I ask over at MSFN.org ( those guys rocks too !!! )

Here are some:

Hate booting into safemode, should I start right away into normal mode after HAL change ? If you answer is to keep booting safe, please explain why

Can I make SAD run the driverpack finisher by itself, or should I keep pressing enter anyways

Thank you !!! Meanwhile I´ve downloaded DPBase and drivers packs, created two SAD folders, one with M1 and one with M2, these two are now on my pendrive and ready to go for some testing at my work big_smile

Thank you !!!!

PS: I created the image with one admin user, after deploy, test, backup copying, THEN it joins our domain, Thanks again, I think that reading some more KBs will help me to clarify this issue.

Regards

Julio

OMG S.A.D. FTW !!! I´ve stumbled upon a post that says that I can make a CD with drivers with S.A.D. and run a batch file to update drivers on a machine !!! that means that I can make a DIRECTORY ( F**K folders tongue ) with all drivers inside, put a batch file to auto-start on first boot and this batch can automagically erase all drivers when finished ??? IF that is true, you guys rock !!! ELSE you rock anyways !!!!

--<edit>--
original Title "Noob in need of some advice here please !!!"

Mass storage has too many drivers for win2k please add some disable tags!

--<edit>--


First of all, please apologize my english, my personal regional settings are from Argentina :P

Se here we go !

I work on a health center, currently with 537 computers and printers, so I started to work on something to deploy windows fast...

Here is what I do:

Install Windows 2000 on VirtualBox, add basic aplications, apply all updates.

Use the reg entries from the KB that describes the issue about STOP 0x0000007B while moving a hard drive from one computer to another.

Use the info from KB that describes changing UP HAL to MP HAL on Windows 2000 to get the list of HALs and the BOOT.INI entries needed

Set BOOT.INI to choose from 3 different HALs and kernels and ALWAYS start in Safemode

Use Acronis True Image to image the disk into another virtual disk, use Winmount v3 to mount the virtual hard disk and then copy the image to the Host machine.

Whenever I see a PC fooling around my desk I deploy that image on it if I haven´t done it yet.

So, I remember myself cooking CDs of Windows XP with bashrath´s driverpacks to deploy on notebooks 2 years ago, but I don´t know how can I add driverpacks properly into mi image:

1) There is any trouble (read pros and cons ) about leaving 1Gb of drivers in every PC ???

2) What about KTD and SAD ??? ( Sorry, I stopped using driverpacks like 2 years ago )

3) It is ok to leave all driverpacks in a folder and change registry driver-search path pointing at it ???

4) How can I tell Windows 2000 to search subfolders anyway ???

5) Hate booting into safemode, should I start right away into normal mode after HAL change ???

6) My boss keeps scaring the S**T outta me talking about SID issues with clones in a domain, and I keep telling him to stop whining, for the SID used in domains is not the local SID but the one in the domain controller, wich one of us is right ???

Thanks for the patience, to anyone, sorry !!!!!

PS:  I wish that one day we can deploy Win 7, but it seems like I have to wait 8 years or more...