6.4 Application Policies
In companies, administrators may want to restrict certain applications, such as BitTorrent clients, download tools like Thunder, chat software, or games. Application control policies can limit client machines from running these programs.
Applications
By default, newly added policies apply to all applications. Administrators must specify which applications to control. There are three ways to enforce application restrictions:
1. By Process Name
Administrators can add the application's executable name, e.g., thunder.exe. The policy works via string matching. If the client renames the program (e.g., thunder123.exe), the policy will not apply. To avoid this, use the second method.
2. By Application Category
Administrators select a category containing all applications to block. Even if the client renames the executable, the policy remains effective as long as the program itself is unchanged.
3. By Execution Path
Administrators can specify a path, e.g., Block APPDIR:e:\*.exe to block all programs on the E: drive. Similarly, to block all programs on the H: drive, set the policy to Block APPDIR:h:\*.exe.
You can also use $UDISK$ to represent USB drives and $CDROM$ for CD-ROMs.
Examples:
APPDIR:$UDISK$:\*.exe — blocks all programs on USB drives
APPDIR:$CDROM$:\*.exe — blocks all programs on CD-ROMs
Services
Application policies can also control the running of services on client machines. When setting the policy, enter the service name in the application field using the format:
SERVICE:ServerName;
Example: To block the service bthserv, enter SERVICE:bthserv in the application field.
Notes:Use English half-width characters when typing.SERVICE must be uppercase; otherwise, the policy will not take effect.ServiceName refers to the service’s actual name, not its display name.
Warning:
- Blocking all applications will disable most processes. To prevent potential issues, configure this policy with caution.
Warning messages can include the name of the process that triggered the policy. To do this, insert $APPNAME$ in the message. For example, if a policy blocks QQ.exe and the warning is set to: "Company policy prohibits running this process: $APPNAME$", then when the client tries to run QQ.exe, the message displayed will be: "Company policy prohibits running this process: QQ.exe".
Don't see what you're looking for?