Starting with Netop Host version 12.72, you can whitelist specific running applications as part of any role definition on the Host. Through whitelisting, a Guest user remote controlling the Host will only be able to see and control the whitelisted applications. Both keyboard and mouse will not be transmitted to other applications except the whitelisted ones and any non-whitelisted application will be masked out from the remote view.
Configuring application whitelisting
- Netop Host version 12.72 or newer
- Any of the following Guest Access Methods should be used on the Host:
- Grant All Guests default access privileges
- Grant each Guest individual access privileges using Netop authentication
- Grant each Guest individual access privileges using Windows Security Management
- Grant each Guest individual access privileges using Directory services
Recommended but not required:
- Netop Guest version 12.72 or newer
The steps below are to be executed on the Netop Host.
- Go to your Netop configuration files folder. Here is the default path to the Host's configuration files by Windows operating system:
Windows 7 32-bit, Server 2008 32-bit, Vista 32-bit
C:\ProgramData\Netop\Netop Remote Control\Host
Windows 7 64-bit, Server 2008 64-bit, Vista 64-bit
C:\ProgramData\Danware Data\C\Program Files (x86)\Netop\Netop Remote Control\Host
- Create and edit a file called whitelisted.txt
- Add the applications which should be accessible by the Remote Control users, one per line. See below more details on how to edit the whitelisted.txt file.
- in the Host, access Tools - Guest Access Security , and choose one of the above Guest Access Methods
- Either change an existing security role, or create a new one
- On the right side of the security role definition, choose Yes for the Whitelisted applications option
- Add users or groups to the above security role. Those users will only be able to access the whitelisted applications.
Note that you can still have other security roles which provide full access to the Host.
Things to consider
- Certain functionality of the Windows operating system (such as: Windows taskbar, logon/lock screen, screen saver, Start Menu) will not be available by default through whitelisting; make sure these are not needed by a remote user, when enabling whitelisting
- Windows 8 Metro applications cannot be whitelisted
- Some functionalities of the Windows operating system will be disabled by default in a Remote Control session with whitelisting, to provide an optimum experience for the user, such as Aero Peek; the keyboard will be automatically switched to Local Keyboard in order to avoid triggering commands which will mask out whitelisted applications, such as pressing the Start menu, CTRL-ALT-DEL or ALT-TAB shortcuts
- if a whitelisted application is completely obscured by a non-whitelisted application, the remote user will not be able to access it, without help from a local user on the Host device; in this case, a gray masking is shown over the obscured area of the whitelisted application, as can be seen in the below image.
Defining the whitelisted applications
Whitelisted applications are defined in the whitelisted.txt file, one application per line, in any of the following ways:
- full path of the application (including the executable name). For instance: C:\Windows\System32\notepad.exe
- executable name. For instance: notepad.exe
- any of the above, including system environment variables. For instance: %windir%\system32\notepad.exe
Customizing the whitelisted.txt location
If you would like to have the whitelisted.txt file in a different location than the Netop configuration files folder, you can customize it in the netop.ini configuration file.
To do that, edit the netop.ini file located in C:\Windows. Open this file using Notepad and look for the heading [HOST]. Under that heading add WHITELISTING_FILE=[file path], where [file path] represents the new location for the whitelisted.txt file. In the end, netop.ini should contain something like: