Remote Desktop scroll bar on Window snap to top of screen issue

I have an external monitor attached to my laptop and it has a screen resolution of 1920 x 1200. My laptop screen has a resolution of 1920 x 1080.
I create remote desktop connection files for connecting to a number of internal servers. When I create them , I set the display resolution to 1920 x 1080. This means that I can snap it to the top of my laptop screen and it will go full screen, or I can snap
it to my external monitor, and it will pseudo full screen (has no side borders, but has a window title), but will leave a small gap at the bottom so I can access my taskbar (which extends across multiple screens thanks to DisplayFusion)
However, recently instead of going into this pseudo full screen, it no opens at 1920x1080, but has vertical and horizontal scroll bars.
Running Windows 7 x64 Ultimate and the Remote desktop versions are Shell version 6.3.9600, Control version 6.3.9600, Remote Desktop Protocol 8.1 supported.
Does anyone know why this would have start doing this?
Thanks

Thanks for your reply Alex.
I'm not sure what you mean by configured the screen resolution of my 1920x1080 monitor? The resolution of both screens have been set : The one on my laptop is 1920x1080, and the external monitor is 1920x1200.
My remote desktop session resolution is set to 1920x1080, and if I drag it to my laptop monitor it makes it full screen, exactly as I want.
If I drag the remote desktop session to my external monitor, I would expect it to snap to the top of my screen, filling the width, but leaving some space at the bottom. This is how it used to behave, but recently, it has started to show scroll bars.
There are no remote desktop policies related to resolution settings.Karl

Similar Messages

Remote desktop connection manager on windows 8.1, can't connect to windows server 2012 R2, Socket closed

remote desktop connection manager on windows 8.1, can't connect to windows server 2012 R2, Socket closed each time i try to open remote connection to the server,
does remote desktop connection manager V2.2 not compatible with windows 8.1, and if so, is there are any other compatible versions
or what's the problem,
Mahmoud Sabry IT System Engineer

this issue maybe will be fix by latest version, we still waiting for it
maybe your issue can be fix using this methods
https://social.technet.microsoft.com/Forums/windowsserver/en-US/61f218a5-5ef8-49da-a035-90cdd64fc9a0/problem-with-remote-desktop-connection-manager-error-3334?forum=winserverTS
http://shawn.meunier.com/?p=1#comment-43

Remote Desktop Connection imac27" to Windows 7

Remote Desktop Connection imac27" to Windows 7
I have a two imac21" & imac 27" local network
imac21" working fine Remote Desktop connection (imac21" to Window 7/xp/2003r2) [OS-10.6.7 CPU-2.4Ghz core to Duo, HDD-150GB]
imac27" could not connect remote desktop connection following message appear (Remote Desktop 2.1.1)
The Mac cannot connect to the Windows-based computer.
This problem can occur if:
• The Windows-based computer is not set up to accept remote connections.
• The Windows-based computer is not turned on.
• The Mac, or the Windows-based computer is experiencing network problems.
Try connecting to the Windows-based computer again, or contact your administrator.
imac27"
OS-10.6.7
CPU-3.6 Ghz core to duo
Ram-4GB
HDD-1TB

I haven't tried it with Windows 7 but am having pretty good luck with a Windows XP Professional machine. What I did was just found the IP address to the Windows machine by:
Command Prompt, type ipconfig and locate the IP address.
Start RD, enter the IP address of the Windows machine, if the machine has a user name and password you have to enter that and then it works.
At least that's all I had to do. The key is knowing the IP Address and login and password of the Windows machine.

Scroll bar on the right is off the screen. How is this fixed?

In the 11.0.1 version of iTunes, when I go to full screen, the window is too big and the scroll bar on the right is off the screen. Can this be fixed, or do I have to wait for the next version?

Yep. For all us spreadsheet geeks, this is a real sinker. Anyway, here's my workaround. Not free, unfortunately. I have a macro program called QuicKeys installed on my Mac that I've used for countless years, and which I highly recommend for other reasons. Anyway, one of QuicKeys' many features is simulating a scroll wheel using the keyboard. I have it simulating a cell-by-cell scroll using cmd-arrow keys. The only drawback is that I have to release the cmd key each time I want to move another cell.

Remote desktop policy works on Windows 7, but not on Windows 8

