Client Connector availability with Windows Home Server, Small Business Server and Windows Server Essentials for Supported Client OS

Статья
11/17/2015

[This post comes to us courtesy of Schumann GE from Product Group, Sabir Chandwale and Sandeep Biswas from Global Business Support]

[This post is updated on October 21, 2015]

In today’s post we will discuss about the client connector availability for supported client OS joined to the following Server OS:

Windows Home Server 2011
Small Business Server 2011 Essentials
Small Business Server 2011 Standard / Premium
Windows Server Essentials 2012
Windows Server Essentials 2012 R2
Windows Server 2012 R2 Standard/Datacenter with Essentials Experience Role

Client OS: Windows 7

SERVER OS	Client OS
	Windows 7
	Installation	Client Connect to Server	Client Backup	Client Backup restore	Package availability	Known Issue
Windows Home Server 2011	Working	Working	Working	Working	INBOX	NONE
Small Business Server 2011 Essentials	Working	Working	Working	Working	INBOX	NONE
Small Business Server 2011 Standard	Working	Working	NA	NA	INBOX	NONE
Windows Server Essentials 2012	Working	Working	Working	Working	INBOX	NONE
Windows Server Essentials 2012 R2	Working	Working	Working	Working after client OS hotfix installation	Auto download from DLC	NONE

Client OS: Windows 8/8.1

SERVER OS	Client OS
	Windows 8 / Windows 8.1
	Installation	Client Connect to Server	Client Backup	Client Backup restore	Package availability	Known Issue
Windows Home Server 2011	Working	Working	Working	Working	INBOX	NONE
Small Business Server 2011 Essentials	Working	Working	Working	Working	INBOX	NONE
Small Business Server 2011 Standard	Working	Working	NA	NA	INBOX	NONE
Windows Server Essentials 2012	Working	Working	Working	Working	INBOX	NONE
Windows Server Essentials 2012 R2	Working	Working	Working	Working after client OS hotfix installation	Auto download from DLC	NONE

Client OS: Windows 10 RTM

SERVER OS	Client OS
	Windows 10 RTM
	Installation	Client Connect to Server	Client Backup	Client Backup restore	Package availability	Known Issue
Windows Home Server 2011	Working	Working	Working	Working	INBOX	NONE
Small Business Server 2011 Essentials	Working	Working	Working	Working	INBOX	NONE
Small Business Server 2011 Standard	Working	Working with work-around	NA	NA	INBOX	Follow instructions as mentioned under Appendix-A
Windows Server Essentials 2012	Working	Working	Working	Working	INBOX	NONE
Windows Server Essentials 2012 R2	Requires manually installation	Working	Working	Working	X64 X86	User needs to manually download and install the client connector until the fix on the server is available which is being targeted to be released tentatively in October November 17, 2015.

Appendix-A

User needs to add the following two lines to the XML file on the server located at -
C:\Program Files\Windows Small Business Server\Bin\WebApp\ClientDeployment\packageFiles\supportedOS.xml

So what do we mean by the terms used above:**

Working: No user functional loss when the client OS is upgraded to Windows 10 RTM. There is no change on the Current User Experience

INBOX: The client connector software is available on the respective server and it is not required by the user to download it manually and install. There is no change on the Current User Experience
Auto download from DLC : The client connector software is automatically downloaded from the download center when user runs https://servername/connect on the client. There is no change on the Current User Experience
Working after client OS hotfix installation: It requires the user to install the client OS Hotfix manually for the Client Restore to function properly
NA: The respective feature is not applicable
NONE: No issues experienced while in-house repro

Resolution (Updated on 29/07/2015):

The Client Connector for Windows 10 to connect to Windows Server 2012 R2 Essentials has been released.

For x64 bit Windows 10 Client download it from here.

For x86 bit Windows 10 Client download it form here.

Note :

- The Client Connector needs to be manually downloaded and installed on the Windows 10 Client OS. Once the installation is completed follow the steps listed below,

- Click on Start, All Apps

- Scroll down till "Windows Server Essentials", expand and run "Windows Server Essentials Connector Configuration Wizard".

This is a known issue and the fix on the server is being targeted to be released tentatively in October 2015.

Once the fix is patched, then there will be no user intervention required, all the downloading, installation and configuration will be automatically carried out

- With the release of Windows Server 2016 Essentials, all client connector software will be available and no user intervention will be needed.

Update (21/10/2015):

- There will be a Windows Update released on 17th,November 2015 for Windows Server 2012 R2 Essentials.

- This Windows Update will enable the Windows 10 clients to be joined to the Windows Server 2012 R2 Essentials. In current scenario, the user has to download and install the client connector manually on the Windows 10 client, this manual process would not be required after applying this Windows Update to the Server.

- This Windows Update will not affect any of the existing Windows 10 clients connected to the Windows Server 2012 R2 Essentials.

Update (17/11/2015):

The update to support auto-redirection of Windows Server 2012 R2 Essentials for Windows 10 client connector is now available at:

https://support.microsoft.com/en-us/kb/3105885

Comments

Anonymous
July 24, 2015
Thanks Microsoft ! Many of us Windows 10 Insiders have been eagerly awaiting the restoration of our connect to our Windows Server 2012 R2 Essentials after installing Windows 10. I think I speak for everyone by saying that we appreciate Microsoft acknowledging the incompatibility, the plans to resolve it and what exact steps to take to implement the fix when it is released. Let us know when the revised connector is ready for download. THANKS!
Anonymous
July 24, 2015
Yay! Thanks for the official update. I eagerly await the download to reconnect my Windows 10 machine.
Anonymous
July 25, 2015
Finally! Had to uninstall Windows 10 Preview because this wasn't available. Hope it's out by next week when W10 releases.
Anonymous
July 25, 2015
So, when you say that the 2012R2 Essentials client "Requires Manual Installation" on Windows 10 how is that done? I've tried installing it manually and it fails.
Anonymous
July 25, 2015
In our implementation of WSE 2012 and Win0 10240 the connector does not work as well as it did before we in-place upgraded the PCs from Win7. We get false errors and one machine fails to let the user login to the aap but fortunately still magically banks up (whew)
Anonymous
July 25, 2015
I'm confused too. It indicates "Requires manually installation" [sic], yet no link is provided to download. If the connector is not ready for download, then "Client Connect to Server", "Client Backup" and "Client Backup restore" are all incorrectly labeled for "Windows Server Essentials 2012 R2" on Windows 10.
Anonymous
July 26, 2015
Great! Thanks for the update!
(Will check out the new connector as soon as it is available)
Anonymous
July 26, 2015
Will the connector work with Windows 10 Home for connecting to a Windows Server? I'm assuming it will by the over-arching phrase "Windows 10 RTM" - some clarification would be good though :)
Anonymous
July 26, 2015
As I understand it from Microsoft's comments above: A new connector that is compatible with windows 10 is currently in development and WHEN IT IS READY there will be an update on this webpage with a download link. The connector will be a stand-alone download for now (not a download from server essentials itself to the client PC's and than LATER (estimated October 2015) an update to Windows Server Essentials will update the server with a Windows 10 compatible direct download as we currently use to connect a Windows 7 - 8 - 8.1 pc to server essentials today.
Anonymous
July 27, 2015
I think, if I am reading this correctly:
There is no connector for Win10 to 2012R2 Essentials, yet.
MSFT will release one at some point, date not yet known, but it would appear to be imminent.
When it is first released it will need to be downloaded from MSFT to the client machine directly and installed, not from the server as currently happens. The link for that will appear on this page.
At some point (October is suggested) the connector available from the server will be updated for Win10.
Anonymous
July 27, 2015
Is there any indication as to when the Windows 10 connector for Server Essentials 2012 R2 will be available for download? This will determine when I decide to upgrade my machines and it would helpful if there were some indication whether this is imminent (next few days) or weeks away.
Anonymous
July 28, 2015
Great news to get an official update, although it took too long. Disappointing really...anyway moving on...
When will this be out for manual download and installation?
Anonymous
July 28, 2015
I Can't wait for this to work, I was still debating on delaying the upgrade to windows 10 for this to be fixed. But after playing with the finished product for the last few days I can't wait for it. I need windows 10 to control my boys with the added features it has compared to windows 7.
Anonymous
July 29, 2015
I am stuck until this appears. All my machines are ready to go, but without the backup strategy in place they will stay on Windows 8.1 and 7 until this has been made available and I have tested it.
Anonymous
July 29, 2015
Well, Windows 10 is out and I installed it. Where is the manual install?! We need it. Come on MS.
Anonymous
July 29, 2015
Please at least show us the manual steps involved getting it connected. Thanks
Anonymous
July 29, 2015
Where is the client connector that needs to be manually downloaded and installed for 2012R2 Essentials?
Anonymous
July 29, 2015
The comment has been removed
Anonymous
July 29, 2015
There is always some one company that forget to update their app in time for the release of the new Microsoft OS. Happened to me every time. :(
Anonymous
July 29, 2015
I hope that soon means in the next few days. (End of the week would be great).

I hate it when something gets released "soon". That could be a few days,weeks, month .....
Anonymous
July 29, 2015
The Connector was just released. Lets see if it works.

Thank you very much Microsoft :)
Anonymous
July 29, 2015
The Hotfix posted today doesn't work. "Cannot get information from XXSERVER. Please contact your server administrator."
Anonymous
July 29, 2015
My windows 10 does not accept login name/user. Says its home version of windows and has to be connected by administrator
Anonymous
July 29, 2015
YES!!! Update is ready for Win 10 and 2012 R2. I was sad I couldn't upgrade when I got home from work but you came thru Microsoft!!! Thanks!!!
Anonymous
July 29, 2015
Great - downloaded the connector (thank you MS) and have all the latest drivers and software updates ready to go, just waiting for a final backup to the server before I start the upgrade :-)
Anonymous
July 29, 2015
I just tried using this new connector soiftware on the Hyper-V instance that has been running the preview program for months now and is at RTM. Unfortunately it does not work and all I get is "An Unexpected error occurred" after entering my credentials. What Gives?
Anonymous
July 29, 2015
My edge does not work anymore after connecting to server...... Installes chrome so no real issue but just dissapointing.
Anonymous
July 29, 2015
same error as steve:
"Cannot get information from XXSERVER. Please contact your server administrator."
Anonymous
July 29, 2015
The comment has been removed
Anonymous
July 29, 2015
Works with a local account, doesn't work when logged in with a MS account.
Anonymous
July 29, 2015
Edit: working for me! IIS site was stoped for any reason, started it and the installation was successful
Anonymous
July 29, 2015
The comment has been removed
Anonymous
July 29, 2015
The comment has been removed
Anonymous
July 29, 2015
To no avail, still got the same errors as I posted above
Anonymous
July 29, 2015
At this point I am asvising all of my clients that they will not be able to update to Windows 10 Pro untill sometime in Octobe4r when a server-based solution is in place. :-(
Anonymous
July 29, 2015
Yep, no dice. The connector installs but when I run the wizard it cannot find my server. I manually specify it and it fails to connect, "The server is not available." A Windows 7 machine connects without problem though.
Anonymous
July 29, 2015
The comment has been removed
Anonymous
July 30, 2015
Thanks Microsoft! The connector worked flawlessly.
Anonymous
July 30, 2015
"Cannot get information from XXSERVER. Please contact your server administrator."
Anonymous
July 30, 2015
Worked fine here on the first PC I tried. Will do another tomorrow.
Anonymous
July 30, 2015
HI. I have just tried to run the new connector to connect my Windows 10 Pro (French) Workstation to my Windows Server R2 Essentials (French) and it says this update is not for my computer. Would this be a language issue?

Thanks

Yves Leduc
Anonymous
July 30, 2015
The Client Connector (Windows10.0-KB2790621-x64.msu) will not run on my client computer because "The update is not applicable to your computer". I just installed W10 x64 on the client,
Anonymous
July 30, 2015
Why are you guys using the supporting assemblies from Windows Server 2016 Essentials in your newly released Windows 10 client connector that is for use with Windows Server 2012 R2 Essentials (e.g. ProviderFramework.dll, etc.)? Doing that seriously breaks any add-ins that happen to be using Providers, Health add-ins, etc. (that were built against the older Windows Server Essentials SDK).

Shouldn't all of the assemblies being used in the connector software be from the older version 6.3.9600 release, and not from the newer version 10.0.10240 release (i.e. they should be the ones that ship with Windows Server 2012 R2 Essentials and not the ones that will be shipping with Windows Server 2016 Essentials)?

So what are developers supposed to do now... Should we distribute all of the older v6.3.9600 SDK assemblies with our add-ins? If so, that doesn't make a whole lot of sense to me (or am I simply just missing something here).
Anonymous
July 30, 2015
The connector worked for me in my Windows Server Essential 2012 R2 Environment. The computer is a MacBook Pro running Parallels 10. I upgraded from Windows 8.1 Pro. The language would be English, as I'm located in the U.S.. I had to run the connector installation software twice, with the first attempt hanging up. The second attempt had little delay at each step.
Anonymous
July 30, 2015
Progress report: I have tried the new x64 version of the connector on two W10 installations. The first one was tried on a W10 pro version, and I get the message quoted by others: "The update is not applicable to your computer". Then I tried it on a W10 Enterprise version, and it worked! Both versions originated out of the Technical Preview program. I see nothing in the blog to indicate that some W10 versions will work and others will not. Any ideas about why my W10 pro version will not work???
Anonymous
July 30, 2015
The comment has been removed
Anonymous
July 30, 2015
Getting "The Server is not available. Try connecting this computer again.
Anonymous
July 30, 2015
It can be almost impossible to find well-qualified users on this matter however you look like you be aware of exactly what you’re covering!
http://staygreenacademy.com/sharepoint-training/
Anonymous
July 31, 2015
This worked a treat for me! thanks Microsoft :)
Anonymous
July 31, 2015
It worked flawlessly on my Surface Pro 3 after a clean install of Windows 10.
Anonymous
July 31, 2015
OK, i spoke to soon regarding clean install. when i did an UPGRADE it worked just fine...however when i reset my Surface Pro 3 and then installed the update listed i ended up with the PC being stuck at the login screen displaying user clientsetup$ and no way of logging in...
certainly needs refinement.... I'm still not sure if i have joined this PC to the domain 100% correct???
Anonymous
July 31, 2015
The comment has been removed
Anonymous
July 31, 2015
So far I have successfully used the connector on Windows 10 Pro and Windows 10 Enterprise.
Anonymous
July 31, 2015
Ok, so at the start of Windows 10 setup if you say the machine belongs to the organisation, things go a little smoother. i was starting with creating a user account based around a microsoft account.
however once i install the connector and join the domain in a matter that seems successful, folder redirection is still not working. i use my won account and my desktop item do not appear, my documents folder is empty, etc etc etc
Anonymous
July 31, 2015
Further Report: I reported earlier that my W10 pro version would not install the connector package, giving the message "The update is not applicable to your computer". Well, there was very good reason why it was not applicable: I already had a connector installed for Windows Home Server!!! Once I uninstalled it, the new connector installed just fine. Moral: Uninstall all other connectors before trying to install the one for the W10 client.
Anonymous
August 01, 2015
The file path listed at the top of appendix doesn't exist for WSE Role for Windows 2012 R2. Is there a different path?
Anonymous
August 01, 2015
Hi all,

Just to let you know, I have finally succeeded to connect my Windows 10 Pro Workstation to my Windows Server 2012 Essentials R2. In fact, after resolving a bunch of issues, I made it. First issue was with the supported display languages. For instance, this connector could not be installed since my Workstation had "French Canadian" as the display language. After searching quite a lot on the Web, I discovered the only supported (as of now) "Display languages" were the followings;" English (US), Chinese, French, Japanese, Arabic, Russian, Turkish, Swedish, Spanish, German, Portuguese (Brazil), and Korean languages". So in may case, I've changed my workstation's display language to "French" and I finally succeeded to install it. By the way, there is a misleading piece of information as directed above for updating the file named "supportedOS.xml ". It simply doesn't exist anywhere on the server. Don't waste you time with that!

Second issue: WMI filter named "WSE GROUP Policy WMI Filter" has to be tweaked a bit. In fact, this filter is being used by two GPOs, i.e. Folder Redirection and Security templates. This WMI filter doesn't take into account Windows 10 version's number when it does its version comparison! Why is that you say? Versy simple! Version number is expressed as a caracters string, i.e., ">= 6.1". String caracters "10.0" is lower than "6.1". isn't it?. There you go. So… To have a WMI filter that matches Windows 7 or later (including Windows 10) then you need to use the following WMI filter caracters string; select * from Win32_OperatingSystem where Version like "10.%" or Version >="6.1". So once this filter is corrected, just reissue a GPUPDATE /Force so the missing GPOs get pushed normally onto your Windows 10 workstation(s). Now, everything is back to normal...but the normal way to connect your Workstation to your Windows Server 2012 Essentials R2.

Good luck and thanks Microsoft!
Anonymous
August 01, 2015
Program keeps crashing after I put in my credentials. Any ideas?
Anonymous
August 01, 2015
Yves Leduc, that is wonderful information! I will try this when I'm in the office tonight! thankyou :)
(talking about the WMI filter change)
Anonymous
August 01, 2015
Just so everyone is clear...
Appendix A only applies to Small Business Server 2011 Standard.
Anonymous
August 02, 2015
On the chart above under Client OS: Windows 10 RTM it states that if you are running Windows Server Essentials 2012, there is no issue and that the connector should work. I have clean installed one pc and upgraded another pc to Win10 Pro, and they both fail with the connector. It does not work at all to add these machine back to the server. It does not come up with an error code just a big red X, and a message that the software cannot be installed and to contact your server administrator, which is actually a useless message. I am the administrator and only use my server as a replacement to WHS, so I am not sure what I should be doing now. I tried to manually download the installer, but when I try that I get a message saying this is not required for your machine. Please help!
Anonymous
August 02, 2015
Jeremy, you're right, Appendix A only applies to Small Business Server 2011 Standard. Sorry folks, misreading!
Anonymous
August 02, 2015
Yves, your tip on the Group Policy filter worked a treat! i can now proceed to join Win 10 clients to my SBS/Essentials network! thank you so much :)
Anonymous
August 02, 2015
ok so i have made this change to my Group Policy WMI Filter. Client connects all fine and folders are being redirected. only thing that is weird currently and leads me to believe that not everything is 'ok in the hood', is that in the Sever Essentials Dashboard under the Devices tab, my machine is listed, i see green shields all around (which is great) but under group policy it says 'Not Applicable'. this is obviously wrong....
Anonymous
August 02, 2015
frozenwaffles,

Your right! I'll have to investigate this.

Thanks.
Anonymous
August 03, 2015
frozenwaffles ,

This glitch has nothing to do with the WMI filter. I tried every possible combinations of parameters. I suspect this issue has do to with one the the XML files used by WSER2 to display this group Policy status. There must be some kind of Windows version number validation. Unfortunately, I don't know where to look for!

Thanks.
Anonymous
August 03, 2015
Yves or frozen waffles. I am not proficient with Group Policy or WMI filters. Would you please outline where these would be located and if you don't mind, a detailed description on how to adjust them. Thanks!
Anonymous
August 03, 2015
Tbone, open Group Policy Management, then expand the tree until you get to WMI Filters.
Forest
Domains
(your domain)
WMI Filters

Then edit the WSE Group Policy WMI Filter (right click, edit)
Highlight the Query, then click on edit
Change the Query to:

select * from Win32_OperatingSystem where (Version >= "6.1%" or Version like "10.%") and ProductType = "1"
Anonymous
August 03, 2015
Don't forget guys, we're still facing the issue frozenwaffles had reported! Don't have a clue yet how to resolve this. gitch. I'll probably call Microsoft tomorrow using my partnership id with them.

Cheers
Anonymous
August 03, 2015
@Robag, the current existing client connector should be working fine to connect to Windows Server Essentials 2012. Please let me know more detail. After you upgraded to Windows 10, do you restart the client connect again?
Anonymous
August 03, 2015
@Yves Leduc， what's the issue you are talking about, would you please more specific ?
Anonymous
August 04, 2015
@S Ge, the problem is that the client (by way of connector or otherwise) does not report back to the server and say that Group Policy has been implemented. this to me means that something is not right and if this is not right, what else is not right?
you can see the problem I am talking about in the Sever Essentials Dashboard under the Devices tab, my machine is listed, I see green shields all round (which is great) but under group policy it says 'Not Applicable'. this is obviously wrong....
Anonymous
August 04, 2015
@S Ge. The connector still does not install on Windows 10 Pro. I have tried numerous times. Always get "Cannot get information from XXSERVER. Please contact your server administrator."
1. Updated PC from 8.1 and attempted install. PC was not part of Domain. No luck.
2. Tried installation so as to join Domain. No luck.
3. Formatted drive and installed as a new Windows 10 Pro, Tried domain and non-domain installs. Still cannot successfully run connector. Same error message. "Cannot get information from XXSERVER. Please contact your server administrator." No luck.
Anonymous
August 04, 2015
Worked perfectly with the new Hotfix on an upgraded machine. Thanks for the quick fix.
Anonymous
August 04, 2015
I have now successfully upgraded two domain computers (one laptop and one desktop). Both were running Windows 8.1 Pro.
Anonymous
August 04, 2015
The comment has been removed
Anonymous
August 05, 2015
...another thing can tell you is EDGE does not play nice with redirected folders...
Downloads appear to fail, but they actually work and get saved to the right location.
I can't import my favourites from IE11, just says there is an error.
As much as i kind of have this windows 10 client connected to my WSE 2012 R2 server, there is so much more that Microsoft need to do to make this work properly!
Changes need to be made to the server to support EDGE and other features of Windows 10. Massive enhancements need to happen to the connector to make that work properly.

Get to it Microsoft! :)
Anonymous
August 07, 2015
Thanks for only releasing this a few days before Win 10 is released. You could have done a lot more to make this work far sooner for testing for businesses. Shame on you. And Microsoft question why more and more companies are moving to Linux.
Anonymous
August 07, 2015
I have changed the WMI Filter Query to:
select * from Win32_OperatingSystem where (Version >= "6.1%" or Version like "10.%") and ProductType = "1"

It still does not allow me to successfully connect. Always get "Cannot get information from XXSERVER. Please contact your server administrator." This is happening on multiple Windows 10 upgraded machines, both in a domain and out of a domain.

Microsoft. Please fix this so we can successfully connect to the Windows Server 2012 R2 Essentials!!!
Anonymous
August 08, 2015
The comment has been removed
Anonymous
August 09, 2015
All cliënts connected and working like a charme...
Anonymous
August 09, 2015
Are you sure Coolske?
Anonymous
August 10, 2015
All computers connected now
Had to change two of them to wired connection to make it solid .
And i had to uninstall antivirus before they could find The server
Anonymous
August 10, 2015
I'm having much the same problem as several others having been through the motions of all the described options several times and still not progressed any further.

One thing that nobody seems to have mentioned between those that have got it to work and those that have not is if they are running Windows 10 Home or Pro. I am using Home having started from a Windows 7 build and am deferring upgrading my Windows 8.1 Pro PCs to Windows 10 Pro till I'm convinced it will work.

Can anyone confirm if Pro is good :-) and Home a big thumbs down :-(
Anonymous
August 10, 2015
Navigator. I have 2 Windows 10 Pros that will not successfully connect to my Server 2012 Essentials R2. One an 8.1 upgrade, and one a fresh install. Always get "Cannot get information from XXSERVER. Please contact your server administrator." I don't want to try any more machines until the connector software works.
Anonymous
August 10, 2015
The comment has been removed
Anonymous
August 11, 2015
Not sure if this comment is worth anything to anyone, but...
Im testing windows 10 on my SP3 in a Server Essentials 2012 R2 environment and i am thinking of going back to win 8.1...
I have constant problems with win 10 always asking for credentials, file transfer issues, group oilily is not 100%, EDGE does not sync favourites, its messed up my windows phone 8.1 experience....mainly due to favourites not syncing.
im excited for windows 10 but maybe in 2016 when all the stage 1 bugs are wiped out...and windows 10 phone is out and stable :)
Anonymous
August 11, 2015
The comment has been removed
Anonymous
August 13, 2015
I have come to the conclusion that even though some users are still struggling to join Windows 10 Pro to their Domains there is no chance whatsoever to manage this with Windows 10 Home without upgrading the OS to Pro.

The other issue I am experiencing is the change in Windows update procedure and even though the relevant registry settings have been applied on the client I can only get updates from Microsoft direct and not via WSUS running on my local Windows Sever Essentials R2.

