troubleshooting Question

Can't get access to Win 2k recovery console due to admin password with extended characters.

Avatar of Mindstream
Mindstream asked on
Windows 2000
12 Comments1 Solution154 ViewsLast Modified:
I have a client with a windows 2000 server (domain server).  After installing the Windows 2000 rollup 1 for SP4 update, I get stop errors (related to ntoskrnl.exe 0x0000001e (oxc0000005, 0x804a1a51,0x00000000,0x000000b0)) on every attempt to boot windows (safe mode, regular etc etc).  This is not the primary problem/  

I found a solution (I think) to this problem, ( http://board.iexbeta.com/index.php?s=97f25c1babe85a9b694a1c869c6f5f92&showtopic=56004&st=15 ) but to implement it, I have to use the recovery console.  

The problem is that the client has a password that has a "$" and a"#" in it.  According to Microsoft, recovery console won't recognize extended characters (kb304099).  The solution they have to this problem is to change the password (kb293904), but if I can't get access to win2k, I can't do that.  To complicate matters just a little more, the system is using an adaptec raid (AAA-131u2).  I have tried a few of the linux based password changing boot cds, but none of them seem to recognize the raid.  I'm stumped, and would really rather not reinstall win2k server as this client has a rather complex setup.  ANy ideas out there?

Thanks!

Darren
Join the community to see this answer!
Join our exclusive community to see this answer & millions of others.
Unlock 1 Answer and 12 Comments.
Join the Community
Learn from the best

Network and collaborate with thousands of CTOs, CISOs, and IT Pros rooting for you and your success.

Andrew Hancock - VMware vExpert
See if this solution works for you by signing up for a 7 day free trial.
Unlock 1 Answer and 12 Comments.
Try for 7 days

”The time we save is the biggest benefit of E-E to our team. What could take multiple guys 2 hours or more each to find is accessed in around 15 minutes on Experts Exchange.

-Mike Kapnisakis, Warner Bros