Been struggling to reconnect my clients after the Anniversary update.

I have uninstalled all of the Previous Connector install from all clients.

In an attempt to "get 'er done" I rebuilt my Windows Server Essentials 2012 R2 server. I even changed the name of the server to avoid any certificate issues on the clients.

I connect to the server via http://<myServernamehere>/Connect and get the download screen. The installation file downloads to my downloads folder and after I click to run I get the following message when attempting to install the first client:

Installation did not succeed

Windows Server Essentials Connector has not been installed because:

Cannot download the package

Verify that your device is connected to the internet, and then install the Windows Server Essentials Connector.

I can ping the Essentials server with both the server name and the internal IP address. Both Client and Server are on the internet.

I have run the essentialsstester.ps1 and all is well with no "red" errors.

I am not joining the clients to the domain. I have run as administrator the command: reg add "HKLM\SOFTWARE\Microsoft\Windows Server\ClientDeployment" /v SkipDomainJoin /t REG_DWORD /d 1 command.

 Can anyone help me please?

Hi,

I have a new install of Windows Server 2012 Essentials, which is a migration from Small Business Server 2008 Standard (as per the TechNet instructions).  Migration seems to have gone in ok, no errors anywhere including BPA but I can't seem to enable the Office 365 integration.

I run the setup wizard, I'm ticking the option re have an existing subscription, entering valid (Global) administrator credentials and after about half a minute I get the error There Was a Problem Configuring Office 365 Integration -- Cannot connect to Microsoft Office 365.

I tried to look in the Windows Server\Logs folders for some further information but couldn't find anything.  Does the process create any log files in there?  Or anywhere else for that matter?

Any suggestions ?

Mark

I have a 2012 Essentials server that's acting as a file server for the company I work for. I've been running into strange network issues and I'm not sure what's causing them.

For the last week or so it has been issues connecting to my ReadyNAS. The NAS is connected to Active Directory and it shows up in File Explorer under Network. When I click on the NAS to open it I get almost always get 'Windows cannot Access \\NAS - Check spelling...'. If I close the error and click on the NAS again it opens and the shares are there. Sometimes it opens the first time. I would like to setup the backup to use the NAS as the destination but it keeps failing and I'm wondering if it's because of this network issue.

Any ideas? I have checked all the network settings. I also installed SMB Plus on the NAS and set the SMB version to 2.0.

Hope anyone can help. The windows server health service has stopped running and cant be started again, as soon as I start the service it stops straight away. This affects the dashboard now all clients show offline. Nothing in event log it only shows its was terminated. Any ideas or has anyone got same problem?

THanks,

Daniel

I've got a recurring issue where the WSSBackup.exe service terminates while backing up client computers. I've set the service to automatically restart upon failure, and it does restart. 

This occurs not on every backup, but I would say on about 30% of backups.  It does not seem to be any specific computers either, as when this happens the computer backup status will show 'incomplete'.  The next day the PC may backup correctly, but a few others will show the incomplete status.

When the service does crash, the errors below will appear.  I've patched the server to the latest versions.

Any ideas?

Application 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: 0x1e90

Faulting application start time: 0x01cfb6feee000e29

Faulting application path: C:\Windows\System32\Essentials\WSSBackup.exe

Faulting module path: C:\Windows\System32\Essentials\WSSBackup.exe

Report Id: f1505f80-22f2-11e4-80ca-fc4dd4f53430

Faulting package full name:

Faulting package-relative application ID:

System log:

The Windows Server Essentials Computer Backup Service service terminated unexpectedly.  It has done this 1 time(s).  The following corrective action will be taken in 60000 milliseconds: Restart the service.

On two separate Server 2012 R2 ESS site having same problem with multiple clients after 1607 update.

On the Shared Folders when a user tries to create a new folder or rename a existing file File Manager times out (Not Responding).  Error 0x8007003b is then reported on the client.  Close File Manager and then reopen and a New Folder has been created called New Folder.  At that point the folder can be renamed

Kent

Connection broken after Win 10 feature upgrades5qn 

I think I have followed posted procedure. Deleted connector software, left domain, removed pc from Dashboard and tried to reconnect using browse to server. After starting connection I get something happened and roll back.

ClientDeployLog shows Errorc code 1603

