I tryto integrateO365 into my Server 2012 R2 Essentials over the dashboard.Therealways appearsthemessagethat there is nointernet connection, but everthing else works fine (Windows Updates, webbrowser, etc).

Wherecould be the problem?

Here is the SharedServiceHost-EmailProviderServiceConfig.log (removed ActivateAAD and server name):

---------------------------------------------------------
[6264] 160803.162052.5328: SharedServiceHost: Information: [0] : ==========================================================
[6264] 160803.162052.5953: SharedServiceHost: Information: [0] : "C:\Windows\System32\Essentials\SharedServiceHost.exe" C:\Windows\System32\Essentials\EmailProviderServiceConfig
[6264] 160803.162052.5953: SharedServiceHost: Information: [0] : Loading service information from "C:\Windows\System32\Essentials\EmailProviderServiceConfig".
[4440] 160803.162052.6110: WinSrvEmailProviderSvc: Microsoft.WindowsServerSolutions.O365Integration.O365ManagementService, Wssg.O365Provider, Version=6.3.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35 is created as hosted email service provider
[4440] 160803.162052.6110: WinSrvEmailProviderSvc: Microsoft.WindowsServerSolutions.PasswordSync.PwdSyncManagementService, Wssg.PasswordSyncProvider, Version=6.3.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35 is created as hosted email service provider
[4440] 160803.162053.1266: O365Integration:BackgroundTaskManager: BackgroundTaskManager.StartTasks called
[4440] 160803.162053.1266: O365Integration:BackgroundTaskBase: Starting UpdateDomainTask
[4440] 160803.162053.1422: O365Integration:BackgroundTaskBase: updating UpdateDomainTask timer to: TimerSettings: DueTime=00:00:00, Interval=01:00:00
[4440] 160803.162053.1422: O365Integration:BackgroundTaskBase: Starting UpdateSharepointAddressTask
[4440] 160803.162053.1422: O365Integration:BackgroundTaskBase: updating UpdateSharepointAddressTask timer to: TimerSettings: DueTime=00:00:00, Interval=1.00:00:00
[4440] 160803.162053.1422: O365Integration:BackgroundTaskBase: Starting UpdateO365IntegrationDataTask
[4440] 160803.162053.1422: O365Integration:BackgroundTaskBase: updating UpdateO365IntegrationDataTask timer to: TimerSettings: DueTime=00:00:00, Interval=01:00:00
[4440] 160803.162053.1422: O365Integration:BackgroundTaskBase: Starting UpdateCachedSkuInfoTask
[4440] 160803.162053.1422: O365Integration:BackgroundTaskBase: updating UpdateCachedSkuInfoTask timer to: TimerSettings: DueTime=00:00:00, Interval=1.00:00:00
[4440] 160803.162053.1422: O365Integration:BackgroundTaskBase: Starting UpdateMSOSecurityGroupDataTask
[4440] 160803.162053.1422: O365Integration:BackgroundTaskBase: updating UpdateMSOSecurityGroupDataTask timer to: TimerSettings: DueTime=00:00:00, Interval=1.00:00:00
[5848] 160803.162053.1579: UpdateMSOSecurityGroupDataTask: Start UpdateMSOSecurityGroupDataTask
[4440] 160803.162053.1579: PasswordSyncManagementCoreFactory: Creating PasswordSyncManagementCore instances
[3636] 160803.162053.1891: MSOSecurityGroupManager: Sync queue is empty.
[5848] 160803.162053.1891: MSOSecurityGroupManager: Full sync task will start in 00:10:00 minutes.
[4072] 160803.162053.3141: O365ManagementProvider(IO365Callback): ActivateAAD:---- starts
[4072] 160803.162053.3297: O365Integration:BackgroundTaskManager: BackgroundTaskManager.StopTasks called
[4072] 160803.162053.3297: O365Integration:BackgroundTaskBase: Stopping UpdateDomainTask
[4072] 160803.162053.3297: O365Integration:BackgroundTaskBase: updating UpdateDomainTask timer to: TimerSettings: DueTime=-00:00:00.0010000, Interval=00:00:00
[4072] 160803.162053.3297: O365Integration:BackgroundTaskBase: Stopping UpdateSharepointAddressTask
[4072] 160803.162053.3297: O365Integration:BackgroundTaskBase: updating UpdateSharepointAddressTask timer to: TimerSettings: DueTime=-00:00:00.0010000, Interval=00:00:00
[4072] 160803.162053.3297: O365Integration:BackgroundTaskBase: Stopping UpdateO365IntegrationDataTask
[4072] 160803.162053.3297: O365Integration:BackgroundTaskBase: updating UpdateO365IntegrationDataTask timer to: TimerSettings: DueTime=-00:00:00.0010000, Interval=00:00:00
[4072] 160803.162053.3297: O365Integration:BackgroundTaskBase: Stopping UpdateCachedSkuInfoTask
[4072] 160803.162053.3297: O365Integration:BackgroundTaskBase: updating UpdateCachedSkuInfoTask timer to: TimerSettings: DueTime=-00:00:00.0010000, Interval=00:00:00
[1224] 160803.162055.1110: PfBinding: Information: [0] : Adding service dns identity [Servername] in proxy endpoint.
[5848] 160803.162113.3923: BecWebServiceAdapter: Connect to BECWS failed due to known exception : System.TimeoutException: Beim Anforderungskanal ist während eines Sendeversuch nach 00:00:20 eine Zeitüberschreitung aufgetreten. Erhöhen Sie den an den Aufruf übergebenen Zeitlimitwert auf "Request", oder erhöhen Sie den SendTimeout-Wert für die Bindung. Der für diesen Vorgang zugewiesene Zeitraum war möglicherweise ein Teil eines längeren Timeouts. ---> System.TimeoutException: Die HTTP-Anforderung an "https://provisioningapi.microsoftonline.com/provisioningwebservice.svc" hat das dafür vorgesehene Zeitlimit von 00:00:19.9840000 überschritten. Der für diesen Vorgang zugewiesene Zeitraum war möglicherweise ein Teil eines längeren Timeouts. ---> System.Net.WebException: Timeout für Vorgang überschritten
   bei System.Net.HttpWebRequest.GetRequestStream(TransportContext& context)
   bei System.Net.HttpWebRequest.GetRequestStream()
   bei System.ServiceModel.Channels.HttpOutput.WebRequestHttpOutput.GetOutputStream()
   --- Ende der internen Ausnahmestapelüberwachung ---
   bei System.ServiceModel.Channels.HttpOutput.WebRequestHttpOutput.GetOutputStream()
   bei System.ServiceModel.Channels.HttpOutput.Send(TimeSpan timeout)
   bei System.ServiceModel.Channels.HttpChannelFactory`1.HttpRequestChannel.HttpChannelRequest.SendRequest(Message message, TimeSpan timeout)
   bei System.ServiceModel.Channels.RequestChannel.Request(Message message, TimeSpan timeout)
   --- Ende der internen Ausnahmestapelüberwachung ---

Server stack trace:
   bei System.ServiceModel.Channels.RequestChannel.Request(Message message, TimeSpan timeout)
   bei System.ServiceModel.Dispatcher.RequestChannelBinder.Request(Message message, TimeSpan timeout)
   bei System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
   bei System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
   bei System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)

Exception rethrown at [0]:
   bei System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
   bei System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
   bei IProvisioningWebService.MsolConnect(Request request)
   bei Microsoft.WindowsServerSolutions.O365Integration.BecWebServiceAdapter.Connect()
[5848] 160803.162113.3923: UpdateMSOSecurityGroupDataTask: Failed to run UpdateMSOSecurityGroupDataTask: O365ConfigurationFault = Communication
Microsoft.WindowsServerSolutions.O365Integration.O365ConfigureException: Connect to BECWS failed.
   bei Microsoft.WindowsServerSolutions.O365Integration.BecWebServiceAdapter.Connect()
   bei Microsoft.WindowsServerSolutions.O365Integration.BecWebServiceAdapter.get_Client()
   bei Microsoft.WindowsServerSolutions.O365Integration.BecWebServiceAdapter.<>c__DisplayClass70.<ListSecurityGroups>b__69(ListGroupsRequest r)
   bei Microsoft.WindowsServerSolutions.O365Integration.BecWebServiceAdapter.InvokeWebServiceWithRetry[TRequest,TResponse](Func`2 func, TRequest request)
   bei Microsoft.WindowsServerSolutions.O365Integration.BecWebServiceAdapter.InvokeWebService[TRequest,TResponse](Func`2 func, TRequest request)
   bei Microsoft.WindowsServerSolutions.O365Integration.BecWebServiceAdapter.ListSecurityGroups()
   bei Microsoft.WindowsServerSolutions.O365Integration.MSOSecurityGroupManager.CleanUpMSOSecurityGroupData()
   bei Microsoft.WindowsServerSolutions.O365Integration.UpdateMSOSecurityGroupDataTask.Run().
[5848] 160803.162113.3923: UpdateMSOSecurityGroupDataTask: End UpdateMSOSecurityGroupDataTask
[4072] 160803.162113.4079: O365Integration:BackgroundTaskBase: Stopping UpdateMSOSecurityGroupDataTask
[4072] 160803.162113.4079: O365Integration:BackgroundTaskBase: updating UpdateMSOSecurityGroupDataTask timer to: TimerSettings: DueTime=-00:00:00.0010000, Interval=00:00:00
[4072] 160803.162134.4392: O365ManagementCore: failed to install MSOIDCRL, 0 times remaining, exp = Microsoft.WindowsServerSolutions.MailService.MailServiceException: Die Verbindung mit dem Remoteserver kann nicht hergestellt werden.
   bei Microsoft.WindowsServerSolutions.MailService.MailServiceUtils.InstallMsoIdCrl()
   bei Microsoft.WindowsServerSolutions.O365Integration.O365ManagementCore.ActivateAAD(String adminUserName, String adminPassword)
[4072] 160803.162155.4392: O365ManagementCore: failed to install MSOIDCRL, 1 times remaining, exp = Microsoft.WindowsServerSolutions.MailService.MailServiceException: Die Verbindung mit dem Remoteserver kann nicht hergestellt werden.
   bei Microsoft.WindowsServerSolutions.MailService.MailServiceUtils.InstallMsoIdCrl()
   bei Microsoft.WindowsServerSolutions.O365Integration.O365ManagementCore.ActivateAAD(String adminUserName, String adminPassword)
[4072] 160803.162216.4705: O365ManagementCore: failed to install MSOIDCRL, 2 times remaining, exp = Microsoft.WindowsServerSolutions.MailService.MailServiceException: Die Verbindung mit dem Remoteserver kann nicht hergestellt werden.
   bei Microsoft.WindowsServerSolutions.MailService.MailServiceUtils.InstallMsoIdCrl()
   bei Microsoft.WindowsServerSolutions.O365Integration.O365ManagementCore.ActivateAAD(String adminUserName, String adminPassword)
[4072] 160803.162216.4705: O365Integration:BackgroundTaskManager: BackgroundTaskManager.StartTasks called
[4072] 160803.162216.4705: O365Integration:BackgroundTaskBase: Starting UpdateDomainTask
[4072] 160803.162216.4705: O365Integration:BackgroundTaskBase: updating UpdateDomainTask timer to: TimerSettings: DueTime=00:00:00, Interval=01:00:00
[4072] 160803.162216.4705: O365Integration:BackgroundTaskBase: Starting UpdateSharepointAddressTask
[4072] 160803.162216.4705: O365Integration:BackgroundTaskBase: updating UpdateSharepointAddressTask timer to: TimerSettings: DueTime=00:00:00, Interval=1.00:00:00
[4072] 160803.162216.4705: O365Integration:BackgroundTaskBase: Starting UpdateO365IntegrationDataTask
[4072] 160803.162216.4705: O365Integration:BackgroundTaskBase: updating UpdateO365IntegrationDataTask timer to: TimerSettings: DueTime=00:00:00, Interval=01:00:00
[4072] 160803.162216.4705: O365Integration:BackgroundTaskBase: Starting UpdateCachedSkuInfoTask
[4072] 160803.162216.4705: O365Integration:BackgroundTaskBase: updating UpdateCachedSkuInfoTask timer to: TimerSettings: DueTime=00:00:00, Interval=1.00:00:00
[4072] 160803.162216.4705: O365Integration:BackgroundTaskBase: Starting UpdateMSOSecurityGroupDataTask
[4072] 160803.162216.4705: O365Integration:BackgroundTaskBase: updating UpdateMSOSecurityGroupDataTask timer to: TimerSettings: DueTime=00:00:00, Interval=1.00:00:00
[4072] 160803.162216.4705: O365ManagementProvider(IO365Callback): ActivateAAD:---- failed due to O365ConfigurationFault = Unexpected
Microsoft.WindowsServerSolutions.O365Integration.O365ConfigureException: Die Verbindung mit dem Remoteserver kann nicht hergestellt werden.
   bei Microsoft.WindowsServerSolutions.O365Integration.O365ManagementCore.ActivateAAD(String adminUserName, String adminPassword)
   bei Microsoft.WindowsServerSolutions.O365Integration.O365ManagementProvider.<>c__DisplayClassd9.<InvokeOperationWrapperAsync>b__d8()
   bei Microsoft.WindowsServerSolutions.Common.ProviderFramework.ProviderBase`1.InvokeOperation[TResult](String operationName, Func`1 func)
[7932] 160803.162216.4861: UpdateMSOSecurityGroupDataTask: Start UpdateMSOSecurityGroupDataTask
[7932] 160803.162216.4861: MSOSecurityGroupManager: Full sync task will start in 00:10:00 minutes.
[7988] 160803.162218.4861: O365Integration:BackgroundTaskManager: BackgroundTaskManager.StopTasks called
[7988] 160803.162218.4861: O365Integration:BackgroundTaskBase: Stopping UpdateDomainTask
[7988] 160803.162218.4861: O365Integration:BackgroundTaskBase: updating UpdateDomainTask timer to: TimerSettings: DueTime=-00:00:00.0010000, Interval=00:00:00
[7988] 160803.162218.4861: O365Integration:BackgroundTaskBase: Stopping UpdateSharepointAddressTask
[7988] 160803.162218.4861: O365Integration:BackgroundTaskBase: updating UpdateSharepointAddressTask timer to: TimerSettings: DueTime=-00:00:00.0010000, Interval=00:00:00
[7988] 160803.162218.4861: O365Integration:BackgroundTaskBase: Stopping UpdateO365IntegrationDataTask
[7988] 160803.162218.4861: O365Integration:BackgroundTaskBase: updating UpdateO365IntegrationDataTask timer to: TimerSettings: DueTime=-00:00:00.0010000, Interval=00:00:00
[7988] 160803.162218.4861: O365Integration:BackgroundTaskBase: Stopping UpdateCachedSkuInfoTask
[7988] 160803.162218.4861: O365Integration:BackgroundTaskBase: updating UpdateCachedSkuInfoTask timer to: TimerSettings: DueTime=-00:00:00.0010000, Interval=00:00:00
[7932] 160803.162236.6424: BecWebServiceAdapter: Connect to BECWS failed due to known exception : System.TimeoutException: Beim Anforderungskanal ist während eines Sendeversuch nach 00:00:20 eine Zeitüberschreitung aufgetreten. Erhöhen Sie den an den Aufruf übergebenen Zeitlimitwert auf "Request", oder erhöhen Sie den SendTimeout-Wert für die Bindung. Der für diesen Vorgang zugewiesene Zeitraum war möglicherweise ein Teil eines längeren Timeouts. ---> System.TimeoutException: Die HTTP-Anforderung an "https://provisioningapi.microsoftonline.com/provisioningwebservice.svc" hat das dafür vorgesehene Zeitlimit von 00:00:20 überschritten. Der für diesen Vorgang zugewiesene Zeitraum war möglicherweise ein Teil eines längeren Timeouts. ---> System.Net.WebException: Timeout für Vorgang überschritten
   bei System.Net.HttpWebRequest.GetRequestStream(TransportContext& context)
   bei System.Net.HttpWebRequest.GetRequestStream()
   bei System.ServiceModel.Channels.HttpOutput.WebRequestHttpOutput.GetOutputStream()
   --- Ende der internen Ausnahmestapelüberwachung ---
   bei System.ServiceModel.Channels.HttpOutput.WebRequestHttpOutput.GetOutputStream()
   bei System.ServiceModel.Channels.HttpOutput.Send(TimeSpan timeout)
   bei System.ServiceModel.Channels.HttpChannelFactory`1.HttpRequestChannel.HttpChannelRequest.SendRequest(Message message, TimeSpan timeout)
   bei System.ServiceModel.Channels.RequestChannel.Request(Message message, TimeSpan timeout)
   --- Ende der internen Ausnahmestapelüberwachung ---

Server stack trace:
   bei System.ServiceModel.Channels.RequestChannel.Request(Message message, TimeSpan timeout)
   bei System.ServiceModel.Dispatcher.RequestChannelBinder.Request(Message message, TimeSpan timeout)
   bei System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
   bei System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
   bei System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)

Exception rethrown at [0]:
   bei System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
   bei System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
   bei IProvisioningWebService.MsolConnect(Request request)
   bei Microsoft.WindowsServerSolutions.O365Integration.BecWebServiceAdapter.Connect()
[7932] 160803.162236.6424: UpdateMSOSecurityGroupDataTask: Failed to run UpdateMSOSecurityGroupDataTask: O365ConfigurationFault = Communication
Microsoft.WindowsServerSolutions.O365Integration.O365ConfigureException: Connect to BECWS failed.
   bei Microsoft.WindowsServerSolutions.O365Integration.BecWebServiceAdapter.Connect()
   bei Microsoft.WindowsServerSolutions.O365Integration.BecWebServiceAdapter.get_Client()
   bei Microsoft.WindowsServerSolutions.O365Integration.BecWebServiceAdapter.<>c__DisplayClass70.<ListSecurityGroups>b__69(ListGroupsRequest r)
   bei Microsoft.WindowsServerSolutions.O365Integration.BecWebServiceAdapter.InvokeWebServiceWithRetry[TRequest,TResponse](Func`2 func, TRequest request)
   bei Microsoft.WindowsServerSolutions.O365Integration.BecWebServiceAdapter.InvokeWebService[TRequest,TResponse](Func`2 func, TRequest request)
   bei Microsoft.WindowsServerSolutions.O365Integration.BecWebServiceAdapter.ListSecurityGroups()
   bei Microsoft.WindowsServerSolutions.O365Integration.MSOSecurityGroupManager.CleanUpMSOSecurityGroupData()
   bei Microsoft.WindowsServerSolutions.O365Integration.UpdateMSOSecurityGroupDataTask.Run().
[7932] 160803.162236.6424: UpdateMSOSecurityGroupDataTask: End UpdateMSOSecurityGroupDataTask
[7988] 160803.162236.6424: O365Integration:BackgroundTaskBase: Stopping UpdateMSOSecurityGroupDataTask
[7988] 160803.162236.6424: O365Integration:BackgroundTaskBase: updating UpdateMSOSecurityGroupDataTask timer to: TimerSettings: DueTime=-00:00:00.0010000, Interval=00:00:00
[7988] 160803.162236.6737: O365ManagementProvider(IO365Callback): Channel_Closed called
[7988] 160803.162236.6737: O365ManagementProvider(IO365Callback): Provider disconnected
[6264] 160803.162236.7674: O365Integration:BackgroundTaskManager: BackgroundTaskManager.Dispose called
[6264] 160803.162236.7674: O365Integration:BackgroundTaskBase: Stopping UpdateDomainTask
[6264] 160803.162236.7674: O365Integration:BackgroundTaskBase: updating UpdateDomainTask timer to: TimerSettings: DueTime=-00:00:00.0010000, Interval=00:00:00
[6264] 160803.162236.7674: O365Integration:BackgroundTaskBase: Dispose for UpdateDomainTask called
[6264] 160803.162236.7674: O365Integration:BackgroundTaskBase: Stopping UpdateSharepointAddressTask
[6264] 160803.162236.7674: O365Integration:BackgroundTaskBase: updating UpdateSharepointAddressTask timer to: TimerSettings: DueTime=-00:00:00.0010000, Interval=00:00:00
[6264] 160803.162236.7674: O365Integration:BackgroundTaskBase: Dispose for UpdateSharepointAddressTask called
[6264] 160803.162236.7674: O365Integration:BackgroundTaskBase: Stopping UpdateO365IntegrationDataTask
[6264] 160803.162236.7674: O365Integration:BackgroundTaskBase: updating UpdateO365IntegrationDataTask timer to: TimerSettings: DueTime=-00:00:00.0010000, Interval=00:00:00
[6264] 160803.162236.7674: O365Integration:BackgroundTaskBase: Dispose for UpdateO365IntegrationDataTask called
[6264] 160803.162236.7674: O365Integration:BackgroundTaskBase: Stopping UpdateCachedSkuInfoTask
[6264] 160803.162236.7674: O365Integration:BackgroundTaskBase: updating UpdateCachedSkuInfoTask timer to: TimerSettings: DueTime=-00:00:00.0010000, Interval=00:00:00
[6264] 160803.162236.7674: O365Integration:BackgroundTaskBase: Dispose for UpdateCachedSkuInfoTask called
[6264] 160803.162236.7674: O365Integration:BackgroundTaskBase: Stopping UpdateMSOSecurityGroupDataTask
[6264] 160803.162236.7674: O365Integration:BackgroundTaskBase: updating UpdateMSOSecurityGroupDataTask timer to: TimerSettings: DueTime=-00:00:00.0010000, Interval=00:00:00
[6264] 160803.162236.7674: O365Integration:BackgroundTaskBase: Dispose for UpdateMSOSecurityGroupDataTask called
[3636] 160803.162236.7831: MSOSecurityGroupManager: MSO Security Group Sync Worker Thread Stopped.
[6264] 160803.162236.7987: SharedServiceHost: Information: [0] : Exiting with code 0
[6264] 160803.162236.7987: SharedServiceHost: Information: [0] : ==========================================================

Sorry for my terrible english.

So today I installed the anniversary update on 2 of our windows 10 pro machines and yet again it broke the client connector ap, so i removed it and re installed it again but it is definitely broken. When i log into the server via remote desktop and try to customise a backup i get this message 

Backup cannot connect to the windows server essentials client computer management service on your network computer. if this problem persists you may be able to resolve the issue by restarting the client computer 

By the way I dont use the server as a domain controller so mainly client backup secure shares and remote access so i use the reg switch to not join the domain upon set up, this is a home environment not an office . 

Anyone that has used the above windows server will know that the last  upgrades  8-8.1, 8.1-10 and now this one will be familier with the fact that MS manage to screen the client connector up every time.

Any help/advice or thoughts will be very much appreciated.

KR

 Doug

I'm getting this in the System Event Log:

The Windows Server Essentials Computer Backup Service service terminated unexpectedly

And this in the Application Event log:

Faulting application name: WSSBackup.exe, version: 6.3.9600.17088, time stamp: 0x533cc5ee
Faulting module name: WSSBackup.exe, version: 6.3.9600.17088, time stamp: 0x533cc5ee
Exception code: 0xc0000025
Fault offset: 0x000000000004e84c
Faulting process id: 0x2a28
Faulting application start time: 0x01d1eeb39e6ff00b
Faulting application path: C:\Windows\System32\Essentials\WSSBackup.exe
Faulting module path: C:\Windows\System32\Essentials\WSSBackup.exe
Report Id: 4bd230d2-5aa7-11e6-80c8-00155d010b16
Faulting package full name: 
Faulting package-relative application ID: 

These occur frequently and randomly during Client Computer backups.

How can I fix this? A database repair task completes almost immediately with no action taken, reporting that none is necessary.

Thanks,
Jeff Bowman
Fairbanks, Alaska

I have Server 2012 R2 Essentials running in my home as a "Home Media Server" and as a backup device for my computers and tablets.  The client computers are joined to the server without being part of the domain.

The problem is that major Windows 10 updates to the clients are handled or seen by the server as new devices and unable to continue the backup lineage of the client without modification.  I can reconnect the client device by re-running the server connector but that method informs me that another device with the same name is already being used and then treats the client drives as new drives and previous backed up drives as missing drives, very confusing for restoring.

How do we manage the major updates and have continuity with the previous backups? 

In my case, computers originally installed with Windows 7 and manufacturer included software was updated to Windows 8, then Windows 8.1, then Windows 10 and I have no wish to restart this process, that is why I have this server.  But taking a client computer with Windows 8.1 and removing it and archiving the backups adds additional space requirements for the server drives for client backup and server backup.

So is this lack of forward thinking on Windows 10 development or is there some simple way this is supposed to work properly that I don't know about?

Thanks

Relatively new Server 2012r2 Essentials with workstation backup feature disabled from the get go.  It's been running for a few months without issue however this morning the workstations displayed backup failure messages.  Workstation event logs show the following...

Application, Event 2305, ServerEssentials-Control, START_BACKUP_SVC

The only thing that changed today is that I restarted the server over the weekend, which went smoothly.  I could use some advice on preventing these messages in the future as we don't use the workstation backup feature and said messages generate unnecessary alarm to users (and calls to IT staff).

Much appreciated.

Hello There,

I was trying to use MS Windows Server 2012 facility of Authentication server, i enabled the Server's NPS, facility and configured the Roles. Then i followed https://support.microsoft.com/en-us/kb/922574 thread to add MD5 support as by default it's deprecated.

Now i am able to see the added registry entries and can select the method MD5, but i dont know where to give the password of the request. I added the InvodeUsername and InvokePasswordDialog in regedit but its not giving me any such option to select the username and password.

I am getting MD5 challenge sent by 2012 to the Authenticator switch and finally Request-Reject.

Can you know me how to provide the Username/Password in 2012.

Thanks

Anurag V

Hi everybody,

I have a question, If I install windows 2012 r2 essentials , trial version for 180 days, and it complaint with

all my expectations, I can buy the final licence with out reinstall again and configure the product.

If someone know the answer I wil be very gratefull.

Thank you

Dimitry Alexie Alarcón Flores

IT PROFESSIONAL 

Guatemala, América Central

dimitryalarcon@hotmail.com

dimitry.alarcon@gmail.com

++502 53084569

I am not sure how if this is supposed to work or not, but I figure I would ask the experts.

I have Win Server 2012 Essentials (for simplicty we can call it ZZZ) running on my home local network. On the home network I have a desktop computer (XXX) running win10 and a tv-receiver (YYY). I also have a laptop running win10 (let's call it QQQ) that is on the network when at home. Note the devices are connected through workgroup and not domain!

When at home all these computers can be seen under the network in explorer and I can browse their shared folders without a problem.

Now when I'm away with my laptop I connect remotely with VPN to my server through SSTP.

Question: Am I supposed to be able to see the other computers on my home local network under network when connected through the VPN? Because I'm not...

I can connect to my server though if I use:  \\ZZZ               or     \\ip-of-server    in the explorer, but I can't see ZZZ listed under computers in the network like I can do if I'm on the local network.

Additionaly, I cannot connect to the TV-receiver if I try  \\YYY           BUT it works if I use the actual ip of it        \\ip-of-tv-receiver . Which seems weird that it differs from the connection of the server. There doesn't seem to be any consistency in it.

I've made sure that all advanced sharing options are enabled on both server and client.

Is there any settings for the ipv4 with the VPN-connection? Under advanced settings TCP/IP for ipv4 I have this right now:

right now "use standard gateway on remote network" is enabled (checked)

Under DNS tab nothing is enabled.

Under WINS tab "activate NetBIOS over TCP/IP" is enabled.

Any thoughts?

I am unable to connect my desktop PC which is running Windows 10 to Windows Server 2012 Essentials R2.

I downloaded and ran the latest patch for the Connecter Wizard -- several times actually. It gives me the sign on page, and after signing on "thinks" for a long time, then gives me a message that says "Cannot connect this computer to the network","The server is not available. Try connecting this computer again.".  I tried signing on both with my administrator ID and my desktop ID, with the same results.

Windows Server is running on an HP ProLiant MicroServer.  I have other systems running Windows 7 and Windows 8 connected in OK.

My desktop, back before I upgraded it from Windows 7 to Windows 10, had successfully been connected to another server running Windows Server 2003, using the same router, etc.  My desktop is able to access all other network resources like stand-alone hard drives, printers, other PC's, etc. with no problems.

I have tried rebooting everything as well, with the same results.

Any suggestions?

Thanks

I tried to install the update Windows10.0-KB2790621-x64.msu for connecting the windows 10 pro x64 clientto the windows server 2012 R2 essentials server,but the msu package always fails on the client.

any idea how to solve that or manually install the connector software ?

i already tried to copy the files "system32\essentials" from a working client to the client with the installation problems

but the deploy.exe wont work. do i have to register all the dlls ?

Hello, I am running a server 2012 R2 machine for my business and it has 2 raid arrays on it, one consisting of 4 samsung 850 evo drives in a RAID 10 and the other array is 2 western digital RED 3tb drives, both of these arrays are on the internal raid on the motherboard. I am trying to backup this server to another physical machine with identical hardware using the boot media then going to repair your computer and doing the system image recovery option, I am then loading the intel sata driver and intel RST driver and am getting the 0x80042414 error saying that it is not finding any drives to partition, can anyone help me with this issue?

Hello,

I had windows server 2012 r2 essentials set up just fine.

After the latest LARGE update for windows 10, which appears to have made some changes, Launchpad is now gone from my computer.

I am still able to connect to our VPN (anywhere access) and my shared server folders are accessible.

Launchpad is gone from the taskbar, I can't find it on my computer at all.

What's the best course of action?

Thanks!!

I have a client who has been using the Remote Web Access.  When their SSL cert. expired we installed a new third party SSL.  

Since that time the Web Access seems to lock up every 24 hours with various errors in the event viewer.  You could stop the various services but it wouldn't pull the website back up without rebooting the server.  Finally out of frustration I uninstalled the Essentials roles along with Remote Desktop.  Then re-installed the Essentials.  The website now seems stable but the only device that shows up for remote access under devices is the actual server.

I have taken one workstation. Uninstalled the Connector from the windows update list,  un-joined it from the domain. Reset the computer in ADUC. And re-installed the connector from the Connect webpage.  The computer is back on the domain but it still doesn't show up under devices on the web page.

What am I missing?  Will I need to unjoin and re-join the other computers in the office?  Any advice?

I have a Windows 2012 R2 Essentials system acting as a primary domain controller, ad server, NTP server, DNS server. I also have a secondary domain controller that is acting as a backup for some of these services. I have the current Essentials system in a tower PC and am planning on replacing it with a rack mount server. If I shut off the current server after a backup, and restore it using the external drive that it backs itself up to onto the new compute rand turn it on, besides some driver detection, should everything continue working? Syncing of policies and DNS settings and the like? Want to make sure the other server doesn't see it as some rogue system and drop it from the group.

Thanks.

Steve

The way I read this dialog box, it is asking for the User name and Password for my GoDaddy account.  I enter my correct GoDaddy credentials yet the dialog responds with "The user name or password is incorrect.  Retype your user name and password."

This prevents me from setting up the Remote Anywhere"!

I am building a new Server 2012 R2 Essentials server to replace my (too difficult to keep running) SBS 2011 Standard server.  My domain name is the same.  My public IP address is the same.  My MAC will be the same upon retiring that SBS, so my router and router's firewall remain unchanged (that is a minor issue since I can rebuild the router firewall in a few minutes).  I already have a valid current certificate (from GoDaddy) and that will remain unchanged.  If I could just bypass this setup Remote anywhere dialog.

Either the dialog must accept valid GoDaddy credentials by fixing the dialog, or provide information to allow me to configure Remote Anywhere manually (bypassing Essentials faulty dialog).

The old SBS server is up merely for Exchange.  Everything else is already migrated to the Server 2012 R2 Essentials.

- Michael Faklis

Hi

I am having a problem since running the Windows 10 anniversary update, the client connector had disappeared completely from the PC post update, now my issue is when re-installing the installation completes successfully but fails when doing it gets to "Configuring you computer..." ( See error Below )

And the event viewer log:

I have tried uninstalling the application and re-installing, leaving the domain and then running the application but everytime this fails on the exact same place and with the error listed above.

any help would be much appreciated

1. Host physical machine running Essentials Hyper-V function only.

2. VM 1 running Essentials, various server roles

3. VM 2 running Windows 10

4. VM 3 running Windows 10

Therefore, one Essentials license and two Windows 10 licenses.

Does above scenario meet MS license rules?  If not, would changing 1. above to Hyper-V Server make it legal?