Hey all,
We have a mixed environment of Windows 7 and Windows 8.1 machines.
Our standard policy enables remote desktop on all machines (and another part of the policy sets the groups allowed to remote access).
On windows 7, we are able to RDP to all machines
On windows 8.1, remote clients cannot connect, with a timeout error. This occurs from other Windows 7 or Windows 8 machines.
I have confirmed:
- The policy has applied (by looking in the registry under HKLM\software\policies\Microsoft\windowsNT\Terminal services)
- The windows firewall is letting the RDP traffic through (and the issue still occurs if the firewall is off)
- The group policy templates being used in the policy are Windows 8.1 and the GPO was created on a Windows 8.1 machine
- If I set the registry key HKLM\System\CurrentControlSet\Control\Terminal Server\fDenyTSConnections = 0, manually or via GP Prefs, it still does not work
- There are no visible errors in the application, system or security logs
- I have compared registry snapshots before and after the change below and cannot see any differences in the relevant keys
If I take the machine out of the OU and place it into a "noPolicy" OU, connections still do not work (after setting the regkey above) - however, if I use the GUI to turn off remote desktop then turn it back on, it works. I can then place the computer
back in the original OU (where policy is applied) and it still works.
All this leads me to believe that remote desktop is not being turned on "properly" (for want of a better term) by group policy and doing so via the GUI is doing something different/additional.
So...
- Has anyone seen this before ?
- Anyone know how to turn on some sort of trace logging for this ? I have been unable to find a setting for this as yet ?
Thanks.

Hi Ben,
Did this happen to all Windows 8.1 clients?
>>however, if I use the GUI to turn off remote desktop then turn it back on, it works. I can then place the computer back in the original OU (where policy is applied) and it still works.
Did we try restarting the machine to tackle the issue, for sometimes restarting can be helpful.
>>Anyone know how to turn on some sort of trace logging for this ?
I am not sure this is what we want for tracing this issue, but for tracing group policy processing, Gpsvc.log can be helpful.
Regarding how to collect Gpsvc.log, the following blog can be referred to for more information.
Userenvlog for Windows Vista/2008/Win7
http://blogs.technet.com/b/mempson/archive/2010/01/10/userenvlog-for-windows-vista-2008-win7.aspx
Best regards,
Frank Shen

Remote Desktop Connection Problem in Windows 7 Home Premium

First off i have changed most of my computers in the house to static IP addresses. I only configured one static IP address to the router which is my laptop out of the two computers i am working with. Desktop and Laptop. Second I have enabled the Remote Desktop
on both computers and changed the firewall setting for the computer or the anti virus software. I tried the netstat -a but dont understand how to read it and when I did i never saw a host or port number for 3389 at all.
Then finally I went into the registry/regedit to try to see if I had the port number available and port 3389 was not there is just had #"2" in hexadecimal and the file says ehshell.exe which I have no clue what that means. When i click on that it
does not have the Port Number as the Title nor the port number itself as decimal which should be 3389 as decimal data but instead it has 2 as the data for hexadecimal. I can change the data for the port numbe and change to 3389 but I can't change the title
from ehshell.exe in the decimal value to PortNumber? The letters on my keyboard just will not coroperate or respond but it will highlight the word and thats it but not make a change to the data value ehshell.exe to something else.
Is it supposed to do that or what I wonder does anybody have any solutions to this so I can get my Remote Desktop running as soon as possible and no I do not have an Nvidia graphics card. I dont know what the problem is so can somebody please help
me? I need it for my Windows Server 2008 R2 class next semester and I need to be able to remote to other computers and devices.

Hi,
You can search and download remote desktop client for Win7.
http://blogs.msdn.com/b/scstr/archive/2012/03/16/download_2d00_remote_2d00_desktop_2d00_client_2d00_rdc_2d00_7_2d00_0_2d00_or_2d00_7_2d00_1_2d00_download_2d00_remote_2d00_desktop_2d00_protocol_2d00_rdp_2d00_7_2d00_0_2d00_or_2d00_7_2d00_1.aspx
Hope this will help you.

Remote Desktop Connection from a Windows 8.1 laptop to a work PC using Windows 7

