Re: Does Entourage cache password expiration notices?

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance



William,

No one changed their passwords. That was the point of turning off the
global 90-day expiration rule on the server??the users are not at a point
where a password change would go smoothly at all (once I get them all
integrated into the AD forest, which is the next thing with which I've been
tasked, we'll be ready for that). There is a lot of corporate inertia here
(mostly bad practices) that we're trying to overcome....but baby steps are
necessary in this environment.

As it turns out, after reviewing the Exchange server logs with a Microsoft
engineer, there was a permissions issue on the server with the temp
directories that was affecting not only my Mac users, but the Windows users
in the parent organization as well (however, Outlook was not presenting
those users with any authentication errors, just quietly trying again).
Apparently, Outlook is a little more fault-tolerant than Entourage.

To summarize, the permissions problem on the server has been corrected, and
there have been no more authentication issues.

Thanks,
--Jamie



On 2/25/09 10:46 PM, in article u4xhRT8lJHA.5732@xxxxxxxxxxxxxxxxxxxx,
"William Smith [MVP]" <mecklists@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote:

Jamie_Rasmussen@xxxxxxxxxxxxxxxx wrote:

My question is this: Did Entourage cache the password expiration
notice it received from the server last week, and even though the
password expiration was halted, ³helpfully² expire (or forget) users¹
passwords anyway?

Entourage does not store that information. It comes directly from your
Active Directory servers when Entourage attempts authentication through
Exchange.

The "impending password expiration notice" was just that, impending.
Your boss was being notified that he'll soon have to change his
password, not change it immediately. Entourage will do this too starting
about six days before the change is required.

My guess is that your Entourage users saved their passwords, which are
stored in the Mac OS X keychain, and later you had your "change
password" training. They all changed their passwords. Then they launched
Entourage. Entourage tried the old saved password and told them "This
password doesn't work. Do you want to try a different password?" Users
enter their new password and everything worked.

This is normal behavior.

Or did your AD admin disable password expiration notifications but not
disable password expirations themselves?

.



Relevant Pages

  • Re: smtp access security
    ... Therefore, you will have to leave Basic Authentication checked, which is the lowest common denominator. ... I am running an exchange 2003 server on a basic LAN, I have most 80% of users that are running outlook XP and some that use Entourage on MAC. ...
    (microsoft.public.exchange2000.admin)
  • Re: Configuring LDAP on Entourage 2004 OS X
    ... On the SBS server box, open Server Management console, navigate to ... by companies that are independent of Microsoft. ... Configuring LDAP on Entourage 2004 OS X ...
    (microsoft.public.windows.server.sbs)
  • Re: Entourage 2004 authentication errors
    ... > versions of Entourage, I cannot send mail. ... I have EntourageX and I am getting similar authentication errors when I log ... I am using a Email server called Imail from ... I get the message back from EntourageX that " The SMTP server does not ...
    (microsoft.public.mac.office.entourage)
  • Re: Secure SMTP does not work
    ... Chris Ridd wrote: ... >> If I use the secure server but uncheck the authentication option, ... >> authentication methods supported by Entourage. ...
    (microsoft.public.mac.office.entourage)
  • Re: Entourage versus Thunderbird versus Mail
    ... things as examples off the top of my head, but rest assured, there ... Mail has no smart mailing list manager like there is in Entourage. ... For some silly reason, Mail dumps IMAP messages in the same Inbox as POP and all other IMAP messages, making it so that you'll never know which messages actually reside on a given server as opposed to POP messages already deleted from their respective server. ... But what *really* sucks about this is rather than simply detecting the difference and adjusting to it, Mail creates a *new* folder with that default name on the server and places sent messages into the new folder. ...
    (comp.sys.mac.system)