Client Access For Mac Os X

  1. Access Software For Mac
  2. Ibm Client Access Mac Os X
  3. As400 Client Access For Mac
  4. Ibm Client Access For Mac

Horizon Client for Mac OS X 4.2 15 September 2016

Mar 28, 2007  Our company is heavily invested in a bunch of IBM iSeries AS/400's. I can connect via Telnet and IBM 5250 emulation software to run the AS/400 programs we use without much problem. Nov 04, 2009  In the same spirit as the thread titled 'VI3: Linux client,' I'd like to propose a client for Mac OS X, too. At present, I need to VNC from my Mac laptop to a Windows workstation to then console into my VM's.

Last Updated: 16 September 2016

These release notes cover the following topics:

Key Features

Horizon Client for Mac OS X makes it easy to access your Windows or Linux remote desktop or hosted Windows remote desktops or applications from your Mac with the best possible user experience on the Local Area Network (LAN) or across a Wide Area Network (WAN).

  • Support for Mac OS X Mavericks (10.9), Mac OS X Yosemite (10.10), and Mac OS X El Capitan (10.11) - Use a 64-bit Intel-based Mac to work on your remote desktop or application.
  • Unmatched performance - The adaptive capabilities of the PCoIP display protocol and the VMware Blast display protocol are optimized to deliver the best user experience, even over low-bandwidth and high-latency connections. Your remote desktop or application is fast and responsive regardless of where you are.
  • Simple connectivity - Horizon Client for Mac OS X is tightly integrated with VMware Horizon 6 and VMware Horizon 7 for simple setup and connectivity. Quickly reconnect to your remote desktop or application by selecting shortcuts in Horizon Client.
  • Secure from any location - At your desk or away from the office, your data is delivered securely to you wherever you are. Enhanced certificate checking is performed on the client. Horizon Client for Mac OS X also supports optional RADIUS and RSA SecurID authentication.

Features Supported on Windows Desktops for Mac OS X Clients

Horizon Client FeatureSupported in Horizon Client for Mac OS X
Single sign-onX
PCoIP display protocolX
VMware Blast display protocol X
RDP display protocolX
USB redirectionX
Client drive redirectionX
Real-Time Audio-Video (RTAV) X
Wyse Multimedia Redirection
Windows 7 Multimedia Redirection
Virtual printingX
Location-based printingX
Smart cardsX
Multiple monitorsX


  • You can use Horizon Client for Mac OS X to securely access remote Windows-based applications, in addition to remote desktops.
  • You can use remote Windows-based applications only if you are connected to a VMware Horizon 6.0 with View or later server.

What's New in This Release

  • URL Content Redirection (Tech Preview)
    An administrator can configure URL links that you click inside a remote desktop or application to open in the default browser on your client system. A link might be to a Web page, a phone number, an email address, or other type of link.
  • Exclusive mode
    With Exclusive mode, the VMware Horizon Client menu bar and Dock do not appear when you move your cursor to the edges of the screen in a remote desktop.
  • Open recent desktops and applications
    You can now open remote desktops and applications from the Dock and from the Horizon Client File menu.
  • H.264 hardware decoding support
    Horizon Client for Mac OS X now supports H.264 hardware decoding as well as H.264 software decoding.
  • Username hint field support for smart card authentication
    Smart card users that use a single smart card certificate to authenticate to multiple user accounts can enter their user name in the Username hint field in the Horizon Client login dialog box during smart card sign-in. To make the Username hint field appear on the Horizon Client login dialog box, an administrator must enable the smart card user name hints feature for the Connection Server instance. This feature also requires Horizon 7 version 7.0.2.
  • Pass command-line arguments when launching a remote application from a URI
    You can use the args query to pass command-line arguments when you launch a remote application from a URI.
  • Spanish language support
    Both the Horizon Client for Mac OS X user interface and the documentation are now available in Spanish.


The user interface and documentation for Horizon Client are available in English, Japanese, French, German, Simplified Chinese, Traditional Chinese, Korean, and Spanish.

