Heh. Great minds...
On Mon, Jun 1, 2009 at 15:48, Richard Stovall <[email protected]> wrote: > You could always blank the password with ntpasswd > (http://home.eunet.no/pnordahl/ntpasswd/), then use the windows recovery > console to disable whatever services/drivers you need to prevent from > starting. > > > > From: Daniel Rodriguez [mailto:[email protected]] > Sent: Monday, June 01, 2009 6:41 PM > To: NT System Admin Issues > Subject: Re: Windows 2003 Server Issue. > > > > I have tried Safe Mode, Safe Mode Command Prompt, Last Known Good Settings, > and selected the option to Not to reboot on System Error. > > > > I am at a total loss on how to recover from this. All I know is, the person > who had the admin rights tried to change the password and it not here and > there is now one here who remembers what that password was. I am thinking > that maybe there is a sevice that is/was tied to the Admin password. > > On Mon, Jun 1, 2009 at 6:35 PM, Jeff <[email protected]> wrote: > > how about last known good? > > > > On Mon, Jun 1, 2009 at 3:18 PM, Daniel Rodriguez <[email protected]> wrote: > > I have a Dell PowerEdge with Windows 2003 Standard Server. > > > > Someone with admin rights has done something to the server. > > > > Issue: When powering up the server, shows that it is loading, gets to the > grey screen with status messages. When it gets to 'Network Connections' > there is an error message stating that a service or drivers did not load and > to look at the Event View for more details. It then shows the login screen > for a split second and then Windows performs a shutdown. > > > > This happens when I try to go into Safe Mode, as well. > > > > Ideas? > > > > > > > > > > > > > > > > > > > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
