Outlook 2007 not saving Exchange Password
Outlook is on the same domain and LAN as the Exchange server, and we are NOT using RPC/HTTP.
However the Exchange account is different than the Windows Domain logon account.
Outlook prompts every time it is opened for the Exchange account password, and there is not a save password option.
I know it is prompting because I have it set to always prompt in the security tab of the Exchange account settings.
If I do not set Outlook to always prompt, the Exchange account is unable to send email. This is obviously due to the fact that the exchange account is different than the logon account.
Is there a way to get the save password option in Outlook to appear, or another work around with this setup?
However the Exchange account is different than the Windows Domain logon account.
Outlook prompts every time it is opened for the Exchange account password, and there is not a save password option.
I know it is prompting because I have it set to always prompt in the security tab of the Exchange account settings.
If I do not set Outlook to always prompt, the Exchange account is unable to send email. This is obviously due to the fact that the exchange account is different than the logon account.
Is there a way to get the save password option in Outlook to appear, or another work around with this setup?
ASKER
There were 2 simultaneous businesses running under the same Exchange server. They wanted separate mailboxes for the second business. I created new AD accounts for these mailboxes.
So secondary accounts were setup, and used with POP3, but the same Windows domain logon was used. Well now the original business is gone, and they wanted to use the accounts originally setup as POP3, as Exchange.
I kept the same logon accounts, and just added the new Exchange accounts to Outlook, then copied the POP3 account mail from the PST, over to the Exchange mailbox.
I realize that just adding the secondary business account, as a secondary mailbox, probably looks like the better option originally, but there was an issue with that setup. I can not remember what that issue was, possibly default sender address. I am not sure.
Anyway, sort of painted into a corner.
So secondary accounts were setup, and used with POP3, but the same Windows domain logon was used. Well now the original business is gone, and they wanted to use the accounts originally setup as POP3, as Exchange.
I kept the same logon accounts, and just added the new Exchange accounts to Outlook, then copied the POP3 account mail from the PST, over to the Exchange mailbox.
I realize that just adding the secondary business account, as a secondary mailbox, probably looks like the better option originally, but there was an issue with that setup. I can not remember what that issue was, possibly default sender address. I am not sure.
Anyway, sort of painted into a corner.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Ill try it out today and let you know. Thanks!
Make sure Outlook 2007 has sp2 installed.
ASKER
SeaSenor is that required for the autologin suggested by Praveenraj04, or is that something that could resolve the missing save password box?
It could possibly solve the password issues....
ASKER
Excellent.
I'm sorry...after re-reading, I see that you have the security setting to always prompt.
sp2 will not likely solve that, but I do again, recommend making sure it's installed.
You can check by opening Outlook, clicking Help- About...
and actually I recommend sp3 if possible for you.
Next,
I'm with marcustech, and am a little confused about the setup.
what version of exchange and AD are you running?
sp2 will not likely solve that, but I do again, recommend making sure it's installed.
You can check by opening Outlook, clicking Help- About...
and actually I recommend sp3 if possible for you.
Next,
I'm with marcustech, and am a little confused about the setup.
what version of exchange and AD are you running?
ASKER
2003.
Did you see my comment above, clarifying the reason it is setup this way? It is the second comment on the post, 1st by me.
Did you see my comment above, clarifying the reason it is setup this way? It is the second comment on the post, 1st by me.
Yes.. I did see it...
I'm a little thick skulled though so I don't get the entire picture :)
did you have seperate email addresses, such as domain1.com and domain2.com for their email?
I'm a little thick skulled though so I don't get the entire picture :)
did you have seperate email addresses, such as domain1.com and domain2.com for their email?
ASKER
Right, two different email domains, under a single domain controller.
Each user, had 2 users.
AD user 1 - email domain 1.
AD user 2 - email domain 2.
AD user 1 was always used as the windows logon. The problem with Outlook is, authenticating to the Exchange mailbox for AD user 2, while logged into the domain as AD user 1.
If I uncheck the "always prompt" the user can not send e-mail. It's strange because they can receive email with "always prompt" unchecked, and the emails they send, actually appear to send, they go to sent items, and get no error message. But the email never gets sent, never hits the queue, and I don't even see it get passed to the server while doing a packet capture, on the server. And the email is gone forever, it doesn't show up after Outlook authenticates. Exchange just kills it with no bounce message.
Each user, had 2 users.
AD user 1 - email domain 1.
AD user 2 - email domain 2.
AD user 1 was always used as the windows logon. The problem with Outlook is, authenticating to the Exchange mailbox for AD user 2, while logged into the domain as AD user 1.
If I uncheck the "always prompt" the user can not send e-mail. It's strange because they can receive email with "always prompt" unchecked, and the emails they send, actually appear to send, they go to sent items, and get no error message. But the email never gets sent, never hits the queue, and I don't even see it get passed to the server while doing a packet capture, on the server. And the email is gone forever, it doesn't show up after Outlook authenticates. Exchange just kills it with no bounce message.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Yea that's where my thick skull came into action. :)
I should have done that, but instead I exported the mail from the pop3 pst, which was being used for AD user 2, and then imported it into the Exchange mailbox for the same AD user 2.
Instead, as you suggested, it was probably better to import the pst to the AD user 1 mailbox, and assign the email address from AD user 2, to AD user 1.
I could still do that, but is it worth it, just to avoid 1 extra logon step whenever Outlook is opened? It doesn't constantly prompt which is positive. However I am concerned if the authentication were to be lost, Outlook might not re-authenticate until it is reopened, causing an untold number of sent emails to disappear forever.
I should have done that, but instead I exported the mail from the pop3 pst, which was being used for AD user 2, and then imported it into the Exchange mailbox for the same AD user 2.
Instead, as you suggested, it was probably better to import the pst to the AD user 1 mailbox, and assign the email address from AD user 2, to AD user 1.
I could still do that, but is it worth it, just to avoid 1 extra logon step whenever Outlook is opened? It doesn't constantly prompt which is positive. However I am concerned if the authentication were to be lost, Outlook might not re-authenticate until it is reopened, causing an untold number of sent emails to disappear forever.
I would do it if it were me, but only you can decide.
I've come to the conclusion over the years, that the simpler you can make exchange, the better :)
You could approach it in the fashion of doing 1 or 2 mailboxes and then wait a day or two to see if it all works well... then continue.
I've come to the conclusion over the years, that the simpler you can make exchange, the better :)
You could approach it in the fashion of doing 1 or 2 mailboxes and then wait a day or two to see if it all works well... then continue.
ASKER
Yea that's a great call. I will do one mailbox tomorrow and see what happens.
Will I be able to export the mailbox to PST and import the PST, all within Outlook? I am envisioning the imported PST will become a second datafile/mailbox in Outlook, and then I can just drag the mail folders over to the new Exchange Mailbox in Outlook. Or will the PST import directly into the Exchange mailbox in Outlook?
Will I be able to export the mailbox to PST and import the PST, all within Outlook? I am envisioning the imported PST will become a second datafile/mailbox in Outlook, and then I can just drag the mail folders over to the new Exchange Mailbox in Outlook. Or will the PST import directly into the Exchange mailbox in Outlook?
yes it will export from one mailbox and import to the other....
a google search will provide multiple links for reference.
good luck!
a google search will provide multiple links for reference.
good luck!
ASKER
Thanks again .
Why? If the mailbox being opened doesn't belong to the logged on user then it should be delegated to them and opended as an additional mailbox. I'm not sure whether this is a supported configuration at all, and I certainly can't see why it is necessary?
Please give us some more information about your setup.