Before You Begin

  • Horizon Client requires a Mac OS X Mavericks (10.9), Mac OS X Yosemite (10.10), or Mac OS X El Capitan (10.11) operating system running on a 64-bit Intel-based Mac.
  • Horizon Client is supported with the latest maintenance release of VMware View 5.3.x and later releases.
  • To install Horizon Client for Mac OS X, download the disk image file from the VMware Horizon Client download page. For system requirements and installation instructions, see Using VMware Horizon Client for Mac OS X.

Access Software For Mac

Resolved Issues

No issues were resolved in this release.

Known Issues

  • If you use the PCoIP display protocol, connecting some password-protected storage devices (such as IronKey USB flash drives) might not work correctly. For example, after you redirect the device to the remote desktop, the password prompt does not appear. The remote desktop shows that a new drive was added and so displays a new drive letter but no corresponding label to identify the device.
    Workaround: Configure Horizon Client to automatically connect the device when you insert it. From the Horizon Client menu bar, select Desktop > USB > Autoconnect USB Devices on Insert.
  • Because the key combination Command+Tab on an Apple keyboard is used for switching applications on Mac OS X, using this key combination has no effect in a remote desktop. For remote desktops that run Windows 7, this means that there is no equivalent of the key combination Windows+Tab for using Windows Flip 3D.
    Workaround: You can use the key combination Command+Control+Tab for Windows Flip 3D, but you must also press Enter choose the application you want to switch to.
  • If Microsoft Remote Desktop Connection for Mac version 2.1.1 is installed on the Mac client system and you use the RDP display protocol to connect to a desktop on a Windows Server 2008 R2 RDSH server for which RDS licensing is specified, the following error message occurs: You were disconnected from the Windows-based computer because of problems during the licensing protocol. This is a third-party issue.
    Workaround: None.
  • Changes to webcam and audio devices that are connected to, or disconnected from, the Mac client system during a remote desktop session are not detected by the Real-Time Audio-Video feature.
    Workaround: Disconnect and reconnect to your remote desktop session to detect webcam and audio device changes. For example, if you connect a USB headset to the Mac client system during a remote desktop session and you want to use that headset on the remote desktop, you must disconnect and reconnect to the remote desktop session to make the headset available.
  • If Microsoft Remote Desktop Connection for Mac version 2.1.1 is installed on the Mac client system and you use the RDP display protocol to connect to an RDS desktop hosted on Windows Server 2012, the following error message appears: Remote Desktop Connection cannot verify the identity of the computer that you want to connect to.
    Workaround: Use Horizon Client for Mac OS X 3.0 and select the PCoIP display protocol when you connect to the remote desktop. Note: If you are using a pre-3.0 version of Horizon Client for Mac OS X, you cannot select the PCoIP display protocol.
  • The keyboard language is not synchronized with the language in desktop and application sessions.
    Workaround: None.
  • When you insert an SD card into a Transcend USB 3.0 card reader attached to your Mac client system, the SD card is not mounted automatically. Because the SD card is not mounted on your Mac client system, the device does not appear in the Connection > USB menu in Horizon Client and you cannot use the USB redirection feature to connect the device to the remote desktop.
    Workaround: Reinsert the SD card into the Transcend card reader. After the device is connected to the remote desktop, reinsert the SD card again to make the disk volume appear in the remote desktop.
  • If you use the USB redirection feature to connect a Transcend USB 3.0 external hard drive to a remote desktop from your Mac client system, files that you copy or move to the drive do not appear on the drive after you disconnect the drive from the remote desktop.
    Workaround: Redirect the external hard drive to the remote desktop again. The files appear on the drive.
  • If an administrator edits an application pool in View Administrator and changes the path to point to a different application that already has an application pool associated with it, unexpected results can occur. For example, the original application might be launched from the Mac OS X Dock instead of the new application.
    Workaround: Make sure that each application in a farm is associated with only one application pool.
  • Users cannot launch an application from the Mac OS X Dock if multiple application pools point to the same application in one farm, and if the application pool the users selected was created with associated parameters in View Administrator. If a user saves the application in the Mac OS X Dock and tries to open the saved item, the application fails to launch with the associated parameters.
    Workaround: Make sure that each application in a farm is associated with only one application pool.
  • If multiple Horizon clients connect to the same RDS desktop or remote application simultaneously and map to a location-based printer with the same name, the printer appears in the first client session, but not in later client sessions.
    Workaround: For the client sessions in which the printer does not appear, perform a manual refresh. For a remote desktop, press F5 or refresh the Devices and Printers window. For a remote application, close and reopen the application print dialog box. The location-based printer appears in the printer list.
  • Sometimes the virtual printing feature and location-based printing feature are not able to display the correct list of printers in the Devices and Printers window of a remote, session-based desktop. This issue can occur with desktops provided by Windows Server 2012 RDS hosts. The printers shown within applications are correct, however.
    Workaround: Log off the desktop running on the Windows Server 2012 RDS host and reconnect to it.
  • If you use a PIV smart card to authenticate to a Windows 7, XP, or Vista remote desktop on which ActivClient is installed, Horizon Client might stop responding when you log off from the desktop.
    Workaround: On the Windows 7 remote desktop, uninstall ActivClient and use Windows Update to install the PIV smart card driver. There is no workaround for Windows XP and Vista desktops.
  • If you set the Horizon Client security preference (VMware Horizon Client > Preferences > Security) to Do not verify server identity certificates and connect to a View server that has a valid root-signed certificate, Horizon Client might stop responding.
    Workaround: Unplug the smart card reader and then plug it back in.
  • You cannot use a PIV smart card to authenticate to a Windows 8 or 8.x remote desktop from a OS X Mavericks (10.9) or OS X Yosemite (10.10) client system, or to a Windows Vista remote desktop from an OS X Yosemite (10.10) client system.
    Workaround: For OS X 10.10 and later client systems, use charismathics software for PIV smart cards.
  • Keyboard shortcut mappings do not work if you are connected to a remote desktop or application and the Mac Input Source is Traditional Chinese or Korean.
    Workaround: Before you connect to the remote desktop or application, switch to the English Input Source on the Mac client system. If you are already connected to the remote desktop or application, reconnect to the View Connection Server instance and switch to the English Input Source on the Mac client system before you connect to the remote desktop or application.
  • If you use a PIV smart card to authenticate to a Windows XP remote desktop on which ActivClient is installed from an OS X Yosemite (10.10) client system and the smart card removal policy is set to disconnect user sessions on smart card removal, the desktop might not unlock automatically when you reconnect to the desktop. The smart card removal policy is a View Connection Server setting.
    Workaround: None.
  • If you use a PIV smart card to authenticate to a Windows XP remote desktop on which ActivClient is installed from an OS X Yosemite (10.10) or OS X Mavericks (10.9) client system and the smart card removal policy is set to disconnect user sessions on smart card removal, the PIN dialog box in the Windows XP desktop stops responding when you reconnect to the desktop. The smart card removal policy is a View Connection Server setting.
    Workaround: None.
  • If you launch a remote desktop with the PCoIP display protocol or the VMware Blast display protocol in full screen or window mode on an iMac with Retina 5K display and the screen size is more than 4K (4096 x 2160), auto fit does not work for the remote desktop if you change the display to full resolution (Connection > Resolution > Full Resolution).
    Workaround. None. This problem is caused by a PCoIP or VMware Blast limitation.
  • If you use the client drive redirection feature to share a folder or drive with remote desktops and applications, but you connect to a remote desktop or application that does not support client drive redirection, an error message is not displayed to notify you that the folder or drive was not shared.
    Workaround: Install View Agent 6.1.1 or later in the remote desktop or RDS host. View Agent 6.1.1 or later is required to use the client drive redirection feature.
  • When you connect to a Windows desktop, start USB services, redirect a USB storage device to the desktop, disconnect from the desktop, and then try to reconnect to the desktop, either USB services are not available in the desktop or you cannot reconnect to the desktop. In View Administrator, the state of the machine is Agent unreachable.
    Workaround: If you are an end user, restart Horizon Client and try again. If you are a View administrator, restart View Agent in the machine.
  • If you use the client drive redirection feature to share a USB drive with a remote desktop, and you unplug the device and then plug it back in during the desktop session, you can no longer access the device in the remote desktop. Unplugging a USB drive during a session also removes the drive and folder entries from the Folder list on the Sharing panel in the Preferences dialog box and you must reshare the drive the next time you connect to the remote desktop.
    Workaround: Do not unplug a shared USB drive during a remote desktop session unless you intend to stop using the device.
  • If you use Horizon Client on a new MacBook, and you use the USB-C port to connect to the network, you might notice poor performance when copying and pasting between a remote desktop to a shared folder.
    Workaround: None.
  • If you enable the Allow access to removable storage setting for the client drive redirection feature, and you also select the Automatically connect at startup or Automatically connect when inserted setting for the USB redirection feature, USB redirection does not work as expected. For example, non-storage devices, such as USB card readers, are not redirected automatically with the USB redirection feature.
    Workaround: Manually redirect the USB devices.
  • After you install Horizon Agent 7.0 in a Windows 7 remote desktop, you can no longer use Microsoft Remote Desktop Connection Client for Mac 2.1.1 to connect to the remote desktop. This problem occurs because TLSv1.0 is disabled by default in Horizon 7 version 7.0 and later.
    Workaround: Install Microsoft update 3080079: Update to add RDS support for TLS 1.1 and TLS 1.2 in Windows 7 or Windows Server 2008 R2 in the Windows 7 virtual machine and perform the steps in VMware KB 2059786: Establishing a RDP connection with a Windows 8.1 desktop from Horizon View Client for Mac OS X.
  • If you select the Remember this password check box when you log in to a server, you cannot log in to the same server as a different user if the credential caching timeout period (clientCredentialCacheTimeout) on the server has not yet expired. Horizon Client will automatically use the saved credentials to log you in to the server.
    Workaround: Remove the server from the Selector window (right-click the server icon and select the Delete menu item), click the Add Server button to add the server again, and then log in to the server as the different user.
  • When you connect to a remote desktop with the VMware Blast display protocol from a Mac client system that has an NVIDIA GeForce GT 755M graphics card, the desktop stops responding.
    Workaround: None. This is a third-party issue.
  • If you use a local certificate for server authentication, authentication sometimes fails and an SSL error occurs.
    Workaround: Disable TLS 1.2 in Horizon Client. For information, see 'Configure Advanced TLS/SSL Options' in Using VMware Horizon Client for Mac OS X.
  • If you connect to a remote desktop with the PCoIP display protocol, enter full-screen mode, and then connect an external monitor, the display on the external monitor is black and the mouse jumps to the right edge of the screen if you move the mouse in the primary monitor.
    Workaround: Quit and reenter full-screen mode.

