?
Solved

re apply policies /force Windows 2003

Posted on 2012-03-11
5
Medium Priority
?
355 Views
Last Modified: 2012-03-27
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
0
Comment
Question by:hernanv70
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
  • 2
5 Comments
 
LVL 11

Accepted Solution

by:
Khandakar Ashfaqur Rahman earned 1500 total points
ID: 37707846
0
 
LVL 20

Expert Comment

by:compdigit44
ID: 37710410
What OS are your clients running? Are they all on the same network / subnet?
0
 

Author Comment

by:hernanv70
ID: 37711615
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
 
LVL 11

Expert Comment

by:Khandakar Ashfaqur Rahman
ID: 37711782
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
 
LVL 20

Expert Comment

by:compdigit44
ID: 37711933
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

Featured Post

Does Powershell have you tied up in knots?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Here's a look at newsworthy articles and community happenings during the last month.
This process allows computer passwords to be managed and secured without using LAPS. This is an improvement on an existing process, enhanced to store password encrypted, instead of clear-text files within SQL
This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles from a Windows Server 2008 domain controller to a Windows Server 2012 domain controlle…
Attackers love to prey on accounts that have privileges. Reducing privileged accounts and protecting privileged accounts therefore is paramount. Users, groups, and service accounts need to be protected to help protect the entire Active Directory …
Suggested Courses
Course of the Month10 days, 12 hours left to enroll

765 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question