Windows Server 2012 R2 Download Iso Direct Link

The topic lists the minimum hardware and software requirements to install and run SQL Server on the Windows operating system. SQL Server 2017 introduces support for. If your license is VLK download it from the VLSC, if it is OEM or retail you should have got a disk when you purchased it or a link to download from. Digital River does (or did) provide legit download links for ISO.

A step by step guide to build a Windows 2012 R2 Remote Desktop Services deployment. Part 3 – Adding Session Hosts and Load Balancing session collections. In part two I detailed how to do an advanced installation, using separate servers for each role.

In case you missed it, or want to check it out, look at this post: In part one I detailed how to do a single server installation. In case you missed it, or want to check it out, look at this post: In this step by step guide we’ll be adding an extra RD Session Host server: ITWRDS05 will be the extra server. I used the same specs as in step 2 in this guide for the member servers, and used IPv4 192.168.66.25/24 and made it a member server of the domain. If you’re building along and want to continue doing so for the next parts in this complete series, make snapshots of the servers before adding this extra server. Software used in this guide: Windows Server 2012 R2 ISO (evaluation can be downloaded here: ) This guide will not focus on adding a member server to the domain. And again some basic knowledge is assumed in this guide. Installing the Remote Desktop Services Roles Log on to the Domain Controller, and in Server Manager right-click the All Servers node and add the new server using the Add Servers command (or select the All Servers node, click Manage and click Add Servers).

Now that all servers needed in this deployment scenario are present, click Remote Desktop Services. Server Manager In Overview, right-click RD Session Host and click Add RD Session Host Servers. Note that the Remove RD Session Host servers option is used to remove one or more Session Host servers from the deployment.

This will not uninstall the RD Session Host role service from the selected server(s), unless you choose to do so in the wizard. Select a server Click the newly added server and click the Add button. Notice here that the only server missing to choose from is ITWRDS04, which is of course because this already is a RD Session Host in the current deployment. Confirm selections Check Restart the destination server automatically if required.

View progress Wait until the RD Session Host role service is deployed and the new RD Session Host server has restarted. If you want Web Access users to be able to log on to this server, you need to add this server to the Resource Group for which we configured a policy on the RD Gateway server in the previous guide. On the RD Gateway server, open the RD Gateway Manager tool and expand the server node, expand the Polices node and click the Resource Authorization Policies node. RD Gateway Manager Click Manage Local Computer Groups. Make sure the Resource group is selected and click Properties. Type the name of the new server and click Add.

The Note you see here refers to the Remote Desktop Session Host server farm principle in case you also publish Windows 2008(R2) Remote Desktop deployments. In Windows 2012(R2) the farm concept is handled by the RD Broker and the RD Session Collections. Click OK to apply the settings to the resource group and click Close to close the group manager. Now let’s see what we can do if we have multiple Session Hosts in our deployment. Of course you could add a new collection using the new session host server, but that’s no different than what I explained in step 2 of this guide collection. Let’s do some new stuff with the new session host instead. Load balancing an existing collection In Server Manager click Remote Desktop Services, and then click the existing collection “Full Desktop”.

Scroll down to Host Servers if this section is not immediately visible. Click Tasks and click Add RD Session Host Servers. Note that the Remove RD Session Host servers option is used to remove one or more servers from a load balanced session collection. Specify RD Session Host servers Since there’s only the new server in the deployment which has the role but isn’t assigned yet, that’s the only server we see here. Select the server and click the add button.

Confirm selections The Wizard confirms that you selected the server. View progress Wait until the server is added to the collection. The Full Desktop collection is now load balanced over 2 Session Hosts. To confirm this, and see how we can influence the load balancing properties go back to Server Manager and click Remote Desktop Services, then click the Full Desktop collection. Full Desktop collection Click tasks, then select Edit Properties. Session Collection In this load balancing setup both servers are equally weighted for sessions. You could re-balance this if hardware resources are not the same across all servers in the collection.

While you’re in this screen, review the other properties of this session collection. In this example we load balanced a Full Desktop session collection, but the steps to take for doing so is exactly the same for load balancing a RemoteApp program collection. Managing a load balanced collection Load balancing a collection makes it possible to do maintenance on your servers without annoying your users.

