asked on re apply policies /force Windows 2003
I am a network administrator of Windows 2003 with approximately 800 servers.
I often happens that clients lose terminal configuration of the startup url internet explorer and I have to verify which server is being performed coonecciòn, connect to the server and run a gpupdate / force.
I wanted to know how I can make troubleshooting this to see what happens, for policies that are lost and I have to reapply with a / force
I often happens that clients lose terminal configuration of the startup url internet explorer and I have to verify which server is being performed coonecciòn, connect to the server and run a gpupdate / force.
I wanted to know how I can make troubleshooting this to see what happens, for policies that are lost and I have to reapply with a / force
Active DirectoryWindows Server 2003
Last Comment
compdigit44
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.
What OS are your clients running? Are they all on the same network / subnet?
ASKER
there are a lot of differents networks / subnets .
There a are terminal servers farms (w2k3) and the clients are the rdp connection(w2k3)
users often call because they can not navigate the intranet.
The problem is that the ie start page dissapears
The intranet url is the start page by policy.
But often this policy, do not know why dissapaers and i have to make gpupdate / force to reapply that...
There a are terminal servers farms (w2k3) and the clients are the rdp connection(w2k3)
users often call because they can not navigate the intranet.
The problem is that the ie start page dissapears
The intranet url is the start page by policy.
But often this policy, do not know why dissapaers and i have to make gpupdate / force to reapply that...
Sounds like connectivity issue when problem happens,Did you ping and check connectivity when problem happens ?
Are you using DHCP ? It's necessary to know your network scenario/diagram to identify the problem.
Are you using DHCP ? It's necessary to know your network scenario/diagram to identify the problem.
I had an issue in my enviroment with Windows XP client the Firewall keep turning on even though our domain policy was set to disable the client firewall domain and stand-alone profile. I found this issue was always happened after the client was powered off then powered on again. After months of research I found the issue was becuase the "Network Location Awareness Service" was starting before the computers network services were fully online. Further research on the MS site found that MS was aware of this issue with XP and it was Corrected in Vista and Windows 7. I ended up added some dependencies to the NLA service to slow it down on startup which corrected the issue for me.