![Remote desktop connection client for mac downloads Remote desktop connection client for mac downloads](/uploads/1/2/4/2/124240190/191515328.png)
My existing setup: iMac 2010 base model (I3, 3.1GHz) with 12GB ram. I have got plex server, mysql server, vmware fusion 5.1 with windows 8 (for.net development) running on them. Of late, I have noticed my machine is slowing down and seeing lots of applications hanging and spinning beach ball. I have checked the hard drive using disk utility and it hasn't reported any errors. So thinking about reducing the load/pressure on the iMac, by buying a mac mini (both iMac and mac mini will be connected to a gigabyte switch) and moving the vmware fusion instance, mysql server and plex server to it. Mac mini will run as headless and i can screen share with iMac, if i need to configure something on the mac mini. The reason i want to go down mac mini route, rather than new iMac, is i can get current generation mac mini for £200 discount (on both i5 and i7 models) from work (strangely i don't get discount on iMac).
My concern with this setup is, as i am planning to run the mac mini as head less, i need to access vmware instance on it using windows rdp or screen sharing from iMac. So i want to find out how the response would be.
The virtual machine must be powered on, running a Windows guest OS, and have Remote Desktop enabled in the guest OS. The virtual machine must have an IP assigned on its network that is accessible by the client. The RDP port 3389 must be open on the guest OS. I've Mac OS X (El Capitan) VMs in ESXi 6 on our local network that I can SSH into and I can VNC into and I can connect Xamarin Mac Agent to but I can't Remote Desktop Connection (Windows 10) into. Our developers are all on Windows but need access to the Mac VMs for cross-platform development, particularly viewing the iOS Simulator.
Will there be any lag or will there be any other issues which i haven't thought about with this setup. I can buy a cheap windows laptop, but i don't think i can go back to using cheap laptops after using macbook air and premium windows laptops will cost me at least £800. Any help, suggestions or comments about the setup or lag issues with accessing vmware instance using windows rdp or screen sharing will be greatly appreciated.
Thanks for reading my post. What you are suggesting in your original post will work fine. Screen sharing I would suggest by using Apple Remote Desktop to the Mac Mini, and you will be able to use Microsoft RDC to access the Windows VM, though I prefer a more stable RDC client (Jump or Cord) as MRDC is unstable on Mac OS X 10.7/10.8 installations. There may be a little lag over the screen sharing, but your services certainly wont have any issues. A decent RDC client will allow fairly seamless access to your VM, so I see no reason this wont work. What you are suggesting in your original post will work fine.
Screen sharing I would suggest by using Apple Remote Desktop to the Mac Mini, and you will be able to use Microsoft RDC to access the Windows VM, though I prefer a more stable RDC client (Jump or Cord) as MRDC is unstable on Mac OS X 10.7/10.8 installations. There may be a little lag over the screen sharing, but your services certainly wont have any issues. A decent RDC client will allow fairly seamless access to your VM, so I see no reason this wont work.
VMware recently released a (VMRC) application for OS X users. This application is designed to complement the browser-based console for vSphere users by providing a native application for launching a remote console session with a vSphere-hosted virtual machine. A nice bonus is that. This provides a way for users of free ESXi to access ESXi-hosted VMs via a remote console session without needing to run either the Windows vSphere client. For more details, see below the jump. To use the VMRC without the vSphere Web Client, you will need to construct the VMRC URI which looks like the following: vmrc://@HOST:PORT/?moid=VM-MOREF.
HOST = the hostname or IP address of the ESXi server. PORT = the HTTPS port of the ESXi server, which is usually 443 Finding for the VM can be accomplished by one of two methods: 1. If you have SSH enabled on your ESXi server, connecting via SSH and running the following command: vim-cmd vmsvc/getallvms William Lam’s script is well-documented, so I’m going to look at using SSH to get the MoRef identifier. Pre-requisites: 1. Make sure you have SSH enabled on your ESXi server. SSH in and run the following command: vim-cmd vmsvc/getallvms In my case, as that will display back just the information I’m interested in. That should produce something that looks like this: 3.
Use the appropriate entry under Vmid for the MoRef value which the VMRC connection string is looking for. Once you have the Vmid entry for your VM identified, use the following address in a web browser: vmrc://@servernamehere:portnumberhere/?moid=vmidnumberhere 5.
Enter the ESXi server’s login and password when prompted. Accept the certificate if needed. The remote console session will open. In addition to opening via a web browser, you can also open the VMRC using the following process: 1. Open Terminal 2.
Run the following command: open 'vmrc://@servernamehere:portnumberhere/?moid=vmidnumberhere' You’ll be prompted for the ESXi server’s login and password, as well as the certificate if needed, then the remote console session will open.