<div>
what if you use pstools to install the vnc server ?
</div>


<div>
You may be blocked by the Windows Firewall, try disabling it with the command below;<br />
<br />
psexec \\&lt;hostname or IP&gt; netsh firewall set opmode disable
</div>


<div>
how would I install the ultraVNC remotely?<br />
<br />
I tried remote desktop after disabling the FW with psexec and it's just a black screen. &nbsp;Could lack of memory be the culprit here?
</div>


<div>
try to log in blindly, while in the black screen, pres ctrl+Alt+Ins, then type the username, press tab, then the password, then press enter. see if it logs you in.<br />
<br />
also check the link below, should help you fix the black screen issue.<br />
<a href="https://support.microsoft.com/en-us/kb/906510" rel="ugc nofollow">https://support.microsoft.com/en-us/kb/906510</a>
</div>


<div>
you would have to review the ultravnc documentation for install. i have seen low memory prevent me frm remoting into a server before so i would recommend a restart to see if the issue persists. if it is still a problem on next boot then i wouldnt think it is memory.
</div>


<div>
theres no access using either rdp, direct terminal only with no access to the box. &nbsp;I'm guessing it would need to be through a script ? &nbsp;i do have remote registry and domain credentials working on it, file access file and print but cannot install anything using normal methods.
</div>


<div>
i'm unable to use control, alt delete to logon. &nbsp;the screen appears and there's no way to input any remote inputs. &nbsp;Please advise?<br />
<br />
is there a way to kill services i'm not using safely to test ram usage?
</div>


<div>
At that stage you probably are hamstrung. GUI resources are exceeded, and you won't be able to use anything giving you a screen. If psExec works, great - you have a command prompt! If that doesn't suffice, you'll need to reboot, and take no prisoners.
</div>


<div>
I have rebooted and the same thing keeps happening. &nbsp;a lack of access to the box via rdp only. &nbsp;I'll try psexec today and see if that helps. &nbsp;<br />
<br />
Anything else you can advise me to try to gain control of the box? <br />
<br />
thanks in advance.
</div>


<div>
Then you seem to have some issues with the graphics appartment. Maybe driver issues. Safe mode should make a difference locally if I'm correct, but that does not really help ...
</div>


<div>
dcdiag should work fine with a remote cmd.exe using psExec.
</div>


<div>
this is not working so no remote access to cmd through &nbsp;psexec. &nbsp;it seems like every remote process is hung. &nbsp;it responds to remote registry, pslist and others but nothing memory intensive. &nbsp;any gui process doesn't work like rdp, vnc and but print server and ad with fmos so. &nbsp;?
</div>


<div>
Check the virtual memory (pagefile) size, e.g. with<br />

<pre><code class="code-1 nolinks" id="code-20-41396563-1"><span>wmic /node:TheRemoteServer pagefile list /format:list</span>
</code></pre>
If it is too small, create or change the pagefile with something similar to:<br />

<pre><code class="code-1 nolinks" id="code-20-41396563-2"><span>wmic pagefileset create name=&quot;C:\pagefile.sys&quot;</span>
<span>wmic pagefileset where name=&quot;C:\\pagefile.sys&quot; set InitialSize=2048,MaximumSize=2048</span>
</code></pre>
</div>


<div>
page file:<br />
<br />
AllocatedBaseSize=2046<br />
CurrentUsage=60<br />
Description=C:\pagefile.sy<wbr />s<br />
InstallDate=20050810191954<wbr />.680000-24<wbr />0<br />
Name=C:\pagefile.sys<br />
PeakUsage=69<br />
Status=<br />
TempPageFile=<br />
<br />
do I need to run 1 and 2 from above ?
</div>


<div>
Excellent work. &nbsp;that really saved me the pdc.
</div>


<div>
What exactly helped? The accepted answer is no solution, just a confirmation.
</div>


<div>
<div class="content wysiwyg-content">
Just inherited a 2003 server with only 2GB of memory which i cannot log on to but is &quot;online&quot;.<br />
<br />
Its acting as a dc, holds fmos, &nbsp;print server and dns server. &nbsp;<br />
<br />
I need to be able to rdp, install vnc or other software to gain access to the machine. &nbsp;I've tried using pstools, set rdp through remote registry, with no success.<br />
<br />
Once online I need to be able to then fix replication with dns using dcdiag support tools.<br />
<br />
please help!<br />
<br />
metalfubar
</div>
</div>


Just inherited a 2003 server with only 2GB of memory which i cannot log on to but is "online".

Its acting as a dc, holds fmos,  print server and dns server.  

I need to be able to rdp, install vnc or other software to gain access to the machine.  I've tried using pstools, set rdp through remote registry, with no success.

Once online I need to be able to then fix replication with dns using dcdiag support tools.

please help!

metalfubar

Remote access to windows 2003 server needed asap!

Windows Server 2003 was based on Windows XP and was released in four editions: Web, Standard, Enterprise and Datacenter. It also had derivative versions for clusters, storage and Microsoft’s Small Business Server. Important upgrades included integrating Internet Information Services (IIS), improvements to Active Directory (AD) and Group Policy (GP), and the migration to Automated System Recovery (ASR).

Windows Server 2003

Remote access may refer to the connection to a data-processing system from a remote location, for example through a virtual private network remote desktop software, terminal emulation, or the activation of features of a business telephone system from outside the business's premises.

Remote Access

The Microsoft Legacy Operating System topic includes legacy versions of Microsoft operating systems prior to Windows 2000: All versions of MS-DOS and other versions developed for specific manufacturers and Windows 3/3.1, Windows 95 and Windows 98, plus any other Windows-related versions, and Windows Mobile.