Screens for Mac and iOS is the best remote access solution for accessing our Macs when away from home. It uses industry-standard technology for remote access (VNC), but the free Screens Connect service makes it easy to setup. This removes the requirement to use a static IP address or configure your router manually.

If your machine is behind a corporate network that prohibits Screens from working remotely, we recommend LogMeIn. The iOS and Mac apps are free, but the service is prohibitively expensive for most users.

Free Productivity Guide: Download our simple guide to productivity to help you improve your workflows and be more focused with your time and attention. Get it here.

Why do you need remote access?

With the rise of services like Dropbox, Google Drive, and iCloud, remote access services aren’t necessary for simply accessing files remotely. There are countless ways to sync documents and access them from anywhere. Accessing a PDF file using PDF Expert that is stored in Dropbox is certainly better than remotely controlling a Mac and opening the document. I use remote access to manage a Mac mini at Mac mini colo and my Plex server at home. Accessing a Mac remotely allows you to run desktop applications, have access to a full web browser from iOS, and access files and programs that are only on that one machine.



How does it work?

Screens, at its core, is a VNC client. VNC stands for virtual networking computing. It was created by The Olivetti & Oracle Research Lab back in the late 90s. The lab was later purchased by AT&T, but shut down in 2002. The original VNC source code is now open source. With VNC apps, there are two pieces. You have the VNC server (typically a laptop, server, or desktop) and the VNC client (another laptop, desktop, or mobile device). The client generally connects to the server from port 5900 and allows the client to see the display of the VNC server. Screens is using industry-standard technology, but with an easy-to-use and beautiful user interface.


