One2Many Plan - Computers getting removed if added to multiple plans
This is in relation to an issue observed with one of the features in LogMeIn : One2Many à Plans
Case 1:
For any One2Many plan which is planned for future deployment, a specific task is selected and the required target computers are added in the One2Many plan followed by the scheduled date and time for future run. Let’s call this Plan A.
Now let’s take another One2Many plan (let’s call it Plan B) is created with some target computers which are already part of Plan A. Now, it is observed, the computers which are common in both plans, are automatically being removed from Plan A which is scheduled for a future run.
Now in these situations, Plan A is again re-created by adding all the required computers. But this again result in computers automatically being removed from Plan B.
However, this phenomenon is not observed all the time, but 90% of the cases are observed with this. This kills a lot of time keeping the plans up-to-date with right computers for a single execution. There are multiple LMI administrators under a single account holder who make use of this feature and creates and schedule multiple One2Many plans for future deployments. We all have to keep updating the plans multiple times before the scheduled run.
Case 2:
However, if multiple plans are created by adding a LogMeIn group, instead of selectively adding some computers, it never cause any issues.
Question for LogMeIn:
- Is it true that a single computer cannot be part of multiple One2Many plans?
- What could be the possible reason for the above said observation? Is it something related to overlapping time while creating multiple plans that causes this?
- Any workaround available to overcome this issue?