Oct 21 2020 06:36 AM - edited Oct 22 2020 06:11 AM
Hi everyone,
I've created a particular Proactive Remediation script set and deployed it. It's marked as active and is assigned to a test group. However, after two days, it still indicates that there are no devices pending and none have completed it. The scripts contains logging as well, which is not present on the target machine (the only in the testing group).
For some unknown reason, the Proactive Remediation item simply isn't applying to the group. I removed and reassigned the group at some point to see if it would accomplish anything. But it netted no difference.
I do have another Proactive Remediation that is working, and I did no different in setting it up. So, I'm not sure why it is fine and deployed to the machines without issue while this new one is hung-up.
Any suggestions would be much appreciated.
EDIT: After two and a half days, it simply just started working. It appears to have been some extensive delay on the Intune/Endpoint Manager side.
Nov 13 2020 11:56 AM
@devinm_ I have similar situations where proactive remediation were slow 30/300 computers for almost 3 weeks and suddenly increased to 245 and again slowed down. Have a ticket with MS and waiting for an update from them on this
Dec 29 2020 01:21 PM
Hi @Ambarish RH,
Did you hear back from MS with respect to your ticket? I'm curious what they had to say about it.
Regards,
Devin
Jan 03 2021 10:42 AM
Jan 06 2021 10:04 AM
Feb 08 2023 08:53 AM
Feb 08 2023 11:36 PM
Feb 09 2023 05:06 AM
@Rudy_Ooms_MVP So when it comes down to it, we cannot tell the users that on this day and time, you are going to get a message (provided through the remediation script) on your screen warning you that we are about to stop all the office365 apps so intune can redeploy to resolve missing app issues etc.
We have found that the Intune app deployment will not run successfully because it cannot install with the apps running (Teams primarily is the culprit).
I have created a remediation script to go through all the processes and stop anything with a name -like any of the O365 apps. It runs successfully when it runs but predicting when it will run the first time (or second or third) is impossible, even with my test machine(s) right in front of me, logged in with the apps running.
Feb 09 2023 05:07 AM