All Answers

WSE RemoteApp doesn’t currently support the redirection of client-side smart card devices I’m afraid. We’ve never had a single request for this up until now (and Microsoft doesn’t even offer it within the default “Essentials” experience). I’ll certainly look into adding smart card redirection to a future release of WSE RemoteApp for you though.

disregard the last answer, the server essentials services were stopped

tried to run the installer again, and it susceeded

thanks for your help!

By default, access to a published RemoteApp program is indeed granted to all users that have been “allowed” access to WSE RemoteApp. To change that behavior (i.e. to assign only a specific set of users access to a published RemoteApp program), simply open the server Dashboard application, go to the “WSE RemoteApp” page, click on the “RemoteApp Programs” subtab, select (i.e. highlight) the published RemoteApp program of interest, click on the “View the RemoteApp program properties” task (or you can simply double-click on the published RemoteApp program instead), and on the second page of the “RemoteApp Properties” wizard that opens you can set the User Assignment of the RemoteApp to specified users.

Pricing for all of our products can be found on our Pricing page. Simply select your Windows Server operating system version, and then scroll the resulting page in order to find all of the pricing details.

Absolutely! WSE RemoteApp works just fine when your client computers are not domain joined.

That being said, WSE RemoteApp works best if you set up your non-joined client computers so that they use the exact same sign in credentials as the server’s user account. For example, if your user name on the server is “Joe“, and your password is “joe’spassword1234“, then use those exact same credentials to sign in to your client computer as well. Doing so, will make things go much smoother for the end user.

However, if you prefer to use a Microsoft account to sign in to your client computers, or if you choose to use a different set of sign in credentials than what’s being used for the user over on the Essentials server, then the user will first need to open the Launchpad application (by right-clicking on the Windows Server Essentials Connector icon that appears down in the notification area of the Taskbar, and choosing “Open Launchpad“), and sign in there before they will be able to successfully connect to WSE RemoteApp (i.e. it will require one extra sign in).

The RemoteApp sessions do indeed run in the security context of the authenticated users (and not in a System or Administrator context). You can allow users with administrator rights to connect to WSE RemoteApp, but doing so is certainly not recommend (for security reasons). And the security context remains the same (i.e. at the User level) even when you have enabled the add-in’s “multiple simultaneous connections” feature (with each user being allowed a single remote session).

That doesn’t sound like a problem that is related to WSE RemoteApp 2016 seeing as the add-in does not use a registry key named “ADTestHook” (i.e. I have no idea what that registry key is for/from, and I’m not currently able to replicate the problem you’re having here on any of our in-house test servers).

Have you tried uninstalling WSE RemoteApp 2016 just to see if the problem goes away or not? If the problem does not go away after uninstalling WSE RemoteApp 2016, then it’s obviously a problem with the setup/configuration of your server (or more specifically, with its Anywhere Access/Remote Web Access setup/configuration) that has nothing to do with WSE RemoteApp 2016.

Also, are you running the latest version of Windows Server 2016 (Essentials or Standard/Datacenter with the WSEE server role) with all of the latest Windows Updates applied (i.e. Version 1607 – OS Build 14393.693)? And the latest version of WSE RemoteApp 2016 (i.e. Version 1.255.1278.3)?

Alternatively, you might want to try restoring your server from server backup back to the state it was in before you installed the latest set of Windows Updates (i.e. back to a date/time before you started having the aforementioned problem).

WSE RemoteApp 2012 is a standard Windows Server 2012 Essentials add-in (with both a server-side and a client-side component). It is installed just as any other Windows Server Solutions .WSSX add-in is.

Basically, you just execute the “WSERemoteApp2012.wssx” file (that you downloaded from here) from any of your client computers that have the Windows Server Essentials Connector software (i.e. the Launchpad) installed on them. The installer will then copy all of its files over to the server and install the add-in’s server-side component on the server itself. The server will then distribute the add-in’s client-side component back out to all of your client computers (that have the Launchpad installed on them), and install it on them as well (adding shortcuts to the add-in on the client computer’s desktop, Start menu, and Launchpad).

If you are not able to execute the “WSERemoteApp2012.wssx” file from your client computer, that probably means that you either do not have the Windows Server Essentials Connector software (i.e. the Launchpad) installed on it, or if it is installed, then it is probably not properly connected up to the server. Alternatively, you can also start a standard Remote Desktop Connection with your server, sign in as a user with admin rights, and execute the “WSERemoteApp2012.wssx” file directly from the admin user’s server desktop instead.

To uninstall WSE RemoteApp from the server and from all computers on the network:

1. Make sure that all of your client computers are online and connected to your Essentials network so that the client-side (i.e. Launchpad) components of the add-in can be removed from them.

2. Open the server Dashboard and go to the “APPLICATIONS” page.

3. Select (highlight) the “WSE RemoteApp” add-in in the list of installed add-ins.

4. Click on the “Remove the add-in” task and follow the on-screen prompts.

5. Restart the server Dashboard application to finish uninstalling the add-in.

6. Restart the Launchpad application on each of your computers on the network to finish uninstalling the add-in. This can be done by clicking on the ‘X’ located in the upper right-hand corner of the Launchpad application’s window, and then double-clicking on the Windows Server Essentials Connector notification area icon to open it again (or by right-clicking on the Windows Server Essential Connector notification area icon and selecting “Open Launchpad” from its context menu).

NOTE: If it is not possible to have all of the computers on the network online, then you can manually uninstall the client-side components of the add-in from any computer on the network at a later time by uninstalling the “Client Connector for WSE RemoteApp …” program via the Control Panel’s “Programs and Features” (“Add or Remove Programs“) applet.

Lastly, please note that uninstalling WSE RemoteApp will remove all of its published RemoteApp programs and settings. Therefore, you might want to make a note of the applications that you currently have published (as well as any properties/settings that you may have changed) so that you can publish them again once you have reinstalled the add-in.