Although device management is enabled, the process to deploy the Remote Assistance Settings Profile remains indefinitely pending. All devices report successful check-ins, yet the inventory update is missing and no managed policies are recorded. Furthermore, troubleshooting is challenging since most devices are located in India while I operate from the USA. This geographic separation has made resolving the issue extremely difficult despite extensive attempts with local users.
hey, i had a simlar problem. sometimes the client agent doesnt update fully even tho devices chk in. try checking if any agent updates or permission issues might be blocking the inventory update. a reinstall helped me once. hope this gives u a lead.
hey, i faced something like this before. check your tz and syn schedule, might b a misconfig. sometimes a minor firewall or network hiccup stops the inventory update even when devices chk in. give it another look.
Hey ClimbingMountain, I’ve been mulling over your issue and I can totally see how frustrating it can be, especially when you’re dealing with a geographical gap like that. It makes me wonder whether the Remote Assistance Settings Profile might be getting delayed or even blocked by some subtle network or time sync misconfiguration that’s not immediately obvious. Have you had a chance to try forcing a manual inventory update on one of the remote devices? I’m curious if that might shed some light on whether the problem is purely on the policy application side or if it’s a broader communication hiccup. Also, sometimes digging into any available logs on the client side can hint at what might be tripping things up. Could it be that the remote devices are silently failing a step in the process? I’d love to hear if anyone else has encountered a similar scenario and what they discovered. What do you think might be the next step to test out your theories here?
The scenario seems to challenge the server-client communication at a deeper layer. In my experience, the persistent absence of an inventory update combined with policy non-application might indicate a more serious back-end syncing error or misconfiguration at the management server. I have seen cases where some network proxy or even a misconfigured certificate delayed profile delivery. A systematic check of device logs often reveals intermittent issues that are easy to overlook. Given your devices are geographically diverse, even a slight difference in regional settings might compound the problem.