jmwills Posted February 8, 2016 Share Posted February 8, 2016 Just to be clear MS admit that Feature Upgrades will break the connector but Servicing Updates should not. A fix will be sent to the WS 2012 R2 E and a new client connector package (This does not apply to WS 2012 E just the R2). When these arrive you will have to reconnect clients for hopefully a final time. The fix is due "in the coming months". https://blogs.technet.microsoft.com/sbs/2016/01/22/windows-10-feature-upgrade-breaks-client-connector-for-window-server-2012-r2-essentials-windows-server-2012-essentials-and-windows-small-business-server-2011-essentials/ My guess it will be fixed with 2016 Essentials. Link to comment Share on other sites More sharing options...
Poppapete Posted February 8, 2016 Share Posted February 8, 2016 My guess it will be fixed with 2016 Essentials. Did you see this: http://homeservershow.com/forums/index.php?/topic/10642-tech-preview-4-is-out/#entry111879 Link to comment Share on other sites More sharing options...
jmwills Posted February 9, 2016 Share Posted February 9, 2016 I guess so since I posted in that thread. Lol Link to comment Share on other sites More sharing options...
Poppapete Posted February 10, 2016 Share Posted February 10, 2016 I guess so since I posted in that thread. Lol Sorry can't keep up with the threads. You sure did, actually more than anyone else. Link to comment Share on other sites More sharing options...
Jay2001 Posted February 11, 2016 Share Posted February 11, 2016 (edited) Just to be clear MS admit that Feature Upgrades will break the connector but Servicing Updates should not. A fix will be sent to the WS 2012 R2 E and a new client connector package (This does not apply to WS 2012 E just the R2). When these arrive you will have to reconnect clients for hopefully a final time. The fix is due "in the coming months". https://blogs.technet.microsoft.com/sbs/2016/01/22/windows-10-feature-upgrade-breaks-client-connector-for-window-server-2012-r2-essentials-windows-server-2012-essentials-and-windows-small-business-server-2011-essentials/ I have went through a batch of windows updates 2/9/2016 that would normally (for me anyway) cause the server to become disconnected from the windows 10 pro. client computer but this time did not, after the required reboot. I don't know what the difference is whether an update from the last batch or this batch fixed the problem but at least this time it didn't do it! This was the first time since the first "Feature upgrade" to windows (that completely seemed to uninstall the connector) that I haven't had to reconnect the client to the computer via the "windows server essentials connector configuration wizard" (keep in mind that the connector was not becoming uninstalled like with the feature upgrade but was simply becoming disconnected from the server after the required reboot of the "Servicing Updates". Edited February 11, 2016 by Jay2001 Link to comment Share on other sites More sharing options...
Poppapete Posted February 12, 2016 Share Posted February 12, 2016 That is exactly what has happened to me. Some clients loose connection to the server after a reboot after a service update but the connector is still installed. After a features update the connector is uninstalled after the reboot. MS does not admit to the first bug but admits to the second. As I have mentioned here or elsewhere I have server connection icon in my taskbar on each client so I can see at a glance if there is a connection to the server. Link to comment Share on other sites More sharing options...
Jay2001 Posted February 12, 2016 Share Posted February 12, 2016 That is exactly what has happened to me. Some clients loose connection to the server after a reboot after a service update but the connector is still installed. After a features update the connector is uninstalled after the reboot. MS does not admit to the first bug but admits to the second. As I have mentioned here or elsewhere I have server connection icon in my taskbar on each client so I can see at a glance if there is a connection to the server. Ok, cool up till now I thought I was the only one noticing that particular behavior. Well like I said It did it religiously every time I had to do service updates...... till now; So hopefully the problem has been addressed I guess I'll find out as more service updates are released! Link to comment Share on other sites More sharing options...
jmwills Posted February 12, 2016 Share Posted February 12, 2016 There was a new Build released this week? Right? Link to comment Share on other sites More sharing options...
Poppapete Posted February 12, 2016 Share Posted February 12, 2016 I am not on any Windows Insider Programs (except for windows phone). Current Version for WS 2012 R2 E is 6.3.9600 Build 9600 Current Version for W10 is 10.0.10586 Build 10586 Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now