nmX.Memnoch

There's a utility called NETUSER.EXE that will allow you to rename accounts. Once you find it simply add the following somewhere in your install scripts: netuser Administrator /name:<new_admin_account_name> Edit: Found where I'd downloaded it from before: http://www.jsifaq.com/SUBB/tip0500/rh0570.htm

Especially when the card is HIGHLY overclocked. From the article:

That won't work...at least not in SLI mode. The release 80 drivers allow you to have the same GPU but from different card manufacturers for SLI. Before if you wanted SLI you had to get, for example, two BFG 6600GT based cards. But with the Release 80 drivers you'll be able to do like a BFG 6600GT based card and an Asus 6600GT based card. It doesn't allow you to mix GPUs, just manufacturers.

That's odd...the same exact code worked perfectly when I tested it.Try the attachment. Just extract to an empty folder. KIX32.EXE will also need to be in either the same folder or somewhere in your path (i.e. in %WINDIR%). Run wkid.cmd to execute the script. wkid.zip

No problem. Glad to help.

Sure thing.

The utility for reading NTFS in Windows 98 can be found here: http://www.sysinternals.com/Utilities/NtfsWindows98.html But as was mentioned, you'll only get read access to those partitions.

Sabrent makes a nice adapter that you can attach any IDE drive to (3.5", 2.5" with included adapter, CD/DVD, etc). http://www.sabrent.com/products/specs/SBT-UI235.htm That can be found for less than $20. They're handy to have around. You'll still need a boot disk and some sort of imaging software though. There is a Ghost plugin for BartPE. Just put the plugin in, boot the system from a BartPE CD and run Ghost...that's just about the easiest solution.

Nope. No such permissions. They use a tool called Active Directory Resource Assistance from NetIQ to granularize the permissions. We can't even add our own user or computer accounts. We can manage/delete existing accounts...but not create them.

This is a feature that I WISH I could use. I work on an Air Force installation and they don't give unit FSA's (Functional Systems Administrators) domain admin privs...and we don't get access to edit or own OU GPO's either. We're lucky to even be able to unlock our users' accounts at this point. For this reason I sometimes forget about other settings available for use via GPO. We do have full admin privs on the servers/workstations we're responsible for though. What I did was used gpedit.msc on one workstation to configure the settings I want...and then copy the .pol files (along with the gpt.ini) during unattended setup. Works like a charm and we automatically get added to the local admin group when the machine is joined to the domain.

Ok...try this. It's been tested and you can run it from your workstation instead of on each workstation. I used part of Yzöwl's CMD script. Grab KiX from www.kixtart.org. There is no install...just drop KIX32.EXE in an empty folder with the .kix script. You can either run it from the command line or via a CMD file...either way the syntax to run it is simply: KIX32.EXE <scriptname.kix> ; Allow script to be exited. Set to 'On' for testing and 'Off' for production ; 'Break Off' will automatically log the user off if they force ; the script to exit while it's running Break On If Exist("_PCNAMES.TXT") ? "Deleting old _PCNAMES.TXT file" Del "_PCNAMES.TXT" EndIf If Exist("_OUTPUT.CSV") ? "Deleting old _OUTPUT.CSV file" Del "_OUTPUT.CSV" EndIf ? "Querying for computer names" Shell '%COMSPEC% /C NET VIEW |FIND "\\" > _PCNAMES.TXT' ? "Reading values and creating new _OUTPUT.CSV" If Open(1,"_PCNAMES.TXT",2) = 0 $LINE = ReadLine(1) While @ERROR = 0 $WK = Trim(Left($LINE,20)) $Val = ReadValue("$WK\HKLM\SOFTWARE\InterNetworX Systems\ICS\Configuration","Workstation ID") If Open(2,"_OUTPUT.CSV",5) = 0 $X = WriteLine(2,"$WK,$Val@CRLF") $X = Close(2) EndIf $LINE = ReadLine(1) Loop Else ? "File not opened." EndIf

You can change that in the registry at the following key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion Just change the RegisteredOwner and RegisteredOrganization values.

There's no install, but the KIX32.EXE executable does need to be available. The executable doesn't have to be on the local machine, it could be on a network share. Using GPO you can set a CMD file as a startup script that has this command in it: \\<server name>\<share name>\KIX32.EXE \\<server name>\<share name>\wkid.kix You could also use the WKIX32 version and hide it with a /i switch: \\<server name>\<share name>\WKIX32.EXE /i \\<server name>\<share name>\wkid.kix

