none
Windows 7 Rejoining Domain

    Question

  • We have a Windows Server 2003 SP2 AD structure and domain. I can join Windows 7 PCs to the domain initially. However, if the Windows 7 PC is removed from the domain and rebooted, it will not rejoin. This is true whether the existing PC account is left in AD or deleted. However, if the AD account is deleted, it IS recreated in AD after the PC is rebooted. The error at the PC is “Unable to create offline join information. Please ensure you have access to the specified path location and permissions to modify its contents. Running as an elevated administrator may be required.”  I am logging in to the PC as "Administrator" and logging in to the domain as a domain admin when attempting to rejoin.

    Thursday, February 25, 2010 2:55 PM

Answers

  • Hi,

     

    Please also try the following steps to troubleshoot the issue.

     

    1. Uninstall some Windows updates and rejoin the domain for a tests.

     

    2. Please click "Advanced settings" on the Windows Firewall, and allowed all incoming and Outgoing traffic in the below profiles:

     

    a. Private

    b. Domain

    c. Public

     

    Then, please restart "Windows Firewall Service"

     

    3. Change the Workgroup name and revert it back, and then join the domain again.

     

    If issue still occurs, please transfer a large file and perform following steps to capture a log file.

     

    Collect the Netmon trace

    =========================

    a. Download NetMon3.3 from the following website and install it on the computer

     

    http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=983b941d-06cb-4658-b7f6-3088333d062f

     

    b. Launch NetMon3.3.

    c. In the Microsoft Network Monitor 3.3 window, click Create a new capture tab …

    d. In the new tab, select all the Network Adapters in the Select Networks window.

    e. Then, switch to Network Monitor, press F5 to start NetMon.

    f. Try to join the domain again. When it failed, go to step 7.

    g. Go back to the NetMon window and press F7 to stop the NetMon.

    h. Press Ctrl+S to save the Netmon file named test.

     

    Then please upload to SkyDrive (www.skydrive.live.com ) and share the link to me.

     

    Thanks,

    Novak

     

    • Marked as answer by Novak Wu Tuesday, March 02, 2010 2:52 AM
    Friday, February 26, 2010 7:18 AM

All replies

  • try reseting the computer account in AD before rebooting and rejoining.


    windows 7 newbie
    Thursday, February 25, 2010 3:13 PM
  • Thanks.

    The PCs I am having the problem with are built and have Windows Updates, Office, etc.  installed. I built a "clean" Windows 7 without anything else other than anti-malware (no updates of any kind) and it removes from and joins the domain fine. I think I need to investigate the "add-ons" post Windows install.
    Thursday, February 25, 2010 6:28 PM
  • Hi,

     

    Please also try the following steps to troubleshoot the issue.

     

    1. Uninstall some Windows updates and rejoin the domain for a tests.

     

    2. Please click "Advanced settings" on the Windows Firewall, and allowed all incoming and Outgoing traffic in the below profiles:

     

    a. Private

    b. Domain

    c. Public

     

    Then, please restart "Windows Firewall Service"

     

    3. Change the Workgroup name and revert it back, and then join the domain again.

     

    If issue still occurs, please transfer a large file and perform following steps to capture a log file.

     

    Collect the Netmon trace

    =========================

    a. Download NetMon3.3 from the following website and install it on the computer

     

    http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=983b941d-06cb-4658-b7f6-3088333d062f

     

    b. Launch NetMon3.3.

    c. In the Microsoft Network Monitor 3.3 window, click Create a new capture tab …

    d. In the new tab, select all the Network Adapters in the Select Networks window.

    e. Then, switch to Network Monitor, press F5 to start NetMon.

    f. Try to join the domain again. When it failed, go to step 7.

    g. Go back to the NetMon window and press F7 to stop the NetMon.

    h. Press Ctrl+S to save the Netmon file named test.

     

    Then please upload to SkyDrive (www.skydrive.live.com ) and share the link to me.

     

    Thanks,

    Novak

     

    • Marked as answer by Novak Wu Tuesday, March 02, 2010 2:52 AM
    Friday, February 26, 2010 7:18 AM
  • Thanks for the responses. The culprit appears to have been the "Anti-virus Standard Protection:Prevent user rights policies from being altered" Access Protection setting in McAfee VSE.
    Tuesday, March 02, 2010 3:28 PM
  • hi this is sonu saini.

    same kind of problem i am facing now.

    kindly advise mee.

    • Proposed as answer by saini sonu Wednesday, March 02, 2011 9:52 AM
    • Unproposed as answer by saini sonu Wednesday, March 02, 2011 9:52 AM
    Wednesday, March 02, 2011 9:51 AM
  • tanks Todd2008

    that`s works. i disabled the Mcafee VSE and problem solve

    Sunday, March 13, 2011 8:26 AM
  • I also found that if you restart into SAFE MODE you can join the domain as Mcafee is not interfering.
    Tuesday, April 05, 2011 9:47 PM
  • Hello Todd,

    If you said the Mcafee policy is the culprit,that means something must have been triggered that rule,were you able to find out what triggered the rule.if you did let me know pls thanx

    Wednesday, April 27, 2011 11:21 AM
  • todd,

    can you also let me know the version of mcafee virus scan you are running, thanx

    Wednesday, April 27, 2011 11:29 AM
  • Hi my friend, only need to disable McAfee, no more easy. 
    Friday, September 09, 2011 3:28 PM
  • Recently at the organization I support we started having these problems, searched the internet for answers and although most sites inform to remove McAfee, we tried this and still got the same error. So after a lot of time spent on this, the solution is simple:

    > Open MSconfig utility

    >Select the boot tab, select Safe boot, click the radio button for Active Directory repair.

    >Apply and reboot. The computer boots into Safe Mode Active directory repair. Rejoin the computer to the domain.

    >Reverse the options made earlier in MSconfig so that the system boots into Windows normally.

    Tuesday, January 21, 2014 3:57 PM