Screens has stayed current, following Apple’s ever-changing design standards. Both apps received quick updates for the new iOS 7 design a couple years back. The iPhone and Mac apps share a lot of similar buttons and layout functions, so users of both apps can swap back and forth without having to re-learn workflows. The apps look for available machines on the local network, and also shows you the ones available with Screens Connect (more on that later). Double tapping/clicking on a machine launches it and either logs you in or prompts you for the passcode depending on how the security of that machine is setup.

Once you are logged into a machine, you are free to use it like you would just sitting in front of it. There is a dedicated Screenshot button, options to send/receive the clipboard, an option to scale down the display when network conditions are not optimal, and the ability to manage multiple displays if they are available.

On the Mac side, using a remote machine feels extremely normal. Both devices use a mouse and keyboard, so it’s fairly easy to implement that.

On the iOS side, you are taking a touch screen device and making it work with a desktop OS.

You quickly find out why Apple didn’t simply port Mac OS X as-is to the iPad. A touch-based OS requires drastically different interactions than a mouse/keyboard paradigm. With that being said, Screens offers the best experience in my opinion. It’s easy to zoom in and tapping moves the cursor to your desired location and initiates a click on the server. There is also an optional trackpad mode that turns your display into a trackpad and will make the cursor follow your finger around as you track. Both options work well, and it just comes down to personal preference.

