9:15 CET, 1st July 2013 By Kent Agerlund, Senior consultant and Configuration Manager MVP at Coretech.
Lately I have done a lot of Secunia CSI installations. One of the questions that keeps coming up is “what client scanning options do we have, if we do not install the CSI agent locally?”. You basically have three options as described below.
You can use ConfigMgr Inventory and gather information about *.EXE, *.OCX and *.DLL files. This process will get the job done although you are gathering much more information than CSI requires. This method requires that the Site Server (where you installed CSI) have access to the Cloud based database hosted by Secunia.
Perform a network scanning works nicely in a small lab enviroment, but I often find it to be to unrealiable when working in the “real world”.
The CSI agent dosn’t really have to be installed on the local host in order to do the scanning. I often create a traditional package in ConfigMgr and run the scan on a weekly basis. This approach requires that each of the clients will have Internet access and can connect to the CSI Cloud based database. In order to run the agent inside a ConfigMgr package follow these steps:
You will be able to monitor the scanning result from the CSI console.
Visit Kent Agerlunds original blogpost on coretech.dk