allen2

If they don't have the ntfs right to write/modify in this folder, they won't be able to rename a file.

You should create a partition image of your xp before messing with it. You might need to use this tool => http://www.911cd.net/forums//index.php?showtopic=22523 to change to sata ahci drivers.

I found a problem when using lastest printmig version from Microsoft: it doesn't handle drivers containing .cab files as stated by MS => http://blogs.technet.com/askperf/archive/2008/10/17/why-printmig-3-1-is-retired.aspx I had to sync print servers monthly and they had print drivers like HP P2015 (which contains cab file) so i looked into it. I found that MS excluded cab files in printmig there (see png there: http://img408.imageshack.us/img408/7798/printmig.png ) So one could replace one or more character there to avoid this problem although it is against the EULA.

Hi, I'm looking for a tool to take ownership a registry key. I tried setacl, subinacl and regacl and none of them can do it (at least i didn't found how). The targeted reg key was set by a virus and it set only the full control for the system. I would like to remove this reg key with a script but the administrator don't have the rights on it. Also i can do it without taking ownership with regedit but it would take a long time to do it this way.

I use dumpsec (from systemtools) to get the security rights. Then i'll dump the groups content with dsget or net group or net localgroup depending on your AD and your groups.

With dcpromo but you'll need to do a AD schema update.

I don't think this can work easily: - replacing a 2k .dll with an XP .dll shouldn't work as the dll is dynamically linked. It is almost sure that update.sys is linked against other dll and those would be needed also...... - sfc doesn't allow the chenge of only a few dll like this. You'll need to disable it.

Perhaps an ip mask is wrong.

I would also backup the data and try to check it with the testing software from the drive maker (seagate/western digital/hitachi/samsung each of them have a tool to check the physical integrity of the drive.). Also did you removed the partition and recreated it when you reinstalled ?

Ok that was also the only thing i could came up with but i didn't want something like this because it's for a server in a multi-user environment and the application is very sensitive (it is processing order from clients). I guess we'll need to buy an iscsi or san solution.

Does someone know how to use a shared folder as a local drive (not a network drive) for a specific application like iscsi would do ?

Did you tried to check your ram with memtest86 ?

You could also boot with a cd or floppy disk with ntfs read access and save %windir%\system32\config folder. It contains the registry.

When your install Vista or XP, the install process rewrite the MBR with its code without trying to modify the existing parameters. One thing to do would to try using the Bios Boot Selection menu (if your bios have it) to choose from which disk you want to boot. This way vista or xp would have a MBR on each disk. Another way to do it would be disable or unplug a drive when installing the second OS. I suggest you install first XP Pro 64 bit on first drive then unplug or disable it and then install vista rc2 on the second drive. This way it should be ok. Another solution would be to use vista bcdedit : http://g.msn.com/9SE/1?http://download.mic...CS=AWP&SR=4

Jondercik told you the solution. You can do it with a domain group policy using the restricted groups.

I found out that Dumpel got many bugs so i use systemtools dumpevt which is much more customisable to export eventlogs in a lot of ways.

Assigning password policy to the DCs should affect all AD users.

If your XP cd doesn't contain SP2, you'll need to make one slipstreamed XP SP2 CD.

First: Do you disconnect the DSL connexion before hibernate ? If no, check your routes (with "route print" from dos), after being reconnected. The old route might be still here. If yes, try disabling and disabling after a few seconds the network interface. Second: Most of the time, when going to hibernate, programs won't be able to access network again if you at least don't reload them. Also networking and hibernating doesn't work well usually.

Also i don't think the system user will have acces to \\server\share$\task\. So it'll never run. You have to use either an account with ntfs and share rights on \\server\share$\task\ or copy the files needed on each computer.

Why not simply use: "%userprofile%\local settings" ?

Perhaps setres.exe will work. I am not sure if it support wide resolution.

If you relabel your drive D:, then your subst drive will be also inherit this new label. That's the only way.

If the cpu or the new motherboard chipset are differents (for example cpu: amd to intel chipset: nvidia to sis) from the old ones then XP should not boot, if you don't make a sysprep before. You'll also need to activate again XP if you are not using a corporate XP.

There is also dsquery/dsget which will run from dos but if i remenber well it doesn't work from XP only from 2003.