Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 8 Next »

Problem

A manually created blacklisting or deny execute policy that has no application targets will apply to all programs and services and prevent them from running on an end-user's machine. If a new deny execute policy is created and enabled with out limiting the application target scope of the policy or is not being used with a proper whitelist, the bad blacklist policy will get rolled out and begin denying execution of all applications. This include userinit.exe which will prevent users from logging in after a reboot. Those computers will act as if they are frozen because no new processes can get created.

Solution

  1. First login to the Arellia Management Console on the Server and disable the bad Blacklisting Policy.
  2. After the policy has been disabled, each of the endpoints need to do a configuration update so they remove the bad policy.
    1. The easiest way to do this is to run an Update Client Configuration task on each of the endpoints. To do this, simply create a new Update Client Configuration Task to run ASAP and schedule it to run now on all machines, or on machines that are known to have the bad blacklist.
    2. Alternatively, you can do it manually by following these steps:
      1. Restart the computer that has been effected by the Blacklisting Policy in Safe mode.
      2. Open the Administrator Tools in the Control Panel and then Services.
      3. Find Arellia Application Control, right click and select Properties.
      4. Change the Startup Type to Disabled, Click OK and restart the computer.
      5. After restarting the computer right click on the Symantec Management Agent icon in the taskbar and select Symantec Management Agent Settings and then click Update to update your policy.
      6. You should now be able to open all the programs and services that were previously blacklisted.
      7. Open Services again from the Control Panel and change the Arellia Application Control Startup Type to Automatic.
  3. Restart the endpoints. After the endpoints have been restarted everything should work normally.

More information onĀ how to configure blacklisting policies

  • No labels