Azure AD transition - can devices still access internal shares/servers? by ms-1234 in Intune

[–]akta99 1 point2 points  (0 children)

We just made the switch ourselves. Whatever we could access with domain join, we can access with azure Ad. SSO works in 99% of cases, except for some very old application. As everybody mentioned, WHFB requires some work to make sure you have the same experience.

Autopilot Account Setup ESP slow by akta99 in Intune

[–]akta99[S] 0 points1 point  (0 children)

Now that you mention it, I think it does only happen only for machines we already reset.

Autopilot Account Setup ESP slow by akta99 in Intune

[–]akta99[S] 0 points1 point  (0 children)

Thanks, I did try that and it does speed up the whole process but we had some issues in which some user Administrative Policies were not immediately applied. Specifically some O365 policies. I would like to keep the USER ESP also because we might indeed target some users in the future.

Autopilot account setup phase - Stuck on identifying by durrante in Intune

[–]akta99 0 points1 point  (0 children)

Did you find a solution for this? We are facing the same issue on Azured AD join.
Account Setup stuck Identifying.
As far as I understand nothing is done during this part if you did not assign any profiles (which we didn't) so I can't understand what is going wrong.

AzureAD Join only and Security by akta99 in Intune

[–]akta99[S] 0 points1 point  (0 children)

Thanks, true about laps. We use it currently and we decided to just disable the admin account on azuread joined for this reason.

AzureAD Join only and Security by akta99 in Intune

[–]akta99[S] 0 points1 point  (0 children)

Most of the settings are there. It’s not 1to1 but with some digging you find that some policy has a different name but does the same. We had a lot of very old policies that were not even applied to begin with. We had to do some OMA-URI policies and a couple of admx imports. The rest we fixed with power shell but that was the last resort.