Our friends at MacMini Colo discovered a great product to use on a remote Mac that is “headless” (a Mac mini or Mac Pro) in order to use higher resolutions. If you plug this dongle into the HDMI port, you’ll get access to all available resolutions up to 16×9 1080p.


Since Screens is built on open source technology, it is probably always going to lose the feature check list game when compared to custom-built services like LogMeIn or TeamViewer. Companies that are building their own technology have the ability to do whatever their product managers can come up with. Screens is built on open-source VNC technology, so it’s going to be a much simpler design. Most of the extra features aren’t needed in 2015 for most people (remote printing, file syncing, etc) anyways. Screens offers exactly what I want out of remote access without a monthly fee.

Access Options

Screens is available for Mac OS X and for iOS. It does lack a web access component, so if that is a feature that you need, then you should look at one of the other options below. Web access used to be important to me, but that was before I had multiple iOS devices in my bag. I’ve actually found myself using Screens on my iPhone 6 Plus quite a bit, not to mention the extremely capable iPad version.


As I mentioned earlier, Screens is really just a beautiful VNC application. VNC server support is built into Mac OS X by default, and this app is just building a VNC client. The main downside with VNC, since it’s an open-source platform, is that the setup can generally be tricky. You have to make sure the computer is configured right, and you need a static IP from your internet provider (or use a service like No_IP to update your dynamic DNS to a static host).

Screens has a free service called Screens Connect that takes care of that for you. You create an account, install the Screens Connect app on the Mac you want to remotely access, and log in with your user name and password. On the client side, you simply log in with your Screens Connect account, and you see your logged in computers. The only place this service won’t work is when a corporate firewall is blocking VNC traffic. Screens also offers a free program called Screens Express that makes it easy to connect to a friend or family member’s Mac with a temporary link.


In my experience, Screens has been rock solid. I bought it a few years back after LogMeIn discontinued their free service and haven’t looked back. Screens is really the best of both worlds. It’s pairing open-source technology that’s built right into Mac OS X with a well-supported and frequently updated app. On iOS, the developer has worked to add things like TouchID support, Touch Bar support, an adaptive toolbar and more. Regular updates help us feel more comfortable relying on this app day in and day out.

Runner Up


