G
Guest
For several years, we ran an Exchange server within our own Windows
domain. User authentication was simple back then - when the user
logged into the domain, they were authenticated for access to our
Exchange server once their profile was created.
We're now in a situation where individuals continue to login to our
Windows domain, but must now retreive their e-mail from an Exchange
server in a completely independent domain (a trust relationship
between domains is not an option).
We created e-mail profiles which allow users to authenticate to the
second domain when opening Outlook (when using username (second
domain/username) and their password on the second domain). If they
follow this procedure, they attach to the remote Exchange server
without a problem.
Unfortunately, old habits die hard. Many of our individuals are
skipping past the authentication screen for Outlook by hitting
"Cancel" when prompted for credentials. Consequently, they do not
authenticate to the second domain, and Outlook goes offline.
The user thinks they are online, because they see their Inbox from
before and do not notice the Offline indicator. We then get
complaints that they are not receiving new messages.
We recognize this is a training problem, but I think we're not going
to get through to some users and we're looking for someway to smooth
this process for them.
I'm not sure how we get around this - is it possible that if a user
hits "Cancel", we can force an exit to Outlook rather than going
offline? Or force it to prompt again for credentials to the second
domain?
Any ideas as to how to address this problem are greatly appreciated.
One user hit "Cancel" and went offline 4 times today, even after we
explained things to him. They miss the simplicity of the previous 1
domain/1 credential system. Or, if there's nothing we can do to
idiot-pro....err...simplify this, we'll just go from there.
domain. User authentication was simple back then - when the user
logged into the domain, they were authenticated for access to our
Exchange server once their profile was created.
We're now in a situation where individuals continue to login to our
Windows domain, but must now retreive their e-mail from an Exchange
server in a completely independent domain (a trust relationship
between domains is not an option).
We created e-mail profiles which allow users to authenticate to the
second domain when opening Outlook (when using username (second
domain/username) and their password on the second domain). If they
follow this procedure, they attach to the remote Exchange server
without a problem.
Unfortunately, old habits die hard. Many of our individuals are
skipping past the authentication screen for Outlook by hitting
"Cancel" when prompted for credentials. Consequently, they do not
authenticate to the second domain, and Outlook goes offline.
The user thinks they are online, because they see their Inbox from
before and do not notice the Offline indicator. We then get
complaints that they are not receiving new messages.
We recognize this is a training problem, but I think we're not going
to get through to some users and we're looking for someway to smooth
this process for them.
I'm not sure how we get around this - is it possible that if a user
hits "Cancel", we can force an exit to Outlook rather than going
offline? Or force it to prompt again for credentials to the second
domain?
Any ideas as to how to address this problem are greatly appreciated.
One user hit "Cancel" and went offline 4 times today, even after we
explained things to him. They miss the simplicity of the previous 1
domain/1 credential system. Or, if there's nothing we can do to
idiot-pro....err...simplify this, we'll just go from there.