asked on gpudate /force over PPTP
I have several users that work from home but their systems were setup to be in our domain. When they change their password (via a 3rd party tool that updates our domain controller from a web interface) and then try to run a gpupdate /force it will not complete so their local machine doesn't know that the password as been changed.
I do understand that it has to do with the DNS not finding the domain controller. However, I am hoping there is a way to force this to process sucessfully through a batch file or something that they can run once the have the VPN connection active.
Has anyone else already came across this? How did you resolve it?
I do understand that it has to do with the DNS not finding the domain controller. However, I am hoping there is a way to force this to process sucessfully through a batch file or something that they can run once the have the VPN connection active.
Has anyone else already came across this? How did you resolve it?
Active DirectoryWindows 7Windows Server 2008
Last Comment
yo_bee
SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
Thanks yo_bee, I thought the same thing but he says he gets an error when he does that. I will reset his password and get him to do that again and then give me the exact error he gets.
ASKER
ok when he does this he is getting the error:
Configuration information could not be read from the domain controller, either because the machine is unavailable, or access has been denied.
Configuration information could not be read from the domain controller, either because the machine is unavailable, or access has been denied.
ASKER
It was a DNS issue. I had him manually enter in the DNS for our network and he was able to change his password.
Nice.
Error:
Updating Policy...
User policy could not be updated successfully. The following errors were encountered:
The processing of Group Policy failed. Windows attempted to read the file \\MYDomain.com\SysVol\MYDo
could be caused by one or more of the following:
a) Name Resolution/Network Connectivity to the current domain controller.
b) File Replication Service Latency (a file created on another domain controlle
has not replicated to the current domain controller).
c) The Distributed File System (DFS) client has been disabled.
Computer Policy update has completed successfully.