Cannot remote login to windows server 2003

This has been successfully tested in our internal test environment and also with production server from a customer. It is important to note that:. This entry from Microsoft KB is also available. However, the "Phone" reactivation method didn't work as we were expecting. The concept is the same, however, this solution implies the reactivation of the licensing server after deletion of the keys.

Also this link shows the steps to follow in order to go around this issue on a Windows Server R2. Technical Support - PPR. Search Community and Knowledge Base.

Sign in to ask the community. Home Technical Support Why should I register? Bar Code Scanners. System Article Number. Last Modified Date. Applies To. In order to solve this problem, follow these steps: Note: This solution contains steps that tell you how to modify the server registry. Make sure that all Windows updates and service packs have been successfully applied to the server. Log into the server as an Administrator.

From the pop-up menu, click on "Properties". Does anyone have any insight or solution? I would rather not burn an incident with MS. Thank's in advance, Adam Murphy. Share Flag. All Answers. Collapse -. SID problems? I forgot about changing the Sids. I can solved with this. Reponse To Answer. Zombie Alert!!! Back to Networks Forum. Start or search. Start New Discussion. Create a new discussion If you're asking for technical help, please be sure to include all your system info, including operating system, model number, and any other specifics related to the problem.

Track this discussion and email me when there are updates. Reset Post Submit Post. Since i only have RDC 5. I have an application that needs to start from the console session. Once started all users can utilize it much like any service. Do you know of any tools that would allow me to have that start as a service on boot up? Reply to Ron Ron you can use srvany to launch an application as a service. I do this on my server alot to launch standard exe's.

There's workarounds by logging into other servers and connecting to the target server and logging someone off, but that's not an option for small companies with 1 server. This is because of the design enhancements in Windows Vista and Windows Server , by virtue of which you cannot connect to Session 0, which is the default session. Running services and user applications together in Session 0 poses a security risk because services in Session 0 run at elevated privileges and therefore can be targeted by malware that attack by attempting and exploiting a privilege escalation.

The new generation of the Windows operating system mitigates this security risk by isolating services in Session 0 and making Session 0 non-interactive to the user.

The first user logs on to Session 1. Subsequent users log on to subsequent sessions Session 2, Session 3 etc. It has a checkbox option to connect to console. You can save all your desktops as one config file and move it between computers. The only problem I have is that I want to disable automatic printer installation and I don't know how. I have an number of developers who constantly don't connect to the console session and start to screw things up.

I second JamesM's question. No luck yet. Anyone know the way? To shadow another users session in RDP, open the terminal services manager, find out their session then open the command prompt and type shadow session. It can be simply by: 1.

Thanks so much.