Group Policy not applying to client computers

Discussion in 'Windows Small Business Server' started by wmartz, Jan 2, 2007.

  1. wmartz

    wmartz Guest

    My problem is that the Group policy i created on the server works when any
    user logs onto the server directly... however none of the client machines
    will accept the group policy...

    I run gpresult /v which yields an error and rsop.msc errors out as well when
    i am logged onto the domain... locally rsop.msc works fine...

    Currently i was running SMB Server 2003 R2 and the Client is Windows XP SP1

    i am currently running windows updates on both to see if that alleviates the
    problem...

    On the server gpresult /v and rsop.msc work properly...

    In the end i would like to have WSUS setup, folder re-direction and a few
    locked down settings like screen saver timer and auto lock...
     
    wmartz, Jan 2, 2007
    #1
    1. Advertisements

  2. Well the very first thing obviously is to get the workstations up to date
    with security patches at the SP2 level
    Is this a new install? Has the problem existed since the install?
    You do know that "WSUS" is a part of the R2 Technologies CD, right? It
    will take care of those Group Policies for you
     
    Cris Hanna [SBS-MVP], Jan 2, 2007
    #2
    1. Advertisements

  3. wmartz

    wmartz Guest

    Yeah this was a brand new install of both the server and client...

    Originally i wasnt running any of the scripts, configuring everything
    manually like it was Server 2003 standard... turns out that if you follow the
    tutorials everything seems to work...

    thx for the quick response... not sure why the group policies wouldnt work
    when you manually add the client to the domain

    SO all in all follow the wizards and things work...

    Thanks again, i know everyone here appreciates all your answers!

     
    wmartz, Jan 2, 2007
    #3
  4. Glad you got it working. Most likely, the GPOs did not work when you
    manually added the client because they ended up in a different
    Organizational Unit than where the wizards place the accounts. Some
    GPOs are linked to the OUs used by the wizards, so that may be part of
    the problem.

    As you found, the three rules for easily setting up SBS are:

    1. Use the Wizards
    2. Use the Wizards
    3. Use the Wizards

    If you have not seen this document, it's worthwhile reading for
    experienced IT pros new to SBS:

    Introduction to Windows Small Business Server 2003 for Enterprise IT
    Pros
    http://www.microsoft.com/downloads/details.aspx?familyid=71211053-CCD6-
    4F2B-BBD9-5E7B97C232EC&displaylang=en

    -- Owen Williams (SBS MVP)
     
    Owen Williams [SBS MVP], Jan 2, 2007
    #4
  5. wmartz

    cmpolito

    Joined:
    Jul 20, 2011
    Messages:
    1
    Likes Received:
    0
    Fix it every time

    Dns my friends! Make sure that your client's dns is facing the domain controller or it will never work right!
     
    cmpolito, Jul 20, 2011
    #5
  6. wmartz

    justintjacob

    Joined:
    Jun 26, 2013
    Messages:
    27
    Likes Received:
    0
    you can use PsExec a sysinternal tool to update group policy to single remote computer or to all domain computers,download the PsExec,the syntax is follows

    PsExec \\Computer command argument

    for eg

    psexec \\computer1 gpupdate /force

    if you want to update all computers in a domain

    psexec \\* gpupdate /force
     
    justintjacob, Jun 26, 2013
    #6
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.