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
hernanv70Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Khandakar Ashfaqur RahmanExpert/ConsultantCommented:
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
compdigit44Commented:
What OS are your clients running? Are they all on the same network / subnet?
0
hernanv70Author Commented:
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...
0
Khandakar Ashfaqur RahmanExpert/ConsultantCommented:
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.
0
compdigit44Commented:
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.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Active Directory

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.