This is a known bug, at least in 41.199 and 41.202 (not sure about 41.189). Apparently they aren't going to issue a fix until the 2012 release due in April-ish.
Support gave me a "PopulateOldScriptsWithNew" stored procedure (below), and then you have to run a script on your Labtech server every Sunday morning.
For lurkers, this bug effectively silently deletes all scripts added to any group since 41.199 was installed, each week. Old scripts are left. (hmm, not sure if they bring back any that were deleted...?) A horrible bug.
Ah, found their message:
If you have sqlyog or something similar you can create a stored procedure in the Labtech database with the follwoing snip.
CREATE PROCEDURE `PopulateOldScriptsWithNew`()
insert ignore into scripts() SELECT scriptID, 0, ScriptName, '0,', '', 1, '', '', '', '0,', 0, 0, ScriptGUID, 0, 0, 0, 0 from lt_scripts where scriptID not in (select ScriptID from scripts);
Then you can create a script in labtech that will be one line that is an if True. The line will be an SQL Execute and the parameter will be: Call PopulateOldScriptsWithNew;
Then schedule this to run weekly as a client maintenance script on sundays @ 1AM and then with any new scripts created in that week they will not be removed from the group joins.
This is the current resolve that we have until the 2012 release where this will be addressed in the code.