Hi
Anyone knows of an application running on PDA/Cellphone running symbian OS, that connects to windows Remote Desktop?
Thanks
Itamar
Discussion on:
View:
Show:
I have a nokia device that uses symbian. Nokia does not make this device anymore but I believe the upgrade model the new Nokia 9500 should be the same
does this only work when connecting to server 03? or 2000 as well?
what admin tasks can you not do in virtual mode vs console mode? i have been using remote desktop for years to manage my 2000/2003 servers and rarely have i seen a need to go directly to the console.
is there any option in RD that will open it in console mode by default or do you always have to use the run cmd with /console switch?
what admin tasks can you not do in virtual mode vs console mode? i have been using remote desktop for years to manage my 2000/2003 servers and rarely have i seen a need to go directly to the console.
is there any option in RD that will open it in console mode by default or do you always have to use the run cmd with /console switch?
There are applications that run on servers that can't be seen in virtual mode. For example, if you are running Domino mail servers or just about anything that runs in that stack, it can't be seen or administered too unless you are directly on the box or in console mode via RDP.
Sure the ?mstsc /console? method does work, but there are a couple easier ways. Microsoft planned ahead for the typical IT person that enjoys shortcuts (or they think we can?t spell) because if you use ?mstsc /con?, ?mstsc /cons?, ?mstsc /conso?, etc RDP knows you want to use the consol. This method works on RDP 5.1 and above.
The other method involves the GUI in version 6.0. When you enter the server to connect to, put /console at the end (ex: server /console). As a note, in the GUI you have to use /console because /con and such does not work. I have tested RDP v5.1 and this method did not work.
Terminal Services Client 6.0 can be found in the Microsoft KB article 925876.
The other method involves the GUI in version 6.0. When you enter the server to connect to, put /console at the end (ex: server /console). As a note, in the GUI you have to use /console because /con and such does not work. I have tested RDP v5.1 and this method did not work.
Terminal Services Client 6.0 can be found in the Microsoft KB article 925876.
When I logged out of the session it also logged out the user on the server. How do you log out of the session so that it does not disturb the actual console?
To avoid logging out the console user just disconnect the RDP session (click the X, or go to Start -> Disconnect). Also, if you do log out the console user you can still log back into the server?s console remotely and it will lock the console?s screen.
I have noticed that when you login remotely using console mode and no console user is actually logged in, the virtual and console modes are mixed. For example, some system tray icons only appear when logged onto the console itself (Symantec AV), but when performing the initial login using console mode only the server only displays 1/2 of those icons. Plus, when you login using plain virtual mode more icons are missing. However, if you log into a console session that has already been logged onto from the console itself, all normal icons appear. It's weird, but I have seen it in many places (including XP).
I have noticed that when you login remotely using console mode and no console user is actually logged in, the virtual and console modes are mixed. For example, some system tray icons only appear when logged onto the console itself (Symantec AV), but when performing the initial login using console mode only the server only displays 1/2 of those icons. Plus, when you login using plain virtual mode more icons are missing. However, if you log into a console session that has already been logged onto from the console itself, all normal icons appear. It's weird, but I have seen it in many places (including XP).
Over seventeen years in IT and LAN Admin and I think I am losing it some days. I have setup many a VPN through a myriad of prior challenges and proprietory equipment...BUT one client I have with W2k3 SBE cannot connect to remotely [WAN side] even if when I expose it as a DMZ. I have even gone back to basics and exploring packets through 'ethereal' to determine the cause. Any ideas?
I've used RDP [vX.X] for years for simplicity and use with Terminal Server console operations. But does anyone know of a service or config setting that is prohibiting connectivity? Perhaps a GPO or something that I've missed?
Desparate!
I've used RDP [vX.X] for years for simplicity and use with Terminal Server console operations. But does anyone know of a service or config setting that is prohibiting connectivity? Perhaps a GPO or something that I've missed?
Desparate!
I would recommend logoff instead of just disconnecting from a remote session. Disconnect keeps the session count (limited to just two in Administration mode). When muliple people have logon priveliges this can become a problem. Also note that closing the window or letting it timeout is the same as disconnect. Please do not say that everyone knows the password and can reconnect, that is a whole nother security rant.
If you have a long task, it should be scheduled to run in the background (instead of tying up a console session) and email you upon completion. I define "long" as over 3 minutes.
Applications that require running in a window, instead of as a service, are consumer grade and should not be installed on a server.
If you have a long task, it should be scheduled to run in the background (instead of tying up a console session) and email you upon completion. I define "long" as over 3 minutes.
Applications that require running in a window, instead of as a service, are consumer grade and should not be installed on a server.
- Keyboard Shortcuts:
- Prev
- Next
- Toggle
