locked
DirectAccess GPOs work fine, and then "system cannot find the path specified". RRS feed

  • Question

  • Hi,

    I have deployed DirectAccess 2012 onto my server. After the intiial deployment, the GPOs (Directaccess 2012 client settings and Directaccess 2012 server settings) come up in the gpo console. However, after changing the client AD group in the configuration console of directaccess 2012, I get an error stating file not found. See below:

    Why is this happening?

    Friday, March 15, 2013 4:08 PM

Answers

  • Hi,

    This issue can be the problem with your GPO, which has been corrupted in GPT.

    As far as I know, GPO has two parts: GPT and GPC. You can see the GUI indicating that your GPc is working properly, because it is replicated with AD replication. However, GPT is replicating with FRS, which may be incorrect.

    Now, in order to fix this problem, you need to delete this GPO, and configure it again to re-write the GPT information in the AD database.

    If you have any problem, please feel free to let me know.

    Thanks.

    Best Regards,

    Annie Gu

    Tuesday, March 19, 2013 9:40 AM

All replies

  • Hi,

    Thank you for the post.

    It seems like policy was corrupt. Please reconfigure DirectAccess policy and restart server see if it helps.

    Regards,


    Nick Gu - MSFT

    Monday, March 18, 2013 9:25 AM
    Moderator
  • The problem is, I can't uninstall DirectAccess (server manager does not allow this) and I can't load the configuration console for DirectActess so I can't do anything else. I had to reinstall the entire OS, which to me is VERY VERY bad design (I'm a software developer).

    The problem has not occurred now but if I change something, it may.

    Monday, March 18, 2013 10:45 AM
  • Hi,

    This issue can be the problem with your GPO, which has been corrupted in GPT.

    As far as I know, GPO has two parts: GPT and GPC. You can see the GUI indicating that your GPc is working properly, because it is replicated with AD replication. However, GPT is replicating with FRS, which may be incorrect.

    Now, in order to fix this problem, you need to delete this GPO, and configure it again to re-write the GPT information in the AD database.

    If you have any problem, please feel free to let me know.

    Thanks.

    Best Regards,

    Annie Gu

    Tuesday, March 19, 2013 9:40 AM