-
Título
O365 Hybrid to O365 Hybrid Migration -
Descripción
QMM DOES NOT SUPPORT O365 or Hybrid Sources, the following is provided at your own risk.The machines run through RUM without errors in terms of profile failures.Upon reboot, the user is logging into to the machine with the target domain ID and password. When trying to open Outlook for the first time the user is presented with a logon dialog.The machine will then loop repeatedly around the Outlook start up. Sometimes a logon prompt is displayed but no amount of re-entering the password will resolve the issue.The PCs already have Office 365 installed and fully functional in the source domain. Excel, PowerPoint and Word work, but the Office login is not presentAll of the machines were fully rebooted (not just logged off), and were sitting at the logon prompt prior to Discovery through Move. No user activity occurred at any point through the process.No errors are present in the event logs indicating any out-of-norms failure through the migration and post-migration time.The issue can be cleared if a brand new user profile is created.The Windows profile appears good. The Ofiice 365 components within the Windows profile are not updated to the target account, while everything else (registry settings, drive maps, desktop, etc) in the Windows profile is. The users are able to log in with their target credentials, and their profile is available as expected. -
Causa
The way Microsoft explained it is that there are registration, identity, and tokens set for each user profile under Office 365 that are exclusive to that user’s profile. When another domain binds to that user profile it acts as a security measure because the system thinks of it as an impersonation attempt. If the profile is built new the tokens and registrations are rebuilt or this script can be ran under our scenario to reset what a new profile would do by stripping all the remnants out. -
Resolución
The fact that RUM (Resource Updating Manager) doesn't work with the Office 365 licenses is not a product bug, as we do not claim to be able to work with any source Office 365
Here is the recommendation from R&D:
1) There are 2 ways to resolve the issue with the script provided by Microsoft through RUM: at the end of the processing task 2 separate script task,but you should run the script not under admin credentials but from each user who's profile was processed on each host This can be resolved by adding full path to script into HKLM\Windows\Run so it will be run on logon of each user. Also the script should be run only once. This can be resolved by creating a file %USERPROFILE% or reg key in HKCU and add condition to run script only if such file/reg key does not exist Microsoft provided the following script to resolve the issue:
2) Name: OLicenseCleanup.vbs - v 1.15 ' Author: Microsoft Customer Support Services ; Copyright (c) Microsoft Corporation Removes all licenses for Office 2013 and 2016 from thee (Office) Software Protection PlatformSEE ATTACHED FOR THE SCRIPT., which needs to be renamed .vbs
RUN AT YOUR OWN RISK.It would be best to contact Microsoft, to ensure you have the latest version of the Script. -
Adjuntos