You can put a server in maintenance without disrupting functionality. In the Host Servers section for the collection right-click the server you want to do maintenance on. Then select Do not allow new connections. Of course, you will have to wait until existing sessions are completed, or instruct users to log off and log back on, in which case they will be redirected by the RD Broker to the other server. Yes, this is a new session, there is currently no way to migrate sessions to other hosts without annoying the user. If you want to continue building along with this series, remove everything that’s installed in this guide.

You can revert to snapshots, or remove everything manually. – Remove the server from the session collection. – Remove the server from the RD deployment, removing the role services as well. – Remove the server from the RD Gateway Resource group – Remove the server from the domain And I will see you in the next part in which I will finally show a step by step guide on deploying and publishing a RemoteApps program collection. Arjan Update: is now published. Hey Arjan, This was so far a very helpfull blogg on how to implement and configure RDS 2012. I like it alot so thank you for using your time on this:) I have a issue where i try to connect to broker.domain.local from a client in the same network.

I dont want to use RemoteApps, I just want high availablity for regular RDP sessions, but when I try to use RDP i get: “The connection was denied because the user account is not authorized for remote login” When I use RemoteApp, its all good, the users is able to logon and no problem. I have a server with Conenction Broker, LIcensing, Web Access and Gateway and four servers that is Session Host. One issue I am having is when we disable connections to one server users will still get connected to that server anyway and it will say logins have been disabled. Our setup One Server for RDGateway and RDWeb 2 x Servers with Connection Broker and Session host roles DNS Round robin is enabled and A Record is created pointing to both IPs of the 2 CB / SH Servers When I ping rdcb.company.com its returning the IP of the server we disabled new connections on, also when we ping that FQDN from the Gateway server we get the same IP. My guess would be its something to do with the fact DNS is resolving the farm name to the IP of the Server that is not allowing new connections. How do we work around this issue?

This is internal test so its bypassing the gateway i would guess as thats the default setting. I tried unchecking that option to make local connections go through the gateway but I get an error when launching the full desktop saying, Your computer can’t connect to the remote computer because no certificate was configured to use at the Remote Desktop Gateway server. Hi I know this article has been up for a while but hoping you may be able to help with an issue I’m running into. I followed the previous 2 parts fine. But when I try to add an additional session host like in this Part.

But when I to the step in server manager to ” add RD Session host servers” I get a compatibility Check failed. ” the RD Session host role service is not installed on the server” and my options are to Exclude or cancel.

Clicking either takes me back to the previous menu in the wizard to choose a different server. Im confused because in the wizard at the top it clearly says ” the wizard allows you to add rd session host servers. Select the severs on to which to INSTALL rd session host role service.

I was hoping you could provide some insight on this. Thanks again. Hi Arjen, I have used your step by step guide to build our new RDP enviroment and so far it works great, however i have come across a few limitations RDP server 2012R2 brings. I hope you have any ideas on the issues im facing. Our setup is: 2 connection broker servers in HA 1 Gatway server 1 Webaccess server 15 session host servers The default setup allows only one collection for a full desktop session spread out over the host servers. My company would like our users the choice of having the session started with a lower resolution (purpose to make stuff bigger:) ).

The other is we have HP thinclients and default USB drive redirection is disabled, however a few users do have access. Also customizing this would require a second collection. Ideal would be to create multiple collections with the above settings directing you to all sessions host servers. I have found its possible for a collection pointing to a single server but using this means loadbalancing is gone. Any thoughts would be appeciated. Hello, thank for for this terrific guide! I followed this guide but combined a few roles to save resources.

My setup: –1 New 2012 R2 DC –1 New 2012 R2 server hosting broker, gateway and web server roles –2 New 2012 R2 session servers –1 SSL wildcard cert (seems to be working fine) From outside I am able to login to the web logging. Login works, click full desktop and login to desktop session works fine. My scenario is we have existing thin clients, many are older. I want to use the RDP client to connect to the FQDN outside address.

I have checked on the Gateway properties within the Remote Desktop client. When I initiate a session, I am placed on to the web server, meaning my session foes directly to the web server. I do not have port 3389 open to any server at the firewall. I am not redirected to a session server.

I have opened ports TCP 443 and UDP 3391 to the Gateway / Web server. How do I get an RDP client from outside the LAN to be able to receive a session from the “farm.” We are only looking for full desktop sessions, not RemoteApp sessions. Thank you for any assistance. I’m typing this on a public computer with no resources at hand to check my setup, so this response is unverified: – If you want your TCs to connect to the outside address you might want to disable “do not use gateway for local addresses” in the app settings of IIS that hosts your WebAccess pages – If you want clients to connect using RDP I suggest using the Remote Applications app found in control panel. Your clients would connect to If you want your clients to use MSTSC.exe you must create an RDP file for those users with the Gateway option enabled. Thank you for the quick response.

We are trying to use the native RDP (mstsc.exe) from Windows 7 Embedded, Windows 8.1 desktop and older thin client devices that have older RDP versions. They currently hit Windows 2003 terminal servers so we want to deliver a similar desktop experience with minimal for the user to change, i.e., change the current IP address for the FQDN on the RDP client software. When we do this we get a session from the web server. If we login to the RdWeb site, pass logon credentials and download the RDP shortcut and manually run it we get a session from the session server. So when the.rdp file comes down from the web server everything works as expected. When we try to copy all the settings from that rdp file to a new one and save it we get connected to the web server and not the session server. How can we make the typical remote desktop client whether on a thin client or Windows machine work with the gateway services?

Hi Arjan, Very nice and detailed post. Kudos for the time spent on putting this together. I have a small setup and am wondering if this is possible, if so you can just give an highlight on how: 1. Can i Load balance between two nodes SERVER A and SERVER B with each servers hosting all the roles (RD Connection Broker, Session Host, Web Access and Licensing etc. No need of RD Gateway, its being used internally) such that if SERVER A goes down, SERVER B will accept connections etc. I currently have one server setup with a few users doing remote apps. Which is working fine and wondering how i can have redundancy should server A goes down.

Keep in mind like i said, my present server is hosting all the roles including licensing. If that is possible, would it mean that i will have to separate the License Server role? Thanks Yinka. Hello Arjan, great and crystal clear tutorial.

After building a working 2012 R2 RDS farm, I started to create a VDI farm with multiple collections for Windows 7 SP1 and Windows 8.1. Unfortunantly I have a problem connecting to my Windows 7 VDI desktops externally, but I cant find a solution that solves my problem. Hope you can help me out.;-) My setup: Our RDS/VDI farm has 1 RDWEB/GW, 1 RDS host, 2 HA RDBrokers and 1 RDVH. All servers are Windows Server 2012 R2. The domain internally and externally is the same “corpxx.eu”. Connecting via RDWeb to our 2012R2 RDS host works great, as well as connecting to our Windows 8.1 VDI desktops. This works internally as well as externally.

We use a Comodo Possitive SSLwildcard certificate for “*.corpxx.eu”. I also created a collection for Windows 7 SP1 desktops.

The Windows 7 master image has SP1 installed as well as all Windows Updates (including KB2592687). When I login externally via RDWeb and connect to the Windows 7 desktop pool, I get an certificate warning that “Win7-1.corpxx.eu” is using an non trusted certificate. We are able to logon to Windows 8.1 VDI desktops with no certificate warning, as well as our 2012 R2 RDS hosts. Only with Windows 7 SP1 VDI desktops we get this certificate warning. After pressing “yes” on the certificate warning the connection tries to establish but it hangs for hours on “The remote connection is starting” and nothing happens. After hours of googling I cant find the solution.

Hope you are familiar with my problem and you can help me out? Many thanks for your help. I have been struggling to produce a flawless RemoteApp deployment. Now I’m down to one last problem, but it’s a major one. There are two distinct user groups for my deployment.

One group is remote web users. The second group is local users accessing via a thin client. If I set the Session security to “Negotiate”, then the deployment works correctly for Remote users, but local thin client users get prompted for a second set of credentials; moreover, once they type in the password again, it never works. If I set the Session security to “RDP Security Layer” or “TLS”, the local users work fine but the remote users hang and never can run the Remote Apps.

Advice and suggestions welcome. I know this is an older article but I had a few questions that I can’t seem to find the answers to. 1) If I want to load balance multiple SH Application servers, do the same exact apps need to be installed on each SH?

Does the CB know that the same apps are installed on each SH? And 2) If they are setup on the CB as being load balanced, do I still need to setup a round robin DNS entry for the farm name? It appeared according to this article that the CB performs all the load balancing between the SH’s. I currently have 2 RDS servers where both are SH’s but one of the two has all the other roles as well. My plan is to create a new server with just the CB, Web Access, and gateway roles and implement my existing SH’s (while removing the CB roles from the one) and create a new load balanced collection.

