venerdì 27 gennaio 2012 16:17When do we stop using the BPOS sign in tool? Should it be before, during or post transition? It currently runs every time users log on to the computer.
Tutte le risposte
lunedì 30 gennaio 2012 05:20I need this info as well!
martedì 31 gennaio 2012 17:01
Since no response from the transition team was forthcoming, I'll relate my experience. It is a shame that we can't get "official" guidance. Note: the behavior described is for a user logging in to a Remote Desktop Server on Windows 2008 R2.
The answer is that it didn't seem to make much of a difference for us. The morning after the migration, folks fired up their desktops and the BPOS Sign-in-Tool ran as usual. We opened Outlook and it prompted for a user name and password. We fed it the appropriate credentials, checked the box that says "remember my password" and it connected. The user immediately got the "The Exchange Administrator has made a change that requires you quit and restart Outlook." error message. When we quit and restarted Outlook it again asked for the user name and password and we again entered the appropriate credentials and again checked the box that says "remember my password". Outlook would now open and close without a password nag. At this point, we opened the already running BPOS Sign-in-Tool and under the Options Tab, deselected the "automatically sign me in" and "automatically start when Windows starts" check boxes. We then clicked on "Sign Out" and the BPOS Sign-in-Tool closed, never to be heard from again.
I hope that helps.
mercoledì 1 febbraio 2012 14:45
My users is on 2008 R2 too.
giovedì 2 febbraio 2012 02:58
Hi Paul, sorry for not responding, this Forum is really popping these days.
The BPOS Sign-In Client (SIC) should be maintained and up and running until after the Transition. The SIC, upon login AFTER Transition will query the BPOS SSO Service and determine the user and tenant have Transitioned and issue a directive to the local machine to do the following:
- Remove all Outlook Autodiscover registry references, such as PreferLocalXML = c:\xxxx\autodiscover.xml, which directs Outlook to use the BPOS EXO Availability services, for things like Offline Address Book (OAB), Free/Busy, Out-of-Office (OOF),. etc
- Reconfigures the SIC to not launch at startup, effectively disabling the SIC
So you will find that post-Transition, say Monday morning users will find that the SIC is no longer running. This is a clear indication that the SIC has determined the user has moved and taken the proper steps to disable the SIC and clean up the registry so Outlook can work using the newly EXO365 Messaging environment.
Let me take a minute to talk about that. The admin checklist states that you as an Admin should look to update/create a DNS Messaging Autodiscover record which points to autodiscover.outlook.com. This can be done ahead of the Transition as your Outlook clients running the SIC are manually configured to use BPOS EXO, so this DNS setting will NOT impact those Outlook users. So if you are using a custom domain of contoso.com, you would create an autodiscover.contoso.com --> autodiscover.outlook.com and have that ready. When the user logs into their machine Monday morning and the user logs in, SIC will pick up the fact that the user has been migrated and remove the AutoD registry settings. Or the SIC was left signed in, the user when they login will already have these settings removed.
When the user launches Outlook, it will NOT find the PreferLocalXML and query DNS for autodiscover.contoso.com and find Outlook must go to autodiscover.outlook.com, which then points the user to the proper Exchange Online 365 front-end server to connect. EXO asks for creds and the user is logged in. because the users MBX is the SAME MBX that was used in BPOS, the user won't have to sync the offline .ost file, which will not require lots of bandwidth, so the user should connect, find the same content, calendars, etc and will probably never know they are in a different environment.
So while the above is hopefully helping, to address you specific question, you can STOP using the SIC after transition WHEN your users see that the client does not automatically launch and sign into BPOS when the user logs into their local machine. Again this signifies that the SIC can picked up the directive that the user has been moved. At this point the SIC can be uninstalled without any negative impact. it can remain installed if you would like and over time uninstall this client, but it will not be used in any way within Office 365.
Again, sorry it took so long to get back with you. Please let me know if the above did not answer your questions and I can hopefully clarify the above!
Transitions Community Lead ...Ryan J. Phillips