mirror of
https://github.com/KelvinTegelaar/CIPP.git
synced 2026-04-25 16:26:09 +03:00
[GH-ISSUE #1078] AddMSPApp: Datto RMM detection is intermittent #574
Labels
No labels
API
Feature
NotABug
NotABug
Planned
Sponsor Priority
Sponsor Priority
bug
documentation
duplicate
enhancement
needs more info
no-activity
no-priority
not-assigned
pull-request
react-conversion
react-conversion
roadmap
security
stale
unconfirmed-by-user
unconfirmed-by-user
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/CIPP#574
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @ChrisFoulstone on GitHub (Aug 24, 2022).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/1078
Description
The current deployment of Datto RMM works fine most of the time. In odd cases, like during recent Datto platform instabilities, it's possible that the AEMAgent.exe exists in programdata, but the associated service has not managed to initialise properly. In this case, the device obviously does not report into DRMM.
Adjusting the detection to path
%programfiles(x86)%\\CentraStageand fileCagService.exe.confighas provided more reliable results. MEM will then retry the installation if there is a failure due to those odd instances.Environment data
@github-actions[bot] commented on GitHub (Aug 24, 2022):
Thank you for creating a bug. Please make sure your bug is indeed a unique case by checking current and past issues, and reading the complete documentation at https://kelvintegelaar.github.io/CIPP
If your bug is a known documentation issue, it will be closed without notice by a contributor. To confirm that this is not a bug found in the documentation, please copy and paste the following comment: "I confirm that I have checked the documentation thoroughly and believe this to be an actual bug.".
Without confirming, your report will be closed in 24 hours. If you'd like this bug to be assigned to you, please comment "I would like to work on this please!".
@ChrisFoulstone commented on GitHub (Aug 24, 2022):
I confirm that I have checked the documentation thoroughly and believe this to be an actual bug.
@KelvinTegelaar commented on GitHub (Aug 25, 2022):
Changing in next major release. :)
@ChrisFoulstone commented on GitHub (Aug 25, 2022):
Awesome, thank you