c4p0ne

Thanks, that's useful information and in fact, I've found 6 "update.exe" files on the disk but unfortunately they seem to be for R2's "extra components" which can be installed after the R2 installation has gone well. There doesn't seem to by any update.exe file in the root directory or root of the "R2" subdir. Funny I can't even seem to find stuff about slipstreaming R2 on MS's website! (!@*&%?). Well there is a slipstream.inf file in the root that looks like the following: <- start -> [Version] Signature = "$Windows NT$" DestinationPlatform = i386 LanguageType = %Locale% NtMajorVersionToUpdate = 5 NtMinorVersionToUpdate = 2 SKU = ia DriverVer=10/01/2002,5.2.3790.2075 [strings] Locale = 0x00000409 <- end -> I just can't figure this out and what kills me is that I'm sure the integration is something almost rediculously simple to do.

Whether or not that is true, it still does not answer my question. I have 1 W2K3SP1 Disc, and 1 R2 Disc. Obviously the R2 Disc is meant to be either installed directly, or slipstreamed. The R2 Disk is less then 140 Megabytes so again, it's obviously an upgrade. The only problem is that it's not like a "single file" service pack (like SP1 for W2K3). It has a root folder with files and subfolders and the documentation says nothing about slipstreaming even though it's clear by the directory structure that it can and was meant to be done. Its kind of frustrating but I'll keep digging.

I have a Volume License version of Windows Server 2003 with SP1 already integrated (I don't know if that was done with nlite). The question is, we have a VL version of the x86 R2. I know for a fact that it can be slipstreamed because there is a slipstream.inf in the root folder (of the R2 Disc) but the problem is, how can this be done with nlite? And what category would that go under in options? Service Packs? Hotfixes? Patches?

Here's some strange news... Did an install of XP Home (Streamed SP2) on a normal system. when the first logon prompt was displayed with the default "Administrator" field already filled in for "user name", Instead of logging in with that I just changed Administrator to "Owner" and pressed enter. Ok so far no problems, logged in just fine with "Owner" account. Now, while in the owner account I created another admin account (peon) and logged in as peon, then deleted "owner" thru the standard "user accounts" option in control panel. THEN, while under peon, I used that command-line tool (renuser.exe) to raname the default "Administrator" account to "sammy" It worked the account was apparently renamed... BUT, then when I logged off of the peon account and tried to log into the default admin account (now sammy) it gave me an error of "could not login due to a logon restriction". WTF could that be? Hmmmmmmmmmmmmm...

Nice, nice! Much appreciated dude.. So you're saying that I could just as well simply use "renuser.exe" after Windows is installed to rename the Administrator account? If so then that's excellent. I don't like the "default" name of "Administrator", that's why I wanted to change it to something inconspicuous like "mom" or some crap like that.. hehe, combine that with no null sessions, other security measures and "outsiders" will have a much more difficult time determining which is the right account to attack. =) Well, about the folder still being named Administrator, are you sure that's right because in XP Pro I've done it after the OS was installed and the folder was named properly. What I'm saying is that if one does NOT login to the main Admin account before renaming it, it should be ok right? Anyway thanks.

There don't seem to be any tools like in XP Pro that allow one to rename the Administrator Account. Is there ANY way to do this task from the command-line or thru some other means? Perhaps even during the installation process somehow? Remember this is crappy XP HOME we're talking about, not crappy XP Pro.

There don't seem to be any tools like in XP Pro that allow one to rename the Administrator Account. Is there ANY way to do this task from the command-line or thru some other means? Perhaps even during the installation process somehow? Remember this is crappy XP HOME we're talking about, not crappy XP Pro.