Any help would be greatly appreciated. Hello Arjan, just wanted to understand the role of CB in 2012r2 with a simple three servers setup: two RDSH and one CB (with web service installed). I’ve read that with 2012r2 the role is different from 2008r2, in the meaning all the connections pass trhough the CB and later distributed to the avaialble RDSH. So teoretically a DNS RoundRobin of the RDSH should not be necessary. Is that correct?

If so, why do I get “connection denied because the user is not authorized for remote login” when I connect directly to the CB? Arjan, thanks for your quick answer! Well I know It’s now a session host, either I did not install the service on that server, only Broker and it’s web part. My wondering was why is not redirecting to my RDSH servers For what I’ve read before jumping to your page, with 2012R2 the broker plays a more central role and clients should connect directly to him, via its web page or rdp and once the connection is set the broker redirects to the session hosts. Right now I’ve found this technet page that might explain why it’s not working: we are trying to use some old sunray2 thin clients, so why we wanted a more “direct” connection thanks for your help!

Hello, I am having trouble with multiple rdp session (saved on network location) trying to connect a 2012 server and can’t remember the password. When password entered manually it works? Have enabled delegate NTLM setting in local GPO with.

Followed all mentioned below: When using remote desktop connection to connect to windows server 2008, 2008 R2, sbs 2008, vista or windows 7 and would use saved credentials. This doesn’t work when you start the connection you get the following error: “Your system administrator does not allow the use of saved credentials to logon to the remote computer computername/ipadress because its identity is not fully verified. Please enter new credentials.” “The logon attempt failed” Solution: This happens when trying to connect to a computer / server in another domain and no trust relationships exists. Windows then steps back to use NTLM and the default domain machine policy prohibits use of saved credentials. You can change this domain based or for a individual machine: Start local group policy editor, start – run – gpedit.msc Go to Local Computer Policy –>Computer Configuration –>Administrative Templates –>System –>Credentials Delegation Edit “Allow Delegating Saved Credentials with NTLM-only Server Authentication” Enable the policy, click Show and enter the value “TERMSRV/*” into the list. Do the same thing for the following policies: “Allow Delegating Saved Credentials”, “Allow Delegating Default Credentials with NTLM-only Server Authentication” en “Allow Delegating Default Credentials” Close the policy editor, open a command prompt and use “gpupdate /force” to apply the policy directly – See more at: But DOESn’T work at all. HI 1 server RDCB,RDG,RDWS,RDLS hostname rdcb.xyz.com 3 server RDSH host name sh1.xyz.com,sh2.xyz.com,sh3.xyz.com I just want high availability of my all RDSH servers if i add a record on my DNS of all mt RDSH server with single name like remote.xyz.com 10.10.10.5 remote.xyz.com 10.10.10.5 remote.xyz.com 10.10.10.5 question is 1 How many certificate I need as per my understanding we need wild certificate right?

3 how client can access my RDS from outside with which name? (should I point my public IP to one of my RD host server with nat or what? 4 what I need to do with public dns point to remote.xyz.com? Thanks is advanced.

Hi Arjan, Me again, bumped into an issue. So my setup has 3 session hosts servers. I have already applied the wildcard certificate using the sever manager for webaccess,gateway,connectionbroker. I am using a DNS round robin session host farm for RDP. What I am noticing is, when I am trying to rdp using a the farm name, I am getting certificate error saying that the certificate was issued from the session host and the certificate has the internal fqdn of the session host server name and doesn’t have the wildcard cert name although I imported the wildcard cert in each session host servers local computer personal store.

Any suggestion? Hi Rei, and sorry Joel for missing this one, You should not connect to the farm name, or use round robin for the session hosts. You should connect to a session host name. The session host will always redirect the session to the broker and the broker then determines which session host will handle the session. So loadbalancing sessions is no longer handled by DNS round robin (which isn’t loadbalancing at all!!) but by the broker. Do not let your users connect to the broker or the dns farm name.

Both won’t work. Hi Hasnain, It totally depends on the kind of applications that will run on the session hosts. Take Azure for example. Azure Remote Apps by default runs on A3 machines.

That’s 4 cores, 7GB of ram, and depending on the plan that VM will host 10 sessions, or 5. Whenever I need to calculate on on-premise hardware however I stick by the ancient rule of thumb: 4cpu 30GB memory for 20 sessions, and work from there. Loadbalancing over the session hosts is handled by the connection broker. Word of caution however. Free Download Rafta Rafta Dekho Aankh Meri Ladi Hai Remix Songs there. 5000 Sessions is pushing the limits for Microsoft RDS. The server manager will disappoint you when 500+ concurrent sessions are reached, so look for other ways to manage sessions (powershell!).

Microsoft recommends using partner software like Citrix of Dell Wyse vWorkspace (my favorite) when reaching 1000+ expected sessions. Hi, I’m trying to make HA RDS Farm but with round robin DNS functionality it seems to be not very HA at least not that responsive as I want it to be so I have two Connection Brokers configured in HA (should be fine but I haven’t tested yet what happens if one CB is down), I have one RDGW server and two RDSH servers. In my DNS server I have two records, say: rds.mydomain.com pointing to RDSH1 and another rds.mydomain.com pointing to RDSH2.

When do nslookup for rds.mydomain.com I of course get two IP addresses, but when I do ping to rds.mydomain.com it stick with one IP address and doesn’t switch between two very often. So if I shutdown RDSH1 we will never be able to connect to RDSH2 using round robin DNS record. Some users will be lucky, but this doesn’t look like a solution. I think should be another way where we connect to a broker (otherwise what’s the point of that broker???) and broker determines which RDSHxx is alive which one is least loaded and so on Thoughts? Hi, We have an RDS environment that has 7 collections in it with 35 Hosts. Everything works great, but last month we started to experience an annoying problem. One of the hosts will just stop accepting connections randomly and the users get “stuck” trying to login.

It basically times out. The suspect host already has quite a few users on it.

We have found the only way to resolve this is to reboot the server and all is well again. What could be causing this? We never lose the network connection to the hosts.

We are thinking that it was caused by the last round of updates from M$ as that is when the issues started. Any feedback would be great. Thank you in advanced for taking the time to read all of our questions and reply them. I have the following scenario: 1x Web Access Server 1x Broker Server 1x Gateway Server 2x Session Host Servers I posses a SSL certificate under the name webaccess.mydomain.cl which contains inside two other subdomains: gateway.mydomain.cl and broker.mydomain.cl. I have installed this certificate on all servers; I followed all of the steps on the previous part but I do have an issue: I can connect internally and even run my APP (paint or calculator), but externally I can access the website, authenticate and even see the apps listed; once I try to open the rdp file that downloads, I authenticate (or at least asks for authentication) and then gives an error about gateway being temporarily unavailable.

Do you have any ideas on what might be causing this issue? I only posses one public IP at the moment and I am redirecting 443 to the webaccess server and udp 3391 to the gateway server. Still wont work.

Thanks again! Hi, I went through whole thread and like to clarify a few things that piggy back to your answer on this thread. If I had following resources, what would be best setup? 2 Public IP to map to outside world and 1 wildcard certificate to use on all hosts where needed. 4 Windows 2012R2 servers.

One of it is running as domain controller and TS license server. Let’s call them TS1, TS2, TS3 and DC1 c.

A Barracuda load balancer that could load balance whatever I tell it to balance. Goal: Avoid single point of failures. Would this work?

Assign Session Host role to all 3 TS. Assign Broker role to TS1 and TS2 3.

Assign Web Access role to TS1 and TS2 4. Assign Gateway role to TS1 and TS2 5. Configure load balance policy for HTTPS for Web access traffic. Let’s assume the load balancer VIP is x.x.x.x. Map that x.x.x.x address to a public IP(A.A.A.A) for external access. Configure load balance policy for RDP for the Gateway. Let’s say VIP is x.x.x.y.

Map a public IP(A.A.A.B) for external access via TCP/3389. On public DNS map rdp.mydomain.com to Gateway VIP public NAT address. People who uses native RDP client would come through this DNS record. On public DNS map rdweb.mydomain.com to Web Access public NAT address.

People would come through Web Access interface uses this DNS mapping. Would this work? OR is there a better way to achieve this?

Right now I have Barracuda doing RDP load balance for the session host IPs and have lots of intermittent connection issues. People sometimes get connections while sometimes not. Trying to simplify it without loosing redundancy.

Hi, I have set-up two RDSH, one of the servers being a RDCB, a session based full remote desktop deployment with intention to evenly use resources between the the two RDSH. Right now, i am connecting to the RDCB which is also one of the session host server’s, and the sessions are being redirected across the two.

We are connected via VPN to our local network and access these server’s, in this scenario, do i need a RDGW at all? Articles on the internet point to 2008 R2 and kind of mix up the deployment scenarios between the two, which is adding up to the confusion. Windows Xp Ice Iso Download Torrent. Could you please explain? Secondly, i’ve created a upd share and intend to make it HA share ( can i use failover clustering for this HA share?) can more than one server simultaneously access the share using failover clustering here?). Hi Arjan, if you’re still around. I’d like to get an advice.

I have a setup of two NLB-enabled RDG servers united in a RDG-farm with several unlinked RDSH servers behind, of either 2012R2 or 2008R2 OS version. I have discovered that one of the RDG servers constantly throws errors “Http transport: IN channel could not find a corresponding OUT channel” whenever some user connects through it. NLB states everything is OK and that server is listed as one that has the least priority.

Therefore all connections are going through the second server if at all. Should I disable NLB in some way (leave that host as the only one actively accepting connections), connections are stable. As soon as I re-enable NLB, HTTP connections drop. The NLB settings are as follows: – NLB cluster mode: Unicast – Port balancing rules: TCP/443 – multiple hosts, single IP affinity; UDP/3391 – multiple hosts, single IP affinity. Both RDG servers have a single network interface.

Also should I set cluster to multicast, it stops working – apparently for multicast NLB I need extra setup on network level, which I might not be able to perform. How should I set up NLB so that the servers will not drop RDP connections?

Generally, a download manager enables downloading of large files or multiples files in one session. Many web browsers, such as Internet Explorer 9, include a download manager.

Stand-alone download managers also are available, including the Microsoft Download Manager. If you do not have a download manager installed, and still want to download the file(s) you've chosen, please note: • You may not be able to download multiple files at the same time. In this case, you will have to download the files individually. (You would have the opportunity to download individual files on the 'Thank you for downloading' page after completing your download.) • Files larger than 1 GB may take much longer to download and might not download correctly.

• You might not be able to pause the active downloads or resume downloads that have failed. The Microsoft Download Manager solves these potential problems. It gives you the ability to download multiple files at one time and download large files quickly and reliably.

It also allows you to suspend active downloads and resume downloads that have failed. Microsoft Download Manager is free and available for download now. • Microsoft® Hyper-V™ Server 2008 R2 is a stand-alone product that provides a reliable and optimized virtualization solution enabling organizations to improve server utilization and reduce costs. With the addition of new features such as live migration and expanded processor and memory support for host systems, it allows organizations to consolidate workloads onto a single physical server and is a good solution for organizations who are consolidating servers as well as for development and test environments. By having the ability to plug into existing IT infrastructures Microsoft Hyper-V Server 2008 R2 enables companies to reduce costs, improve utilization and provision new servers.

It allows IT professionals to leverage existing patching, provisioning, management and support tools and processes. IT Professionals can continue to leverage their individual skills and the collective knowledge of Microsoft tools, minimizing the learning curve to manage Microsoft Hyper-V Server 2008 R2. In addition, with Microsoft providing comprehensive support for Microsoft applications and heterogeneous guest operating systems support, customers can virtualize with confidence and peace of mind. Supported Operating System Hyper-V Server 2008 • A list of supported guest operating systems can be found • Processor: x64 compatible processor with Intel VT or AMD-V technology enabled. Hardware Data Execution Prevention (DEP), specifically Intel XD bit (execute disable bit) or AMD NX bit (no execute bit), must be available and enabled.

• Minimum CPU speed: 1.4 GHz; Recommended: 2 GHz or faster • RAM: Minimum: 1 GB RAM; Recommended: 2 GB RAM or greater (additional RAM is required for each running guest operating system); Maximum 1 TB • Available disk space: Minimum: 8 GB; Recommended: 20 GB or greater (additional disk space needed for each guest operating system) • DVD ROM drive • Display: Super VGA (800 × 600) or higher resolution monitor • Other: Keyboard and Microsoft Mouse or compatible pointing device Note: The actual system requirements will vary based on your system configuration and hosted guest operating systems.