[11708] 160811.161919.1282: ClientSetup: Downloaded file C:\WINDOWS\Temp\Client Deployment Files\ClientCore.cab
[11708] 160811.161919.4564: ClientSetup: Found MSI file within cab: ClientCoreX86.msi
[11708] 160811.161919.4564: ClientSetup: Found MSP file within cab: KB2862554-x86.msp
[11708] 160811.161919.4564: ClientSetup: Exiting DownloadSoftwareTask.Run
[11708] 160811.161919.4564: ClientSetup: Task with Id=ClientDeploy.DownloadSoftware has TaskStatus=Success
[11708] 160811.161919.4564: ClientSetup: Task with Id=ClientDeploy.DownloadSoftware has RebootStatus=NoReboot
[11708] 160811.161919.4564: ClientSetup: Running Task with Id=ClientDeploy.InstallSoftware
[11708] 160811.161919.4564: ClientSetup: Entering InstallSoftwareTask.Run
[11708] 160811.161919.4720: ClientSetup: Install package C:\WINDOWS\Temp\Client Deployment Files\ClientCoreX86.msi
[11708] 160811.161919.7220: ClientSetup: Running MSI: C:\WINDOWS\Temp\Client Deployment Files\ClientCoreX86.msi  SOFTWARE_NAME="Windows Server 2012 Essentials" PATCH="C:\WINDOWS\Temp\Client Deployment Files\KB2862554-x86.msp" REBOOT=ReallySuppress
[11708] 160811.162415.2277: ClientSetup: Running MSI threw an exception:Microsoft.Deployment.WindowsInstaller.InstallerException: Fatal error during installation.
   at Microsoft.Deployment.WindowsInstaller.Installer.CheckInstallResult(UInt32 ret)
   at Microsoft.WindowsServerSolutions.ClientSetup.ClientDeploy.Helper.RunMsi(String msiPathOrProductCode, String logFilePath, Dictionary`2 msiProperties, Boolean install, ProgressChangedEventHandler progressHandler)
[11708] 160811.162415.2277: ClientSetup: RunMsi returned error: RetCode=1603
[11708] 160811.162415.2277: ClientSetup: Failed to install C:\WINDOWS\Temp\Client Deployment Files\ClientCoreX86.msi
[11708] 160811.162415.2277: ClientSetup: Set CD Fail reason 6 for SQM in ClientDeployment.exe
[11708] 160811.162415.2277: ClientSetup: Exting InstallSoftwareTask.Run
[11708] 160811.162415.2277: ClientSetup: Task with Id=ClientDeploy.InstallSoftware has TaskStatus=Failed
[11708] 160811.162415.2277: ClientSetup: Task with Id=ClientDeploy.InstallSoftware has RebootStatus=NoReboot
[11708] 160811.162415.2277: ClientSetup: Exting ConnectorWizardForm.RunTasks
[11708] 160811.162417.1961: ClientSetup: Running Tasks for Wizard Page InstallationError
[11708] 160811.162417.1961: ClientSetup: Entering ConnectorWizardForm.RunTasks
[11708] 160811.162417.1961: ClientSetup: Running Task with Id=ClientDeploy.UninstallSoftware
[11708] 160811.162417.1961: ClientSetup: Entering UninstallSoftwareTask.Run
[11708] 160811.162417.1961: ClientSetup: Client MSI is not installed
[11708] 160811.162417.1961: ClientSetup: Exiting UninstallSoftwareTask.Run
[11708] 160811.162417.1961: ClientSetup: Task with Id=ClientDeploy.UninstallSoftware has TaskStatus=Success
[11708] 160811.162417.1961: ClientSetup: Task with Id=ClientDeploy.UninstallSoftware has RebootStatus=NoReboot
[11708] 160811.162417.1961: ClientSetup: Exting ConnectorWizardForm.RunTasks
[6752] 160811.162417.2117: ClientSetup: Back from the Client Deployment Wizard
[6752] 160811.162417.2273: ServerDiscovery:HostsFileUpdater: Removing hosts file entry: NJHS01
[6752] 160811.162417.3054: ClientSetup: Saving Wizard Data
[6752] 160811.162417.3054: ClientSetup: NetGetJoinInformation (server = [], ...)
[6752] 160811.162417.3054: ClientSetup: Deleting user: [__clientsetup__$].
[6752] 160811.162417.3367: ClientSetup: End of ClientDeploy: ErrorCode=1603

Hi,

I've recently moved for Office 365 Small Business Premium to Business Premium.  As far as I can see the Office 365 integration is work i.e. password sync, the dashboard is talking to Office 365 ok.  However I am seeing an error in the health check dashboard that is saying "One or more of your Office 365 subscriptions have expired" which relates to the old subscription.  Is there a way to kill this warning? I've tried setting it to "Ignore" but it keeps getting activated again.

Cheers

Rob

[I did intend to start this post with a screenshot of the above error when I initiate the transfer from Windows Explorer, but apparently 'Body text cannot contain images or links until we are able to verify your account.' so I will just have to do some typing, viz the error dialog says:

 'An unexpected error is keeping you from copying the file. If you continue to receive this error, you can use the error code to search for help with this problem.

Error 0x800705AA: Insufficient system resources exist to complete the requested service.'

I get this error pretty much 100% of the time from one particular PC when trying to copy a folder of 10 2GB files to a server with both mirror and parity storage spaces.

I recently purchased a Thecus W5000 running Windows Storage Server 2012 R2 Essentials. Absent any guidance either way I decided to set up a storage pool across the three 3TB WD Red drives that I have installed in it and to allocate 1.5TB of that space to a mirror storage space and the remainder to a parity storage space. Having read some faily dire things about storage spaces, but wanting the resilience provided by those two types of storage space, I decided to run some benchmarking tests before finalising anything.

To that end I only went as far through the Essentials setup as creating a handful of user accounts before setting up the storage spaces and sharing both of them, with all authenticated users permitted full control. My benchmarking consists of a Take Command batch file timing three large directory copies - one with 10 2GB files, one with 10240 10K files and another with a multi-level directory with a variety of files of differing sizes. The first two are completely artificial and the latter is a real world example but all are roughly 20GB total size.

To test various aspects of this I copied the three structures to and then from a partition created on the internal disk (the W5000 has a 500GB SSHD) and to the two storage space partitions. I also created a version of the batch file for use internally which did something similar between the internal disk and the two storage space partitions, and another as a control that tested the same process between the two Windows PCs. The internal test ran to successful completion, as did the PC to PC copy and the external one from my Windows 8.1 64-bit system (i5 3570K, 16GB RAM, 1TB HD) but when I ran it from my Windows 7 Pro 64-bit gaming rig (i7 2600K, 8GB RAM, 1TB HD) I got a number of failures with this error from Take Command:

TCC: (Sys) C:\Program Files\bat\thecus_test_pass.btm [31] Insufficient system resources exist to complete the requested service.

(where line 31 of that batch file is a copy command from local D: to the parity space on the Thecus).

The error occurs only when copying large files (the 2GB ones already mentioned but some of those in the real world structure that are about 750MB in size) from the Win7 system to the Thecus and only when doing so to the storage space volumes - ie. copying to the internal disk works fine, copying from all volumes works fine, copying internally within the Thecus works fine, copying between the Win8 and Win7 machines works fine and initiating the copy as a pull from the server between the same two disks also works fine. One aspect of this that surprised me somewhat was just how quickly the copy fails when initiated from Windows Explorer - checking out the details section of the copy dialog I see roughly ten seconds of setting up and then within five seconds after the first file transfer is shown as starting the error dialog pops up (as per the image no longer at the top of this post).

There are no entries in the event log on either machine related to this error and I've had the System Information window of the Sysinternals Process Explorer up and running on both machines whilst testing this, and it shows nothing surprising on either side. I've also run with an xperf base active and I can't see anything pertinent in the output from either system.

Frankly, I am at a loss and have no idea what other troubleshooting steps I should try. The vast majority of the existing advice for this error message seems to relate to Windows 2003 and memory pools - which both the fact that this works from one PC but not the other and the SysInfo/xperf output seems to suggest is not the issue. The other thing I've seen mentioned is IRPStackSize, but again if that was the problem I would expect the failure to occur where ever I initiated the large file transfer from.

Hello, I can not hibernate/sleep when Hyper-V is enable. The spec/doc specify it should work. Many people complain on diver forums about this issue, when will this bug be solved?

Note: If I disable Hyper-V then hibernate and sleep work properly

Note: https://technet.microsoft.com/en-us/library/hh831410.aspx#BKMK_Sleep1

Hyper-V is ON:

C:\windows\system32>powercfg /h on
Hibernation failed with the following error: The request is not supported.

The following items are preventing hibernation on this system.
        An internal system component has disabled hibernation.
                Hypervisor

C:\windows\system32>powercfg /a
The following sleep states are not available on this system:
    Standby (S1)
        An internal system component has disabled this standby state.
                Hypervisor

    Standby (S2)
        The system firmware does not support this standby state.
        An internal system component has disabled this standby state.
                Hypervisor

    Standby (S3)
        An internal system component has disabled this standby state.
                Hypervisor

    Hibernate
        An internal system component has disabled hibernation.
                Hypervisor

    Standby (Connected)
        The hypervisor does not support this standby state.
        The system firmware does not support this standby state.

    Hybrid Sleep
        Standby (S3) is not available.
        Hibernation is not available.
        The hypervisor does not support this standby state.

    Fast Startup
        Hibernation is not available.


C:\windows\system32>

Note: I used win server 2008 for years with hyper-v and sleep/hibernate, it always did work fine (until the hardware failed and I upgraded everything to ws essential 2012)

Note: there are divers work around involving modifying the registry every time to enable/disable hyperV but this not solving the issue and is very impractical. I just want to be able to have all my VMs on and be able to hibernate/sleep my server when I need to.

thanks

w

w.

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?

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 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.

Hi all.

I have a customer who has installed Windows server 2012 R2 foundation on an ML310 server (1 processor, 4 cores=

It is a domain controller (the only one of the domain)

since few weeks, customer reported that this popup apprears every 2 ot 3 days:
"The server did not finish checking the license compliance. If the server is joined to a domain, make sure that the server can connect to a domain controller.
If the license compliant check cannot be completed, the server will automatically shut down in 2 days, 7 hour(s) 30 minute(s). "

Every time it happens, the server seems to be not operational :
port 389 seems to be not available anymore  (tested with ldp) , Internet Access is down, ADUC is not accessible, with the message "the server is not operational", etc..

After the reboot, the server is again functional for 2 or 3 days..

Below are the elements already checked:

1/
The license seems to be well registered:

------------------
slmgr.vbs /dlv all
------------------
Version du service de licences logicielles : 6.3.9600.17809

Nom : Windows(R), ServerWinFoundation edition
Description : Windows(R) Operating System, OEM_COA_NSLP channel
ID d'activation : 00b997e2-864d-40b5-b80c-112aaed7bc5b
ID d'application : 55c92734-d682-4d71-983e-d6ec3f16059f
PID étendu : 06401-02538-000-146808-02-1036-9600.0000-0742015
Canal de la clé de produit (Product Key) : OEM:NONSLP
Identificateur d'installation : 006598659521630795763392760173850155117126244293546676706933200
URL de licence d'utilisation : https://activation-v2.sls.microsoft.com/SLActivateProduct/SLActivateProduct.asmx?configextension=Retail
URL de validation : https://validation-v2.sls.microsoft.com/SLWGA/slwga.asmx
Clé de produit partielle : RJP23
État de la licence : avec licence
Nombre de réinitialisations de Windows restant : 1000
Nombre de réinitialisations de la référence (SKU) restant : 1001
Heure approuvée : 21/08/2015 16:21:03

2/
Customer has only 5  users + Administrator...

3/
DC is DNS client of himself.
DC seems to be well registered in DNS.
4/
Only one physical processor

It seems the problem is related to the license popup. How can we check what is the the element which is no compliant ?
If no, how can we troubleshoot the problem ?

Thanks in advance for your responses.
Patrick.

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

This post describes a tempory solution that allows client computers to connect to Windows Server 2012 Essentials without joining the Windows Server 2012 Essentials domain. Please read the following Notes carefully before you take any actions.

Description

When deploying Pro/Enterprise/Ultimate Windows client computers in a Windows Server 2012 Essentials network, joining the Windows Server 2012 Essentials domain is mandatory. If the client computer is already joined to another domain, you are required to manually leave the existing domain; otherwise, the client deployment process will be blocked.

Currently we have received requests from customers asking for the option to skip domain joining in a client deployment. As a result, in this article we provide a solution so that the client can connect to the server and utilize the majority of client features without joining the domain.

Before you take any action, please read the following note. 

Note:  

If you skip joining the domain, the following areas will be impacted:

• All features that require that you be joined to the domain will not be available, including domain credentials, Group Policy, and VPN.
• Any third-party add-ons and applications that require that you join the domain will not be working properly.
• Skipping domain joining in an off-premises client deployment is not supported.
• This solution is only supported on the following Windows client versions:  
  • Windows 7 Professional
  • Windows 7 Enterprise
  • Windows 7 Ultimate  
  • Windows 8 Pro
  • Windows 8 Enterprise

To skip joining the domain during a client deployment

1. On your client computer, go to Start and search for command prompt "cmd".
2. In the search results, find cmd.exe and run as administrator.
3. Type the following command prompt:
   reg add "HKLM\SOFTWARE\Microsoft\Windows Server\ClientDeployment" /v SkipDomainJoin /t REG_DWORD /d 1
4. Complete the steps on the Connect Computers to the Server Help topic.