locked
Connector software for Windows 10 Pro to Server Essentials 2012 RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    1
    Sign in to vote

    Is there a fix yet to enable Windows 10 Pro to connect to Windows Server Essentials 2012 (but not connecting to a domain). There are fixes for the non-pro versions at following site http://www.microsoft.com/en-us/download/details.aspx?=40285 but not for W10 Pro.

    The original connector didn't work with W8.1 Pro when you didn't want to connect to a domain but there was a fix to allow it to work.

    Has anyone found a fix once you upgrade from W8.1 pro to W10 Pro?

    Wednesday, August 5, 2015 3:26 PM

Answers

  • Question
    Sign in to vote
    1
    Sign in to vote

    Graham,

       Got the following to work for Server Essentials 2012 R2, hope it helps:

    1)  Applied the registry hack from KB2752321.  Right click on the Start Menu, and select "Command Prompt (Admin)" and click "yes."  Once the Command Prompt window opens, type the following and hit enter:  reg add "HKLM\SOFTWARE\Microsoft\Windows Server\ClientDeployment" /v SkipDomainJoin /t REG_DWORD /d 1

    2)  Download the Windows 10 Connector Software from KB2790621, and install it.  You might have to restart after installing it.

    3)  Open File Explorer, right click "This PC," and select properties.  In the window that opens, find the section for Computer name, domain, and workgroup settings.  Click "Change Settings" on the right hand side.

    4)  In the window that opens, enter your computer description.  Where it says "To rename this computer or change its domain...." click "Change..."

    5)  Change your computer name if you want (helpful if you did a "clean install" and have a generic Microsoft name assigned), and click "more."  If anything is in the Primary DNS suffix of this computer box, delete it.  Leave the box for "Change primary DNS suffix when domain membership changes" checked, in case you decide to join a domain later on.  Click "OK"

    6)  Where it says Member of Domain or Workgroup, make sure Workgroup is selected.  Change the name from WORKGROUP to HOME, and click OK.  Reboot to apply the changes.

    7)  Run the Windows Server Essentials Connector from your apps menu, and it should work.

    I think what happened for me, was I never uninstalled the connector before upgrading to Windows 10.  I noticed that even though the computer wasn't joined to the domain after a "clean" install, it still had the domain's DNS suffix applied.  Removing that and "forcing" it into the HOME workgroup is what I think fixed it.

    Hope that helps,

    Ben

    • Proposed as answer by Michael_LS Wednesday, August 19, 2015 2:50 AM
    • Marked as answer by Deason Wu Friday, August 21, 2015 6:43 AM
    Saturday, August 8, 2015 4:34 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi GM,

    Currently it seems to be that the connector is not available for Windows 10.

    Since the Preview build, see:

    https://social.technet.microsoft.com/Forums/en-US/86d5139b-1a37-4b05-9cc4-2efccd392572/windows-server-2012-connector-for-windows-10?forum=WinPreview2014Setup

    There would be newer version, or some updates published soon.

    Regards

    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    Friday, August 7, 2015 9:31 AM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi GM,

    Currently it seems to be that the connector is not available for Windows 10.

    Since the Preview build, see:

    https://social.technet.microsoft.com/Forums/en-US/86d5139b-1a37-4b05-9cc4-2efccd392572/windows-server-2012-connector-for-windows-10?forum=WinPreview2014Setup

    There would be newer version, or some updates published soon.

    Regards

    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    Friday, August 7, 2015 9:31 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Graham, are you attempting to connect to Server 2012, or Server 2012 R2?  KB2790621 released on 29 July 2015 for Server 2012 R2 has support for Windows 10, in both x64 and x86 versions.

    Unfortunately, I've had issues getting to work with Windows 10 Pro and Server 2012 R2 - did a clean install last night, and will try it again after I have my coffee - perhaps this time I'll try it without joining the domain (using the fix in KB2752321)

    Cheers,

    Ben

    Saturday, August 8, 2015 3:43 PM
  • Question
    Sign in to vote
    1
    Sign in to vote

    Graham,

       Got the following to work for Server Essentials 2012 R2, hope it helps:

    1)  Applied the registry hack from KB2752321.  Right click on the Start Menu, and select "Command Prompt (Admin)" and click "yes."  Once the Command Prompt window opens, type the following and hit enter:  reg add "HKLM\SOFTWARE\Microsoft\Windows Server\ClientDeployment" /v SkipDomainJoin /t REG_DWORD /d 1

    2)  Download the Windows 10 Connector Software from KB2790621, and install it.  You might have to restart after installing it.

    3)  Open File Explorer, right click "This PC," and select properties.  In the window that opens, find the section for Computer name, domain, and workgroup settings.  Click "Change Settings" on the right hand side.

    4)  In the window that opens, enter your computer description.  Where it says "To rename this computer or change its domain...." click "Change..."

    5)  Change your computer name if you want (helpful if you did a "clean install" and have a generic Microsoft name assigned), and click "more."  If anything is in the Primary DNS suffix of this computer box, delete it.  Leave the box for "Change primary DNS suffix when domain membership changes" checked, in case you decide to join a domain later on.  Click "OK"

    6)  Where it says Member of Domain or Workgroup, make sure Workgroup is selected.  Change the name from WORKGROUP to HOME, and click OK.  Reboot to apply the changes.

    7)  Run the Windows Server Essentials Connector from your apps menu, and it should work.

    I think what happened for me, was I never uninstalled the connector before upgrading to Windows 10.  I noticed that even though the computer wasn't joined to the domain after a "clean" install, it still had the domain's DNS suffix applied.  Removing that and "forcing" it into the HOME workgroup is what I think fixed it.

    Hope that helps,

    Ben

    • Proposed as answer by Michael_LS Wednesday, August 19, 2015 2:50 AM
    • Marked as answer by Deason Wu Friday, August 21, 2015 6:43 AM
    Saturday, August 8, 2015 4:34 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    I found my PC was using IPv6 for DNS resolution, so I manually set the IPv6 DNS server address on the client PC to be the IPv6 address of the server.  This sorted my problem.
    Wednesday, September 12, 2018 6:54 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Ben, none of those versions on KB2790621 are for Windows 10.

    What version should we be downloading from that page?

    Thanks! Looking forward to your reply.

    Wednesday, September 25, 2019 4:45 PM