Re: Change local cached domain user password

Hi,
Use this policy !
Always wait for the network at computer startup and logon


Determines whether Windows XP waits for the network during computer startup
and user logon. By default, Windows XP does not wait for the network to be
fully initialized at startup and logon. Existing users are logged on using
cached credentials, which results in shorter logon times. Group Policy is
applied in the background once the network becomes available. Note that
because this is a background refresh, extensions such as Software
Installation and Folder Redirection take two logons to apply changes. To be
able to operate safely, these extensions require that no users be logged on.
Therefore, they must be processed in the foreground before users are
actively using the computer. In addition, changes that are made to the user
object, such as adding a roaming profile path, home directory, or user
object logon script, may take up to two logons to be detected. If a user
with a roaming profile, home directory, or user object logon script logs on
to a computer, Windows XP always waits for the network to be initialized
before logging the user on. If a user has never logged on to this computer
before, Windows XP always waits for the network to be initialized. If you
enable this setting, logons are performed in the same way as for Windows
2000 clients, in that Windows XP waits for the network to be fully
initialized before users are logged on. Group Policy is applied in the
foreground, synchronously. If you disable or do not configure this setting,
Windows does not wait for the network to be fully initialized and users are
logged on with cached credentials. Group Policy is applied asynchronously in
the background. Note: If you want to guarantee the application of Folder
Redirection, Software Installation, or roaming user profile settings in just
one logon, enable this setting to ensure that Windows waits for the network
to be available before applying policy. Note: For servers, the startup and
logon processing always behaves as if this policy setting is enabled.

Regards.
"Juan" <Juan@xxxxxxxxxxxxxxxxxxxxxxxxx> a écrit dans le message de news:
91C26E92-C097-49A2-9F03-973AEC613529@xxxxxxxxxxxxxxxx
Hi!

we have are running an active directory domain on w2k3 dcs. 50% of our
clients are w2k prof and the rest is wxp.

As you know windows caches the user-domain-password on the local machine
and
if the the network is not available you can log on with these stored
credentials.
Now the user is on a journey and has to change its password. He changes
his
password and can't log on to his machine with the new password because
it's
not the same than the cached one. The user tries and tries and gets
locked,
so he calls the helpdesk.

Do you know a solution for this - changing the local stored password?

If found a windows xp tool called "control userpasswords" / "control
userpasswords2". But it doesn't help because it does not show me the the
logged on user. I also tried to log on the local administrator and run the
tool but the user I need not is there.


Thanks in advance

Juan



.

Relevant Pages

  • Windows Shortcut Keys and "ALT+TAB" not working because of GPO
    ... We've got an issue with a machine policy which prohibits us of using Windows ... Deny access to this computer from the network Support_388945a0, ... Policy Setting ...
    (microsoft.public.de.german.windowsxp.gruppen.richtlinien)
  • Re: local GPO question
    ... synchronous or asynchronous policy processing. ... Windows XP lets you wait for the network or not. ... > "Note that Windows XP clients support Fast Logon Optimization in any ...
    (microsoft.public.win2000.group_policy)
  • Re: No Shut Down or Restart for Domain Admins
    ... run rsop.msc from your DC and check which policy is responsible to this. ... I have created a group policy in a development network and imported it ... NT AUTHORITY\Authenticated Users Read (from Security Filtering) No ... Enforce user logon restrictions Enabled ...
    (microsoft.public.windows.server.active_directory)
  • Re: Server 2K3 Remote Desktop Access - is this right place?
    ... All roads for that particular error of 'You do not have access to logon to ... On Windows Server 2003, launch GPEDIT.MSC from Start -> Run. ... Drill down and expand the following for Local Computer Policy: ... > Strange - when I activate the Remote Desktop Terminal from the server, ...
    (microsoft.public.win2000.advanced_server)
  • Re: Change local cached domain user password
    ... Always wait for the network at computer startup and logon ... Determines whether Windows XP waits for the network during computer startup ... Group Policy is applied in the ...
    (microsoft.public.windows.server.active_directory)