What happened to the 'Sign in with this account first' option?

  • Thread starter Thread starter Chris
  • Start date Start date
C

Chris

We are using .NET Passport and Exchange IM. We migrated our userbase from
various versions of MSN Messenger and Windows Messenger to Windows Messenger
5.0. Now, users are asking what happened to the Tools > Options > Accounts >
"Sign in with this account first" option.

Users are saying that they liked the ability to specify Exchange to be
first. Apparently, if .NET was set to be first and was unavailable for some
reason, they would not be logged into Exchange IM either. I'm not sure how
well WM5 handles this scenario; is there a way to specify in WM5 which
service should be tried to login to first?
 
Hi

Chris said:
We are using .NET Passport and Exchange IM. We migrated our userbase from
various versions of MSN Messenger and Windows Messenger to Windows Messenger
5.0. Now, users are asking what happened to the Tools > Options > Accounts >
"Sign in with this account first" option.

Users are saying that they liked the ability to specify Exchange to be
first. Apparently, if .NET was set to be first and was unavailable for some
reason, they would not be logged into Exchange IM either. I'm not sure how
well WM5 handles this scenario; is there a way to specify in WM5 which
service should be tried to login to first?
Click to expand...

I miss this feature too!

MfG
Gerhard
 
Hi Chris,

Still looking into this for a more exact answer but -- this option is no longer present. I
haven't yet figured out [or heard back] about what happens if the .NET Messenger service is
actually down but I believe that the other services would still login but I'm not ready to
say so with 100% certainty (as of yet).
____________________________________________
Jonathan Kay
Microsoft MVP - Windows Messenger/MSN Messenger
Associate Expert
http://www.microsoft.com/windowsxp/expertzone/
Messenger Resources - http://messenger.jonathankay.com
 
Thanks for the update. I tested this in my own way by signing out, entering
a bogus .NET password on the Accounts tab, and then attempting to login. I
was immediately greeted with a 'bad password: retry/cancel' dialog box. When
I hit Cancel, I was signed in to EXIM without difficulty. Seems fine to me.
This really isn't an authoritative test, however.

This seems to be different from WM47; when I performed this same test, I was
not logged in to EXIM until I successfully logged in to .NET.

Here's my dilemma: Users are reporting that (for whatever reason) .NET will
occasionally not respond for quite a while (minutes?); and until it does
(the retry/cancel dialog box appearing?), they are prevented from accessing
EXIM. One user reported that .NET never responded....and they were unable to
login to EXIM. They ended up logging out of Windows, logging back in,
unchecking .NET, then logging into WM5/EXIM.

I'm still testing this, but I appreciate any information you can find. The
developer must have removed the 'Sign in with this account first' option for
some reason. Perhaps it's only hidden--and can be made visible via the
registry?




Jonathan Kay said:
Hi Chris,

Still looking into this for a more exact answer but -- this option is no longer present. I
haven't yet figured out [or heard back] about what happens if the .NET Messenger service is
actually down but I believe that the other services would still login but I'm not ready to
say so with 100% certainty (as of yet).
____________________________________________
Jonathan Kay
Microsoft MVP - Windows Messenger/MSN Messenger
Associate Expert
http://www.microsoft.com/windowsxp/expertzone/
Messenger Resources - http://messenger.jonathankay.com

Chris said:
Do you have any comments on this, Jonathan? :^)
Click to expand...
Click to expand...
 
Back
Top