![]() ![]() You can then use something like this to query for the exe you are looking for, which will change over time with new OneDrive releases: (Get-ChildItem -Path "$\\Microsoft OneDrive" -Filter FileCoAuth.exe -Recurse).FullName Again, if suppressing the prompt is not sufficient enough and you either find that features do not work as you wanted, or you wish to set a firewall policy anyway, then after performing the above suggestion about getting the binary installed at the system level, depending on your licensing, you have two further options to handle this:įunctionally, the concept is the same, in that you are running a PowerShell script on a specific cadence, but Proactive Remediations offers you more in direct reportability back to your console. That said, despite the single rule mentality, you have to recognize that the path will change, even within that directory, because it is based on a version-number folder, not a root folder. Not that you can't do a user-based firewall rule, as you certainly can via script (I did one for Teams, probably like you did), but now you are talking about a single firewall rule that should apply to all users in the system, instead of needing distinct rules for each user's individual copy of the binary. ![]() This is two-fold, one, get just a single general location and two, get it out of a place where an end-user can modify it. I can say that we have had no issues with co-authoring despite the fact that we have not made any special Windows Firewall rules for this binary and thus would be "getting blocked" inbound (which does not appear to matter in any way.)īut, assuming you don't want to just suppress the prompts, what I can suggest is that you push out the OneDrive installer to all systems using the '/allusers' switch to move the installation into "Program Files (x86)" (assuming 64-bit Windows). My group policy settings (or rather, Intune settings), suppress the notifications to the user, since it does them no good when they do not have the ability to accept the prompt anyway. I have not specifically encountered this, but that could be a matter of the prompt being suppressed from the user's view. ![]() If any of you have encountered this with a Intune only resolution, I'm all ears. I'm assuming since the remote user's device thinks they are in a Public network (even though they are just working from home), that this prompt is asking to allow it through Windows Defender firewall. In this case it is based on a user path which was the issue in the above link. I know you can create Firewall rules in Intune, and I do that via a script specifically for Teams so users don't get a similar prompt. I found one reference to this, but not with a helpful answer. This is the OneDrive configuration policy Everything is working fine, but some users are reporting Defender prompting them to allow filecoauth.exe. We are deploying Office 365 apps to devices during Autopilot and the users are not local administrators. Fairly new to Intune for the last few months and I have but one issue I can't seem to solve regarding applications. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |