All Answers

@Michael,

By chance are any of the client machines where you are seeing this issue still running Windows 7? If so, then you’ll need to make sure that KB2857650, KB2830477, and KB2574819 are all installed on them otherwise the RADC web feed will NOT work from them.

I’d also make sure that the Essentials server itself has all of the latest Windows Updates installed on it, and that you are running the latest version of WSE RemoteApp 2012 R2 (which is Version 1.255.1550 as of this writing).

Other than that, I’m afraid that I’m stumped seeing as I can’t reproduce the problem here on any of our in-house test servers (or clients).

UPDATE #3: KB4284848 has now been released and it addresses the following issue on Windows 10 1803 clients:

Addresses issues with the Remote Desktop client in which pop-up windows and drop-down menus don’t appear and right-clicking doesn’t work properly. These issues occur when using remote applications.

Therefore, please make sure that all of your Windows 10 1803 clients have the latest set of Windows Updates installed (including KB4284848) in order to successfully use WHS / WSE RemoteApp from them.

I had a similar issue where I needed some things to be set up for specific users.
The simplest solution was to write a batch file with the specific user settings and then publish that instead of the application itself.

For example. Copy the below lines into Notepad, change the usernames and command lines as needed, then save as something like StartApp.bat. You can then publish that batch file.

if “%username%”==”UserName1” c:\Program\Appname.exe /SomeNumber

if “%username%”==”UserName2” c:\Program\Appname.exe /SomeOtherNumber

Correct. It is installed on the Essentials server and it all works when using the Microsoft Remote Desktop 8 from the Mac App Store. However, Microsoft Remote Desktop 8 is being deprecated and you have to use Microsoft Remote Desktop 10 on the Mac, the one Microsoft is going to continue to support and update.

When I log in to the server from my MacBook using MRD8, I get the WSE RemoteApp window that is served to the client from the server… when I log in to the server from my MacBook using MRD10, it takes me to the server desktop… I need it to open the WSE Remote App window as served to the client from the server… see attached.

It doesn’t do this with the new MRD10 on the Mac.

My apologies… When you wrote “WRD 10 for the Mac“, I assumed that you were talking about Microsoft Word. I now see that you were actually talking about the Microsoft Remote Desktop (MRD) for Mac client app.

If the older v8 Mac client app was working for you, but the newer v10 Mac client app isn’t, then that indicates to me that the problem lies with the v10 Mac client app itself (and has nothing to do with WSE RemoteApp per se). In addition, I’m also seeing others reporting similar problems with being able to connect to RemoteApp programs (as well as standard Remote Desktop connections) from the latest release of the v10 Mac client app now showing up over in the Remote Desktop clients Microsoft TechNet form.

Therefore, I’d say that you’ll probably just need to hold out until Microsoft releases a newer version of the v10 Mac client app that hopefully corrects the connection issues. As far as I can see, the v10 Mac client app is still a relatively new(ish) release, and so it may just be experiencing some “growing pains” at the moment. I’d just keep checking for updates on the v10 Mac client app and then try it again once Microsoft releases a newer version (or two). As of this writing, the current release is version 10.2.1 (released on August 6, 2018):

Microsoft Remote Desktop for Mac

Also, are you sure that your Essentials server has all of the latest Windows Updates installed on it? Microsoft has been correcting a lot of security issues lately with the CredSSP feature in Windows (in order to deal with encryption oracle remediation protection). CredSSP is what is used by the Mac client app in order to validate your credentials when you sign in to the Essentials server.

Lastly, have you changed any settings from their defaults over on the “Security” tab of the “Remote Desktop Session Settings” task that’s located on the “WSE REMOTEAPP” page of the server Dashboard? By default, the top five checkboxes on that tab are all checked, and the bottom four are unchecked.

Please include a screenshot of the error message that you are seeing (making sure that the “More Information” section is expanded). Also, is there anything special about your Essentials server setup that I should be aware of (language, version info, Windows Updates installed, other add-ins installed, etc., etc.)?

Also, have you ever attempted to manually install Work Folders on your Essentials server in the past?

I’m not seeing any issues here with using WSE WorkFolders to enable Work Folders on a fully updated out-of-the-box Essentials 2016 (or Essentials 2012 R2) server install (i.e. I’m not currently able to reproduce the problem here, so any additional information that you can provide me with may help me to get an indication as to what may be happening on your Essentials server).

I tried the steps above and no luck, I had two clients online at that time and none of them got the WSE RemoteApp installed.

Any help would be appreciated.

I just upgraded to Windows Server 2016 Datacenter and bought a new license for WSE RemoteApp. It used to work on Windows Server 2012 R2.

Regards

Alas, I’m not able to replicate this one here, and to date, no one else has mentioned a similar problem that I am currently aware of (and so it should be working). So… About all I can think of to tell you to try is the following:

1. Try restarting both the server and the client just to see if that happens to shake things loose for you.

2. Make sure that both the server and the client have all of the latest Windows Updates installed on them (or that you are using the latest release of whatever client it is that you are connecting to WSE RemoteApp from – such as the Microsoft Remote Desktop app, etc.).

3. Are you certain that you are redirecting the clipboard (via Remote Desktop Options) when you initiate your WSE RemoteApp connection?

Probably the easiest way to check this is to simply open the WSE RemoteApp Launcher, click the large icon that’s located up in the top left hand corner of its main window in order to display its context menu, and then click on the “About” item in the popup menu that appears.

In the WSE RemoteApp Launcher’s About dialog box that appears, click on the “Show connection details” button, and then look at the list of “Options” that are shown. If your remote session is set to redirect the clipboard, then “Clipboard” should be shown within that list of Remote Desktop Options.

Other than that, can you tell me exactly how you are connecting to WSE RemoteApp from the client computer (i.e. are you connecting locally from the Windows client’s Start menu or desktop shortcuts for WSE RemoteApp, are you connecting remotely via your server’s built-in Remote Web Access website, are you connecting remotely via WSE RemoteApp’s RADC web feeds feature and a RADC client)?

Lastly, what version of WSE RemoteApp are you currently running, and what version is your client (e.g. Windows 10 1803, etc.)?

Hi Mike,

I tested my issue on other PC’s and they don’t have this issue. So, the issue is apparently linked to my client PC….

A remote desktop session via the same VPN tunnel to the server doesn’t have the issue.

Hi again,

I solved the issue. I removed the client software on my computer and had it re-installed by the server. Everything works fine now.

Grtz,

Bart

How can i update a starter edition to an basic edition ?

I dont have this option in the basket ?????

Both computers are on latest versions of windows:

1. Client – Windows 10 Pro 1803
2. Server – Windows Server 2016 Datacenter 1607

And the version of Outlook is – 2016 16.0.9126.2336

Another thing I forgot to mention is my client machine has two monitors.

The other issue I started noticing is when I have a window behind Outlook and I move the mouse over outlook it randomly shows me the window behind it, for example a browser. It’s kind of doing Alt+Tab on it’s own. Could be  a related issue.