Hi!
I posted this question in the MS Community forums and they redirected me here... I searched the forums here but didn't find anything that helped with my problem. So here is my original question (posted originally here: http://answers.microsoft.com/en-us/windows/forum/windows8_1-networking/remote-desktop-connection-to-a-work-pc/5fa25045-de24-4a7c-9c8e-caf9ce17e444):
For the past few weeks, I've been trying to set up a VPN connection to my work PC so I can work from home.
Work PC runs on Windows 7 (I assume Pro, but I can't confirm at the moment).
Home laptop runs on Windows 8.1 (the laptop came with Windows 8 already installed, so I assume it's the standard, or Home, edition. I manually upgraded to 8.1).
Now, after many migraines and sleepless nights fiddling with settings, the VPN connection works. However, what prevents me from completing the connection is Remote Desktop Connection.
Here's the error I get:
"Remote Desktop can't find the computer "<computer name>". This might mean that "<computer name>" does not belong to the specified network. Verify the computer name and domain that you are trying to connect to."
Note:
- I DO have the correct computer name. I have a working connection to my work PC from my personal desktop PC (running XP), though I sometimes need to travel and a laptop is much more practical to carry around than a PC... ;)
The VPN Connection Wizard never asked me to enter my destination PC username and password (so my work Windows credentials). Why?
Any ideas as to why Remote Desktop doesn't want to connect?
Any suggestions as to what I can try to fix the problem?
Thank you for all the help!
Julie

Are you able to ping the remote system by name? It sounds as though you are connecting to VPN but are unable to resolve the names of the host network. A few things that I would think of:
If the home system is not on a domain and the work system is, you may need to use the Fully Qualified Domain Name (FQDN). For example, instead of
computer you would enter computer.domain.com.
You may want to check if your VPN connection is configured as a default gateway, otherwise if your home and VPN network have the same IP address range you may be experiencing a conflict.
See the instructions provided here.
You also may want to check the DNS settings for the VPN connection to ensure that it is finding the DNS server for the remote network and thus is able to resolve the hostname.
You may want to try connecting Remote Desktop via IP address to determine if the issue is with name resolution (DNS) or connectivity.
Brandon
Windows Outreach Team- IT Pro
The Springboard Series on TechNet

IS at work told me I need to upggrade my home Macbook Pro operating system , 10.6.8, to a new version in order to remote desktop connect to my windows 7.1 machine at work. I want to know if I can skip prior upgrades and go to Yosemite or if I have

Since my work machine was upgraded to a Windows 7.1 pc, I can no longer connect remotely with my Macbook Pro with 10.6.8. I need to know the most efficient and economical way of doing this and if I can skip versions to get where I need to be. Supposedly, I need the very latest remote desktop connection software, and it is not compatible with 10.6.8. Help please.
Thanks

Open the Mac App Store and try downloading Yosemite. If you get told it's incompatible, choose About this Mac from the Apple menu, check if the computer has at least a Xeon or Core 2 Duo(not Core Duo) CPU and 2GB of RAM, and if it does, click here and order a download code for Lion 10.7.
Back up your data and check your applications for compatibility before upgrading. In particular, Mac OS X 10.7 and newer don't support PowerPC programs such as versions of Microsoft Office prior to 2008.
(119310)

Microsoft Remote Desktop app ios7 to Windows 8.1 Pro

For anyone using an iPad to remote desktop to your Windows 8.1 pro 64 bit computer, I recently posted the following distress call in the Microsoft Community Windows - Windows 8.1 - Other Windows apps by Microsoft - Other.
A Microsoft Support Engineer there suggested I post it here instead. The 1st part is the distress part, the 2nd part is how I finally solved it and then a different problem started ...
Part 1
Help, I'm going crazy trying to get this Microsoft Remote Desktop app on ios7 to connect to my computer running Windows 8.1.
I've added my computer name, user name and password, but even though it starts to connect it never does and gives me an error message saying:
Timeout while resolving hostname
I've set up my computer to allow remote connections and allow connections only from computers running blah, blah, blah.
What am I doing wrong?
In the past I was able to use logmein free without any problems until they stopped the free version. I can also get through using Team Viewer, so why won't the RD Client app work?
Part 2
Doesn't matter now as I ended up working out that it didn't work with my computer name. What I had to do is go to cmd and type ipconfig to find
the right ip address and insert it where it asked for computer name and it worked! Of course, then it kept disconnecting, so I've totally abandoned it and will use Team Viewer instead (until I'm willing to try again).
So that's where I'm up to.
I didn't find anything useful in this TechNet article: http://technet.microsoft.com/en-us/library/dn473013.aspx
So any suggestions on how to make Microsoft's RD Client app on ios work without disconnecting all the time?

Hi,
For this issue,as Milos said,using the host name requires your network to resolve the host name properly through DNS.
So this issue is related to DNS.In many home network configurations only the IP address will work properly.
Regarding DNS,I suggest you check the configuration on the ipad.
Regarding how to add host name to IOS,I suggest you contact apple support for help.
Regards,
Kelvin Xu
TechNet Community Support

