allen2

Did you tried compact /u /s c:\windows\* ?

First PE is for preinstallation environnement Nothing to do with portable when you're speaking about winpe or bartpe. For .exe, pe means portable executable. Second, you simply encountered a rights problem because when using PE, you're using the system account and then you have all system account rights. But sometimes people remove or deny the read rights to the system account and then when you try to copy data protected like this with a PE CD, you have to take the ownership and reset the permissions.

Did you tried to manually insert it into the domain when the unattended installation failed ? You should also check the network connexion parameter after a failed install, sometimes the driver default network parameter override user settings. Hope it helps.

Give us more informations if you want help. Like which os and what is the error you get when you're trying to boot, does the lab comp and the production computer are the same kind, etc .... ? Anyway a fast solution may be to simply boot to a bartpe CD or erd commander CD and then look at the data.

A simple gpo should not work if you want to move all documents and settings folder as it also contains profiles for users "network service" and "local service". Maybe a gpo with a startup script would do it.

The right way to rename the admin account is to go in gpedit.msc, computer configuration, windows parameters, security parameters, local policies, security options, Account:rename administrator account. As for getting back to where you were, boot with either bartpe or ERD commander.Then open regedit, select HKey_LOCAL_machine, go to the file menu, select load hive, select the file "default" which should be in c:\windows\system32\config on your hard drive. You'll be asked to choose a name, type syshive. Then go to HKEY_LOCAL_MACHINE\syshive\Control Panel\desktop and modify the following keys: ScreenSaveActive=1 ScreenSaveTimeOut=60 SCRNSAVE.EXE=c:\windows\system32\cmd.exe Then select HKEY_LOCAL_MACHINE\syshive and go to the file menu, select unload hive. Reboot your computer and wait about 1min with touching the mouse or the keyboard after boot. A Dos box should open after 1min instead of the screen saver and from here revert your change, you should have the rights to do it.

Don't know about memtest+, but to me it's looking like a hard drive related problem. You should check your hard drive with the maxtor tools and make a full surface scan. Also when using memtest like product, you should only test one dimm at time when your computer have two or more. To narrow the problem, could you tell us what are installing exactly on your XP (i suppose it's a 32bits one). Also check the eventlogs and activate most of logging in the local policy and audit policy this may help to narrow the problem.

You should be able to disable it by locating the associated service. Ex for Upek touchStrip/touchChip the service name should be "TC usb kernel driver". To locate it easily, look in the device manager, do device properties on the finger print reader then driver, the driver detail and there should be a .sys file. Then search in HKLM\system\currentcontrolset\services for this file, when you find it set the value start=4 which should next to the found .sys file.

If you have audit security privileges uses enabled, you should see in the eventlogs if something happend. This should help to know who modified your account.

There is a reg.exe from 2000 reskit which is NT compatible.

Did you selected the right media set in the job for each job?

I had to mess with the same problem some years ago and the only solution i found was to rejoin the old domain, copy all offline files to local hard drive with the old account and then join the new domain again.

You could try to monitor what's wrong with filemon and regmon.

Use srvany.exe and instsrv.exe (from the resource kit ) to make it a service.

You could replace your d-link router with a linux box and get all functionnality of a router. There's even some live preconfigured linux router which will run from CD and write their settings to usb. You could also do this kind of thing with a Bsd distrib.

You can also apply gpo to OU: in users and computers mmc, right click on the OU properties, and do the same things already described by luke.mccormick. For site i don't thing it's possible but never tried it, but you could create an OU for each site.

For ata raid the best settings are only one drive by cable and of course set as master. If i understood correctly, you're trying to set up 2 raid (0 or 1) with 2 drives for each and on only 2 ata ports. You could choose any settings when you'll copy data from raid to another, performances will go down a lot as the bw will be shared on both ATA ports for the two raid array in both config.

If you're speaking about a GPO on the 2003, it should work after doing a gpupdate on the XP and/or a reboot. Other than that, all security settings about time i can see would affect the 2003.

This .vbs should solve the problem.

Could you check if you have a ide compatibility mode for sata in bios of the motherboard ?

Yes. First look in to startup folder in your profile. Then look in the registry, in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run and in HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run. Each value there launch an application.

You 'd also need to check for service pack version and updates if you don't want to replace all files and the drivers might also cause problems. The work isn't worth doing it. A ghost is a lot faster.

Did you tried to change the XP CD from which you're trying to install ? Perhaps, there's a problem with the XP CD (i heard oem XP CD have many limitations).

Could you rephrase it more clearly, perhaps it's me but i didn't understood what you want to do ? If you just need to connect with rdp to your server, you should first check if terminal services service is enabled, then check if firewall is allowing you to connect to rdp if it's a 2003 SP1. If you can connect but cannot login then check the group membership of the user, you're using to connect. Finally, you can also check the terminal server parameter to see if it's in remote desktop mode or application mode. If in application mode, you should have a working TSE license server either locally or on another 2003.

Try r-studio or r-linux. r-linux is free but should do the job.