Environment
- App Control Agent: All Supported Versions
- Microsoft Windows: All Supported Versions
Objective
How to manually import the Configlist on a Windows Agent.
Resolution
Pull Directly From Server: For Agents that are Connected & otherwise healthy:
- Log in to the endpoint and launch a command prompt.
- Issue the following commands:
cd "C:\Program Files (x86)\Bit9\Parity Agent"
dascli password GlobalPassword
dascli configlistrefresh
- This will pull the Configlist directly from the App Control Server.
Import via Dascli: For Agents that are not Connected, or otherwise having issues:
- Acquire the latest Configlist from the application server's directory: \Bit9\Parity Server\hostpkg\configlistwithdeleteditems.xml.egk
- Place the file somewhere on the endpoint, example: C:\Temp\
- Issue the following commands:
cd "C:\Program Files (x86)\Bit9\Parity Agent"
dascli password GlobalPassword
dascli importconfiglist "C:\Temp\configlistwithdeleteditems.xml.egk"
Import On Service Start: For Agents that are not Connected, or otherwise having issues:
- Acquire a copy the latest Configlist from the application server's directory: \Bit9\Parity Server\hostpkg\configlist.xml
- Use an administrative command prompt to issue the following commands:
cd "C:\Program Files (x86)\Bit9\Parity Agent"
dascli password GlobalPassword
dascli tamperprotect 0
net stop parity
- Rename the copy of configlist.xml in the directory: C:\ProgramData\Bit9\Parity Agent\configlistfull.bt9
- Start the Agent service in the administrative command prompt:
net start parity
- After the Agent ingests the file, it will be recreated as: ConfigListBackup.bt9
Related Content
