Re: i Access password weirdness

[Tom Jedrzejewicz <tomjedrz@xxxxxxxxxxxxxx>]

On Tue, Oct 20, 2009 at 6:54 AM, Jeff Crosby <jlcrosby@xxxxxxxxxxxxxxxx>wrote:

> All,
>
> A user has started _not_ logging off at night so he doesn't have to wait
> for
> his roaming profile to load in the morning.  He closes all applications and
> then locks the keyboard.  Next morning he unlocks, starts apps, and away he
> goes.

You need to end this behavior .. it will end up causing you problems down
the road.  Log off is when the roaming profile is sync'ed from the local
computer to the domain.  That needs to happen regularly, otherwise the two
versions of the profile get out of sync.  If he has an abnormal shutdown, he
will lose all of the changes to his profile since his last log off.
 Differences between the local and server instances of the profile also
increases the likeliness of the profile getting corrupted. It also
eliminates the biggest benefit of roaming profiles, which is that a user can
log on to any computer and see the same desktop and favorites.

If it takes a long time to log on and log off, you should adjust the
configuration of what is in the profile to make it smaller.


> Does this make sense that Windows would supply the old password until he
> logs off?  Or do you think the System i Access software cached it
> somewhere?  IOW, is this standard Windows behavior in that _any_ app would
> be provided the old password until log off/on, or is it an i Access issue?

Yes, it makes sense.  The old password is what he used to authenticate, so
when the session is asked to pass "user and password", it sends the old
password.  However, when Windows is talking to Windows apps which use
standard Windows authentication, it does not use "user and password".
 Instead, it uses the Windows "guid" and relies on the known Windows client
having successfully authenticated the user.

---------
Tom Jedrzejewicz
tomjedrz@xxxxxxxxxxxxxx