Install Remote Desktop Services Failed on Windows 2012 Server

I understand RDS is not recommended on DC due to security consideration. However since I want to play it at home, it is not much a concern. Such scenario works fine on Windows 2008 R2. But on Windows 2012, the RDS (session-based, have not
tried VDI, but expect same result) installation always fails and is incomplete on DC.
In \Administrative Tools\Terminal Services, I only have RD Licensing Diagnoser and RD licensing manager. The remote desktop service management service cannot be started (Error code: 0x88250001). Is there any extra configuration needed for RDS
working on Server 2012 DC or before the installation? Thanks.
Update: this issue has been solved in Windows 2012 R2 Server. According to
http://blogs.msdn.com/b/rds/archive/2013/07/09/what-s-new-in-remote-desktop-services-for-windows-server-2012-r2.aspx
"Single server RDS deployment including Active Directory. We now support running our RD Connection Broker role service on the same physical instance as an Active Directory Domain Controller. In addition, we published
guidelines for how RD Session Host could be used without the RD Connection Broker."
The guidelines (http://support.microsoft.com/kb/2833839/en-us) primarily apply to Windows 2012 Server.

Asinine. Simply Asinine. Microsoft took it out because of $GREED$.
RemoteDesktop has become so popular, they had to break it to make more money. Thats why they discontinued SmallBusinessServer.   If this practice is so tabooo... Why did MS go the opposite direction with SBS 2011 Premium Cal's? SBS2011
had DC, Exchange, RDS and Sharepoint,SQL, RemoteWebWorkplace, OWA all working in perfect harmony. It is an untrue statement then, that it was "allowed but not recommended"
Now you by Server2012 (core + two virtual) and its not enough for all this.
You need at least another $700 for another sever licence to have it all
and who knows if SQL will run on a DC, or Exchange, or R-DERP server. Another reacherous bridge to cross.
By far, the absloute worse release since Millennium. The product is not ready for production, we broke our rule of waiting until the first SP1 upgrade for this and Exchange 2013. Problems with USB drivers and networking running extreamly slow.
Our 2003 SBS server was at least three times as fast, and this server has SAS and SSD drives running. It can't get out of its own way, and IE10 is the most unstable piece of crap to come out of Redmond. Open wide and swallow - Mother Microsoft
knows whats best for you. YOU WILL EAT OUR SLOP AND LEARN TO LIKE IT.   Server2012 AKA "METRO-SERVER"
Now here I sit after 50 Hours back to back setting up a new R-DERP server 2012, AD, Have my RDP licences in my hand at $100 each, and WTH does Microsoft care if I install it on my DC. ITS MY DC. And the cost savings versus the "risk" was
previously MY decision.
Sure, I can install a couple of Virtual HyperV sessions but they are so tempremental to a power-outage in a small business its not worth it. I have to double up my server hard drive resources, buy a $800 battery backup unit and make sure to attach
the cable, and even then, if that Bi**H does not shut down properly, one bit goes awry in a VHD or VHDX file and you are screwed. Restore from lastnights backup and forget about todays work. Not to mention it will probably take a half day to try
to fix it, then recover it then tell the 30 users they lost a days worth of work.
HYPER-V is for test servers and has no place in a small (micro) business environment. 5-30 users.
Microsoft's solution, buy another server. Need Exchange? Buy another server or take the risky cheapskate route and spin up some VHD's. Might as well put a gun to your head and play russian roulette, at least you know you have a one in six
chance of failure. With MS, its a 100% failure for a dirty shutdown power loss, motherboard blows, memory goes corrupt in a few years, your conventional method of recovery is gone, and you have some upchucked VHD file to try to recover some of TODAYS
data from.
Screw server 2012 forever.
I will sell 2008 and SBS2011 Premium unitl it rots in hell like XP (of which there is NOTHING wrong with for the average, WORD, EXCEL, OUTLOOK and QUICKBOOKS that all SMB's use. Its MS $GREED$ Grab the world by the B**ls and squeeze with all
your might to squeeze every dime you can out of *SMB* because big business is going to run thier 2003 Exchange and 2008 servers into ground before they switch to this garbage.
YOU CANNOT INSTALL EXCHANGE 2013 on DC , OR on R-DERP server.
Go buy another server license and server or MOVE TO THE CLOUD and get fleeced every month.
I have 30 DC/R-DERP/Exchange and SBS2011 Premium servers all running for years in perfect harmony, locked down with security so the users can't even WIGGLE with something they are not supposed to work with. They get their apps, cannot install anything
and all these servers are running just fine behind the firewall and perfectly save. The track record of this combination is 100% stable and is up 24/7/365 with no problems. Do yourself a favor and throw this 2012 into the river, you don't need
any weights because it is LEAD and will sink to the bottom by itself.
Why, you ask? Official is "Its for your protection" The real reason? To sell you more $700 server licences.
Maybe for SMB, we start selling Linux NAS Servers, host the Exchange in the cloud and be hearded like cattle to the Microsoft slaughterhouse. One way or another, you are going to bleed.    A little each month to move to the cloud, or
a small fortune if you want to have it in house. Microsoft wants it to be more expensive to have in house. No more buying a server and running it for six years before you upgrade. They can't have in house servers competing with their cloud,
and small businesses are the low hanging fruit ripe for the pickin'.

Cannot get Remote Desktop to work on Windows 7

Ok. I am having issues trying to connect remotely using RDP. From what I know, the network was pre-configured from another IT group and was able to get it up and running. My company was commissioned to migrate his old PC (WINXP) to Windows 7. I have gone
through the steps of allowing remote desktop and following instructions:
To configure remote access, follow these steps:
1. In Control Panel, click System And Security, and then click System.
2. On the System page, click Remote Settings in the left pane. This opens the System Properties dialog box to the Remote tab.
3. To disable Remote Desktop, select Don’t Allow Connections To This Com¬puter, and then click OK.Skip the remaining steps.
4. To enable Remote Desktop, you have two options. You can:
Select Allow Connections From Computers Running Any Version Of Remote Desktop to allow connections from any version of Windows.
Select Allow Connections Only From Computers Running Remote Desktop With Network Level Authentication to allow connections only from Windows 7 or later computers (and computers with secure network authentication).
5. Click Select Users. This displays the Remote Desktop Users dialog box.
6. To grant Remote Desktop access to a user, click Add. This opens the Select Users dialog box. In the Select Users dialog box, click Locations to select the computer or domain in which the users you want to work with are located. Type the
name of a user you want to work with in the Enter The Object Names To Select field, and then click Check Names. If matches are found, select the account you want to use and then click OK. If no matches are found, update the name you entered and try searching
again. Repeat this step as necessary, and then click OK.
7. To revoke remote access permissions for a user account, select the account and then click Remove.
8. Click OK twice when you have finished.
One thing that I found odd when he launched Remote Desktop from his home laptop is the IP entry:
Computer> [Public Router IP]:49250
Login> Domain\Admin
Password> *****
From the odd port number I would assume that was for port forwarding so I logged into his router and found exactly that. In port forwarding, he had the in/out as 49250 TCP to 192.168.30. I went into the firewall and enabled Remote Desktop in the inbound
rules.
As of right now, I can use Remote Desktop to remote into the server, and withing their server, I cam use Remote Desktop to remote into the workstation. I just can't remote into the workstation directly using the port 49250. Any suggestions on this, something
I have missing?
He has Norton Security installed on this computer and I tried adding Inbound/Outbound rules to its 'Smart Firewall' to allow remote desktop and the port.

Thanks for the reply.
When I use Remote Desktop and use the Public IP of the router without the port number (49250), I am able to get into the server. However, when I try to use RDP with the [Public IP]:49250, it will not connect to the 192.168.0.30 workstation.
Right now the router is program to forward port 49250 requests to the 0.30 workstation.
I am going to work on the Inbound/Outbound Firewall settings today and see if this will resolve the issue.

Remote desktop to laptop running Window 7 from laptop running Windows 8.1 on same network

I am trying to remote desktop into my Windows 7.1 laptop with my Windows 8.1 laptop. They are both connected to the same network and I can ping each other with their dns names. I can even use Windows Explorer to explore the file system of each
laptop.
When I try to use Remote Desktop Connection I get the error message "The remote computer requires Network Level Authentication, which your computer does not support." How do I turn this on in Windows 8.1?
I was able to figure it out on my Windows 7 laptop which I can remote into my Windows 8.1 laptop.
Thanks for your help,
Fred
Fred Schmid

When I uncheck the "Allow connections from computers running Remote Desktop with Network Level Authentication (recommended)", I still get the warning message:
"The identity of the remote computer cannot be verified. Do you want to connect anyway?"
But it allows me to connect.
What does that tell me?
Also, when I right click on the icon in the upper left corner of the Remote Desktop Connection window it says that Network Level Authentication is support on both computers.
Thanks for your help,
Fred Schmid
Hi,
From the details in the error prompt, We could understand that the RDP client is trying to validate the remote server’s certificate. The RDP client throws error prompt when it could not trust the certificate. The good thing is, the RDP client allows
us to bypass the certificate validation and connect to the server any way.
The Ideal solution for this is to apply the correct certificate on the server. The Microsoft support article (http://support.microsoft.com/kb/2000960) explains how to verify the selected certificate on
the server.
In my case, I don’t have the control over the servers. But I’m sure the servers I connect, are trust worthy. So, It is annoying to see this error message every time when I connect to the servers. And, every time I have to select the check box “Don’t
ask me again for connecting this computer“.
Kate Li
TechNet Community Support

Scroll Bar on Window

Hi. I have a form where the canvas/window is long. As such the Window has a scroll bar that the user can slide to move the canvas up and down within the window.
Are there any programmatic controls for this? 1) After the user commits their changes I'd like the window to scroll back up to the very top. 2) I'd like the user to be able to use the Page Up/Down keys to move this scroll bar - is this possible?
Any help would be greatly appreciated.

Hi. This is the code in my Key-Commit trigger:
-- SAVE AND CLEAR THE FORM
go_item('rcpt_mpi.mailpiece');
clear_form(do_commit);
DO_TRIGGERS.ENTQRY; What do you mean when you say the item at the top of the form should not be visible? Do you mean that the 'visible' property of the item should be set to 'false'?
Right now the item at the top of my form is the first field the user interacts with ('rcpt_mpi.mailpiece'). When the Window scroll bar is at the bottom then 'rcpt_mpi.mailpiece' is not visible simply because it has simply scrolled off the screen. When I save (F10) the data is saved, but the scroll position doesn't change. And when I scroll up manually I find the cursor is sitting in the 'rcpt_mpi.mailpiece' item. So the problem seems to be that the focus isn't changing to 'rcpt_mpi.mailpiece' even after the go_item.
Any thoughts?

SCROLL BAR OF WINDOW DOES NOT APPEAR IN THE WEB

Hi OTN Memebers,
My problem is in one of my form the canvas type is content. It's
size is bigger than that of windows size. When i run the form in
the client/server enviroment, the window scroolbars are
displayed. But when i try to deploy the from on the web , the
window scroll bars are not displayed.
Any solution for this. Please help me out.
Feroz.
null

Feroz A. Khan (guest) wrote:
: Hi OTN Memebers,
: My problem is in one of my form the canvas type is content.
It's
: size is bigger than that of windows size. When i run the form
in
: the client/server enviroment, the window scroolbars are
: displayed. But when i try to deploy the from on the web , the
: window scroll bars are not displayed.
: Any solution for this. Please help me out.
: Feroz.
This is a VERY OLD known problem with the product. The solution
is to put your content canvas on a stacked canvas and give the
stacked canvas scroll bars. Then disable the windows scroll
bars, otherwise you'll end up with 2 sets in Client/Server
mode...
Mark
null

Remote desktop connection limit in windows 2003 administration as well as in the mixed environment of windows 2003 and 2008 servers

RDP protocol i.e. Remote desktop connection is configured to perfrom and manage software administration of ORACLE application and database servers which runs on windows 2003 server. Two sessions are allowed on each of these servers for database
administrators. The question is:
a) if network administrators who perform window server administration (50+) are included in
2 sessions limit or do they manage all these servers through Console Session which is separate from the remote desktop connection limits of 2 sessions.
b) How is the 2 sessions limit prescribed by microsoft (more of a licensing limit) handled in the mix environment of windows 2003 and 2008 server where all these servers are managed on the VMWARE?
avnish sharma

Hi Avnish,
Thank you for posting in Windows Server Forum.
By default any windows server will provide 2 remote session for administration purpose only. No matter which administrator is accessing that server. If you will connect the console session then 3.One server is accessed by 3 Session (console + Remote +
Remote). When the particular server reached this limit then any working administrator will receive a message to log out as other user trying to access the session or if we had provided the setting then new user is restricted to login.
If you want more than 2 remote desktop session than you need to purchase TS\RDS CAL, install TS\RD Licensing role, activate it first and then configure CAL on it. There are 2 types of CAL available (USER & DEVICE). You can purchase CAL according to your
company requirements.
Hope it helps to understand!
Thanks.
Dharmesh Solanki
TechNet Community Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Remote Desktop scroll bar on Window snap to top of screen issue

Similar Messages

Maybe you are looking for