Can 1 instance of Windows 8.1 ENTERPRISE host multiple Remote Desktop connections?

I am shopping for the components for building a machine with fair, high-performance hardware. I have Windows 8.1 Professional. I wanted to know if either Windows 8.1 Professional or Windows 8.1 Enterprise can support multiple remote connections
from users outside the local network. For example, my brother is based in San Diego, CA and has an underpowered laptop. Is there any way to make a remote connection over that much distance, from San Diego to Northern Virginia, from a RDP client running Windows
8.1 Professional to a RDP "server" Windows 8.1 Professional/Enterprise machine, and run a modern, single- or multiplayer- game over smoothly that connection? At the very least, is it possible to run common
apps (e.g. Microsoft Office 2013 IE 11, Adobe Acrobat XI) smoothly on a Windows 8.1 Pro RDP client connected to a Windows 8.1 RDP "server" located 2250+ miles away?
Would upgrading my installation from Professional to Enterprise improve the responsiveness and display quality for my remote users?
I know Windows Server R2 2012 has features specific for handling remote connections, but I am trying to keep a Windows 8.1 user experience. Still, if anyone can show some evidence that Windows Server 2012 R2 Remote Desktop Services (RDS) improves display
and responsiveness over long-distances for remote (RDS) connections, then I will shop for Windows Server 2012 R2 Standard instead. The huge drawback of Windows Server 2012 R2 Standard CALs is the enormous cost to enable 3-5
remote connections for family, non-commercial use.
Has anyone attempted to host long-distance remote access, non-commercially, for 3-5 connections? Has it worked well? What, in general, is required?
T. Webster

Hi,
It depends on the quality of the network connection to run the software smoothly throuth RDP. And I don't think the quality would be better if you upgrade to Windows 8.1 Enterprise.
Windows 8.1 allow only one session of RDP, the Remote Desktop Server in Windows other than the Windows Server edition has a limitation to allow only one concurrent user per session by default, i.e. if someone remotely connects to the computer over RDP then
whoever was logged in at that moment will be automatically logged off, even if that user is physically present at the computer. This is by design.
Regarding more information about RDP, please take a look at the following articles:
Remote Desktop app help
Remote Desktop Connection: frequently asked questions
Best regards
Michael Shao
TechNet Community Support

Similar Messages

Windows XP see blank screen when remote desktop to Windows 7 with fast user switching disabled

All computers are in workgroup environment, no AD.
Windows 7 pro are configured with fast user switching mode disabled so that only one login session can run at a time. When a Windows 7 machine remote desktop to another Windows 7 machine, the remote desktop 'server' will give 30 seconds count-down for the
console logged in user to accept remote connection, or when timeout expires it kicks out the console logged in user. This is completely ok.
This become a problem when a Windows XP rd client try to remote desktop to these Windows 7 machines, Windows XP see a blank screen if the remote Windows 7 machine has a user logged in, as it is waiting for the user to log off first. This is not desirable
as our administrators want the console session to be logged out automatically if they (administrators) want to remote desktop in.
Is this a configuration problem? Is this a OS design, can't be changed?
Valuable skills are not learned, learned skills aren't valuable.

Hi,
As I know, for RDP session in Windows 7, you don't need to configure the fast user switch option disabled. Windows 7 doesn’t support multiple Remote Desktop sessions by design, that means only one RDP session at a time.
I remote into my Windows 7 machine (which has a user logged in) from my XP machine, all work fine, the user logged in Windows 7 machine is automatically "kicked off".
May I ask a question? Does this issue happen in all XP machines? If you leave Windows 7 machine started and no user logged in, the RDP session in Windows XP established quickly?
I would suggest you keep latest drivers graphic card and latest updates paches for both Windows XP (Windows XP has come to its end of the lifecycle)and Windows 7.
Yolanda Zhu
TechNet Community Support

Connecting to a Windows computer using Remote desktop connection

I have connected a Windows 7 computer to my network using an ethernet cable to my Time Machine which is configured as an extension to my Airport network. My Mac sees the computer as shared, and I can connect to it using the name and password so I can browse files on it etc.
Nevertheless Microsoft Remote Desktop Connection will not connect to it, saying there is a network error. It has been suggested that if I use its IP address rather than its name it may work, but how do I remotely find out what its IP address is on the Airport network? I have not found the way using Airport utility or help.
thanks in advance...