LogMeIn ($249.99/year for two computers) is our runner up for remote access solutions. We also recommend it for the times when VNC technology is blocked or a corporate firewall prevents Screens Connect from working. LogMeIn is easy to install and easy to use. In fact, I use it on a few machines at work in order to always have easy access to them from offsite. LogMeIn allows me to keep my firewall locked down, but still get to these machines. It works from the web, but they also recently added a Mac client that is installed when you sign up. It allows quick access to a machine.

LogMeIn also offers free iOS apps. I’ve found that their iOS apps are the easiest to use. I found scrolling and tapping/clicking to feel the most native of anything other than Screens. From a security perspective, LogMeIn uses SSL/TLS for all its communications. You can also use RSA SecurID or 2-factor authentication along with requiring your Mac’s username and password.

One of the main reasons we chose Screens over LogMeIn is the price. Screens is a one-time app purchase where LogMeIn is $249.99/year. It’s difficult to justify that price unless this is something you depend on every day.

Free Productivity Guide: Download our simple guide to productivity to help you improve your workflows and be more focused with your time and attention. Get it here.

Ibm Client Access Mac Os X

The Others

Back To My Mac

Back To My Mac (free) was originally a feature of MobileMe, but it is now a part of iCloud. Since iCloud is free, it’s a natural choice for a lot of users. However, we don’t feel like it’s the best solution due to the fact that we can’t get it to work the majority of the time.

Apple’s support document mentions a few tips related to its own routers, but not much else. Some users have no issue getting it to work, while others have no success at all.

Another reason that it’s not our pick is there is no way to use it on iOS. I use remote access apps as much on my iPhone as I do other laptops. Back To My Mac is free with an iCloud account, but it’s support and features reflect the price tag. Security-wise, Back to My Mac uses IPSec and SSL encryption between your Mac and Apple’s servers. It uses Kerberos with digital certificates to verify that you are authorized to connect to the Mac in question.

Apple Remote Desktop

Apple Remote Desktop ($79.99) is a tool that’s aimed at Mac system administrators, but it’s really not that useful for them any more. It goes years without updates, and the ones it does see are usually for Mac OS X compatibility. Like Back To My Mac, it also lacks an iOS component. Setting it up to work remotely is also going to take some networking configuration on your router and VPN setup. Most Mac system administrators have moved onto a tool like Casper Suite from JAMF Software. Apple Remote Desktop fits in a weird place of not being useful for the prosumer, but not powerful enough for the IT department. I’d rather see it become a Back to my Device app and work with iOS devices (remote access from a Mac to iOS) and make it work similar to Find My iPhone. From a security perspective, you can encrypt your session with an SSH tunnel, but it does come at a security cost. Authentication to clients uses an authentication method based on a Diffie-Hellman Key agreement protocol that creates a shared 128-bit key. This key is used to encrypt the login credentials using AES. The Diffie-Hellman key agreement protocol used in Apple Remote Desktop is similar to the one used in Mac file sharing.

Chrome Remote Desktop

Chrome Remote Desktop (free) is a Google Chrome plugin that allows you to access other Macs that are logged into your Google account (with the Remote Desktop extension installed) through the web browser. The price is right, it’s simple to setup, and offers iOS access. I found the iOS app to be subpar compared to Screens, though. It functionally worked fine, but Screens handled multi-monitor setups better, scrolled easier, and was just all around more functional. Remote access tools are already a bit of a hack, so smoothness and speed are imperative. Chrome Remote Desktop uses Chrome’s SSL features, which includes full support for AES. None of your session data is ever recorded by Google, and in most situations, the connection is directly from the client to the remote session without passing through Google. It’s free, so there is no reason not to give it a shot if a free solution is what you are after.


TeamViewer (free for non-commercial, starts at $795 for commercial) is another popular remote access solution. Like LogMeIn, it handles the router configuration for you. You install the client on your Mac, and then you can log in from the web or an iOS device. TeamViewer works well and is fast, but the setup and configuration was a bit more complicated than LogMeIn. While it is a remote access solution, its also heavily pitched as a remote support and online meeting solution as well. The price is right, but LogMeIn is easier to use, and Chrome Remote Desktop is easier to set up. TeamViewer’s encryption is based on RSA private/public key exchange and AES 256-bit session encryption.


