Bypass Cached credentials when logging onto Windows XP
Hi,
We had a policy on our netword that disabled cached credentials on all workstations. We have managed to remove this in the following location on our Server 2003 machine (Computer Config > Windows Settings > Security Settings > Security Options > "Interactive logon: Number of previous logons to cache (in case domain controller is not available).)
The problem that we have is that we have remote users that use SSL to connect to the network after they logged into their machine and because the cached credentials was disabled on their local policy while they were connected to the domain yestarday, they cannot log into their machines today.
So is there a way to bypass the cached credentials when logging into the machine? Also note that the Administrator account has been disabled so I can not get into the machine at all.
Any suggestions would be greatly appreciated.
We had a policy on our netword that disabled cached credentials on all workstations. We have managed to remove this in the following location on our Server 2003 machine (Computer Config > Windows Settings > Security Settings > Security Options > "Interactive logon: Number of previous logons to cache (in case domain controller is not available).)
The problem that we have is that we have remote users that use SSL to connect to the network after they logged into their machine and because the cached credentials was disabled on their local policy while they were connected to the domain yestarday, they cannot log into their machines today.
So is there a way to bypass the cached credentials when logging into the machine? Also note that the Administrator account has been disabled so I can not get into the machine at all.
Any suggestions would be greatly appreciated.
ASKER
Thanks for your reply. The users that log in from home use 3G, which for some reason does not want to connect. And you need to connect to 3G and then only can you connect through SSL.
They get a connection error when trying to logon using dial up. Have you maybe got any other suggestions, or maybe know of a way to edit the Policy through command prompt before windows starts?
They get a connection error when trying to logon using dial up. Have you maybe got any other suggestions, or maybe know of a way to edit the Policy through command prompt before windows starts?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Hey,
We tried pushing GPUpdate, but for some reason it did not work so I had to get them to send their machines to us to resolve the issue. Thanks for all the suggestions though.
We tried pushing GPUpdate, but for some reason it did not work so I had to get them to send their machines to us to resolve the issue. Thanks for all the suggestions though.
Ok, that's what i thought and was afraid off that a gpupdate wouldn't work.. Unfortenately though...
Because you probably disabled the admin account using a policy, you;d still have the same issue with enabling that account again.