Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Shaun E on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

HELP!!!!

Status
Not open for further replies.

rayzze

IS-IT--Management
Sep 17, 2002
64
US
I installed a Microsoft patch on my Metaframe XP FR2 SP2 server and it killed my drive remap. The system now boots to C: and the user interface woun't load (I cannot get on to the system even from a console...) I can remotely edit the registry but I cannot seem to get the system to go back to M: I have tried deleting the entries under HKLM\SYSTEM\Mounted Devices but this does not work they just reappear. Thanks in advance for you help,

 
hi, correct me if I wrong

- Installed W2K ( boot device was C )
- Activated TS
- Installed MFXP
( first step it rename C in M and inspect registry
and other and replaces all occurencies of C: with M:
- You have installed all programs with M: active

- You have installed that "killer" patch and your boot
disk is named C

Right ?

I belive that many things will not go !
Why not take MFXP CD and reuse the Letter Changer ?

good luck

 
The order of install is correct. That is the way it was installed. Unfortunately I cannot get on a console to run the remap utility and my backup of system state is looking for M: which is my entire problem.... When I attempt to log on to the console it just boots you back to the ctrl-alt-delete screen. I am attempting to figure out how to do this via the registry or maybe write a script to run driveremap on that box remotely...
 
I was using SUS to patch the server, it only does critical updates and did not up rev any service packs or IE versions. But it did a security rollup and many other patches. I tried to use the info in Microsoft Q223188 & Q249321, but no matter what I tried the server kept defaulting back to C: I called Microsoft and there explaination was that the system hive of the registry might have gotten corrupted and that every time the server was rebooted the system would use last known good settings...

The fix was to get the system up and running and fix the user environment using the setting is Q249321 then using the subst.exe utility to create and share a M: drive then restore system state and \winnt directories to return to the unpatched state.

Thanks all for the help,
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top