RealVNC (free and paid products available) was founded by the original developers of the VNC protocol (it’s open source). They offer support for Mac and iOS, and also offer free and paid plans, but it’s not a product we recommend to most people because of how difficult it is to set up for off-site access. It involves knowing your public IP (most residential users have a dynamic IP that can change) and forwarding ports on your router. The paid products offer 128-bit AES encryption or better. If you are looking for a free solution, we recommend Chrome Remote Desktop since it is a lot easier to set up.


GoToMyPC ($11.95/month or $114.72/year) is one of the most well-known remote access plans. It shares a lot of features with other popular options, but it’s a little pricey per computer compared to its competitors. There is no configuration needed on your router. You simply install the client, and then you can access your computer from the web or an iOS app. You can print to your home computer from your work computer, drag and drop files, and copy/paste between computers. From a security standpoint, it supports 128-bit AES encryption, dual passwords, and end-to-end authentication.

Alternative technology

Remote access solutions aren’t as essential as they once were. I used to use them to access files from off-site, but with the popularity of folder syncing services, we can have access to most of our files from any device or location already. Here are a few of the common options for Mac users:


Dropbox (free up to 2 GB, $9.99/month for 1 TB) is the go-to folder syncing solution for a lot of users. Its client is relatively stable, it has great third-party app support, and offers a free plan for beginners. Paid plans start at $9.99/month for 1 TB of storage. This makes it a nice option for storing large amounts of data and having access to it from anywhere.

Google Drive

Google Drive (free up to 15 GB, plans start at $1.99/month for 100 GB) will be a great choice for a lot of users due to the fact they likely already use Gmail. Google Drive is best used on the web, but it has a Mac client as well that works very similarly to Dropbox. The client works well, but it lacks some of the features of Dropbox related to bandwidth control and controlling which folders are stored locally on your Mac. Google Drive only supports selective sync on root folders, where Dropbox supports it for sub-folders. The price is right for up to a terabyte, and then Dropbox offers similar plans. Google Drive is ideal when you need more than 2 GB, but less than 100 GB, and it does offer better web support than Dropbox. Google Docs, Spreadsheets, and Slides are much better than anything Dropbox offers in terms of web-based editing.

iCloud Drive

iCloud Drive (free up to 5 GB, plans start at $.99/month for 20 GB) is Apple’s answer to Dropbox. It’s a folder than syncs on your Mac. Contents can then be synced to an iOS device or another Mac. It lacks true web access, though.


OneDrive (free up to 15 GB, plans start at $1.99/month for 100 GB) is Microsoft’s answer to Google Drive. It includes Microsoft Office online for free. 1 TB is only $6.99/month and it offers access to Office 365 which includes Office for Mac and unlocks a few features on the iOS apps. It offers selective sync support that is similar to Dropbox, but web access that is similar to Google Drive, so it’s an attractive choice for heavy Office app users.


If you want to have a bit more control over your files, consider a device like Synology. It’s a network-attached storage device aimed at the prosumer. It offers a lot of great features, but at its core, it’s storing your files and making them available everywhere (web, iOS, etc).


If the only thing you want to access a Mac remotely for is your media collection, you might consider using Plex as a media manager (movies, TV shows, music, photos, etc). It installs on your Mac, and then you can access it from the web and iOS ($4.99). It handles all of the login management, so there are no router configurations needed. An optional Plex Pass gives you features like syncing offline, camera roll uploads, and cloud sync (backup your media to various cloud services in case your server goes offline).



As400 Client Access For Mac

While remote access to a Mac isn’t as essential as it once was due to multiple options for syncing your files across your various devices at low cost, Screens is the best choice for when you need it. With native apps on Mac and iOS, it offers the most streamlined experience without a subscription. If you have more complex needs or your Mac is behind a corporate firewall, I recommend checking out LogMeIn.

Ibm Client Access For Mac

Free Productivity Guide: Download our simple guide to productivity to help you improve your workflows and be more focused with your time and attention. Get it here.