You can use the Remote Desktop client for Mac to work with Windows apps, resources, and desktops from your Mac computer. Use the following information to get started - and check out the FAQ if you have questions.
We're testing new features on our preview channel on AppCenter. Want to check it out? Go to Microsoft Remote Desktop for Mac and select Download. You don't need to create an account or sign into AppCenter to download the beta client.
If you already have the client, you can check for updates to ensure you have the latest version. In the beta client, select Microsoft Remote Desktop Beta at the top, and then select Check for updates.
A Remote Desktop Gateway (RD Gateway) lets you connect to a remote computer on a corporate network from anywhere on the Internet. You can create and manage your gateways in the preferences of the app or while setting up a new desktop connection.
If you're running macOS X 10.9 and have disabled Displays have separate spaces in Mavericks (System Preferences > Mission Control), you need to configure this setting in the Remote Desktop client using the same option.
Drive redirection is supported for remote resources, so that you can save files created with a remote application locally to your Mac. The redirected folder is always your home directory displayed as a network drive in the remote session.
By default, the remote session will use the same keyboard locale as the OS you're running the client on. (If your Mac is running an en-us OS, it will be used for the remote sessions as well.) If the OS keyboard locale is not used, check the keyboard setting on the remote PC and change it manually. See the Remote Desktop Client FAQ for more information about keyboards and locales.
I just got offered an update for the macOS client 3.10.1. Before I was on 3.10. all working fine on my 2013 iMac running Catalina (macOS 10.15.7). After the update installation was complete, a popup window said it can not run on my system.
PS: An additional information for the thread-opener justincognito:
Please download -3.9.4.pkg and install this package again. At least this solved my problems. Just to be sure I temporarily disabled the auto-update checkbox in the Client-settings.
If eM Client is having an issue with your Gmail account, you can go to Menu > Tools > Operations and look for any error in the Log tab. Or, as the data is not stored on your computer, you can go to Menu > Tools > Accounts and just remove the Gmail account from eM Client, then add it again. That will enable it to resync with the server.
You did not say what version of eM Client you are using. You can find that in Menu > Help > About. If you are using a beta version (8.x) you can get assistance by sending an email to tes...@emclient.com
no issue, will wait until you have some new findings! If I can provide more information to make the analysis easier, simply tell me. Have you considered providing a package with some more debug output?
I created a new group on the server with the settings I desired. (wildcards are not acceptable when defining a backup directory)
I uploaded the client .pkg in Jamf Admin.
I built a .mobileconfig to allow UrBackup Full Disk Access using PPPC and uploaded it as a profile into Jamf and pushed.
I wrote a super simple script in Jamf with the following:
My deployment process is to Add a New Client on the server. I then add that client to the group I created for mac laptops. Failure to do so causes the laptop to try to find a C:\ drive and causes headaches. I copy over the name and authkey into the Jamf policy into Vars 4 and 5. I then scope the policy to 1 laptop at a time.
Please remember that this project is not yet suitable for backing up/restoring complex filesystem objects, such as the system itself. User data should be generally fine with it though - a little more information here: Symlinks Not Working on macOS
Hi @Moisie
I did try this awhile ago, but the server then assumed my mac was a new client, and did not associate the backup history to it. Is it possible to roll back the version while keeping my backups linked to my Mac?
I did try this awhile ago, but the server then assumed my mac was a new client, and did not associate the backup history to it. Is it possible to roll back the version while keeping my backups linked to my Mac?
Hi forum,
I've tried the XG Authentication Agent for the first time - and I've installed it on the newest macOS High Sierra release. To me, it looks like it doesn't work, as it doesn't connect. I've setup the rules in the XG ruleset, and also given the user access to the virtual SSL VPN.
I have opened the Console.app, selected system log and searched for "Client Authentication Agent" and variants of it but I could not find anything. I see the icon of the Client Authentication Agent in the tray bar but it seems inactive.
Sorry about that, Apple changed the logging mechanism and now with the unified log, logs are not written to files anymore, but are most of the time in memory. I tested it on my High Sierra 10.13.1 in the Console app and found the log lines, just select your device in the Devices list and then filter after the desired text.
I also successfully tested latest version 1.2.8 of CAA and it worked, the icon turned orange and the user was live in SFOS. Please make sure to have SFOS as default gateway (because of the 1.2.3.4 IP) and that network connectivity is present, if it still doesn't work then reinstalling the agent alongside with the certificate should work.
Thanks for the logs, it looks like the agent can't establish a connection to 1.2.3.4:9922. That's what I meant with having XG set up as the default gateway for your LAN Mac clients, this is required because Client Authentication Agent connects to this magic IP which will be resolved by the Firewall, resulting in communication being established. This is the normal mode of operation.
Sorry that the support experience was not great.
Thank you Sivu!
What is not clear to me is if this configuration change should be done on the client (my Mac) or I should ask the administrators of the XG Firewall to do that.
In the former case can you point me to some documentation?
You're welcome. Normally it should be done by the administrator, since if you use DHCP you should also get the gateway information alongside the IP. Alternatively you could set up the default gateway yourself on the Mac. Don't know what kind of setup you have, but option 1 (or something similar) should normally be the case.
Thank you for the suggestion! I looked at the linked documentation. This would apply if I were using the VPN to access my GX50 network, but in this case I'm behind my personal GX50 and connecting to my employer's Meraki Client VPN that runs on enterprise hardware (MX84 and MX450 appliances.)
To refresh my memory of the setup routine, I built another network on my GX50 and set it to Guest mode. I came across the following prompt. (Screenshot.) Logically, this prevents guests from seeing internal class A, B, or C networks. I still don't find anywhere that I can control this myself, but what stumps me is that it's affecting the client VPN into another network. It's like the GX50 firewall somehow sees the VPN traffic trying to reach company resources. Ordinarily, I would think that a full tunnel VPN would not be filtered by my own firewall rules. I'll double-check the "Send all traffic over VPN" setting on the work computer, but still scratching my head.
I just started using Synergy, and I am having the same problem, sort of. Both client and server are Mac OS Monterey (Intel). The server is an iMac and the client is a MacBook Pro. When both computers go to sleep at night, only the server responds to mouse movement and wakes up. However, while the client MBP is still sleeping, the cursor will not even move into the client machine in order to wake it. It stops at the edge of the server's screen like it would without Synergy being installed. Both machines have "wake for network access" enabled. This is a bit of a deal breaker. Luckily I still have the hardware mouse/keyboard switch installed that I was hoping Synergy would eliminate the need for, but this makes it still a very much needed device since I use the MBP in clamshell mode all of the time. I realize I could always open the lid and "wake" it but if the client were another iMac or desktop machine, this wouldn't be possible.
Would you mind checking adding Synergy as a login item in MacOS? - Apple KB with instructions.
Also, if the MacBook is running in Clamshell mode, it may be related to power/battery settings - ie. perhaps that the network adapter is shutting down.
Hi thanks for replying. I _think_ the problem may have been related to me manually putting the machine to sleep. If I let it sleep on its own, it seems to work. I will repost here if I can confirm this.
I was wondering if there's a solution to this. I'm also experiencing the same problems. My windows computer is the server, and my M1 MacBook is a client. Whenever it goes to sleep, I get the same problems. I have "Wake for networks access" checked, and I have it added as a login item.
I'm experiencing this too. Windows 10 as server/primary and iMac (Intel) with macOS 12 as client. Windows wakes on mouse move, but the iMac will not wake until I press a key on the iMac keyboard. At which point Synergy works fine at the login/lock screen. Wake for network and the login item are present on the iMac.
I should have made it clear that I am using Synergy 3 Beta. The login screen option is enabled and working well on the Mac when awake. It just won't wake a sleeping Mac. I'm not sure what you mean by step 1, or perhaps that is a v1 only option.
Thought to double check the settings:
1. Do you have wake for wifi access enabled on the Mac?
2. Elevated privleges set to Always
3. The allow Synergy to control at login screen is enabled?