Fixing a little agent mishap

Since the upgrade of the KBOX 1000 from 5.1 to 5.2, the MSI installers which were customized for our environment were automatically overwritten with the new -- uncustomized -- agent. Since that upgrade, we went ahead and deployed the new agents. This resulted in some mis-configured KACE agents, and this specific issue was causing some machines to not show up in the KACE inventory. This was all due to my lack of knowledge about the automatic replacement of agents. Oops....

I have added a function into the login script that would check the configuration file, and will replace it with a working version upon login.

The configuration of the KACE agent is called SMMP.conf, and is located in C:\Program Files\KACE\KBOX\smmp.conf.  The status of the configuration file is also reported in the user's login report and would state either:
"KACE (SMMP.conf) configuration file is OK"  or
"KACE (SMMP.conf) configuration file is misconfigured. Fixing"

If the configuration file is fine, no further action is taken.
If a misconfiguration is detected

• The conf file is replaced with a working one
• The KBOXSMMPService is killed
• The KBOXSMMPService is restarted
• And an Inventory action is triggered. 

If you see any weird behavior that you may think may be attributed to this change. Please let me know immediately. 

• This change was put into production 03/09/2011 @ 16:00