Wondering if Chip's reply from 5 years ago is still true: Does the client software, especially Pub Manager, still run only on Windows?

Oddly enough, after years of running on Windows, I've gotten two requests this week from people who want to be able to run on a Mac.

Thanks.

We have writers on Macs ... they just connect to TDX using a VM.

This was recently shared with us from RWS Support:

• The Publication Manager and Authoring Bridge modules of Tridion Docs can be run on Macs using Fusion or Parallels, therefore allowing these Windows applications to run on a Mac.
• A further option is Remote Desktop which requires you to have another Windows server available that users can access. However, others have observed much slower performance with this method.

Thanks, everyone. So....No native support for the apps on a Mac. But plenty of options for running in a simulated or virtual environment.

Hi Stacey Meggs , I'm in the process of setting up a Windows emulator on my Mac - Have you had (or heard) about success using Parallels vs VMware Fusion? 

Same question to Elizabeth Gschwind if you have any suggestions. 
Thanks in advance for any help! 

Hi Jesse Rumsby-Campton , I am on  Stacey Meggs 's team. I want to share with you what has worked for us with writers running a Windows Emulator. 

1. The writer installed Parallels Pro Edition (annual subscription) and Windows 11 Pro (one-time purchase). This configuration allows the writer to update the environment with the latest security patches. 
2. Install Tridion Docs 15 and Oxygen 21.1 on the virtual machine.
3. Provide the writer a username and password to access Tridion Docs 15 instead of SSO. We found that the virtual machine did not support SSO. There is no YubiKey key support for the version of Windows that runs in a virtual machine. As a result, SSO login fails for Publication Manager.
4. Change the local storage path in Publication Manager from mac/Home/Documents/RWS/InfoShare to C:\Users\<user_name>\Documents\RWS\InfoShare.
5. Change the local storage path for Oxygen from mac/Home/Documents/RWS/InfoShare to C:\Users\<user_name>\Documents\RWS\InfoShare.
6. Change your default web browser in the virtual machine to Microsoft Edge. You can still use Chrome as the default on MacOS. 

Periodically the browser will time out, or writers will get a login screen with blank username and pw fields, rather than the “You are now signed” in message.  But it generally works if the writer retries (sometimes requires clearing browser cache and restarting Edge and Pub Mgr).  Writers find that if they leave Oxygen running rather than closing it after checking in a topic, they have to authenticate less often.

Hi Jesse Rumsby-Campton , I am on  Stacey Meggs 's team. I want to share with you what has worked for us with writers running a Windows Emulator. 

1. The writer installed Parallels Pro Edition (annual subscription) and Windows 11 Pro (one-time purchase). This configuration allows the writer to update the environment with the latest security patches. 
2. Install Tridion Docs 15 and Oxygen 21.1 on the virtual machine.
3. Provide the writer a username and password to access Tridion Docs 15 instead of SSO. We found that the virtual machine did not support SSO. There is no YubiKey key support for the version of Windows that runs in a virtual machine. As a result, SSO login fails for Publication Manager.
4. Change the local storage path in Publication Manager from mac/Home/Documents/RWS/InfoShare to C:\Users\<user_name>\Documents\RWS\InfoShare.
5. Change the local storage path for Oxygen from mac/Home/Documents/RWS/InfoShare to C:\Users\<user_name>\Documents\RWS\InfoShare.
6. Change your default web browser in the virtual machine to Microsoft Edge. You can still use Chrome as the default on MacOS. 

Periodically the browser will time out, or writers will get a login screen with blank username and pw fields, rather than the “You are now signed” in message.  But it generally works if the writer retries (sometimes requires clearing browser cache and restarting Edge and Pub Mgr).  Writers find that if they leave Oxygen running rather than closing it after checking in a topic, they have to authenticate less often.

I have a quick follow-up. We are running Oxygen 23.1, not Oxygen 21.1, as mentioned above.