If you have admin rights on the remote machine then it's possible.
You need to edit the boot.ini file (usually found on the root of the C: drive)
Open a command prompt on your local machine
type:
EDIT \\MACHINENAME\C$\BOOT.INI
The boot ini file will open which usually looks something like this:
[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional"
/noexecute=optin /fastdetect
On the end of the last line you need to add
/safeboot:network
the last line will then read something like
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional"
/noexecute=optin /fastdetect /safeboot:network
Save the changes and then force a reboot from the command line and it should restart into safe mode with networking. Remember to change the boot.ini file back when you're done!
Okay.. had some coffee and thinking a little straighter. Deleting previous responses and providing better info:
The original release of the update from KB2667402 causes this issue. It notes in the known issues that applying SP1 after the update causes RDP issues.
The patch was re-released to address and correct the RDP issue.
So, you should be able to start the server up normally and remotely uninstall the original version of the patch via WMI
wmic /node:<SERVER> /user:<USER> process call create "powershell wusa /uninstall /kb:2667402 /quiet /forcerestart"
After uninstalling the KB and the subsequent forced restart, you should be able to RDP to the server again. At that point, you should be able to install the updated version of the same KB
Footnote: This did solve the problem but it wasn't necessary for me to use WMI remotely. I was able to boot into safe mode using the virtual KVM and use the WUSA command line directly to uninstall KB2667402. All was then working after a reboot. This allowed me to sidestep all the firewall and permissions issues associated with letting a remote user access WMI.
Best Answer
Without knowing your specific guest OS setup, I can't get tell you for certain or give you an exact step by step, but if you want to change how Windows boots, you want BCDEdit.
You can find an intro guide here: http://msdn.microsoft.com/en-us/library/windows/hardware/ff547251(v=vs.85).aspx
More specific boot options for later versions of Windows (Including Server 2012 and 2008): http://msdn.microsoft.com/en-us/library/windows/hardware/ff542273(v=vs.85).aspx