| Re: "Please change your password at another machine" It seems you have intentionally configured your systems so that if
communication is lost / interrupted to the PC, users can't authenticate
to the domain to unlock. If you insist on making sure that is the
situation remains that way, then there isn't much I can suggest.
D. Harrison wrote:
> That is NOT a solution. It's not even a good workaround. What we need is a
> direct causal link - we need to know what generates this message and under
> what conditions. Someone at Microsoft should know where this message comes
> from.
>
>
> "Bob I" wrote:
>
>
>>Then the only option I see remaining is log off the user instead on
>>locking the PC.
>>
>>D. Harrison wrote:
>>
>>>Until there's a solution, the situation won't change. The reason that we have
>>>caching disabled is that it was causing lockout issues with users who log on
>>>to multiple computers. As a result, we will not be enabling that again.
>>>
>>>As for Power Saving, we don't forsee turning this back on any time in the
>>>future.
>>>
>>>
>>>"Bob I" wrote:
>>>
>>>
>>>
>>>>Has the situation changed? I would turn the caching on, and leave power
>>>>saving Off.
>>>>
>>>>D. Harrison wrote:
>>>>
>>>>
>>>>
>>>>>Caching has been disabled and we've turned off Power Saving on system devices.
>>>>>
>>>>>"Bob I" wrote:
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>>Is the caching the users passwords disabled on the PCs in question? And
>>>>>>is perhaps the NIC being turned off by the operating system when the PC
>>>>>>is locked?
>>>>>>
>>>>>>D. Harrison wrote:
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>>Users in a domain lock their computers. When they return and attempt to
>>>>>>>unlock the computer they are unable. We have confirmed that the user account
>>>>>>>is not locked. After resetting the user's password they receive the following
>>>>>>>message when they attempt to unlock the computer:
>>>>>>>
>>>>>>>"Please change your password at another machine and retry or contact your
>>>>>>>Domain Administrator".
>>>>>>>
>>>>>>>Users are not allowed back into the computer. Our only workaround has been
>>>>>>>to reboot the computer. Once the system has been rebooted the users can log
>>>>>>>in.
>>>>>>
>>>>>>
>> |