Problems installing server 2012 r2 connector software on Windows 10 Technical Preview

I'm having trouble installing the server 2012 r2 connector software. I get the following error.

"An unexpected error has occurred. To resolve this issue, contact the person responsible for your network".

It might be that the software just isn't compatible yet. But was wondering if anyone else has come across this? I've been asked to post this here from someone on the community forum Here

Thanks

Michael.

The following can be found in the Computerconnecor.log file.

[10/01/2014 21:06:59  f30] --------------------------------------------------------------------------------------------------
[10/01/2014 21:06:59  f30] wmain: Start of Computerconnector
[10/01/2014 21:06:59  f30] GlobalData::Initialize (192.168.5.2, C:\Users\Michael\AppData\Local\Microsoft\Windows\INetCache\IE\OVO0DBBP\ComputerConnector(192.168.5.2).exe)
[10/01/2014 21:06:59  f30] =================================
[10/01/2014 21:06:59  f30] Current Os information:
[10/01/2014 21:06:59  f30] Suite = [256]
[10/01/2014 21:06:59  f30] Type = [1]
[10/01/2014 21:06:59  f30] Architecture = [9]
[10/01/2014 21:06:59  f30] IsStarterEdition = [0]
[10/01/2014 21:06:59  f30] IsHomeSku = [0]
[10/01/2014 21:06:59  f30] Major = [6]
[10/01/2014 21:06:59  f30] Minor = [4]
[10/01/2014 21:06:59  f30] Build = [9841]
[10/01/2014 21:06:59  f30] SPMajor = [0]
[10/01/2014 21:06:59  f30] SPMinor = [0]
[10/01/2014 21:06:59  f30] =================================
[10/01/2014 21:06:59  f30] ExpandEnvironmentStrings return (C:\Windows\Temp\ClientDeploymentTempFiles\)
[10/01/2014 21:06:59  f30] GlobalData::ConstructConnectorFilenameAndUrl() failed, error hr=0x80004005
[10/01/2014 21:06:59  f30] CComputerconnector::Run: Failed to Initialize the Shared Global Data: hr = 0x80004005
[10/01/2014 21:06:59  f30] wmain: Unexcepted error occured - exiting program.
[10/01/2014 21:07:03  f30] wmain: End of Computerconnector: hr=0x80004005


October 1st, 2014 9:38pm

Having Same problem.
Free Windows Admin Tool Kit Click here and download it now
October 1st, 2014 11:14pm

I got the same error. To resolve it I ran 'my_downloader_installer.exe' as admin. I right clicked on the .exe and chose 'Run as Administrator'.
October 1st, 2014 11:31pm

Running as Administrator and in compatibility mode (8.1) allows it to get a little further but it fails to install KB2790621. What's interesting is it appears to be trying to install the RT version of this file.

ichie1 did you get it to fully install?

Here are the logs:

