At my work we are required to use Smart Card to login to our systems. It works fine as long as we are logging on to our Macs or our Windows Desktops. Even if we use Remote Desktop connection from our Windows desktops to other Windows machines, it works without any issues. The problem occurs when we try to logon to Windows machines from Macs. There aren’t many Remote Desktop client options available for Mac that support Smart Card redirection. Even Microsoft Remote Desktop client on Mac currently does not support Smart Card redirection. I found a nice client Royal TSX that supports Smart Card redirection and it works fine. Actually it worked fine until Windows 7 and Windows 2012 Server. It stopped working with Windows 8 and Windows 2012 R2. It looks like Microsoft has changed the behavior of Smart Card service in Windows 8 and Windows 2012 R2. When I try to logon to Windows 2012 R2 Server or Windows 8 from Mac using Remote Desktop, I get the error “No valid certificates were found on this smart card” as shown below.

hmmm. The workaround I used for this was to connect to my Windows 7 Virtual Desktop and from there connect to Windows 8, Windows 10 or Windows 2012 R2 machines. This was an ok workaround until recently when my Virtual Desktop was upgraded to Windows 10. I was expecting that this Smart Card issue would have been resolved in Windows 10 but Windows 10 has the same issue. After doing some research online I found out that Microsoft has changed how Smart Card service behaves in Windows 8 and later. The Smart Card service only starts when it detects the Smart Card reader. It looks like when I Remote Desktop from Mac to the Windows machine the Windows machine is unable to detect the Smart Card and therefore the service does not start. I tested it by manually starting the Smart Card service and I was then able to logon to the machine. Now the problem is how can I make sure to start the service when I am connecting via Remote Desktop. I noticed that when I connect using Remote Desktop, the event viewer logs an event “9027” in Application Logs, as shown below.

Now I think that I can use this event and use task scheduler to start the Smart Card service whenever there is this event in the Application Log.

I started the Task Scheduler and created a new Task by using the steps below.

Mar 10, 2021 Microsoft Remote Desktop for Mac is an application that allows connecting to virtual apps or another PC remotely. Discover the power of Windows with Remote Desktop designed to help you manage your work from any location over a network connection. Several steps you could have a try: 1.Go to Microsoft Remote Desktop preferences General Tab uncheck “use system proxy configurations “ and Also uncheck “Use hardware acceleration ” This is one suggestion shared in another thread and many users reported that if fixed their issues.

Start Task Scheduler, right-click on Task Scheduler Library and then click on Create Task

Name the task whatever you want, I used “Start Smart Card Service”.

Make sure to use the options as shown in the picture above.

“When running the task, use the following user account:” needs to be set to “SYSTEM”. We want this task to run as SYSTEM user.

“Run whether user is logged on or not” needs to be selected. We want this task to run whether any user is logged on or not.

“Run with highest privileges” needs to be checked. We want this task to run with highest privileges. The task may run fine without checking this box, but I just checked it so that it doesn’t fail because of the lack of any permissions etc.

Now go to “Triggers” tab

Microsoft Remote Desktop Mac Keyboard Not Working

Here click on “New” button to create a new trigger. You will see the following window

Click on the dropbox next to “Begin the task:” and select “On an event”. We want to start the task on an event.

Now in the “Log:” dropbox, select Application

In the “Source:” dropbox, select “Desktop Window Manager”

and in the “Event ID:”, type “9027”.

We saw from the Event Viewer log that the log type of “Application”, Source is “Desktop Window Manager” and Event ID is “9027”. So, we want this task to run on this event only. Now click on “OK” and you will see this trigger added.

Now go to Actions tab

Macbook Air Remote Desktop

Click on “New” button to add an action.

In the “Program/script:”, type “net”. In the “Add arguments (optional):”, type “start scardsvr”. i.e. we want to run “net start scardsvr” to start the Smart Card service. Now click on “OK” to close this window. Everything else can be left as default so you can click on “OK” again to close the properties window.

Now your task is setup and will show up in the list of tasks. This task should start the Smart Card service whenever you connect using Remote Desktop Connection.

Try it, when you connect using Remote Desktop, it should now read the smart card and ask you to enter your PIN, after entering the PIN you should be able to logon to your Windows 10 machine. If it doesn’t work, try taking out the smart card and inserting it again.

Now this resolved my issue with connecting to my Windows 10 Virtual Desktop from my Mac Desktop. But later on I faced another issue, when I lock my Windows 10 machine, after sometime it stops accepting my Smart Card and gives me either “No valid certificates were found on this smart card” or “The requested key container does not exist on the smart card” error. I haven’t found a workaround for this and am still looking to see what event it generates to maybe trigger my task on that event too. But for now, whenever I receive these errors while trying to unlock my Windows 10 machine, I just disconnect the session and reconnect and it works fine. I will update my post if I am able to develop a workaround for this.

Remote Desktop Error 0x207

This workaround should work on Windows 2012 R2 also, the difference is that Windows 2012 R2 server may generate some other event in the event log other than “9027” and you would have to look for that and configure your task to trigger on that event instead.

If you need help, please don’t hesitate to contact me. I would also like to request that if you find a better workaround, please let me know.

Until Microsoft or Apple (whoevers the issue is) resolves this issue, I am using this workaround.

Thanks for reading my post!

Sharing your screen remotely is a convenient way to access another computer as if you’re sitting in front of it. OS X and Windows have this ability built right into them, meaning you can easily share your Mac’s screen with Windows PCs, and vice versa.

Connecting to Windows PC Clients from a Mac

To connect to a Windows PC, you must first turn on remote connections. Open the System Properties and click the “Remote” tab, then make sure “Allow remote connections to this computer” is enabled.

You also want to make sure you install the Microsoft Remote Desktop client on your Mac. It is available in the App Store.

Remote Desktop will be installed in your Mac’s Application’s folder. In our example, we’ve already set up a user profile, which is ready for action. Let’s take a moment, however, to click “Edit” and show you what’s involved.

Next to “Connection name” we give it a friendly name while the “PC name” is either the name we gave our target PC or its IP address.

We don’t worry about configuring a gateway because we’re connecting to our PC within our local network. Also, if you do not want to enter your user name and password every time you connect, you can add them to the “Credentials.” Not entering any credentials means that when you connect to your Windows machine, you will need to log into an account.

If you want to know what your PC’s name and/or IP address is, you need to check. Use the keyboard shortcut “Windows + R” and then type “cmd” to open a command prompt. In the command prompt, type “ipconfig” and hit “Return.” You want to use the IPv4 address it gives you.

If you can’t remember what you named your computer, you can find that information on the “System” control panel.

The rest of the Remote Desktop connection’s settings concern resolution, colors, and full screen options.

When you connect to a new client, you’ll likely see a Verify Certificate dialog. Click “Continue” to connect.

If you don’t want to see this warning dialog in the future, click “Show Certificate” and then check the “Always trust …” option as shown below.

To confirm changes to your certificate trust settings, you will need to enter your system password.

Remember, if you didn’t previously enter anything in the connection credentials, you will see the login screen when you first connect. Once you’ve successfully connected to your Windows PC from your Mac, your Windows desktop will appear.

As we mentioned, being able to connect to a Windows machine is a pleasant convenience. For example, your Windows PC may be a super beefy machine you use to do compiling or rendering. You can use remote desktop to check on a job’s progress or start tasks without actually being physically at the machine.

Connecting to a Mac from a Windows PC

Connecting to a Mac from a Windows PC is a little different. You’re not going to be able to use Remote Desktop, but that’s okay because there’s a free client called RealVNC viewer that does the trick nicely.

Just like with Windows, you first have to set up your Mac for screen sharing. Open the “Sharing” preference panel and check the box next to “Screen Sharing.”

Click “Computer Settings…” and make sure “VNC viewers may control screen with password” is checked. Then enter a simple password.

The VNC Viewer requires installation, but you don’t have to sign up for an account to use it.

Recall from the earlier screenshot that our Mac’s screen can be accessed at 192.168.0.118 or Matt-Air.local. If you’re unsure how to access your Mac, go back to your Sharing preferences and double-check the information on the Screen Sharing settings.

We enter “192.168.0.118” in our VNC client and leave the encryption as it is.

The RealVNC Viewer application has a plethora of options you can peruse at your leisure.

You’ll probably be fine leaving them as is, though, if you want your connection to automatically open full screen, you need to tick the box next to “Full screen mode.”

We return to our connection and click the “Connect” button. An authentication box will appear where you will need to enter the simple password you created in the Sharing preferences on your Mac.

When you connect to the target Mac, you will also need to log into a (presumably yours) user account, just like we had to do with Windows (if we didn’t supply our credentials).

Once logged in, your Mac desktop will now appear in the VNC Viewer window in the same state as you left it.

If you mouse to the top-middle of the window, you can spawn extra controls, which when you hover will give you a tooltip explaining what each one does.

You’ll find handy shortcuts to close and save the connection, as well as to change options, and a full-screen button so your shared desktop fills the screen.

On the Mac side of things, a Screen Sharing icon will appear in the menu bar. This lets you quickly and easily access the Screen Sharing preferences or disconnect clients.

It’s important to remember that sharing a computer screen is really only suited for short bits of work. If you were trying to remotely repair something or show another user how to do something, it’s ideal, but to get any meaningful work done, not so much. You will always experience a little bit of lag and stutter, and there’s not a whole lot you can do about that.

Like we said, however, it’s not intended for heavy-duty work. Keep in mind also, we’re only sharing our screens locally, which means that if you leave the house, say to go get coffee, and you realize you need to connect to a machine at home, you’ll need to know how to connect to it through your router.