19:13 yeah I was thinking remote help didn’t have an unattended feature available just yet. I ran into this same issue. Moved past the notification (notif never actually shows up) and constant “connecting” screen.
Another trouble. When attempting to use remote assistant through intune to reach out to a 365 cloud pc instance. I never make it passed the “sending notification” step. Intune suite license for the user in question (so has remote help), rbac setup, remote help enabled in tennant, but consistent “failed to send notification” One thing I can think of is maybe firewall? Not too informed in setting up firewall rules from intune. I’m assuming setup the fqdn to the remote help service as a “reusable setting” that auto resolves. Then setup a rule for port 443 local and remote, using protocol 6. Then attach the fqdn to the rule? But also…would this be outbound, inbound, or both?
19:13 yeah I was thinking remote help didn’t have an unattended feature available just yet. I ran into this same issue. Moved past the notification (notif never actually shows up) and constant “connecting” screen.
Another trouble. When attempting to use remote assistant through intune to reach out to a 365 cloud pc instance.
I never make it passed the “sending notification” step. Intune suite license for the user in question (so has remote help), rbac setup, remote help enabled in tennant, but consistent “failed to send notification”
One thing I can think of is maybe firewall? Not too informed in setting up firewall rules from intune. I’m assuming setup the fqdn to the remote help service as a “reusable setting” that auto resolves. Then setup a rule for port 443 local and remote, using protocol 6. Then attach the fqdn to the rule? But also…would this be outbound, inbound, or both?