Tuesday, May 4, 2010

Group issue is resolved!

Kevin from Labtech emailed me yesterday morning that he had verified that he had a workable solution for our on-boarding and do-not-touch groups.  We setup a 1 hour meeting for noon to review it with him.  The way we are accomplishing the on-boarding is to create a custom field at the client level called 'on-boarding'.  When this box is checked, all machines that are under that client will be added to the group 'on-boarding'.  The on-boarding group is a master group which will remove machines from all other groups (except other master groups) and prevent it from being added to any others.  We simply ensure that there are no active scripts/hotfixes/alarms etc in the on-boarding group and everything is good.

The do-not-touch is pretty much the same where we have a group of the same name and a customer field (at the machine level) to do the same thing. 

One thing that this requires is that you do not make any other master groups as a machine *can* be a member of more than one master group. 

Two things that I really like about this solution is that it did not require us to modify every search in the system to *exclude* the on-boarding or DNT machines and it is ust a single checkbox (so very little in manual interaction). 

We feel that the solution is going to work perfectly for us.

Thanks to Kevin from Labtech!

No comments:

Post a Comment