Great video, thanks. Wording at 19:43 can be a bit confusing. Pretty sure the setting is applied during enrolment only and doesn't apply to already enrolled devices.
@MSEndpointMgr7 ай бұрын
Correct the tenant wide is only for enrollment scenario, so it wouldn't apply a policy as such on your devices if they already is enrolled. The tenant wide settings is placed under enrollment which gives a hint, but I can see that I should have been more clear on when it applies. Thanks for your comment! 😀
@marvnl7 ай бұрын
49:21 copilot for security is really expensive thus much and fast feedback from use cases will not really flushing in I believe. But I do want to see it grow to easy the troubleshooting for IT support guys, so they can discover the issue faster and less press on second or thirdline teams
@MSEndpointMgr7 ай бұрын
Agree to that. Let’s see where it is headed in the future.
@mortenwiingreen97487 ай бұрын
Hi, great video. Is it possible that you could make a special video with only "Auto update available with Win32 app supersedence". I think as an Intune admin this new feature is great, and I would like to know 100% how to use it. How do I set up the install command lines correctly for the superseeding app, see some examples etc.
@MSEndpointMgr7 ай бұрын
Hi Morten Thanks for your comment. I will ask the team if they have time to do a deeper dive into this area. But in general, supersedence is very hard to make a 100% solution do to limitation of 10 apps and not able to cleanup if older apps is in that chain, which makes a mess in the Intune console.
@IntuneGoogleAccount7 ай бұрын
Hi there, I cant seem to get my head around support approved, am i right in syaing you dont need to create a rule as it should just allow a user to ask for approval on any app ? my user can just simply double click the exe and it runs, is this normal ?
@MSEndpointMgr7 ай бұрын
Thanks for the question. Support approved first needs to be send as a enrollment policy to the client. Then your user will be able to ask for approval on any given EXE file without having a rule. If you user is able to just elevate, that might be related to your enrollment policy where you opened up to much. I usually block if there is no existing rule.
@IntuneGoogleAccount6 ай бұрын
@@MSEndpointMgr turns out they were local admin on the device when i joined it to intune, it was a demo tenant so some funky stuff with adele vance :D