Just another gotcha!!!!!
Anonymous
August 13, 2015
Thanks Microsoft
Anonymous
August 13, 2015
Im going back to windows 8.1 tonight on my surface pro 3. Windows 10 is just not ready... :(
All my other clients will stay on windows 7 till next year some time i imagine...
Anonymous
August 15, 2015
here is another problem...
If you make a new windows 10 machine and then sign in at the start with your Azure ID, this all works and connects just fine.
But then if you try to run the Connector Wizard it will fail!
This whole windows 10 thing is a bit of a failure if you ask me. i was so excited for this...now its nothing but disappointments.
Anonymous
August 17, 2015
The comment has been removed
Anonymous
August 22, 2015
I'm attempting to run install the Client Connector to Windows Server 2012 R2 Essentials on my Surface Pro 3 running Windows 10, but I get the message "The update is not applicable to your computer", and it doesn't install. I've tried the x64 and x86 bit versions of the installer. Any ideas???
Anonymous
August 22, 2015
still doesn't work after installing the fix for 2012 R2 SE. Fix it Microsoft.
Anonymous
August 27, 2015
The comment has been removed
Anonymous
August 30, 2015
had install the Windows 10 x64 Client but connection to Essential Server 2012R2 failed because the connector Software on my Win10 Client is not compatible to my Essential Server 2012R2.
So Client Connect to Server is NOT!!!! working. Correct the Table!
This is real bad.
Anonymous
September 07, 2015
My Client backup no longer works on my Laptop and Desktop that I upgraded to Win10. Now I have to suffer the wrath and cheek of my wife who decided not to upgrade. I like W10, and this isn't a deal breaker. Just flat out frustrating, and well, I don't know how much more mocking I can take from the wife.
Any tips on why my W10's wont backup?
Anonymous
September 07, 2015
OK, sleep easy, found the problem... AppleHFS.sys... http://www.edandersen.com/category/apple/

Works like a charm now!!
Anonymous
September 17, 2015
I have Windows 2012 Essentials - not the R2 version. I downloaded the 64 bit connector but have been unable to connect my brand new Windows 10 Pro (not upgraded - new Dell Build) to my server. After hours of research, I'm concluding it's because I'm not on R2. Does Microsoft plan to upgrade the connector for those of us not on R2? If they aren't, I'd rather wait for Essentials 2016 and not pay / upgrade to 2012 R2...
Anonymous
September 17, 2015
So far the connector install has worked on 1 laptop, My destop and another laptop, the connector software install fails with the message "server not available" even though it finds it during the first part of the install. Really frustrating since no backups for my clients.
Anonymous
October 03, 2015
I have installed the connector fix on each of my workstations for Windows 10, however, I am still waiting for the update on the server; (Server 2012 R2 Essentials).

Do you know when the update will be downloadable for the server?

Will it be an automatic update or an optional one?????

Also, as I understand in your article above, the server connector fix will reestablish all backups, health monitoring, etc
automatically, correct????

Thanks
Anonymous
October 09, 2015
Hi, just an update on this…
I have noticed that all my workstation clients on my WSE 2012 R2 network are now saying i can upgrade them to windows 10! does this mean that my server has all the required updates to it now to support windows 10 clients automatically? i’ll give it a try!
Anonymous
October 15, 2015
I'm running a Windows Server 2012 Essentials R2 network and have received the go ahead from Microsoft to update to Windows 10. The machines I'm upgrading are running Windows 8.1 Pro and are nearly 2 years old. I went ahead and upgraded my test computer and a laptop. So far, it looks like the connector is failing to stay connected following shutdowns and restarts. Re-running the connector wizard is the only temporary fix. I was also experiencing screen flickering on the initial startup, following installation. I was able to use the following as my fix (during the flickering):

1.CTRL+ALT+DEL to display the options (on blue screen)
2.clicked TASK MANAGER,
3.at TASK MANAGER clicked the FILE at the uppermost left hand corner. RUN NEW TASK.
4.Typed (painstakingly, as the screen flickers fast) MSCONFIG command.
5.At the SERVICES tab I tried to disable all service apps but MICROSOFTs. Click APPLY. Screen still flicker.
6.Enable all services that are not from Microsoft again.
7.This time I suspected services from Microsoft and after few trials, by chance, DISABLE the WINDOWS ERROR REPORTING SERVICE from Microsoft Corporation, click APPLY. To my astonishment, the flicker was gone.
8.To confirm that this is the culprit, I tried to enable WINDOWS ERROR REPORTING SERVICE again. Confirmed, WINDOWS ERROR REPORTING SERVICE it was.
Anonymous
October 15, 2015
I want to connect a Computer with fresh install of Windows 10 to a Server 2012 R2 using the above manual method, but the Client Connector Wizard STOPS RESPONDING afer enterin my credentials and having clicked on Next.
The server is found, my credentials are accepted, but the program stops responding after about 15 seconds.
Anonymous
October 15, 2015
The comment has been removed
Anonymous
October 15, 2015

GET YOUR PROBLEM SOLVE TODAY WITH MY PROFESSION IN ANY SPIRITUAL SPELL OR ANY KIND OF PHYSICAL BATTLE THAT NEED, MY NAME IS DR SYLVESTER AND THIS IS MY EMAIL FOR CONTACT (stbenson391@gmail.com) OR YOU CAN FOLLOW HIM UP ON FACEBOOK BY MY NAME (SYLVESTER E BENSON) ON FACEBOOK OR CALL ME ON MY MOBILE NUMBER +2348136090988, AM ALWAYS AVAILABLE TO RENDER YOU HELP WITH EXPERIENCE OF 32 YEARS IN SPELL CASTING AND HERBAL MEDICURE TO CURE ANY KIND OF DISEASE THAT YOU MAY HAVE, CONTACT ME ON ANY KIND OF ISSUES.
Anonymous
October 21, 2015
Any news on the patch for Windows Server 2012 R2 Essentials to fix the connector for Windows 10 support? It was supposed to be October?
Anonymous
October 28, 2015
The comment has been removed
Anonymous
November 01, 2015
This is the first solution to the Win 10 client problem I've found - thanks much!
Anonymous
November 02, 2015
I just ran this installer after doing all new fresh installs of windows 10 Pro on three machines at home. The trick for me was after the clean install, make a temporary account and then to enable the local Administrator account. I would then restart, login as the Administrator and run the connector update. Sometime it would ask me to restart, sometimes it wouldn't. Either way, I would restart and then run the connector wizard once I logged back in as the Administrator. It would ask for a restart (sometimes) again and I'd let it do its thing. It'll try and login as $ClientUpdater$ on the next boot and then all should be good.
Anonymous
November 05, 2015
Wouldn't this be what everyone is waiting for?

http://www.microsoft.com/en-us/download/details.aspx?id=40285
Anonymous
November 06, 2015
Thats the first part of what we're waiting for. Thats the hotfix that will manually install the connector on our Windows 10 machines. The Nov 17th (hopefully) update will be on the server side and allow us to connect by going to SERVER/Connect and running the installer from there. Hopefully it'll squash a few of the bugs with the first rev of the connector too.
Anonymous
November 11, 2015
Looks like the latest Windows 10 build on the fast ring broke the connector again. Hopefully the fix on Tuesday restores it for me.
Anonymous
November 12, 2015
The "November Update" being pushed today uninstalls the connector software... Had to reinstall and run through the setup wizard again. Will this be fixed by the Server update being pushed on the 17th? I'm deferring all my corporate Windows 10 machines updates past this date in hopes of a fix!!
Anonymous
November 12, 2015
Did you get this to work with an Insider Ring install or the latest update from the main branch?
Anonymous
November 12, 2015
It took a long time for the connector to install but all worked fine once I installed and re-ran the wizard. This is on a main branch update...
Anonymous
November 12, 2015
Curious..... My laptop is running the latest release on the fast ring and after doing the install of the connector, it runs, connects to the server and once the login of my account begins, the connector force closes. I've dealt with it for a few days now but hopefully it gets fixed next week.
Anonymous
November 16, 2015
Tried to upgrade another computer and it did the same as you describe...
Anonymous
November 17, 2015
I updated a few of my Win 10 pc's to the 10586 version and the connector worked with no problem. However the one PC that I'm using thats still on the Insider Track, running on 10586, won't connect. I've uninstalled and reinstalled probably half a dozen times at this point with no luck. I guess we'll see after today.
Anonymous
November 17, 2015
So, I just ran the updates on my 2012 R2 server, used my laptop to connect in via VPN, downloaded the connector from SERVER/connector and ran it with no issues. That was certainly a first. However the screen for the connector download does not mention windows 10. I could care less though if it says it or not, so long as it works. Right now I'm connected via VPN and its showing as connected and logged in on the server.
Anonymous
November 17, 2015
Looks like the fix is now available (KB3105885), but it appears to be an optional update (???):

Update to support auto-redirection of Windows Server 2012 R2 Essentials for Windows 10 client connector

http://support.microsoft.com/kb/3105885
Anonymous
November 17, 2015
I've updated 2012 R2 Essentials with KB3105885, downloaded the connector but it cannot install on Windows 10 x64 (french-canada). It says that the installation package failed. Tried it on 2 different server and 2 clients (one updated and one clean install) and the same error appears.

Too bad...
Anonymous
November 17, 2015
Great to see the update. Make install of windows 10 easier now.
Anonymous
November 18, 2015
Downloaded this update on our server and tried to connect two workstation with Windows 10 and they both failed.

Had to connect them manually still.

Update doesn't seem to work.
Anonymous
November 18, 2015
Sorry Microsoft....i can't connect to my server.
Anonymous
November 18, 2015
The comment has been removed
Anonymous
November 18, 2015
Sorry, but after a several updates for 2012 essentials yesterday (18-11-2015 and not R2) the connector failed again to connect my Windows 10 desktop to the server. It seem that the problem is not solved. Can Microsoft arrange in a short way a fix please?
Anonymous
November 19, 2015
Zero change. Cannot find server on the network. Typing in the 0.8 address says it cannot find the server. IPv6 turned off, first entry of DHCP is the server address. Tons of hours spent on this and after waiting for the server side update, it does nothing different than the original download which is to say it doesn't work.
Anonymous
November 19, 2015
The comment has been removed
Anonymous
November 19, 2015
I wish to add my frustrations with this saga as well.

I have one machine that won’t connect at all. I think it may well be the IP V6 issue described by a previous poster. I have just gone back to using the Hotfix and that still works fine.

However, the remaining 9 clients I have all worked when I ran reloaded the connector from my R2 server after Microsoft supplied the fix on the 17th. (KB3105885). At that point, I was quite happy, only one machine to sort out.

Now 3 days later the Windows 10 team decides we all need another update to 1511 (10586.3) and automatically downloaded KB3118754 to all of my machines. This updates their build to 10586.11.

As soon as it installs, the connector again won’t talk to my R2 server and vice versa, so I have to go round and re-install the connector yet again.

These teams need to get together and sort this out. It is not solely a Windows Server 2012 R2 issue.
Anonymous
November 21, 2015
The comment has been removed
Anonymous
November 22, 2015
The comment has been removed
Anonymous
November 22, 2015
Has the Windows 10 connector for 2012R2 essentials just released on 17/11/2015 been broken already by the Windows 10 1511 build 10586 update?
Anonymous
November 22, 2015
@Paul Crowther: Yes, I believe that's the case. May have worked for a couple of days. Now doesn't :-(
Anonymous
November 22, 2015
It still doesn't work! In fact it was working with the manual connector installation, but with the latest update to W10, can no longer connect the client PC's. Zero help in the docs. Useless.
Anonymous
November 22, 2015
All of my current Win 7/8 boxes are tied to my WHS 1.0 mini server for sharing files. Will the new connector software work with my older version of WHS? If not...how about swapping me a Windows 10 license for the WHS license so I can build new file server? Please help. I don't want to take the Windows 10 leap and find out I just lost all connectivity to my server. Thanks.
Anonymous
November 23, 2015
The comment has been removed
Anonymous
November 23, 2015
@Oceang would you please let me know your Client OS version, and more detail information about the issue you are facing will be very helpful. thanks.
Anonymous
November 24, 2015
Hi everyone,

Is it possible that KB2790621 isn't compatible with Windows 10 other than the English version? I'm on Windows 10 x64 (French-Canada) with the november update and I'm getting this every time i try to install the connector;

[11/23/2015 17:23:43 2e30] CComputerconnector::RunTasks: Running Task: Id=-1 Description=Installation du connecteur Windows Server Essentials... Index= 4
[11/23/2015 17:23:43 2e00] CComputerconnector::TaskDlgProc: DIALOG_TASK_PROGRESS: Task Description: Installation du connecteur Windows Server Essentials...
[11/23/2015 17:23:43 2e30] Entering Connector::Install.
[11/23/2015 17:23:43 2e30] Connector::Install - Installing Connector by running ["C:WINDOWSsystem32wusa.exe" "C:WINDOWSTempClientDeploymentTempFilesWindows10.0-KB2790621-x64.msu" /quiet /norestart]
[11/23/2015 17:23:44 2e30] Connector::Install - Connector installation finished with exit code = 0x80240017
[11/23/2015 17:23:44 2e30] Exiting Connector::Install.
[11/23/2015 17:23:44 2e30] Connector Install (C:WINDOWSTempClientDeploymentTempFilesWindows10.0-KB2790621-x64.msu) failed with status 4
[11/23/2015 17:23:44 2e30] CComputerconnector::RunTasks: Task Id=-1 Description=Installation du connecteur Windows Server Essentials... Failed
[11/23/2015 17:23:44 2e30] CComputerconnector::Run: RunTasks: 0x8000ffff
[11/23/2015 17:23:44 2e00] CComputerconnector::TaskDlgProc: DIALOG_UPDATE: FatalError
[11/23/2015 17:23:44 2e00] CComputerconnector::ErrorDlgProc: IDD_PROPPAGE_ERROR Initialization
[11/23/2015 17:23:45 2e00] wmain: End of Computerconnector: hr=0x80004005

Best regards,

Tommy
Anonymous
November 25, 2015
@S Ge. Thanks for taking an interest in this issue. I note you work on the Windows Server Team, so I hope this can be resolved generally, so there is no re-occurrence when another major cumulative update is applied to Windows 10.

First of all, at all times I have had connectivity between the clients and the server in terms of shared folders, it is just the Essentials functionality that wasn’t working due to a connection issue.

Case1: The client is Windows 10 Pro 64 bit. It was a clean install after originally running Windows 10 Pro 64 bit build 10240.

My Original Post was as follows:

“I have one machine that won’t connect at all. I think it may well be the IP V6 issue described by a previous poster. I have just gone back to using the Hotfix and that still works fine.”

My Status as at 25/11:

I could not get the connector to install at all on this client machine after KB3105885 was applied to my server.
At the time, the client OS was on 10586.3. I was getting a connection error at the very first step, before it comes up with the screen identifying potential servers. As I stated, I got around this issue by re-applying the Hotfix (KB2790621).
When the Windows 10 team automatically upgraded my client to 10586.11 via KB3118754, the client lost connection to the server again. Again, I tried to just load the connector from my server and got the same connection error, so re-applied the Hotfix to keep going.

Today (25/11), the Windows 10 team has again decided to automatically upgrade my client via KB3120677. The client OS is now 10586.14. I have re-tried to run the connector wizard downloaded from my server and this time it works. This means I should no longer need the Hotfix on any of my clients.

Whether it will get overwritten by the next major Windows 10 cumulative update is my major outstanding concern.

To be continued in next post.
Anonymous
November 25, 2015
The comment has been removed
Anonymous
November 27, 2015
Is the dashboard likely to be updated to show the status of windows 10 pcs for the group policy, along with the group policy window so it states that it includes windows 10 as it currently only refers to windows 7 and 8.
Anonymous
November 27, 2015
Ńo connector for Windows 10 1511? hhtps://MYSERVER/Connect only gives software for windows 7 and 8
Anonymous
November 27, 2015
Rickard, the connector actually is for Windows 10 if you have installed the optional update (KB3105885). It does work now and it definitely didn't prior to KB3105885.

Microsoft just hasn't changed the text on the "Connect your computer to the server" screen. It should have been updated as part of KB3105885 for completeness.
Anonymous
November 29, 2015
212 Microsoft Team blogs searched, 54 blogs have new articles. 154 new articles found searching from
Anonymous
November 29, 2015
Hi all, I can confirm this is all definitely working now as expected. No manual config required.
What is annoying is that in the Server Dashboard, Group Policy says its still 'Not Implemented' when it is.
Also the Web Page for the initial server connection does not list Windows 10 as an operating system that is supported. Its great that's its working and all, but Windows 10 still feels like the surrogate child in the enterprise environment....
Anonymous
November 29, 2015
The client connector that is compatible for Windows 10 clients is unfortunately ignoring SkipDomainJoin. Does anyone know if it is looking at a different registry key?
Anonymous
November 30, 2015
SkipDomainJoin is working fine on all of my Windows 10 Clients. It is the same Registry setting

You do need to do the Reg Add again as it gets deleted during the various upgrades when the connector gets removed as well.
Anonymous
November 30, 2015
in the GERMAN Version of Windows Server 2012 R2 Essentials (all updates installed incl. KB3105885) i am not able to install the connector via https://server/connect/ (server = servername). The download starts, a small .exe (preinstaller i guess) can be downloaded. If I start it (run) the connector try to install, but quit after a while saying. can't be install, please try again later or contact the sysadmin. Anybody runnnig German versions? Client ist running on Win10 TH2 (GER 11511 Build 10586.14). The "old manuel" installer works . but some bugs ....
Anonymous
November 30, 2015
Same here @Mark_Muc

32bit or 64bit, all machines (incl. server) are absolutely up to date. Now I'm looking for 10240. :-(
Anonymous
December 01, 2015
I've installed the connector on two computers everything appear ok other than the previously mentioned Group Policy being "Not Applicable" and - crucially - backups are failing. Is anyone else experiencing this?
Anonymous
December 01, 2015
My Windows 10 backups are failing as well. In fact when I click on a Windows 10 pro device in the Server Essentials Dashboard there is no option to "Start a backup...", "Restore files...: or "customize backup..." for my Windows 10 client.
Anonymous
December 03, 2015
All my Windows 10 clients were connected to my Windows Server 2012 R2 Essentials server. Yesterday, all of my Windows 10 clients received the Windows 10 November Update (1155, 10586 build). Now, none of my Windows 10 clients are connected to the server. None of the backups are running and if I try to run the client connector wizard again, it errors out.
Anonymous
December 04, 2015
It's frustrating to read that so many people have major problems connecting and no comment from Microsoft here with solutions at all. Where are they when you need them. Is it so difficult to fix this?

I'm very disappointed in Microsoft. I'm seriously thinking about downgrading Windows 10 to windows 7 again so connection and backups working correctly again. (now it still can)
Anonymous
December 04, 2015
I can say ..solved .. the fix yesterday udate für Windows Server 2012 R2 (KB3112336)

fixes the Problem that I coudn't install via http://server/connect ... after installing this update ..everything worked fine ..... but still one Problem with the daschboard still exist ... it doesn't remember the Password .. User Name is fine..
Anonymous
December 06, 2015
The comment has been removed
Anonymous
December 07, 2015
I still cannot connect my windows 10 to my windows home server 2011. When i upgraded to windows 10 i can connect to the server but it was 'offline' then i read that i need to uninstall the connector and re-install, now i cannot even install the connector at all..Is there any fix? Thank for the help.
Anonymous
December 10, 2015
The comment has been removed
Anonymous
December 11, 2015
The comment has been removed
Anonymous
December 15, 2015
I run SBS 2011 Essentials and had to modify a specific Group Policy WMI Filter to get all the functions to work with Windows 10.
Anonymous
December 16, 2015
The comment has been removed
Anonymous
December 20, 2015
WHS Connector is NOT working with Windows 10!
You can follow many reports on that issue in the Internet.
Microsoft must release a fixed-Version.
Some parts of the connector are working, but in generell it is not working as it must be.
It is a pitty that I cannot update my Computers to Windows 10.
Best Regards from Germany
Anonymous
December 21, 2015
WOW! After all this unsolicited nagging and push to Windows 10, machines upgraded to Windows 10 (Pro) will not connect to Microsoft's very own Server 2012 Essentials (non-R2). I love Microsoft but I really hate you for the stupid things you do. Why doesn't somebody lose their job and a fix get done immediately when stupid things like this happen??? Instead, months later, it's STILL not fixed. I'm even more ticked off now over the incessant nagging to upgrade to Windows 10. How about you get your act together before moving on to the next shiny object?
Anonymous
December 21, 2015
I figured it out in my case. It's the certificates. You must have a valid certificate that does NOT error when you browse to the https://server-url/connect. If it gives SSL error then the connection software will fail.
Anonymous
December 22, 2015
I am trying to get Win10Pro laptops on to my SBS 2011 Standard domain following the instructions in Appendix A. When I go to the .xml file the first thing I notice is that the layout of the new information is different than the layout in the existing configurations. Am I supposed to do just a cut and paste of this new configuration or am I to take the information from Appendix A and put it into the pre-existing configuration format?
Anonymous
January 07, 2016
http://www.happylohrii.com/">Lohri
http://www.happylohrii.com/">Happy Lohri
http://www.happylohrii.com/">Lohri Wallpapers
http://www.happylohrii.com/">Lohri Festival
http://www.happylohrii.com/">Lohri Wishes
http://www.happylohrii.com/">Lohri Sms
http://www.happylohrii.com/">Lohri Songs
http://www.happylohrii.com/">Lohri Images
http://www.happylohrii.com/">Lohri Greetings
http://www.happylohrii.com/">Happy Lohri Wallpaper
http://www.happylohrii.com/">Lohri Pics
http://www.happylohrii.com/">Happy Lohri Images
http://www.happylohrii.com/">Happy Lohri Wishes
http://www.happylohrii.com/">Happy Lohri Quotes
http://www.happylohrii.com/">Hindu Festival 2015
http://www.republicdayi.com/">Republic Day
http://www.republicdayi.com/">Republic Day Quotes
http://www.republicdayi.com/">Happy Republic Day
http://www.republicdayi.com/">Speech for Republic Day
http://www.republicdayi.com/">Republic Day Wishes
http://www.republicdayi.com/">Republic Day Images
http://www.republicdayi.com/">India Republic Day
http://www.republicdayi.com/">Republic Day Sms
http://www.republicdayi.com/">Republic Day Songs
http://www.republicdayi.com/">What is Republic Day
http://www.republicdayi.com/">Republic Day Image
Anonymous
January 07, 2016
http://www.happynewyear2016wishesimagessms.com/hindu-festival-2016/
http://www.happynewyear2016wishesimagessms.com/lohri-pics-lohri-sms-lohri-wallpapers/
http://www.happynewyear2016wishesimagessms.com/happy-lohri-images/
http://www.happynewyear2016wishesimagessms.com/happy-lohri-quotes/
http://www.happynewyear2016wishesimagessms.com/happy-lohri-wishes/
http://www.happynewyear2016wishesimagessms.com/happy-lohri-wallpaper/
http://www.happynewyear2016wishesimagessms.com/lohri-greetings/
http://www.happynewyear2016wishesimagessms.com/lohri-images/
http://www.happynewyear2016wishesimagessms.com/lohri-songs/
http://www.happynewyear2016wishesimagessms.com/lohri-wishes/
http://www.happynewyear2016wishesimagessms.com/lohri-festival/
http://www.happynewyear2016wishesimagessms.com/happy-lohri-bonfire-festival/
http://www.happynewyear2016wishesimagessms.com/lohri-bonfire-festival/
http://www.happynewyear2016wishesimagessms.com/lohri-the-bonfire-festival/
http://www.happynewyear2016wishesimagessms.com/up-helly-aa-event-in-scotland/
http://www.happynewyear2016wishesimagessms.com/dinagyang-festival/
http://www.happynewyear2016wishesimagessms.com/sundance-film-festival-2016/
http://www.happynewyear2016wishesimagessms.com/wwe-in-india-wwe-live-event-in-new-delhi/
http://www.happynewyear2016wishesimagessms.com/lohri-wishes-for-friends-family/
http://www.happynewyear2016wishesimagessms.com/cowboy-poetry/
http://www.happynewyear2016wishesimagessms.com/ati-atihan-festival-full-information/
http://www.happynewyear2016wishesimagessms.com/holy-ship-2016/
http://www.happynewyear2016wishesimagessms.com/things-to-do-in-banff-town-canada/
http://www.happynewyear2016wishesimagessms.com/rainbow-serpent-festival/
http://www.happynewyear2016wishesimagessms.com/sundance-film-festival-winners/
http://www.happynewyear2016wishesimagessms.com/junkanoo-parade/
http://www.happynewyear2016wishesimagessms.com/hogmanay-2016/
http://www.happynewyear2016wishesimagessms.com/ice-sculpture-snow-sculpture-festival/
http://www.happynewyear2016wishesimagessms.com/carnevale-di-venezia/
http://www.happynewyear2016wishesimagessms.com/bpm-festival-what-bpm-festival-is/
http://www.happynewyear2016wishesimagessms.com/thaipusam-thaipusam-is-a-hindu-festival/
http://www.happynewyear2016wishesimagessms.com/holy-ship-unveils-massive-lineups-for-2016-cruises/
http://www.happynewyear2016wishesimagessms.com/quebec-winter-carnival/
http://www.happynewyear2016wishesimagessms.com/jam-cruise/
http://www.happynewyear2016wishesimagessms.com/things-to-do-in-edinburgh/
http://www.happynewyear2016wishesimagessms.com/harbin-ice-festival/
http://www.happynewyear2016wishesimagessms.com/the-sundance-film-festival-a-program-of-the-sundance-institute/
Anonymous
January 07, 2016
http://www.republicdayimagesi.com/republic-day-songs/
http://www.republicdayimagesi.com/republic-day-status-republic-day-wallpaper/
http://www.republicdayimagesi.com/republic-day-information-republic-day-photos/
http://www.republicdayimagesi.com/republic-day-pictures-republic-day-pics/
http://www.republicdayimagesi.com/republic-day-messages-republic-day-sms/
http://www.republicdayimagesi.com/republic-day-in-hindi/
http://www.republicdayimagesi.com/essay-on-republic-day/
http://www.republicdayimagesi.com/what-is-republic-day/
http://www.republicdayimagesi.com/republic-day-wishes/
http://www.republicdayimagesi.com/speech-on-republic-day-in-hindi-speech-for-republic-day/
http://www.republicdayimagesi.com/republic-day-speech-in-hindi/
http://www.republicdayimagesi.com/republic-day-image/
http://www.republicdayimagesi.com/india-republic-day/
http://www.republicdayimagesi.com/republic-day-quotes/
http://www.republicdayimagesi.com/images-of-republic-day-pics-of-republic-day/
http://www.republicdayimagesi.com/speech-on-republic-day/
http://www.republicdayimagesi.com/republic-day-2016/
http://www.republicdayimagesi.com/republic-day-india/
http://www.republicdayimagesi.com/republic-day-speech/
http://www.republicdayimagesi.com/republic-day-images/
http://www.republicdayimagesi.com/happy-republic-day/
http://www.republicdayimagesi.com/republic-day/
http://www.republicdayi.com/republic-day-songs/
http://www.republicdayi.com/republic-day-status-republic-day-wallpaper/
http://www.republicdayi.com/republic-day-information-republic-day-photos/
http://www.republicdayi.com/republic-day-pictures-republic-day-pics/
http://www.republicdayi.com/republic-day-messages-republic-day-sms/
http://www.republicdayi.com/speech-on-republic-day-in-hindi-speech-for-republic-day/
http://www.republicdayi.com/republic-day-in-hindi/
http://www.republicdayi.com/essay-on-republic-day/
http://www.republicdayi.com/what-is-republic-day/
http://www.republicdayi.com/republic-day-wishes/
http://www.republicdayi.com/republic-day-speech-in-hindi/
http://www.republicdayi.com/republic-day-image/
http://www.republicdayi.com/india-republic-day/
http://www.republicdayi.com/republic-day-quotes/
http://www.republicdayi.com/images-of-republic-day/
http://www.republicdayi.com/speech-on-republic-day/
http://www.republicdayi.com/republic-day-2016/
http://www.republicdayi.com/republic-day-india/
http://www.republicdayi.com/republic-day-speech/
http://www.republicdayi.com/republic-day-images/
http://www.republicdayi.com/happy-republic-day/
http://www.republicdayi.com/republic-day/
Anonymous
January 07, 2016
http://www.happylohrii.com/lohri-pics-lohri-sms-lohri-wallpapers/
http://www.happylohrii.com/happy-lohri-images/
http://www.happylohrii.com/hindu-festival-2016/
http://www.happylohrii.com/happy-lohri-quotes/
http://www.happylohrii.com/happy-lohri-wishes/
http://www.happylohrii.com/happy-lohri-wallpaper/
http://www.happylohrii.com/lohri-greetings/
http://www.happylohrii.com/lohri-images/
http://www.happylohrii.com/lohri-songs/
http://www.happylohrii.com/lohri-wishes/
http://www.happylohrii.com/lohri-festival/
http://www.happylohrii.com/happy-lohri-bonfire-festival/
http://www.happylohrii.com/lohri-bonfire-festival/
Anonymous
January 12, 2016
I am happy to find this post very useful for me
Happy wheels: http://www.happywheelsy8.com/
Happy wheels 2: http://www.happywheels-2.com/
friv: http://friv4schoolonline.net/
gamesgogirls: http://www.girlsgo2games.com/
games2girls: http://www.games2girls2.com/
Anonymous
January 14, 2016
with big regret and big critic to Microsoft. THE CONNECTOR FOR HOME SERVER 2011 IS NOT WORKING WITH WINDOWS 10!
3 Alienware Computer could not be connected in a correct way. Launchpad and back-up is not working.
Update from Win 8.1 to Win 10!
It is a shame. The mistake is a known issue since nearly 1 year and Microsoft is not doing anything!
I use Microsoft products for over 35 years and never faced such a Situation.
It is a shame!
Regards from Cologne/Germany .... where we have central Office of Microsoft europe :-)
Anonymous
January 15, 2016
After Windows 10 Upgrade (RTM to November Edition) all Essentials connector software is lost. Dashboard and Essentials features are not working anymore. A complete reconnect is necessary, all prior backups seem to be lost. Does it happen on purpose? Is there a way to restore functionality without reconnecting all computers? Please seehttp://www.mcbsys.com/blog/2015/11/windows-10-update-breaks-2012-r2-essentials-connector/ for a further documentation.
Anonymous
January 18, 2016
You still have not fixed the issue. An here it is now Jan 2016, An I have a brand new Windows Server 2012 R2 standard with all updates installed and a brand new Windows 10 Pro (64Bit) system, with all windows updates installed. An still can not connect to a Windows Server 2012 R2 Standard. You Windows Server Essentials connector does not work. So now when is Microsoft programmers going to fix this problem.
Anonymous
January 24, 2016
The comment has been removed
Anonymous
January 31, 2016
The comment has been removed

Поделиться через

Client Connector availability with Windows Home Server, Small Business Server and Windows Server Essentials for Supported Client OS

Comments

Дополнительные ресурсы