azure
5 TopicsAzure AD Endpoint Manager User Profile Corruption: Black Screen Flashing Taskbar Explorer Crash Loop
We are in the midst of a Azure/Endpoint Manager (Intune) Migration. 300+ Endpoints and are running into deployment nightmare: We are experiencing a very odd, completely random issue when a previously Synced Hybrid Azure AD User logs into their endpoint (which was previously working without issue for weeks/months) and then suddenly fails to load. This issue only seems to occur when NEW endpoints are added to the Azure AD tenant/domain. We know the issue is about to happen when you receive a call from an end-user stating their previously working credentials are "no longer working". When the the user attempts to login via "other user"; The login will proceed, and the user will login to a black desktop/screen and flashing taskbar. Windows Task Manager is not responsive; Safe-mode options will not produce a better end result. Upon reviewing the logs you will see "explorer.exe" crash loop prompting urtcbase.dll. Azure AD homed user accounts and local user accounts are able to login without issue into the endpoint. The issue is only specific to Hybrid Azure AD User Profiles (on-premise cached/home' d accounts). I'm thinking it has to do with a conflict of the on-premise SAM Account name. I'm not sure why adding new endpoints to the tenant causes the issue. This particular issue is happening across all different makes, models, and Window Image variations. The issue is specific to only Azure AD Profiles that attempt to login to the endpoint. Precursors: Incorrect password prompt. Requires uses to select "other user" After selecting other user, user profile experiences delayed "Welcome" Black screen appears with flashing taskbar, rending the profile useless If we attempt a Wipe/Restore the issue will randomly reoccur on another workstation. I believe the issue is specific in the way Windows try to load/create the profile for Azure AD users. I'm not sure if AutoPilot is attempting to configure these endpoints in Hybrid mode. However we've noticed discrepancies in the naming convention of some profiles and domains. For example: AzureAD\FirstLastName shortdomain\FLast I believe the User Profile Service is somehow bugged and causing a mismatch between the registry's SID for the user profile. Has anyone else experienced this issue? We are desperate for answers; this is worse than any virus as its random intermittent nature will return after a fresh system restore. I've received a call from another organization stating they are seeing the same issue occur throughout their deployment. I believe this is now a wide-spread issue. We have a ticket opened with the Microsoft on this. Windows Performance Team is reaching out to Azure Team.Solved27KViews0likes52CommentsSuggestion for how to Move user profile data and settings to Azure user accounts
Just started at a new customer who will move mainly laptop users (200+), who work externally, to a clean Azure account. All the laptop users currently have Domain profiles, with data stored locally, but will get a clean Azure Account as they will be in a separate org. My task is how can I create a setup to move their data and settings, browser favorites etc. over to their new Azure profile? This task needs to be simple enough for a group of supporters to be able to carry out. So far only briefly tested Laplink but it crashed Outlook, so it would not open at all. Also it is very expensive. In case you have suggestions for a tool, that you are experienced with (know is good!) and is simple to use for a big group of supporters it would be a big help. Thorough testing takes a really long time 😕 SBabicSolved1.1KViews1like3CommentsFull tutorial on Microsoft Autopilot Intune
Ever wanted a full tutorial how to deal with Microsoft Autopilot Intune technology? Learn more about it on my blog and create the modern workplace today! https://stardestroyer.xyz/autopilot-intune-technology/ Manage your Windows 10 endpoints with Intune and use the public Cloud Azure with all aspects like enrollment, configuration, updating, apps and security. Make your enterprise mobile now!3.1KViews1like0CommentsMicrosoft's Windows 10 20H1 release will be first to RTM in December under Azure schedule
20H1 is Microsoft's first version of Windows 10 to be finalized under the Azure development cycle. What you need to know Windows started operating under Azure's development schedule earlier this year. This means feature updates will now be finalized in December and June. Windows 10X will RTM with 20H2 in June 2020. Microsoft's upcoming 20H1 release of Windows 10 will be the company's first version of the OS to be finalized in December, three months earlier than usual, as a result of Windows moving under Azure and adopting the "semester" based development cycle that Azure is already using. Mary-Jo Foley was first to reveal that the Windows dev cycle was being changed up earlier this year, but here's what this all means for Insiders. In the past, Windows 10 feature updates were typically finalized in March and September, but now, these OS releases are expected to be done in December and June instead. This doesn't mean Microsoft is giving feature updates less development time; this is just a result of Microsoft outright shifting the development cycle of Windows 10 updates by two to three months. Each release still gets the usual seven to nine months in development. Microsoft was able to make this change thanks to a decision it made when first moving Windows under Azure. To allow the Azure and Windows development schedules to align, it needed to skip a feature release. Windows 10's 19H2 release is the result of this, being an update that isn't a proper OS release like previous ones before it. This means Windows 10's 20H1 release is just about done. It was marked as feature-complete internally back in August, and Microsoft has been mostly focused on fixing up bugs and polishing the OS for release ever since. This is why Insiders have not seen any substantial new features in 20H1 builds for a couple of months, because the 20H1 release is done. We've got a month or so left of development before Microsoft signs-off on 20H1 in mid-December. Windows 10 20H2 This also means that work on the next Windows 10 feature update after 20H1, known as 20H2 or "Manganese" has already started development internally, and Insiders should begin receiving 20H2 builds in the next couple of weeks. On this new development cycle, 20H2 will RTM in June 2020. This is important, as this release will play a vital role in the availability of Windows 10X on new foldable PCs expected to start shipping in fall 2020. Now that 20H2 can RTM earlier in the year under the new dev schedule, Microsoft can use 20H2 as the shipping version of Windows 10X that's preloaded onto devices like the Surface Neo. This means Windows 10X will RTM in June alongside 20H2, and not with 20H1 as we had initially assumed. Microsoft needs the extra development time to make sure Windows 10X is as good as it can be at launch. Regarding desktop releases, does this mean new feature updates will be made available to the public earlier than previously? Right now, I'm not too sure. As 20H1 will be done in December, Microsoft could start shipping the update to the public as early as January, but none of my sources seem to be clear if that's actually what's happening. Microsoft may decide to keep pushing out new feature updates in the spring and fall, utilizing the Slow and Release Preview ring for extensive testing of the final build before it goes to the public. Either way, Windows is now operating under Azure's development schedule, and that means we can expect to see new feature updates finalized earlier than we've seen in the past. What are your thoughts on these changes? Let us know in the comments. Original article: Windows Central12KViews2likes1Comment