Mac users have a few choices when it comes to an RDP client for MacOS. There is the one that comes included with MacOS or there is the the one from Microsoft in the App Store.
There is also a beta version of the app store version available from here which, if you like to run beta stuff to get access to new and improved features and bugs is also useful.
I blew away my Mac on the weekend and did a fresh OS install etc because reasons. Unfortunately for me I didn’t remember to save/export my config from the beta client. Fortunately I had my TM backups and was able to grab the config file out of it and copy it over to my new profile. Problem is is that the App Store and Beta versions seem to store their configs in different files. **FURIOUS EYE ROLLING**
For the benefit of other people and for my own future reference the beta version of the app stores its config in `~/Library/Application Support/com.microsoft.rdc.osx.beta`. So, to recover your settings quickly and easily, quit the app, copy the file above from your backups and then restart your Mac. After the restart when you open the beta client you should see all your configs restored.
I had a response from the team that develops the tool to my question about this. They said:
hi Andrew, they are stored under:
this will only transfer your saved desktops, remote app feeds, gateway, and usernames.
it wont transfer your passwords, as they are stored on the keychain.
also please note that this is not an officially supported scenario
The following video was shared by @Gordypls. So HT to him.
Ive seen similar solutions to this need come and go over the years and have never found a solution that I was entirely happy with. This one looks better than other contenders. Its a 4 minute watch and feels like a reasonable solution for use on AWS.
Ive corrected the title on this video because CIFS is a legacy name now. See this.
via Qantas: Building a Highly-Available, Multi-AZ CIFS Cluster on AWS – YouTube
Putting this information up here for future keeping. I seem to need to keep referring to these from time to time and it will be handy to have them saved somewhere.
PIR for RailCorp (Now SydneyTrains) Sydenham Signal Box Failure on April 12th.
Presentation on the Stabilisation of the Melbourne Train Control System
Legacy Train Control System Stabilisation
Probably more information about Windows Event Forwarding (WEF) than you will ever need.
via Windows Event Forwarding – TechNet Articles – United States (English) – TechNet Wiki
The problem occurred again. This time, an uninstall and reinstall of VMware Tools didn’t fix the issue.
The fix was to:
- Open the VMware Fusion Sharing preferences and leave “Enable Shared Folders” ticked but untick all the “Mirrored Folders”.
- When prompted, log off and log back on.
- Open the VMware Fusion Sharing preferences and select the folders you want under ‘Mirrored Folders’.
- You will again be prompted to log off. Log off and then log back on.
The mirrored folders should be accessible again.
VMware Fusion has a nifty feature called ‘Shared Folders’ thats lets you access data on the underlying Mac OSX host from within the guest OS. Fusion must be configured to enable it and VMware Tools must be running inside the guest for it to work.
Recently, mine stopped working. I hadnt disabled the feature in Fusion and nothing lept to mind about other changes I could have made that caused the problem.
Today I had some spare cycles to dig into the cause of the problem and find the fix. See the source below from Nov 2015.
TL;DR: Windows Update nerfs a registry value which VMware Tools uses. The fix was simple, uninstall VMware Tools, reboot, install VMware Tools, reboot.
Source: Shared Folders – Windows 10 upgrade from 15.11. | VMware Communities
A feature-rich and versatile storage testing tool, Diskspd (version 2.0.17) combines robust and granular IO workload definition with flexible runtime and output options, creating an ideal tool for synthetic storage subsystem testing and validation.
Source: TechNet Diskspd Utility: A Robust Storage Testing Tool (superseding SQLIO)
I had to install PowerShell 3.0 on my Windows 7 SP1 VMware Fusion 8.5 VM earlier today and grabbed the installer from https://www.microsoft.com/en-us/download/details.aspx?id=34595. The download was done from Chrome on my Mac and saved to my Mac’s Downloads folder.
I have Shared Folders running in Fusion so I have direct access to the Downloads folder from Windows via the Z:\ drive presented to Windows.
When I ran the .msu file from z:\downloads I would receive an error which said:
Installer encountered an error: 0x80070003
The system cannot find the path specified.
The fix is to copy the .msu file to a VMDK based disk in the VM and run it again.