[10/02/2014 08:47:06 14d8] --------------------------------------------------------------------------------------------------
[10/02/2014 08:47:06 14d8] wmain: Start of Computerconnector
[10/02/2014 08:47:06 14d8] GlobalData::Initialize (192.168.5.2, C:\Users\Michael\Downloads\ComputerConnector(192.168.5.2).exe)
[10/02/2014 08:47:06 14d8] =================================
[10/02/2014 08:47:06 14d8] Current Os information:
[10/02/2014 08:47:06 14d8] Suite = [256]
[10/02/2014 08:47:06 14d8] Type = [1]
[10/02/2014 08:47:06 14d8] Architecture = [9]
[10/02/2014 08:47:06 14d8] IsStarterEdition = [0]
[10/02/2014 08:47:06 14d8] IsHomeSku = [0]
[10/02/2014 08:47:06 14d8] Major = [6]
[10/02/2014 08:47:06 14d8] Minor = [2]
[10/02/2014 08:47:06 14d8] Build = [9200]
[10/02/2014 08:47:06 14d8] SPMajor = [0]
[10/02/2014 08:47:06 14d8] SPMinor = [0]
[10/02/2014 08:47:06 14d8] =================================
[10/02/2014 08:47:06 14d8] ExpandEnvironmentStrings return (C:\Windows\Temp\ClientDeploymentTempFiles\)
[10/02/2014 08:47:06 14d8] SetPackageDlcUrl: .NET url is set to http://go.microsoft.com/?linkid=9816306
[10/02/2014 08:47:06 14d8] SetPackageDlcUrl: Connector url is set to http://go.microsoft.com/fwlink/p/?LinkId=275100
[10/02/2014 08:47:06 14d8] wmain: Calling Computerconnector::ShowWizard()
[10/02/2014 08:47:06 14d8] CComputerconnector::ShowWizard: Initializing common controls
[10/02/2014 08:47:06 14d8] CComputerconnector::ShowWizard: Done initializing common controls
[10/02/2014 08:47:06 14d8] Displaying the wizard
[10/02/2014 08:47:06 14d8] CComputerconnector::WelcomeDlgProc: IDD_PROPPAGE_WELCOME Page Initialization
[10/02/2014 08:47:06 14d8] Current user default UI lang setting is 2057
[10/02/2014 08:47:06 1340] CComputerconnector::Run: Installation is ready to run
[10/02/2014 08:47:08 14d8] CComputerconnector::TaskDlgProc: IDD_PROPPAGE_TASKS Page Initialization
[10/02/2014 08:47:08  40c] CComputerconnector::RunTasks: Running Task: Id=-1 Description=Detecting the current system requirements... Index=  0
[10/02/2014 08:47:08  40c] CMsi::IsMsiInstalled: MsiQueryProductState for ProductCode {21E49794-7C13-4E84-8659-55BD378267D5} returned -1
[10/02/2014 08:47:08  40c] CMsi::IsMsiInstalled: MsiQueryProductState for ProductCode {46DCED50-3A1D-4EF4-94F0-45F2681E3D70} returned -1
[10/02/2014 08:47:08  40c] CMsi::IsMsiInstalled: MsiQueryProductState for ProductCode {C1E4D639-4A33-4314-809E-89BD0EF48522} returned -1
[10/02/2014 08:47:08 14d8] CComputerconnector::TaskDlgProc: DIALOG_UPDATE: Running
[10/02/2014 08:47:08  40c] Connector installation state is 0
[10/02/2014 08:47:08 14d8] CComputerconnector::TaskDlgProc: DIALOG_TASK_PROGRESS: Task Description: Detecting the current system requirements...
[10/02/2014 08:47:08  40c] CComputerconnector::RunTasks: Running Task: Id=-1 Description=Downloading .NET Framework 4.5... Index=  1
[10/02/2014 08:47:08  40c] CComputerconnector::RunTasks: Running Task: Id=-1 Description=Installing .NET Framework 4.5... Index=  2
[10/02/2014 08:47:08  40c] CComputerconnector::RunTasks: Running Task: Id=-1 Description=Downloading the Connector... Index=  3
[10/02/2014 08:47:08  40c] NetworkUtil::DownloadFromLocal(pData, Windows8-RT-KB2790621-x64.msu)
[10/02/2014 08:47:08  40c] NetworkUtil::DownloadFromLocal: the package could not be found in current program location
[10/02/2014 08:47:08  40c] NetworkUtil::DownloadFromServer(pData, Connect/default.aspx?Get=ClientCore.cab&os=Windows8-RT&amd64=1, ClientCore.cab)
[10/02/2014 08:47:08  40c] NetworkUtil::DownloadFile(pData, Connect/default.aspx?Get=ClientCore.cab&os=Windows8-RT&amd64=1, C:\Windows\Temp\ClientDeploymentTempFiles\ClientCore.cab, 443, HTTPS)
[10/02/2014 08:47:08  40c] NetworkUtil::DownloadFile (https://192.168.5.2:443/Connect/default.aspx?Get=ClientCore.cab&os=Windows8-RT&amd64=1, C:\Windows\Temp\ClientDeploymentTempFiles\ClientCore.cab)
[10/02/2014 08:47:08  40c] NetworkUtil::DownloadFile - Create directory [C:\Windows\Temp\ClientDeploymentTempFiles] if not exist.
[10/02/2014 08:47:08  40c] NetworkUtil::_WinInetDownloadFile (https://192.168.5.2:443/Connect/default.aspx?Get=ClientCore.cab&os=Windows8-RT&amd64=1, C:\Windows\Temp\ClientDeploymentTempFiles\ClientCore.cab)
[10/02/2014 08:47:08 14d8] CComputerconnector::TaskDlgProc: DIALOG_TASK_PROGRESS: Task Description: Downloading .NET Framework 4.5...
[10/02/2014 08:47:08 14d8] CComputerconnector::TaskDlgProc: DIALOG_TASK_PROGRESS: Task Description: Installing .NET Framework 4.5...
[10/02/2014 08:47:08 14d8] CComputerconnector::TaskDlgProc: DIALOG_TASK_PROGRESS: Task Description: Downloading the Connector...
[10/02/2014 08:47:08  40c] InternetOpenUrl (https://192.168.5.2:443/Connect/default.aspx?Get=ClientCore.cab&os=Windows8-RT&amd64=1) returns 12038
[10/02/2014 08:47:08  40c] _WinInetDownloadFile returns 0x80072f06.
[10/02/2014 08:47:08  40c] NetworkUtil::DownloadFromServer:DownloadFile(https://192.168.5.2:443, Connect/default.aspx?Get=ClientCore.cab&os=Windows8-RT&amd64=1, C:\Windows\Temp\ClientDeploymentTempFiles\ClientCore.cab) failed with hr = 0x80072f06. Try http.
[10/02/2014 08:47:08  40c] NetworkUtil::DownloadFile(pData, Connect/default.aspx?Get=ClientCore.cab&os=Windows8-RT&amd64=1, C:\Windows\Temp\ClientDeploymentTempFiles\ClientCore.cab, 80, HTTP)
[10/02/2014 08:47:08  40c] NetworkUtil::DownloadFile (http://192.168.5.2:80/Connect/default.aspx?Get=ClientCore.cab&os=Windows8-RT&amd64=1, C:\Windows\Temp\ClientDeploymentTempFiles\ClientCore.cab)
[10/02/2014 08:47:08  40c] NetworkUtil::DownloadFile - Create directory [C:\Windows\Temp\ClientDeploymentTempFiles] if not exist.
[10/02/2014 08:47:08  40c] NetworkUtil::_WinInetDownloadFile (http://192.168.5.2:80/Connect/default.aspx?Get=ClientCore.cab&os=Windows8-RT&amd64=1, C:\Windows\Temp\ClientDeploymentTempFiles\ClientCore.cab)
[10/02/2014 08:47:08  40c] Download from url: http://192.168.5.2:80/Connect/default.aspx?Get=ClientCore.cab&os=Windows8-RT&amd64=1 failed with HTTP error 404
[10/02/2014 08:47:08  40c] _WinInetDownloadFile returns 0x8000ffff.
[10/02/2014 08:47:08  40c] NetworkUtil::DownloadFromServer:DownloadFile(http://192.168.5.2:80, Connect/default.aspx?Get=ClientCore.cab&os=Windows8-RT&amd64=1, C:\Windows\Temp\ClientDeploymentTempFiles\ClientCore.cab) failed with hr = 0x8000ffff.
[10/02/2014 08:47:08  40c] NetworkUtil::DownloadFromDLC(pData, http://go.microsoft.com/fwlink/p/?LinkId=275100, Windows8-RT-KB2790621-x64.msu)
[10/02/2014 08:47:08  40c] NetworkUtil::DownloadFile (http://go.microsoft.com/fwlink/p/?LinkId=275100, C:\Windows\Temp\ClientDeploymentTempFiles\Windows8-RT-KB2790621-x64.msu)
[10/02/2014 08:47:08  40c] NetworkUtil::DownloadFile - Create directory [C:\Windows\Temp\ClientDeploymentTempFiles] if not exist.
[10/02/2014 08:47:08  40c] NetworkUtil::_WinInetDownloadFile (http://go.microsoft.com/fwlink/p/?LinkId=275100, C:\Windows\Temp\ClientDeploymentTempFiles\Windows8-RT-KB2790621-x64.msu)
[10/02/2014 08:47:10  40c] CComputerconnector::RunTasks: Running Task: Id=-1 Description=Installing Windows Server Essentials Connector... Index=  4
[10/02/2014 08:47:10 14d8] CComputerconnector::TaskDlgProc: DIALOG_TASK_PROGRESS: Task Description: Installing Windows Server Essentials Connector...
[10/02/2014 08:47:10  40c] Entering Connector::Install.
[10/02/2014 08:47:10  40c] Connector::Install - Installing Connector by running ["C:\Windows\system32\wusa.exe" "C:\Windows\Temp\ClientDeploymentTempFiles\Windows8-RT-KB2790621-x64.msu" /quiet /norestart]
[10/02/2014 08:47:11  40c] Connector::Install - Connector installation finished with exit code = 0x80240017
[10/02/2014 08:47:11  40c] Exiting Connector::Install.
[10/02/2014 08:47:11  40c] Connector Install (C:\Windows\Temp\ClientDeploymentTempFiles\Windows8-RT-KB2790621-x64.msu) failed with status 4
[10/02/2014 08:47:11  40c] CComputerconnector::RunTasks: Task Id=-1 Description=Installing Windows Server Essentials Connector... Failed
[10/02/2014 08:47:11  40c] CComputerconnector::Run: RunTasks: 0x8000ffff
[10/02/2014 08:47:11 14d8] CComputerconnector::TaskDlgProc: DIALOG_UPDATE: FatalError
[10/02/2014 08:47:11 14d8] CComputerconnector::ErrorDlgProc: IDD_PROPPAGE_ERROR Initialization

Free Windows Admin Tool Kit Click here and download it now
October 2nd, 2014 8:03am

Same Problem here.  Point is that the connector is pushed to the client via windows updte package / msu, which is not suited for Windows 10, yet.

-> C:\Windows\Temp\ClientDeploymentTempFiles\Windows8-RT-KB2790621-x64.msu

  • Edited by sbaudy Thursday, October 02, 2014 9:40 AM
October 2nd, 2014 9:39am

Same Problem here - I hope I don't have to install the Server Preview just to get a Win 10 version of the Connector
Free Windows Admin Tool Kit Click here and download it now
October 2nd, 2014 1:31pm

Same Problem here - I hope I don't have to install the Server Preview just to get a Win 10 version of the Connector

Well I installed Server 10 Preview in a VM, and Win 10 Preview in another VM, then http'd to the Server 10 from Win 10, downloaded the connector and it failed ...

the last bit of the log shows:

[10/03/2014 15:08:51  2b4] CComputerconnector::TaskDlgProc: DIALOG_TASK_PROGRESS: Task Description: Installing Windows Server Essentials Connector...
[10/03/2014 15:08:51  b48] CComputerconnector::RunTasks: Running Task: Id=-1 Description=Installing Windows Server Essentials Connector... Index=  4
[10/03/2014 15:08:51  b48] Entering Connector::Install.
[10/03/2014 15:08:53  b48] Connector::Install - Installing Connector by running ["C:\Windows\system32\wusa.exe" "C:\Windows\Temp\ClientDeploymentTempFiles\Windows8.2-KB2790621-x64.msu" /quiet /norestart]
[10/03/2014 15:08:53  b48] Connector::Install - Connector installation finished with exit code = 0x65e
[10/03/2014 15:08:53  b48] Exiting Connector::Install.
[10/03/2014 15:08:53  b48] Connector Install (C:\Windows\Temp\ClientDeploymentTempFiles\Windows8.2-KB2790621-x64.msu) failed with status 4
[10/03/2014 15:08:53  b48] CComputerconnector::RunTasks: Task Id=-1 Description=Installing Windows Server Essentials Connector... Failed
[10/03/2014 15:08:53  b48] CComputerconnector::Run: RunTasks: 0x8000ffff
[10/03/2014 15:08:53  2b4] CComputerconnector::TaskDlgProc: DIALOG_UPDATE: FatalError
[10/03/2014 15:08:53  2b4] CComputerconnector::ErrorDlgProc: IDD_PROPPAGE_ERROR Initialization
[10/03/2014 15:09:09  2b4] wmain: End of Computerconnector: hr=0x80004005

 Surely MS would have tested the connector  ?


October 3rd, 2014 2:23pm

Same Problem here - I hope I don't have to install the Server Preview just to get a Win 10 version of the Connector

Well I installed Server 10 Preview in a VM, and Win 10 Preview in another VM, then http'd to the Server 10 from Win 10, downloaded the connector and it failed ...

the last bit of the log shows:

[10/03/2014 15:08:51  2b4] CComputerconnector::TaskDlgProc: DIALOG_TASK_PROGRESS: Task Description: Installing Windows Server Essentials Connector...
[10/03/2014 15:08:51  b48] CComputerconnector::RunTasks: Running Task: Id=-1 Description=Installing Windows Server Essentials Connector... Index=  4
[10/03/2014 15:08:51  b48] Entering Connector::Install.
[10/03/2014 15:08:53  b48] Connector::Install - Installing Connector by running ["C:\Windows\system32\wusa.exe" "C:\Windows\Temp\ClientDeploymentTempFiles\Windows8.2-KB2790621-x64.msu" /quiet /norestart]
[10/03/2014 15:08:53  b48] Connector::Install - Connector installation finished with exit code = 0x65e
[10/03/2014 15:08:53  b48] Exiting Connector::Install.
[10/03/2014 15:08:53  b48] Connector Install (C:\Windows\Temp\ClientDeploymentTempFiles\Windows8.2-KB2790621-x64.msu) failed with status 4
[10/03/2014 15:08:53  b48] CComputerconnector::RunTasks: Task Id=-1 Description=Installing Windows Server Essentials Connector... Failed
[10/03/2014 15:08:53  b48] CComputerconnector::Run: RunTasks: 0x8000ffff
[10/03/2014 15:08:53  2b4] CComputerconnector::TaskDlgProc: DIALOG_UPDATE: FatalError
[10/03/2014 15:08:53  2b4] CComputerconnector::ErrorDlgProc: IDD_PROPPAGE_ERROR Initialization
[10/03/2014 15:09:09  2b4] wmain: End of Computerconnector: hr=0x80004005

 Surely MS would have tested the connector  ?


same thing happens if u try it on a windows 8.1 vm, whats happening as far as i can tell is the connector software for the tech preview of windows server is only downloading about 48kb of the msu file needed then failing..... microsoft should have seen this.... i dont get why they didnt test it
Free Windows Admin Tool Kit Click here and download it now
October 4th, 2014 12:52am

Im also having the same issue, any testing needed let me know...

October 4th, 2014 6:29pm

I also have the same issue. Hope we can find a fix for it.
Free Windows Admin Tool Kit Click here and download it now
October 5th, 2014 12:51pm

Could you possibly provide more details on how you resolved it?  Simply put, were you able to get the Windows 10 Tech Preview computer connect to Server 2012 R2 Essentials and is it listed as a client computer now?
October 6th, 2014 1:14am

The current Windows Server Essentials Connector is designed to be installed on Windows 7 Service Pack 1 (SP1), Windows 8, Windows 8.1, and Mac OS X 10.6 -10.8. I'm pretty sure Microsoft will update this software as the development of Windows 10 progresses. Please note the Microsoft does not want this Windows Technical Preview version operating in a "live environment".
Free Windows Admin Tool Kit Click here and download it now
October 6th, 2014 1:45am

While I respect Carey's answer I still consider the connection to Server 2012 R2 Essentials part of normal testing. That does not mean we are in a "live environment". This is what testing is all about: Find problems and report them.

Can we think of a work around my e.g. modifying the MSU package?

October 6th, 2014 6:23am

I would just like to add that it's not just the Win 10 <> Windows Server 2012 R2 connector that's broken, the Win 10 <> Windows Server 10 Preview connector is also broken, and that's definitely not a live environment

 
Free Windows Admin Tool Kit Click here and download it now
October 6th, 2014 6:54am

While I respect Carey's answer I still consider the connection to Server 2012 R2 Essentials part of normal testing. That does not mean we are in a "live environment". This is what testing is all about: Find problems and report them.

Can we think of a work around my e.g. modifying the MSU package?


Agreed on Carey's answer, but as you can add a Win 10 preview build to a company domain (Server 2012R2) for testing I would have expected similar from the Essentials system. IMHO of course.
October 6th, 2014 8:03am

Yep same problem here.

Testing in Hyper V I am unable to connect Windows 10 Tech Preview to either Windows Server (10) Tech Preview with Essentials Experience role installed or Server 2012 R2 Essentials.

Log shows the issue with "Windows8.2-KB2790621-x64.msu failed with status 4"


Im guessing this MSU is not available for download yet as I tried visiting the URL specified in the log file directly and there is no download.
  • Edited by djflex1981 Tuesday, October 14, 2014 1:41 PM
Free Windows Admin Tool Kit Click here and download it now
October 14th, 2014 1:27pm

Disappointed that after today's Patch Tuesday updates to both Windows 10 TP and Windows Server 2012 R2 Essentials the Connector still does not work! I suspect that the problem is simply that the Connector checks the OS and rejects Windows 10 TP as 'not known here'. If this is the case PLEASE update the filter - we were promised frequent updates for Win 10 TP!

One of the most important aspects of testing any OS is surely that the Backup works; more or less 'by definition' any server will have several client computers, most in a "live environment", one only for test purposes e.g. checking out Win 10 TP! 

October 14th, 2014 8:16pm

Still not fixed in November's Patch Tuesday
Free Windows Admin Tool Kit Click here and download it now
November 12th, 2014 9:54am

It'll get here eventually. Frustrating I know but it is very early days!
November 15th, 2014 11:51am

Tried again today with build 9926 with the January Update (KB3034229) and the error is still there.
Free Windows Admin Tool Kit Click here and download it now
January 23rd, 2015 10:47pm

Does anyone know when MS will address this?  I would think they would WANT to test win 10 with a server environment. 
January 25th, 2015 10:54pm

I've had this problem every time I beta tested new Windows on older SBS 2003 and then SBS 2008 (and even WHS I believe). Both times it was an easy fix to edit some XML files to trick the server into talking to, and allowing, newer OS's to join using the connector. Of course MS always ended up patching the Server later once the OS was RTM and the patch would do this for you officially. I searched out one of the old articles online and figured this would quickly get me past this with Win 10 and WSE 2012 R2. Not so fast. I'm posting here incase these clues allow someone smarter than I to piece together a similar fix for win 10.

This is a link to one of many solutions for this problem back in SBS 2008.  Fix for SBS 2008

Since 2012 R2 is no longer SBS, I cannot find the two paths listed in the article.  I was however able to look into the IIS folders for the connect site and found a similar "package" folder (C:\Program Files\Windows Server\Bin\WebApps\Client\package) but it was empty.  Also note that SBS was looking for "PackageFiles" and 2012 R2 only has a "package" folder.  Part of me wants to create the missing folders and files and then edit the supportedOS.xml file but since this is my production server I'm not gutsy enough to try.

With no XML files to be found on the new 2012 R2 server, I thought maybe they changed their process and put the supported OS version into the registry.  I did a quick and dirty look in the registry and quickly stumbled onto the HKLM\SOFTWARE\Microsoft\Windows Server\Version key and see some very similar data being stored here including several "ClientRequired_Win64" keys with versions as well as a "ClientRequired_MacOS" key and version.  Seems like I'm close.

So the only other thought that comes to mind is with Win 10, MS is going to artificially increment the version from 6.x.x to 10.x and I wonder if this is just too big of a change to easily fix?

Again, no solution here and just as desperate as you all to get this fixed.  Just hoping some of what I've discovered might inspire someone else to discover an actual fix!

Chris

  • Proposed as answer by Dansing Proton Tuesday, February 03, 2015 2:03 PM
Free Windows Admin Tool Kit Click here and download it now
January 26th, 2015 4:11pm

Having the same issue with my server as well. I am mainly worried about the backup feature, is there any alternate you guys are using to backup the data on your Win-10 TP maching..??
February 3rd, 2015 2:07pm

While I respect Carey's answer I still consider the connection to Server 2012 R2 Essentials part of normal testing. That does not mean we are in a "live environment". This is what testing is all about: Find problems and report them.

Can we think of a work around my e.g. modifying the MSU package?

I also cannot connect to my Windows 2012 R2 Essentials with either the W10TRPro (9922) or W10E.  I agree MS should have made a work around to enable making a daily method of connecting to the server but only in a home type environment.
Free Windows Admin Tool Kit Click here and download it now
February 3rd, 2015 3:56pm

Tried again today with build 9926 with the January Update (KB3034229) and the error is st
February 3rd, 2015 4:04pm

HI!  I would just like to add my concern to this thread.  As of 4 Feb 2015 I cannot connect a W10 TP computer to the trial version of Windows Server 2012 R2 Essentials.  I need to test this capability before planning to replace a currently working network which uses Windows Home Server 2011 and Vista clients.  I want to plan for W10 clients and the 2012 R2 server.  I see references to a planned W10 server, but I didn't know this was being planned.  I will see if I can find out more about the planned new server.  Maybe it will play well with the W10 client.
Free Windows Admin Tool Kit Click here and download it now
February 5th, 2015 2:44am

I would also like to see a beta connector released so we can test this.
February 5th, 2015 11:35pm

This build of Windows 10 is good enough for daily use, but I do miss my backups :/
Free Windows Admin Tool Kit Click here and download it now
February 8th, 2015 7:27pm

So the only other thought that comes to mind is with Win 10, MS is going to artificially increment the version from 6.x.x to 10.x and I wonder if this is just too big of a change to easily fix?

The reason I had been lead to believe that the upcoming version would be called "10" is that too many application installation programs erroneously parse "OS Name" instead of "OS Version". Installation programs that make this imprecise calculation in the future could foreseeably have difficulty disambiguating Windows 95, Windows 98, and Windows 9.

But maybe Microsoft will artificially increment version from 6.x to 10.x? One might think that would make confusion greater, not less. And yet:

Go figure.

PS: Still no luck connecting Win10 to WSE2012R2 via http://server/connect

February 25th, 2015 1:45pm

On Wed, 25 Feb 2015 13:45:15 +0000, JohnW4 wrote:

But maybe Microsoft will artificially increment version from 6.x to 10.x? One might think that would make confusion greater, not less. And yet:

Microsoft has already announced that kernel version will change

Free Windows Admin Tool Kit Click here and download it now
February 25th, 2015 1:50pm

Currently using build 10049, but still not able to run the connector software :-(

Any news from Microsoft or anywhere when we will be able to connect the Win10TP's to the WSE2012R2 server?

April 14th, 2015 3:42am

Still not working, would love to be able to fully test ..
Free Windows Admin Tool Kit Click here and download it now
April 21st, 2015 4:13pm

Currently using build 10061, but still not able to run the connector software....
April 27th, 2015 1:55am

10074 - still nothing....
Free Windows Admin Tool Kit Click here and download it now
April 30th, 2015 7:33pm

THANKS so MUCH, everyone, for keeping this thread alive.  I expect to read about it here first when FINALLY a W10 connector works from Server 2012 R2!!!

April 30th, 2015 9:23pm

I just found this announcement:

http://blogs.technet.com/b/configmgrteam/archive/2015/05/04/announcing-support-for-windows-10-management-with-system-center-configuration-manager.aspx

Does anyone know if this will allow us finally to connect a W10 client to Windows Server 2012 R2 Essentials???

Free Windows Admin Tool Kit Click here and download it now
May 7th, 2015 3:03am

No.  System Center is a completely separate suite of tools purchased solely to administer and manage clients, servers and VM's in Windows Server.  It is a fairly involved, higher level, enterprise product.

What we are waiting for is a hot fix or patch specifically written for Windows Essentials Server 2012 R2 (or Windows Server 2012 R2 with Essentials experience turned on).  This patch will probably add a registry key or one line to a config file that will simply allow the connector to recognize Win 10 as a compatible OS to connect to the essentials server.  There is no compatibility problem really, this is just an artificial limitation hard coded into Essentials and frankly I am miffed they haven't explained how we can work around it until the hot fix comes out.

May 8th, 2015 12:41pm

Just installed server TP2 and his Essentials role, joined to the domain a 10074 x64 client.
Still wont work.

Here is the relevant log:

>>>
[05/08/2015 14:10:04 1248] NetworkUtil::DownloadFromDLC(pData, http://go.microsoft.com/fwlink/?LinkId=507716, Windows8.2-KB2790621-x64.msu)
[05/08/2015 14:10:04 1248] NetworkUtil::DownloadFile (http://go.microsoft.com/fwlink/?LinkId=507716, C:\WINDOWS\Temp\ClientDeploymentTempFiles\Windows8.2-KB2790621-x64.msu)
[05/08/2015 14:10:04 1248] NetworkUtil::DownloadFile - Create directory [C:\WINDOWS\Temp\ClientDeploymentTempFiles] if not exist.
[05/08/2015 14:10:04 1248] NetworkUtil::_WinInetDownloadFile (http://go.microsoft.com/fwlink/?LinkId=507716, C:\WINDOWS\Temp\ClientDeploymentTempFiles\Windows8.2-KB2790621-x64.msu)
<<<

Right now this URL opens a generic Essentials 2012 page. This page will  save as "Windows8.2-KB2790621-x64.msu" with 40Kb and, of course, the install will fail.


Free Windows Admin Tool Kit Click here and download it now
May 8th, 2015 5:51pm

Microsoft, we are still waiting!  Isn't it odd that Windows 10 TP can receive the connector software from a computer running Windows Home Server 2011 and connect with no problems?  In view of this, I find it ludicrous that Windows Server 2012 R2 Essentials can't provide a similar connector that works.  Come on, Microsoft!  Someone is dragging their heels.  This problem could probably be solved with a couple of lines of well-placed code.     --actor39
May 11th, 2015 6:11pm

On Windows 10 build 10122 and the problem still remains, unable to connect to Windows Server 2012 R2 Essentials.
Free Windows Admin Tool Kit Click here and download it now
May 24th, 2015 3:40pm

Check out this list:

Win7 x64  http://download.microsoft.com/download/4/B/8/4B8C99DA-B764-4F80-8574-CB16A6F37CA5/Windows6.1-KB2790621-x64.msu

Win7 x86  http://download.microsoft.com/download/4/B/8/4B8C99DA-B764-4F80-8574-CB16A6F37CA5/Windows6.1-KB2790621-x86.msu

Win8 x64  http://download.microsoft.com/download/4/B/8/4B8C99DA-B764-4F80-8574-CB16A6F37CA5/Windows8-RT-KB2790621-x64.msu

Win8 x86     http://download.microsoft.com/download/4/B/8/4B8C99DA-B764-4F80-8574-CB16A6F37CA5/Windows8-RT-KB2790621-x86.msu

 win8.1 x64  http://download.microsoft.com/download/4/B/8/4B8C99DA-B764-4F80-8574-CB16A6F37CA5/Windows8.1-KB2790621-x64.msu

win8.1 x86  http://download.microsoft.com/download/4/B/8/4B8C99DA-B764-4F80-8574-CB16A6F37CA5/Windows8.1-KB2790621-x86.msu

win10 x64  http://download.microsoft.com/download/4/B/8/4B8C99DA-B764-4F80-8574-CB16A6F37CA5/Windows8.2-KB2790621-x64.msu

win10 x86  http://download.microsoft.com/download/4/B/8/4B8C99DA-B764-4F80-8574-CB16A6F37CA5/Windows8.2-KB2790621-x86.msu

May 27th, 2015 9:54am

What are these updates supposed to do?
Free Windows Admin Tool Kit Click here and download it now
May 27th, 2015 1:43pm

Check out this list:

Win7 x64  http://download.microsoft.com/download/4/B/8/4B8C99DA-B764-4F80-8574-CB16A6F37CA5/Windows6.1-KB2790621-x64.msu

Win7 x86  http://download.microsoft.com/download/4/B/8/4B8C99DA-B764-4F80-8574-CB16A6F37CA5/Windows6.1-KB2790621-x86.msu

Win8 x64  http://download.microsoft.com/download/4/B/8/4B8C99DA-B764-4F80-8574-CB16A6F37CA5/Windows8-RT-KB2790621-x64.msu

Win8 x86     http://download.microsoft.com/download/4/B/8/4B8C99DA-B764-4F80-8574-CB16A6F37CA5/Windows8-RT-KB2790621-x86.msu

 win8.1 x64  http://download.microsoft.com/download/4/B/8/4B8C99DA-B764-4F80-8574-CB16A6F37CA5/Windows8.1-KB2790621-x64.msu

win8.1 x86  http://download.microsoft.com/download/4/B/8/4B8C99DA-B764-4F80-8574-CB16A6F37CA5/Windows8.1-KB2790621-x86.msu

win10 x64  http://download.microsoft.com/download/4/B/8/4B8C99DA-B764-4F80-8574-CB16A6F37CA5/Windows8.2-KB2790621-x64.msu

win10 x86  http://download.microsoft.com/download/4/B/8/4B8C99DA-B764-4F80-8574-CB16A6F37CA5/Windows8.2-KB2790621-x86.msu

Nice Find, Works Great,

installs Windows Server Essentials Connector run that and you are good to go.

Works with 10074

May 30th, 2015 3:19am

Hmm, win10 x64 seems to not work on 10130, says "update not applicable to your computer".
Free Windows Admin Tool Kit Click here and download it now
May 30th, 2015 4:05am

Same here also on build 10130 Win 10 Pro x64
June 1st, 2015 5:57am

It's strange....I saw a couple of messages here indicating that all the links in the lists above were to connectors served up by Server 2016 preview.  But now those messages are gone.  Anybody know what happened?  And now that the W10 release date is fixed at 29 July, the clock is really ticking to get this connection problem fixed!  Will businesses stay away from W10 because of this defect?  My guess is yes, in BIG numbers.  So if this lack of connector software continues, Microsoft will not get the massive conversion to W10 that they are trying to engineer with the free upgrades. Or else they will have some pretty upset customers who install the upgrade and THEN discover they can't connect to their server.   I guess we just have to stay tuned. 
Free Windows Admin Tool Kit Click here and download it now
June 1st, 2015 3:15pm

I can attest that Windows8.2-KB2790621-x64.msu Effectively joins Windows 10 x64 to Windows 2012 R2 Domain.

What I tried:

1-Open the browser, navigating to http://your-server-name-or-ip/connect. . .

Downloads the connector software but fails to install.

2- Followed the Tutorial described here:  www.youtube.com/watch?v=9Rs4RSfTgL0

Works. The Windows 10 computer, virtual or real joins the domain, but the launchpad and other goodies do not install. Note: In order fort this to work you need to modify the Network adapter settings. You need a static IP address, and you need to point to your server IP address as the primary DNS provider.

3- Installed Windows8.2-KB2790621-x64.msu. Joined the Domain. Installed Launchpad, Dashboard and all the bells and whistles. My Windows 10 is Build 10074 .

June 1st, 2015 5:53pm

I can understand that lots of people use domains with their servers, but for the small network I service, it is not necessary.  And in fact, I have joined a Windows 7 computer to my Server 2012 R2 Essentials without it being a domain member, using the connector software, which apparently manages the connection without requiring a domain join.  So it should also be possible to do the same for a Windows 10 computer.  That is what I am waiting for, and as of yet, I know no way to do it. 

   But I did try to join my W10 computer to the server domain, and I got this error message:  The specified domain does not exist or cannot be contacted.  My server does have a static IP address, and after I pointed to its address as the primary DNS provider, I get this error message:  this user can't sign in because this account is currently disabled. 

Free Windows Admin Tool Kit Click here and download it now
June 1st, 2015 9:16pm

FWIW, I tried the update and it did work but only for Build 10074.  You can also skip domains the same way as in the past.  What I needed though was do a menu search for the connector installer after the update ran since it wasn't obvious where it was hiding. At least with 10074 it seems stable and both Launchpad and Dashboard were available, although the Dashboard indicated the OS was not up to date on the Windows 10 machine. 

The problem was as soon as I updated to 10130, everything fell apart.  Not only did it uninstall the connector but, after the first time the computer (a SP3) went to sleep, it could no longer connect to the server at all.  The odd thing was that I could still execute the VPN connection and it claimed to be connected.  Unfortunately, regardless of what I tried I was stuck with a message when trying to access the server that I didn't have permission and to contact the administrator (who happens to be me). 

I tried this on a second machine (a surplus Dell Inspiron 11 sitting on the shelf in case of emergency). Again everything worked when it was on 10074 and then same problems with 10130.  Since the Dell has Windows 10 on as a second partition I will test more in the future. The SP3 was rolled back to Windows 8.1 since I am finding SP3s to be a nuisance when setting up a dual boot. 

Personally, I am very skeptical Windows 10 will be genuinely ready for prime time in seven weeks, at least for the SP3.  I am also troubled by Microsoft's near complete silence on the subject of the connector for Server Essentials 2012 R2.  Comments about not testing Windows 10 in live environments, etc., are also completely ridiculous.  At some point we need to be able to test the new OS regarding how it interacts with a server and doing Microsoft's bug checking after release is unacceptable.  At this point, however, that appears to be the option on the table.  Since I am not willing to do that, our machines may stay on Windows 8.1 for quite awhile.  Quite frankly, I am extremely disappointed in Microsoft's handling of small businesses in this process.  It seems if you are a consumer they care and if you are enterprise they really care. Small businesses, however, have been given no opportunity to test their new OS with respect to stability with Microsoft's own current small business server OS. 

For some reason I also have a lurking fear that the old Microsoft is going to come to the surface at some point and they will make up some excuse and try to shove Windows Server 10/2016 as the "fix" for connectivity issues. Just not feeling very charitable towards them at the moment given deprecated features in Windows 10 (OneDrive and hamstrung touch interface); the mess that it is on their own premium SP3 hardware; and their inability to release (or even really discuss) a working server connector in more than seven months. 

June 2nd, 2015 11:10pm

I, too, share your skepticism regarding the readiness of Windows 10 in the small business environment using a server with workstations joined to a domain. My business focuses on IT support to small businesses, and every one of our clients is running a domain managed by either Windows Small Business Server 2008 or 2011. Only our own in-house domain is based on Windows Server 2012 Essentials. We are only interested in deploying Windows 10 in server-managed domain networks.

With the lack of a working connector to Windows Server 2012 Essentials, we've postponed the testing of Windows 10 in our in-house system until we can experience the fully managed functions, including status of client updates and backups. That's not possible with the current Windows 10 preview. Worse, we have no information on how Windows 10 clients will work with Windows Small Business Server 2008 or 2011. We haven't even considered trying out that until we see it integrate successfully with Windows Server 2012 Essentials.

Now I have to tell my clients who want to take advantage of the free upgrade to Windows 10 that we don't know when--or if ever--they can do so while retaining their existing Windows Small Business Server 2008 or 2011 environments. We're not sure when we'll even know! And given we'll only have a year to qualify for the free upgrade, I'm not confident we'll get those answers in time.

I agree that small business environments are getting the message that Microsoft doesn't care about them. If they did, they would have given us an opportunity to test Windows 10 for stability with Microsoft's own current small business server (Windows Server 2012 Essentials), and older, still supported small business servers (Windows Small Business Server 2008 or 2011). Indeed, I wouldn't be surprised if/when Microsoft states that moving forward to Windows Server 2012 or even 2016 is the only way to make Windows 10 clients fully operate as expected in a domain environment. So the "free" upgrade to Windows 10 will cost my clients thousands of dollars to buy a new server, new server software, fees for us to perform the migration, and a big interruption of their businesses. I'm not complaining about the opportunity to make some money; instead, I'm angry that we can't do it when it suits our clients. Why Microsoft has to push us head long into these situations with no reasonable chance to prepare for them is really wearing us out.

Microsoft should make the connector work as soon as possible so we can at least gain experience and confidence that Windows 10 will work for our clients in a Windows Server 2012 Essentials environment. And, it should consider doing the work to add Windows 10 to the list of supported clients for the currently supported small business server environments (Windows Small Business Server 2008 and 2011). Also, I think the qualifying business versions of Windows (Windows 7 Professional and Windows 8.1 Pro) should have 2 years to qualify for the upgrade--or at least a year after they provide evidence Windows 10 works as expected (with all the full management features) in a domain environment.

And I thought Windows 10 was going to be re-focused on the business desktop. Apparently, the doesn't include the small business desktop, which I'd guess accounts for something like 80% of all the business desktops. What a disappointment.

Free Windows Admin Tool Kit Click here and download it now
June 4th, 2015 6:30pm

That definitely sums up my opinion.  FWIW, I let all of our staff know today that we will not be upgrading to Windows 10 anytime soon.  Everyone is remote and we rely on stable connectivity. Until I have had time to thoroughly test it, it cannot go onto any company machine. 

The fact that there is a working connector for Windows 10 beta to the beta server OS amply demonstrates something could have been released. I would also challenge anyone at Microsoft to justify why they would release a beta to beta connector, or why the one for the old home server still works, but they couldn't put something out for their supposed current recommended server OS.  We have to be able test Windows 10 in a server environment or a sizeable segment of users need to operate on faith that it will be stable. 

Time is running out to test for implementation in this fiscal year. While some staff may whine about the Windows 8.1 interface, the OS is solid and stable and works well with Windows Server Essentials 2012 R2, provided I periodically delete the latest updates that break the restore functions. Quite frankly, this is the first time I have questioned sticking with a Microsoft Server OS and that I have outright blocked a Windows upgrade cycle.  If there is even a hint of a needed upgrade to a new server OS, I will be looking at server OS alternatives....

June 5th, 2015 12:02am

Worked for me as well on Windows 10 is Build 10074, though Dashboard states Group Policy is "not applicable".... not much good.  I agree with most posters that MS has cut us out, at least for now.

On my win8.1 machines, in C:\Windows\System32\GWX\config.xml, there is this line: <EnableDomainJoined>false</EnableDomainJoined>

Free Windows Admin Tool Kit Click here and download it now
June 9th, 2015 5:29pm

I agree.  I have been able to test in a domain environment ( bunch of VMs to simulate) just to make sure that everything will work for my clients, a lot of which work with sensitive data ad are looking to the biometric logins to enhance security. Unfortunately, I have literally DOZENS of customers that I have to tell they cannot upgrade at this time as we are 6 weeks from release and I STILL cannot fully test in their environments (WSE 2012 R2).  As far as I am concerned, no connector = defective and broken product and promises.

Can Somebody that is within the Microsoft PLEASE:

1. Take ownership of this problem

2. Advise of a reasonable schedule for testing solutions

3. Follow through more than just "It's not my job/forum/responsibility"

I shall eagerly await your reply,

Bob Hessenauer

  • Proposed as answer by BobHessenauer Monday, June 15, 2015 8:20 AM
June 10th, 2015 4:23pm

Just a bit more information in case people are interested. I know many are aware you can connect Windows 10 to the old Homeserver 2011 OS. I just confirmed that you can also connect to WSE 2012 (sans R2). I connected the current Windows 10 build (10130) on a test dual boot system to my old backup server.  It is an old headless server that was never worth the trouble to upgrade to R2 so it just serves as a redundant backup. Out of curiosity though, I downloaded the connector from the machine and it immediately set everything up - went to the dashboard and confirmed everything is correct. BTW, I then disconnected the old server from the network and ran the old 2012 connector on a second Windows 10 dual boot system, input the IP address of the R2 server, and it got about 75% through the setup (and inserted a VPN connection in the network configuration) before getting the usual message and rolling itself back.

I don't like sounding so suspicious and cynical but I am really more and more inclined to believe they intentionally broke the connector for WSE 2012 R2. You can connect Windows 10 builds to an old home server OS and WSE 2012. You can also connect it to Windows Server TP, meaning you can set up a beta OS to work with a beta server OS. Very briefly you could even use the connector for the beta server OS to connect the 10074 Windows 10 build to WSE 2012 R2.  That is something they broke in short order.  It requires a serious bit of suspension of disbelief to accept there is any major limitation other than the fact they do not want any WSE 2012 R2 users to test Windows 10. The utter silence from Microsoft also probably says everything one needs to know. 

Free Windows Admin Tool Kit Click here and download it now
June 11th, 2015 9:51pm

Time is running out to test for implementation in this fiscal year. While some staff may whine about the Windows 8.1 interface, the OS is solid and stable and works well with Windows Server Essentials 2012 R2, provided I periodically delete the latest updates that break the restore functions.

Microsoft has just released a hotfix for this problem. I have tested it on my Win 8.1 Pro 64 bit system and it works.  The Hotfix number is KB3045682.
June 16th, 2015 9:47am

Tim,

Unfortunately, this is not a fix for which this thread was created.  This hotfix (while useful) is for fixing the issue with restore functionality being broken. This thread is for the glaring lack of ability to install WSE 2012 R2 Connector software on a Windows 10 TP or Preview system. This is a problem that STILL remaines unresolved, and with GA coming on July 29th we are lamenting having to tell our clients/co-workers that they will not be able to upgrade because it may break their networks beyond repair.   At least now we can get clean backup and restores from WSE 2012 R2.

Hope this helps,

Bob Hessenauer

Free Windows Admin Tool Kit Click here and download it now
June 16th, 2015 6:31pm

Time is running out to test for implementation in this fiscal year. While some staff may whine about the Windows 8.1 interface, the OS is solid and stable and works well with Windows Server Essentials 2012 R2, provided I periodically delete the latest updates that break the restore functions.

Microsoft has just released a hotfix for this problem. I have tested it on my Win 8.1 Pro 64 bit system and it works.  The Hotfix number is KB3045682.
June 16th, 2015 11:32pm

Back on topic...

I installed the connector into build 10074 but I had to install the English (United States) language, then download the additional language pack and reboot before it would install. I am using the English UK Build so one to look out for.

I then upgraded to build 10130 and the machine remained joined to the domain with the connector installed and working.

This was connecting to the Server Technical Preview 2 build with essentials enabled not SE 2012 R2, but assume it would work on both.

Unfortunately I cant install the connector directly into build 10130 without the "This update is not applicable" error. Does anyone know a way around this?



  • Edited by djflex1981 Wednesday, June 17, 2015 5:53 PM
Free Windows Admin Tool Kit Click here and download it now
June 17th, 2015 5:49pm

Yet another Patch Tuesday goes by with STILL NO RESOLUTION to this problem which has been reported, analyzed, debated, and complained about since LAST YEAR.  At this point I have no choice but to advise ALL of my clients/friends/family that it is definately NOT in their best interest to upgrade to Windows 10 at this time as it is still an untested and incomplete product.

Thanks for once again living down to my expectations Microsoft...I honestly thought you would get it right this time.

Bob Hessenauer

June 17th, 2015 6:02pm

Back on topic...

I installed the connector into build 10074 but I had to install the English (United States) language, then download the additional language pack and reboot before it would install. I am using the English UK Build so one to look out for.

I then upgraded to build 10130 and the machine remained joined to the domain with the connector installed and working.

This was connecting to the Server Technical Preview 2 build with essentials enabled not SE 2012 R2, but assume it would work on both.

Unfortunately I cant install the connector directly into build 10130 without the "This update is not applicable" error. Does anyone know a way around this?



Unfortunately, your assumption is incorrect.  Upgrading to 10130 from 10074 uninstalls the connector when connected to WSE 2012 R2.  One of the problems is they are paying far more attention to the Server Preview than to WSE 2012 R2. As far as I know that is why the connector exists - the fact it worked with 10074 and 2012 R2 was not by intent.  After upgrading to 10130 I also had to do far more work than should have been necessary to even just to get back shared folder access to the server at all.   Clean install of 10130 offers no connector option but at least accessing shared folders was (mostly) straightforward.    

BTW, I believe there is a statement from Microsoft over on the Server Preview side (I think in the blog) about connectivity with build 10130.  As far as I know they will not update the current connector to install between that build and the Server preview.  At least they have had the courtesy to say something to users of the two previews, as opposed to the continued silence re WSE 2012 R2.

  • Edited by StephenTX Wednesday, June 17, 2015 7:13 PM
Free Windows Admin Tool Kit Click here and download it now
June 17th, 2015 7:04pm

Yep! I was just about to edit my post to say it had actually uninstalled... for some reason I thought it had survived the upgrade but it has not :(

Hopefully will be sorted fairly soon with not long to go till release!

June 17th, 2015 9:44pm

Same here. The log file shows now nearly at the beginning, that the system is not supported:

  • [06/23/2015 17:10:56 1598] wmain: Start of Computerconnector
    [06/23/2015 17:10:56 1598] GlobalData::Initialize (10.10.0.4, ...)
    [06/23/2015 17:10:56 1598] =================================
    [06/23/2015 17:10:56 1598] Current Os information:
    [06/23/2015 17:10:56 1598] Suite = [256]
    [06/23/2015 17:10:56 1598] Type = [1]
    [06/23/2015 17:10:56 1598] Architecture = [0]
    [06/23/2015 17:10:56 1598] IsStarterEdition = [0]
    [06/23/2015 17:10:56 1598] IsHomeSku = [0]
    [06/23/2015 17:10:56 1598] Major = [10]
    [06/23/2015 17:10:56 1598] Minor = [0]
    [06/23/2015 17:10:56 1598] Build = [10130]
    [06/23/2015 17:10:56 1598] SPMajor = [0]
    [06/23/2015 17:10:56 1598] SPMinor = [0]
    [06/23/2015 17:10:56 1598] =================================
    [06/23/2015 17:10:56 1598] ExpandEnvironmentStrings return (C:\WINDOWS\Temp\ClientDeploymentTempFiles\)
    [06/23/2015 17:10:56 1598] Failed to know os system info, or the current system is not support
    [06/23/2015 17:10:56 1598] CComputerconnector::Run: Failed to Initialize the Shared Global Data: hr = 0x80004005
    [06/23/2015 17:10:56 1598] wmain: Unexcepted error occured - exiting program.
    [06/23/2015 17:11:07 1598] wmain: End of Computerconnector: hr=0x80004005

But there are some weeks until the release ;-))

Best regards,
RoP

Free Windows Admin Tool Kit Click here and download it now
June 23rd, 2015 3:44pm

I just tried to run the connector from Server 2012 R2 Essentials on build 10158 of W10 TP.  Doesn't work.  Same error notice as usual.  What can we say?  Time grows ever shorter.  I'm about ready to give up hope that it will ever work.  Why else would they wait so long to fix it?
June 30th, 2015 4:08am

In regard to the above post:  I tested once again with build 10159.  Same result. 
Free Windows Admin Tool Kit Click here and download it now
July 1st, 2015 2:49pm

10162 produces the same result...no connector install and errors if you try.

Bob Hessenauer

July 2nd, 2015 11:42pm

Trying to install the connector after each build isn't going to make a difference, the issue isn't the Windows 10 OS, it the connector software.

Until they build a version specifically for Windows 10, it's just not going to work.

When and if, one is built, it should appear here.

Michael.

Free Windows Admin Tool Kit Click here and download it now
July 3rd, 2015 9:46pm

I agree and thanks for the link.

I just think it helps to keep this thread active until Microsoft do something, even some sort of announcement re intent would be a start.

I would have to say your use of the word "if" fills me with dread. I dont see how Microsoft can not support their latest and greatest on the current release of their server OS.

July 4th, 2015 12:19am

Fills me with dread also...  Obviously, there will be no connector for the July 29th rollout or we would have had it by now.  Makes me wonder if MS will make a connector for the Enterprise version of W10 since that won't be a free upgrade... and SMB and WSE home users will be sol since they could upgrade to 10 for free?  At any rate MS seems not to care about the little guys... hope I'm wrong.
Free Windows Admin Tool Kit Click here and download it now
July 4th, 2015 9:39pm

The 'if' was in relation to the fact that they haven't actually said this will be fixed. However, I wouldn't worry I'm sure they'll update the connector. After all 2012 server is still very current. It just may take some time.

I personally just wish they would say they know about the issue, and that an update will be released at some point.

Michael.

July 5th, 2015 9:50pm

I personally just wish they would say they know about the issue, and that an update will be released at some point.

Michael.

This.

Please MS, say something.
In a few weeks I'll have to explain some clients why I wont be updating theyr Windows 8.1 systems. It would be great to have an official say from MS to back me up.

Free Windows Admin Tool Kit Click here and download it now
July 6th, 2015 1:31pm

Another week, including Patch Tuesday and nothing from Microsoft.
July 15th, 2015 3:42am

Another week, including Patch Tuesday and nothing from Micro
Free Windows Admin Tool Kit Click here and download it now
July 16th, 2015 1:26am

I have also tweeted Gabe Aul twice, about a week apart with no response, even a "I'll look into it".  He appears only to respond to people having trouble with the Windows 10 install process and
July 17th, 2015 12:28am

We need a connector!! Please!
Free Windows Admin Tool Kit Click here and download it now
July 19th, 2015 1:52am

All,

What I find interesting is that they have already patched WSUS to include Windows 10, but they cannot release a WSE 2012 R2 Connector for the same. 

Microsoft, we are TEN DAYS from release and GA - where and when can we expect a working connector so we can update our clients to the "flagship" operating system you are releasing.

We are waiting....

July 20th, 2015 1:37am

Still nothing new here? come on Microsoft! The RTM Version of Win 10 is out and still no connector, even not in the Server Technical Preview 2!
Free Windows Admin Tool Kit Click here and download it now
July 21st, 2015 8:51am

I'm keenly following this thread and thank all those that go before in asking the Q.  Like mentioned I too will be unable to upgrade to Win10 on most PC (except the trivial) if they can not be backed up and restored.  With only 10 days to go.... it is hard to understand the silence on this issue from MS as what company would make the switch?

Thanks

Nathan

July 21st, 2015 11:45am

How I see this: MS hate small business. The main reason they killed Windows SBS is because there was too much feature for too little money. Better to sell subscriptions then a full solution.

Essentials is a not so great but still cheap solutions to small business. There is clearly no interest to invest on this "niche" market. Not at the same level as the client and real server OS.


Free Windows Admin Tool Kit Click here and download it now
July 21st, 2015 12:50pm

I hope this gets fixed real soon..... 7 days now :(
July 21st, 2015 11:27pm

Can't believe still nothing and releases next week. Microsoft this is your own product! That still under support and should be fixed/updated!
Free Windows Admin Tool Kit Click here and download it now
July 22nd, 2015 4:26am

Hey Microsoft - in the words of Doctor Evil - "throw me a friggin bone - will ya?"  Hey can we get an update on the plans, progress, anticipated release of a new connector for Windows 2012 R2 Essentials so that we can CONTINUE to back up our systems with Windows Server as we have been with Windows 7, 8 and 8.1?  We UNDERSTAND that it may be that the connector could not be updated until Windows 10 was out of the oven and ready for consumption.  I think we are there by now - release is 7 days away.  What gives?
July 22nd, 2015 12:05pm

I posted the following on Insider forum and tweeted both @GabeAul and @Windowsserver:

http://answers.microsoft.com/en-us/insider/forum/insider_wintp-insider_web/windows-server-2012-r2-essentials-client-connector/cf303cc3-7897-4511-96dc-9796de18b79c. Silence continues....

Free Windows Admin Tool Kit Click here and download it now
July 23rd, 2015 4:06am

Here's another nugget to chew on... I recently noticed that all of my (Windows Server 2012r2 Essentials) domain-joined clients where NOT displaying the  "Get Windows 10" icon in the system tray. When I went to the Windows 10 FAQ site, I found no mention of a compatibility problem with WSE Connector. However, as a test, I removed a Windows 8.1 Pro client from the domain and uninstalled its connector. After the reboot, the icon was present on the system tray. I was then able to "reserve" my Windows 10 copy.

My plan is to install Windows 10 on that system and then try to connect to WSE. Honestly, I do not have a good feeling about this!


hmmmmm this is concerning..... I have the same situation with none of my clients showing the 'reserve windows 10' logo....this is a very good point. either MS certainly haven't worked this out yet (obviously), they don't want to give away windows 10 to small business or they want to keep small business from deploying in the next few weeks to get the 'consumers' out of the way....
July 23rd, 2015 4:39am

Did that myself with all my pc's since I'm using wse 2012 r2 as a home server, got the app and reserved W10, rejoined the server and the app went away.  As I mentioned previously, I can't help but wonder if MS does not want to be obligated to update all the SMB's and HomeServer's clients with a free upgrade since I doubt most do not use the Enterprise client version and MS has already stated that they won't qualify for a free upgrade.

So, where does that put us.... how will MS yank some money from us... maybe we will only be able to upgrade (and get the connector) if we pay for W10 as a service.  At any rate, this has been glaring non-support for their current server OS.

Free Windows Admin Tool Kit Click here and download it now
July 23rd, 2015 5:49am

Here's another nugget to chew on... I recently noticed that all of my (Windows Server 2012r2 Essentials) domain-joined clients where NOT displaying the  "Get Windows 10" icon in the system tray. When I went to the Windows 10 FAQ site, I found no mention of a compatibility problem with WSE Connector. However, as a test, I removed a Windows 8.1 Pro client from the domain and uninstalled its connector. After the reboot, the icon was present on the system tray. I was then able to "reserve" my Windows 10 copy.

My plan is to install Windows 10 on that system and then try to connect to WSE. Honestly, I do not have a good feeling about this!

July 23rd, 2015 6:13am

What's interesting to me is that the ONLY piece of software that I own that does not work with Windows 10 is the Windows Server 2012 R2 Essentials Connector - a Microsoft product.  A stunning omission in compatibility. 

Now it may be that MS is holding the update until after the official release dat (7/29) but in fact as I understand it all Insiders are now using RTM code so I'd think now is the time to text a new connector if indeed one exists.  I'd be surprised if the reason for the lack of a new Windows 10 supported connector is a monetary one as suggested above.  MS knows that if business turns its nose up at WIN10 as they have with WIN8 and WIN8.1 - its all over for that OS and just watch Google go and seize the opportunity. 

VHS did not last, Polaroid Cameras did not last, dBase IV died - let no one be mistaken - that Microsoft monopoly on the desktop can end just as easy with a few missteps - and I say that as a general "fan" of MS.....

Free Windows Admin Tool Kit Click here and download it now
July 23rd, 2015 7:26am

FYI - I've got the 'reserve windows 10' logo on my 8.1 wse 2012 r2 connected PCs
July 23rd, 2015 7:16pm

The installer isn't a failure of Windows 10 but, a failure of logic in the Essentials Connector installer.
Free Windows Admin Tool Kit Click here and download it now
July 23rd, 2015 8:42pm

Finally something from Microsoft.

Not great news really. What a stuffup on their part!

http://blogs.technet.com/b/sbs/archive/2015/07/23/client-connector-availability-with-windows-home-server-small-business-server-and-windows-server-essentials-for-supported-client-os.aspx

July 24th, 2015 1:24am

That's actually great news, just a "bit" late. Manual install doesn't really differ from installing from the server, works for me.

Bookmarked the blog, thanks

Free Windows Admin Tool Kit Click here and download it now
July 24th, 2015 3:23am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics