Still trying to figure out groups and searches

One of our current hold-ups is the problem with have with keeping certain machines *out* of groups.  There are two issues, first we have a client on-boarding process where we install agents, collect data and analyze the reports to look for issues (ie, server that has never been patched). Once we identify and resolve issues, we turn on the monitoring/alerting/patching/scripting.  We fell this is a prudent measure to take as we certainly wouldn't want to have a bunch of stuff blow up on the day we install our agents.

With Kaseya, it was a pretty simple process.  We always created our agents with a *do nothing* template that simply put the machine into the proper client group and audited the machine for system and patch information.  Once we had that we could determine if we needed to take any special remediation measures before we turned on the full management.

With Labtech, we have not found a way to get the machines into the system without having them automatically pulled into all of the groups that provide the monitoring, patching and scripting.  I contacted Kevin at Labtech and he is working on it.

The other issue will be solved by whatever the solution to the first problem is.  That issue is that at a few client sites there are machines that we deem as *do not touch* machines.  These would be machines like laboratory equipment machines, manufacturing automation machines, etc.  Essentially we monitor these machines and do remote remediation, but do not patch/script/reboot them as usual.  We need a way to flag these machines and keep them in special groups.

At this point I am not sure if it is the design of the Labtech groups/searches that is making this difficult, or just the fact that we are not yet aware of how to make it work.

DW