You are using the Mac version of RDC aren't you?
If so, please post questions regarding it on Microsoft's own forums for the Mac version of RDC, as Apple discussions only provide support for Apple products

Remote desktop connection in windows 7 pro

I have a problem accessing remote desktop connection using windows 7 64 bit.
My remote desktop connection shell version 6.3.9600 shows the Network Level Authentication is not supported.
My other computer also win 7 pro 64 bit has a different shell version 6.2.9200 that supports Network Level Authentication.
How do I go backwards to shell 6.2.9200?
I have been trying use remote desktop using the more robust security and could not figure out why I could not log.
I have screen shots of the two shells and my system screens

Hi,
Configure Network Level Authentication
Click Start, click Run, type regedit, and then press ENTER.
In the navigation pane, locate and then click the following registrysubkey:HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa
In the details pane, right-click Security Packages, and then click Modify.
In the Value data box, type tspkg. Leave any data that is specific to other SSPs, and then click OK.
In the navigation pane, locate and then click the following registrysubkey:HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders
In the details pane, right-click SecurityProviders, and then click Modify.
In the Value data box, type credssp.dll. Leave any data that is specific to other SSPs, and then click OK.
Exit Registry Editor.
Restart the computer.
Hope this helps!
Andy Altmann
TechNet Community Support

How can I install Windows 8.1 Enterprise on my Macbook Pro With BootCamp?

How Can I Install Windows 8.1 Enterprise on my MacBook Pro?

Hi Armin.S,
I apologize, I'm a bit unclear on the exact nature of your question. If you are asking about the system requirements for running various versions of Windows under Bootcamp, or just more generally how to set up Bootcamp on your Mac, you may find the following articles/pages helpful:
Boot Camp: System requirements for Microsoft Windows operating systems
http://support.apple.com/kb/HT5634
Mac Basics: Using Windows on your Mac with Boot Camp
http://support.apple.com/kb/HT1461
Apple - Boot Camp Support
https://www.apple.com/support/bootcamp/
Regards,
- Brenden

Can I use Remote Desktop Connection (windows server 2008) even if no user is logged in?

I'm configuring a Server, running Windows Server 2008, to be accessed remotely. Suppose no user is logged in in the server (if it was just turned
on, for instance). Can I use the "Remote Desktop Connection" feature to log in remotely in this case? Or is it always necessary to have a user locally logged in, to remotely log in to one of the users available?

If its a fresh installation, RDM might not work at first.
1. You need to check firewall and allow Remote Desktop. To be specific, communication to port 3389 TCP
2. Right click My Computer --> Properties --> Remote tab
Enable Remote Desktop
Allow connections to this computer
Click users and grant the permissions for the users. By default, Administrators do have the permission. An also, the users who are members of the 'Remote Desktop Users' security group also have the permission

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

I have a time capsule connected directly to fiber connection. I have connected a windows server directly to TC and configured it for remote desktop connection. From my interanet I can access srvr but not from my home. What config I need on TC?

I have a time capsule directly connected to fibre optic point out. All pcs and macs are connected wirelessly to the internet. I have connected a windows server pc to TC. When configured for Remote desktop connection, I can access windows server from within interanet but don't know how to access it from internet. I guess I need to change some settings in TC to get some ip adress for the remote desktop connection from my home. Anyone who can help me out? Appreciate it.
Narmin

