More about that here:
Issue in ConfigMgr Current Branch (1602) with Intune subscription
Some small bugs found in ConfigMgr Current Branch (1602)
The current status after one month looks good to me:
-Issue in ConfigMgr Current Branch (1602) with Intune subscription (when changing tenant) = Fixed
-To enable use the Add Site System Roles wizard to add the Intune Connector role = Fixed
-This device might have Activation Lock enabled and might require the user's Apple id and password to be entered to be reactivated = Won't fix
-Default layout for deployment status of task sequences (Monitoring part) = Active
-To identify the Windows Store link for this application, browse to a computer that has the application installed = Active
Hi mate, when you say ?
ReplyDelete-Issue in ConfigMgr Current Branch (1602) with Intune subscription (when changing tenant) = Fixed
i assume they have fixed internally and will roll out with next update?
You're right on that! Hope they have a solution soon.
Delete[djam] - yes. If the fixes are marked fixed on connect, then they should be in both the very next tech preview; as well as the next production build. Best part about new SCCM servicing model and rhythm - is we can get fixes out to customers quickly.
ReplyDeleteThanks for commment and clarification!
Delete