lags7
New Contributor
Joined 7 years ago
User Profile
User Widgets
Contributions
Re: One2Many tasks not starting
AshCIts been more thana year, me and my team are still stuck with this issue. The count of these affected hosts are now increased to 40. We have re-installed logmein agents on all these affected hosts, and have made sure they are on latest versions. Also there is no firewall restrictions and required IPs are whitelisted. I have sent multiple emails to LogMeIn support in the past 1 year and had tried reaching on support number, but no response and no resolution so far. Are there any troubleshooting steps to try it out. Your help is urgently needed.1.2KViews0likes0CommentsRe: One2Many tasks not starting
AshC - These are on Windows 10 Enterprise. These are Point-Of-Sale devices which run 24/7. I am responsible for managing these stores remotely through LogMeIn. So, its pretty difficult to re-install LogMeIn at the site, as I would loose the remote connection. We would be dependent on a technician to do this at the store. Re-installing LogMeIn would be my last option to try.4.9KViews0likes6CommentsRe: One2Many tasks not starting
Hi AshC, I am also experiencing the same issue with 4 hosts out of 1200 hosts. In fact all users in our LogMeIn account are experiencing this problem with these 4 hosts. 1. All the tasks are being run with Administrator account with correct credentials 2. The tasks being run are simple as a checking the OS name with a simple batch command or very small files distribution (in KBs). Around 40+ tasks are being run periodically for all hosts weekly, but only these 4 hosts fail to run. The status shows "Pending" even if the hosts are online and get aborted when the tasks reaches timeout. 3. I also confirm all hosts are whitelisted to allow communications, and there is no group policy or firewall in place that restricts 4. I had also captured the debug logs for the affected hosts while performing the tasks, and had shared with LogMeIn L2 support (Juliana & Maria). Also did remote sessions with them to demonstrate the issue directly to them, and have been following up constantly for a resolution. I never get back any answers from support no matter how many time I had been following up. This is the ticket number for this case : 09307148 Could you advise per your expertise if there are any workaround for this issue. Thanks in advance!4.9KViews0likes8CommentsRe: One2Many Plan - Computers getting removed if added to multiple plans
AshCI am able to create multiple plans, however if the computers are part of more than 1 plan, the former plan automatically removes the computer. I have exeperienced almost every time I am creating plans. To answer your query, I am creating plans from scratch. Also each computer is already part of one group. For running plans, it is not feasible and worth spending efforts in assigning the required computers to a new group. Moreover this is a recurring activity every month, and consumes a lot of time and does not even assure the plans stay intact after creating for the first time. I am spending a lot of time in keeping a check before the actual scheduled day and update if any computer is removed automatically. This is frustrating.1.9KViews0likes0CommentsOne2Many 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?2KViews0likes2Comments