I am a little lost now.. I have read again your title and your first post.. and they seem inconsistent.
In the title you state.
From my interanet I can access srvr but not from my home.
Interanet is not a word I know.. I assumed intranet...are you talking about internet or intranet? And just to be clear say WAN or LAN.. !! Is your home part of the interanet??
In the first post you state,
I can access windows server from within interanet but don't know how to access it from internet.
Now this is more normal.. the issue is not in the home at all, it is accessible from there but fails from internet. If this is correct, then you can do a few obvious things to determine where the problem is.
But first I need to know are you actually testing from a different internet connection to your home lan.. you are not just trying the public IP from inside the LAN as that will fail due to the TC not doing NAT Loopback.
I am also assuming the TC is the only router in the network, and has the public IP on the WAN interface.
And I am also assuming you have turned on the ping responder and you can actually ping your public ip from the internet and get a response. This helps no end in figuring out where there are issues. Strange but I have no idea if there is a ping responder in the TC WAN so you might need to forward that as well. Also if you have a dynamic public ip address are you using dyndns or no-ip or some other service to connect.
1. Test bypassing the TC.. plug the internet connection straight into the windows server,, and test if you have access. If yes, the TC is the problem.. if not, your setup on the windows server is wrong.. look at firewall in particular.
2. Assuming from test 1 the TC is the problem, Post the screen shots of the port forwarding setup for us to look at.. that is by far the easiest way to check it out.
There are lots of references to port forwarding in the TC.. eg
http://must-know-mac.blogspot.com/2008/07/how-to-port-forward-time-capsule.html
The things that generally go wrong are firewall on the computer that is accepting the port.
The ISP doesn't allow connections on a particular port. (not likely in your case)
The router is behind another router.. double NAT will kill any port forward.
Upnp has already allocated a port.. not an issue as TC doesn't use upnp although a reboot of everything after you set port forwards is well worth it.. amazing how things don't stick properly without a reboot.
IP on the receiving device is not static and so changes.
Not enough or right type of ports are opened. This is always messier than it looks as one port is often not enough for two way communications.

Can't connect to windows 7 machine using microsoft remote desktop connection

I am unable to connect from my home network to the Windows 7 Professional machine at my office, using either Microsoft Remote Desktop Connection (2.1.1) for Mac or the open source CoRD program.
When connected to the office network (which is running MS Small Business Server 2011 Standard) both CoRD and MS RDC will connect to my desktop machine just fine! (My MacBook Pro runs Mountain Lion.)
From my home network, MS RDC will complain that it cannot find the Windows computer if I just use the Windows computer name. If I use the Windows machine's iPV4 address, it works on it for a minute and then tosses up this error message:
Using the IP address of the Windows machine, CoRD just grinds away for a minute or so and then times out.
I should add that using Internet Exporer under Parallels from home, I can get a little closer to success (after fidding around with ActiveX controls for a bit). I will get to the Windows login screen, but then I am told that my user password is wrong (which makes no sense at all)!
Okay, geniuses, have at it, and thanks in advance!!

The genius for Microsoft products an be found onthe Microsoft forums for their Mac software:
http://answers.microsoft.com/en-us/mac

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)

I have mac pro i7 , 8GB RAM , 750 HDD , can i install windows 7 ultimate 64 as a parrallals desktop?

i have mac pro i7 , 8GB RAM , 750 HDD , can i install windows 7 ultimate 64 as a parrallals desktop?

Hello and welcome to Apple Support Communities!
Yes, you can install Windows 7 Ultimate 64-bit in your Mac using Parallels for Mac. Just follow the instructions of the virtualization programs during the install. Should you need any assistance with the installation process, I strongly recommend contacting Parallels Tech Support (you must register with Parallels in order to have tech support).
Alternatively, you can always use Apple's BootCamp if you want to run Windows natively in your Mac. Check their support page, Apple has a lot of good links explaining this solution.
Hope this helps!

Can't get rid of the black window Remote Desktop Connection left on my screen

MacBook Air thinks that Remote Desktop Connection is open but I can't close the black window (where it shows the IP Address of the computer I had remoted into). It left the black windown opened on my screen. I can't even click on any menu tabs or take the app to the trash because it thinks it's still open. Well aware I can use different screens on my Mac but I want that black window gone! Thanks.

I don't understand what you mean when you say 'I can view the main pages', but, you've probably set your video playback to full screen.
Move the cursor to the top of the screen and go to View, down at the bottom of the list go to Video Playback, and then select 'None' from the list of options.

Dymo Labelwriter printers not working via Mac Remote Desktop connection into Windows Server 2008

