IMPORTANT ANNOUNCEMENT: On May 6, 2024, Carbon Black User eXchange (UeX) and Case Management will move to a new platform!
The Community will be in read-only mode starting April 19th, 7:00 AM PDT. Check out the blog post!
You will still be able to use the case portal to create and interact with your support cases until the transition, view more information here!

Bit9 agent shows as Policy Mode = Agent Disabled on the Bit9 console

Bit9 agent shows as Policy Mode = Agent Disabled on the Bit9 console

Version:

 

7.x

 

Issue / Symptoms:

 

Bit9 agent shows as Policy Mode = Agent Disabled on the computer details page on the Bit9 console even though the "dascli status" confirms that the Bit9 agent is connected and on a non-disabled policy.

 

Cause:

 

A previous upgrade through SCCM had set the flag on agent to be on disabled mode but the flag did not reset after the completion of the upgrade.

 

Solution:

 

On the endpoint, open a command prompt and change directory to %Program Files%\Bit9\Parity Agent. Run "dascli status" and confirm that the agent is on a correct policy, Connection shows Connected, and Session shows Active.

 

Use the following SQL script to reset the flag on the DAS database for those agents that are showing with Policy Mode = Agent Disabled:

use DAS

UPDATE hostmain

SET uninstall_date = NULL

WHERE uninstall_date IS NOT NULL

AND upgrade_state & 8 = 0

Important Note(s):

 

Verify that the agent is enforcing the policy properly. The SQL script above is only to reset the Policy Mode value on the DAS database to reflect the correct enforcement policy currently applied on the Bit9 agent.

Labels (1)
Was this article helpful? Yes No
No ratings
Article Information
Author:
Creation Date:
‎12-04-2014
Views:
1453
Contributors