I have something similar to the following in a CMD file that runs as a startup script for all of my workstations. :: Add Domain Users to Local Administrators Group NET LOCALGROUP Administrators DOMAIN\user1 /ADD NET LOCALGROUP Administrators DOMAIN\user2 /ADD :: Add Domain Groups to Local Administrators Group NET LOCALGROUP Administrators DOMAIN\group1 /ADD NET LOCALGROUP Administrators DOMAIN\group2 /ADD This will automatically add them. It'll also automatically add them back should they get accidentally removed from the group.

The default printer settings for a user are stored in the Device value in the key HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Windows What scripting language are you using for your logon scripts? KiXtart has built in functions for managing printers.

The first thing to do is check the Settings tab of the Display Properties. If both monitors are still showing, click the image/number for the one that isn't currently attached. Make sure the Extend my Windows desktop onto this monitor option isn't checked (it will be checked and greyed out for the primary monitor). That should do it. If the 2nd monitor isn't there then try these steps: - Right click the application on the task bar - Choose Move - Press the right arrow key on your keyboard - Move the mouse around until you start to see the edges of the application appear on your screen Do not press any buttons on your mouse or keys on your keyboard while you're moving the mouse around. If you do, you'll have to start back at the first step.

Here is a KiX script that you could run on each machine at user logon. This will automatically update the file, but only if the workstation's information isn't already in the file. Be warned that if two users logon at the same time the first one that gets the file open will be the only one updated. However, since the other workstation's data isn't written it'll be written the next time someone logs onto that workstation. The script can probably be modified to delete any entries older than a set amount of time so that a workstation's information remains relatively current. I used to use something similar to this for gathering information on our PCs at user logon. For example, workstation name, who was logging on, what date/time they logged on, IP address, Windows version, Service Pack level, etc, etc. EDIT: I guess I could've also mentioned that KiXtart can also read from/write to native Excel and Access files. I'm pretty sure it'll even read from/write to a SQL database. ; Allow script to be exited. Set to 'On' for testing and 'Off' for production ; 'Break Off' will automatically log the user off if they force ; the script to exit while it's running Break On ; Common variables ; Edit '<server name' and 'share name' ; Users will need modify access to the share $FILE = "\\<server name\<share name\wkid.csv" $KEY = "HKLM\SOFTWARE\InterNetworX Systems\ICS\Configuration" ; Check for the existence of the InterNetworX Systems key ; If it exists, read the value of 'Workstation ID' ; If it doesn't exists, exit script If KeyExist("$KEY") = 1 $ID = ReadValue("$KEY","ReinstallMode") Else GoTo End EndIf ; Open the file for read to see if this workstation has already been checked ; If this workstation has already been included in the file, the script will exit If Open(1,$FILE,4) = 0 $LINE = ReadLine(1) While @Error = 0 If InStr($line,@WKSTA) $X = Close(1) GoTo end EndIf $LINE = ReadLine(1) Loop EndIf ; Write the data to the file if not previously written $X = WriteLine(1,"@WKSTA,@DATE,@TIME,$ID") ; Close the file $X = Close(1) :end Exit

These machines are in a domain...correct? Are you running any sort of logon scripts?

Those are two words that don't go together when it comes to hardware.

Be sure to add the following command to your CMDLINES.TXT (either before or after the .reg file import...doesn't matter) NET STOP "System Restore Service" That will stop the service. Just disabling the service will leave it running until the next reboot or until it's been manually stopped either in the Services MMC or with the command above.

One main difference is that Windows 2000 Unattended cannot use long file names for files in the $OEM$ structure like Windows XP Unattended can. That's the only major difference I can recall...other than the way the SP's and HF's are slipstreamed.

http://www.nvidia.com/object/win9x_77.72.html That should include drivers for all of the GF FX and GF6 series.

I did some more reading today on the Raptors (was looking up some info on another drive). Apparently there's more of a difference between the 36GB and 74GB models than just the sizes. From what I read WD actually included TCQ on the 74GB version.

You should definitely "cheap out" somewhere else and get the right motherboard the first time. For instance, get a little less RAM and add more later...that's a WHOLE LOT easier than replacing the motherboard later.

Taking that point of view (which I completely agree with) the Exchange server should be on it's own server as well. You could do it this way: --Domain Controller / Exchange Server (recommend SBS2003) --POS Server --Game Server If budget is an issue then I would do two servers...one as a DC/Ex/POS server and the other as the Game Server. If you're basing the business on people coming in to play MP Games then the last thing you want is a laggy game server. As for the "less hardware involved"...definitely max out the game server as much as possible. You can start with a base for the DC/Ex/POS server and then upgrade as necessary. If there aren't that many employees accessing the DC/Ex/POS server then it won't need to be that powerful (i.e. a Hyperthreaded P4 system may serve the purpose just fine).