I'm having a really hard time getting Dymo labelwriters (models 335 turbo and 450 turbo) to work over a remote desktop connection and I'd appreciate any help you can offer.
To briefly describe the situation, I'm working for a Doctor's office, moving their IT from a remotely-hosted environment where employees connect to their Windows Server 2008 virtual machines (hosted off-site) via Windows 7 machines through Microsoft's remote
desktop software.
The new setup will have new servers running in-house instead of remotely and will be based on Apple's Mac Mini machines running Windows 7 for some tasks through Parallels virtualization
software running directly on each employee's Mac Mini.
We have 3 of the Dymo 450 Turbo products and one 330 Turbo, each connected directly to a Mac Mini.
Here's the problem: I have Microsoft's Remote Desktop software running on the Macs natively, connected to each employee's virtual machine on the remote server for now, until the time comes to make the switch to using the new in-house server. The remote desktop
software works fine - employees are able to connect successfully and access their desktops fine. I have the "Forward Printing Devices" option checked in the Microsoft Remote Desktop app so that the hosted virtual desktops can see the local labelwriters.
However, the Dymo Label software running on the remote server will not recognize that a labelwriter is present.
If I go to the Printers and Devices window on the remote server, the labelwriter shows up fine, named "dymo labelwriter 450 turbo (redirected 10)" however running the Dymo Label software gives an error, "Dymo label says no printer connected:
dymo label printer requires a dymo label printer be installed and connected ..."
To try and narrow down the cause of the problem, on the same Mac, I ran Windows 7 via Parallels and set up a new remote desktop connection within that Windows VM. Just to be clear, instead of using the RDC software running in the Mac OS, this new connection
is using a Windows virtual machine running on the same Mac, with the RDC being established from within that Windows VM. Again, I forward printing devices and the labelwriter shows up in Printers and Devices on the remote server as "dymo labelwriter 450
turbo (redirected 10)" This time, the Dymo Label software recognizes the attached labelwriter and runs fine.
I'd appreciate any advice you can give on why, as far as the remote server is concerned, a forwarded labelwriter from Microsoft remote desktop running natively on a Mac isn't recognized
but it is if forwarded from within Windows, bearing in mind that the labelwriter shows up on the remote server in both instances and is called the same name in devices and printers.
Sorry for the long-winded question. I hope you can help me.

Hi,
Thank you for posting in Windows Server Forum.
Firstly please check whether you have driver capable for your printer with MAC MRD. Also I would like you to check with updated MRD version 8.0.9 for MAC OSX.
https://itunes.apple.com/in/app/microsoft-remote-desktop/id715768417?mt=12
Because as you have commented it can work with windows RDP, so please also try to contact Dymo Labelwriter printer and inquire regarding the issue.
Hope it helps!
Thanks.
Dharmesh Solanki
TechNet Community Support

Remote desktop connection problem windows 8

Hi everybody,
I hope you can help us. We run a software package that uses a remote desktop connection. When the program is minimised for more than a couple of minutes, the connection disconnects and takes a while to reconnect. We've been in touch with the guys that run
the program and they've said that there's no problem on their end and that it must be on our end. It's happening with all three computers at one location and it's not happening with our two computers in our other location.
I've been in touch with the online support guys in microsoft and they couldn't help. So I'm wondering if any of you can help us (in laymans terms please!).
All our computers run Windows 8.
Thanks in advance.

Hi,
Thank you for your posting in Windows Server Forum.
Yes, you can check with 2 different settings. 1) By Collection properties (Server 2012\R2) and RDP-Tcp connection under Remote Desktop Service Manager (Server 2008 R2). 2) The other setting is related to GPO (Set time
limit for active but idle Remote Desktop Services sessions) as following path.
Computer Configuration\Policies\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Session Time Limits
User Configuration\Policies\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Session Time Limits
You can check below link (Configuration 1) for more information.
[Forum FAQ] Restrict number of Active Sessions in RDS 2012 and 2012 R2
http://social.technet.microsoft.com/Forums/en-US/00c2252b-8ec0-489f-8da2-07a434a9b5a2/forum-faq-restrict-number-of-active-sessions-in-rds-2012-and-2012-r2?forum=winserverTS
Hope it helps!
Thanks.
Dharmesh Solanki

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

Can 1 instance of Windows 8.1 ENTERPRISE host multiple Remote Desktop connections?

Similar Messages

Maybe you are looking for