Re: Help : Sr. Developer (IT Newbie) removes logon process from startu

From: Steven L Umbach (n9rou_at_nospam-comcast.net)
Date: 03/19/05


Date: Fri, 18 Mar 2005 23:46:26 -0600

If you can connect to it from another computer via Computer Management -
other computer look in Event Viewer to see if you can find ant error
messages to see what the problem may be. Since you do have access to the
command prompt use the command net start to see what services are running.
He may have disabled a necessary service. You can compare the results to
another like configured computer to see what services that are not started.
Another possibility is to use secedit to reset the computers security
settings back to default defined settings as per the link below. You can
append the /areas command if you want to reset only certain parts of
security settings such as services. The free tool psexec from SysInternals
can also be used to manage a remote computers command prompt in most cases
if smb connectivity exists between the computers. An in place upgrade of the
operating system may be another option though there is no guarantee if will
fix your problem and if you do it you will need to first install your
service pack and then all critical updates after the upgrade install. ---
Steve

http://support.microsoft.com/default.aspx?scid=kb;EN-US;313222
http://www.sysinternals.com/ntw2k/freeware/psexec.shtml --- Psexec
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q292175 -- in place
upgrade of W2K. Should be very similar procedure for Windows 2003

"shawnk" <shawnk@discussions.microsoft.com> wrote in message
news:CCD896D4-0315-46E6-A56A-1760DBDD52E5@microsoft.com...
> In an attempt to fix a problem one of our Sr. Developer's used a startup
> manager application on Win 2003 server to temporarily remove some
> applications from the start up process.
>
> Unfortunately it appears they also disabled the logon process for the
> server.
>
> The result is that when you logon to the system (at the machine) you get
> in
> and then the system logs you right out again.
>
> No remote terminal services are enabled.
>
> The only way we can 'get back in' is using the Win 2003 Server CD in a
> very
> limited diagnostic mode (Dos prompt).
>
> Is there an easy way to enable the Remote Desktop service manually or by
> command line?
>
> We have to use a console 'dos' prompt to work from.
>
> Thanks for any help.
>



Relevant Pages

  • Release : ComLog 1.0, a WIN32 command prompt logger
    ... a WIN32 command prompt logger ... DOS sessions on Windows NT/2K (should also work on XP, ... This tool can be used by administrator to keep a history of commands ... typed in the DOS command prompt and the associated output, ...
    (Focus-IDS)
  • [Full-Disclosure] Release : ComLog 1.0, a WIN32 command prompt logger
    ... a WIN32 command prompt logger ... DOS sessions on Windows NT/2K (should also work on XP, ... This tool can be used by administrator to keep a history of commands ... typed in the DOS command prompt and the associated output, ...
    (Full-Disclosure)
  • Re: Windows could not start because the following file is missing or corrupt: System32DriversNtfs.sy
    ... the recovery disk are no longer available. ... Alt and D keys at the same time to go to a command prompt. ... Once the floppy disc is ready, change the boot device priority by: ...
    (microsoft.public.windowsxp.general)
  • Re: Attn. Microsoft - BUG REPORT!
    ... if you are upgrading a Win98se system to Windows ... then the Windows XP upgrade ... > application will halt early in the installation process. ... > It's NOT because it was run from the command line (though ...
    (microsoft.public.windowsxp.general)
  • RE: Unattended Install Dilemma
    ... I am putting into the command line for winnt. ... the bat file is the same, ... file doesnt give the Product Key error. ... >you only need an upgrade key if you are using upgrade ...
    (microsoft.public.windowsxp.setup_deployment)

Quantcast