Noise

Awesome work, as usual, Xper. Minor Issue: I noticed clicking on the page link to goto the next section gave a 404 error, clicking the descriptive link for the next page worked. I realize this is a work in progress, just an FYI. Edit. I just realized this issue only shows up on Page 4.

Can you poke him or something? He's not on camera. Maybe make a USB poking stick so we can poke him online?

If you have the service disabled, then the status of the checkbox in drive properties does not matter. Indexing will still be disabled. If the fact that it remains checked, even though indexing is disabled, bothers you... it shouldn't

Use UniExtract to extract the drivers from the exe file.

The AMD Athlon 64 X2 6000+ is a relatively new CPU. You may need to upgrade the BIOS on your motherboard to support it.

I really like MSFN, it's been helpful over the last couple years. Enough kissing a**; we need an option to filter the nlite and vlite crap from these forums. I hate the nlite noobs. I hate every time I check these forums (which used to be helpful) all I see is someone posting about how, "I disabled dcom in XP, now I can't get my mail". "I've disabled svhost, now nothing works!" "I used n/v-lite to deploy 99 computers, now my policies don't work" God, it's tiresome. Bring MSFN back to the days when greenmachine and gosh used to post! F*ck nlite and its dirivitaves, nihu has ruined these forums for the experts.

If youre using Cisco switches make sure fastport is running.

It isnt easy to do. I've done it about 5 times for different companies, and there's always a glitch to overcome. If you're in the L.A. area you can contract me for the job, It would save you a ton of time, and I'll show you how it's administered and how to setup the clients. PM me if interested.

You need an OSX server, then you hook Open Directory to Active Directory, then you join your OSX Mac's to the Open Directory server. The trick is getting Kerberos on the OSX Server to connect correctly to the Active Directory. Kerberos on the Mac is a b***h to get working correctly.

Set it up as a policy. Research how to make ADM files. oops, sorry, must learn to read the whole post before responding.

You can do it tab stops.

diskpart, a commandline utility that comes with WinPE, can do it. It works really well too.

There is no built-in command line utility for determining a files version. And I don't know of any third party utility that does this. However, you might be able to get away with using the "find" command. echo *** Checking For Latest Version of SpyBot SET CHECKFILE=%ProgramFiles%\Spybot - Search & Destroy\spybot.exe IF EXIST "%CHECKFILE%" ( ECHO - File Found, Checking Version... FIND /I "1.4" "%CHECKFILE%" > NUL: IF ERRORLEVEL 0 ( ECHO - Version at 1.4 ) ELSE ( ECHO - Incorrect Version Found CALL UPDATESPYBOT.CMD ) ) ELSE ( ECHO - Spybot not found, Installing... CALL UPDATESPYBOT.CMD ) I just wrote this off the top of my head. It probably contains bugs, but you get the general idea. The trick is to use the "find" command and errorlevel checking.

This is great, but I don't know if this will work. Mass storage drivers are assigned by PNP Device ID's from what I understand. I think you'd have to modify the inf file to include the device id of your controller for this to work.

In DOS, off the top of my head I'd try: @ECHO. > LPT1: Then check errorlevel. But I don't remember of the ECHO command in DOS will return an errorlevel. You might have to use something like the type command (type autoexec.bat > LPT1:)

I don't think certified drivers for Vista allow video mirroring. It was something to do with DRM I think.

Nitro, Just wanted to thank you for a fantastic utility. Very nice work, I love this utility.

No, I don't think so. I do it by editing the registry during cmdlines.txt to disable the service. Windows Security Center was introduced with Service Pack 2 in XP. It came a little late in the game to be included in the winnt.sif. But I could be wrong, to tell the truth I havent really looked because the registry method works so well.

This is going to be an interesting thread. If any of you have been playing with the beta, I have a few questions. I assume autounattend.xml works like winnt.sif and unattend.txt? Do you create it and toss it in the i386 directory? Is there even a i386 directory? (Sorry, I've been avoiding Vista until necessary). Can you deploy Vista with a Unattended Installation CDROM? Will it even fit on a CDROM (700MB)? Probably not. What about a Unattended Installation DVD, will that work? Any clarifacation would be appriciated

Wow Weed. That is one nice utility! Way better than the SendToX Microsoft Powertoy. And I have been using SendToX since Windows 95. I'd never heard of this, thanks for the info

I'm sure Microsoft loves giving money away on "contests" like this one. It fits right in with their business model.

Crahak, You're right about the number of administrators using image based deployment. The reason isn't because it better, it's because it's easy. And yes, I know what I'm talking about. I've managed the deployment of literally tens of thousands of PC's. I've been administrating computers since 1990 for a fortune 100 company. I know corporate deployment. I've used ghost for deployment in the past. I don't hate the product, I hate the way it's used by inexperienced admins. And I've seen many many bad admins in charge of major operations. Always the same "fanboy" attitude towards Ghost. They never listen to my arguements and reasoning not use it. They don't want to hear it. They don't want to learn how to script. The ONLY way to properly use Ghost for deployment is to image the reference disk immediately after the text mode portion of setup, before the hardware detection begins. Indeed, this is the only way Microsoft will "officially" support ghosted PC's. (reference) And don't insult me saying HALS and SIDS arn't an issue, they are very much at issue. Sysprep like tools only reset SIDS they are programmed to know about. Many programs use SIDS and GUIDS. If these programs are pre-installed in the ghosted image, there will be problems. Usually weird, hard to qualify problems that people don't trace back to the ghosted installation. In addition, most people dont realize that shortcuts (.lnk) created on a ghosted PC will try to contact the original ghosted PC. (reference) And yes, this is an issue in XP, and not just for broken links. It results in unnecessary network traffic and slow-to-launch shortcuts. But I've argued these points ad nauseam here in these forums. I try to tell aspiring admins about the hazards of using ghost. Always someone comes and argues the point. Frankly, I'm tired of idiocy I see in most windows administrators.

First of all, get rid of ghost. Every noob administrator out there uses ghost to deploy windows. Any administrator worth their paycheck will do a scripted (unattend.txt/winnt.sif) installation. Unattended installations get rid of HAL and SID issues that are inherent in ghosted (image) based installations. In addition, unattended installations are much easier to keep updated (hotfixes slipstreamed, adobe reader updated, etc). My installations go as follows: Unpack PC; Configure CMOS; Insert floppy disk (yes - my PC's must have a $4 floppy drive) with customized winnt.sif; boot from build CDROM. - Wait 50 minutes - (get lunch, have a smoke, or do like I'm doing now and read msfn) When I get back the PC is ready for the user. I help them log in and restore any data the first time. Setup custom printers and network drives unique to them. Then, in a week - I yank their admin rights, 70% of the time, they never even realize it. That's it.

Thanks Mulder! How did you happen to find these? I've been searching for two hours!

Anyone got the full version download for KB919007 and KB920685 ??? the_guy is usually really good at finding these kinds of things