I haven't touched my server in a long time besides applying updates and Plex.  For some reason, the last two weeks the dashboard has been crashing / will not stay open. 

Anyone know why this may be occurring?

Hi

I have a 2012R2Essentials box supporting a small team of remote office workers using AnywhereAccess (both web and VPN). Our main internet connectivity has down times more than I would like. (Dynamic IP addreess, in reality it rarely changes) I use a abc.remotewebaccess.com URL to allow web or VPN connectivity

I would like to add a 2nd internet connection probably a mobile/cellular broadband connection and have it configured so that when our main ineternet connection goes down it can swap over to the 2nd. (very much dynamic IP address)

Hiowever to me there are a few issues that need to be understood and I cant seem to find out any info on them.

1) the whole dynDNS process is hard to find any info.....why on earth did they have to use dynDNS to describe it when that is both a commercial offering and also a generic technology..makes googling not a lot of fun....... anyway I presume on the server there is a service or a scheduled task that tests your internet facing IP address and updates the remotewebaccess.com dynamic DNS service. However I dont understand what that process/task/service is and how often its triggered. Further I dont understand how long it takes for the change to find its way to the client.... I mean there is no value if the internet goes down for 15 minutes but a client wont see a changed IP address available to it for 20 minutes....those numbers are plucked I really don't understand how close to real time they ar, except to say that the registry entry at HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Server\Domain Manager\DynDNSInfo seems to suggest via LastSuccessfulDNSUpdate that at the time I checked it was 20hours past...but then as I said my dynamic IP doesn't change all that often, so perhaps "nothings changed" checks might not result in that key being updated.

2) My server is a HP server with plenty of spare ethernet ports so pressuming that 1) isnt actually an issue should I use a spare ethernet port as the host for the 2nd WAN connection, or should I use a H/W load balancer like one of the TP-Link boxes that can auto swap to mutliple WAN connections depending on the config. If I use the load balancer then to the server connectivity is never affected so what triggers the dynDNS process....

3) How would I set up the multiple WAN connections directly on the Server if we ditch the whole H/W load balance thing....

I really hope someone understands the whole dynDNS process and can explain it to me, and also someone can explain how to set up dual WAN connections in a redundant manner. I'm not looking to load share across both connections, in fact the opposite I want to use the main connection for the majority of the time and only use the expensive cellular solution for as short a time as possible until the main service comes back up. I fully understand that in terms of client  state such a need to change will drop my remote users offline until they reconnect. In my ideal world I presume the dynDNS process is close to real-time and the clients ability to query the updated DNS record is also close to real-time.....So enough of fairy tales back to reality...

As the title sais... When trying to complete Windows Server Essentials configuration it displays "preparing your server" for just a second and then displays the error.

"Configuration encountered some issues."

"Please Click Retry. If the issue still exists please refer to the help link for more troubleshooting steps"

Clicking retry does not help, troubleshooting info does not produce anything helpful. There's nothing in the logs that can correlate to this error. Searching the web also does not produce any helpful results.

Any assistance with this would be much appreciated.

azmp1

Migrating from 2012R2 STNRD (S1) to 2012R2 Ess (S2). Following this article <https://blogs.technet.microsoft.com/sbs/2014/02/21/deploying-windows-server-2012-r2-essentials-in-an-existing-active-directory-environment>. Replicating DC went smoothly. FSMO are with S2 now. Will retire S1 after successful Migration. So will have Single DC. 

DCDIAG produces following warning & errors

Starting test: Advertising
 Warning: DsGetDcName returned information for \\S1.domain.org, when we were trying to reach S2.
 SERVER IS NOT RESPOINDING or IS NOT CONSIDERED SUITABLE.
.................. S2 failed test Advertising

Starting test: DFSREvent
  There are warning or error events within the last 24 hours after the SYSVOL has been shared. Failing SYSVOL replication problems may cause group policy problems.
.................... S2 failed test DFSREvent

Starting test: NetLogons
  Unable to connect to the NETLOGON share! <\\S1\netlogon>
 [S2] An net use or LsaPolicy operation failed with error 67,
 The network name cannot be found
.................. S2 failed test Netlogons

Running enterprise test on: domain.org
 Starting test: LocatorCheck
 Warning: DcGetDcName<TIME_SERVER> call failed, error 1355
 A Time Server could not be located.
 The server holding the PDC role is down.
 Warning: DcGetDcName<GOOD_TIME_SERVER_PREFERRED> call failed, error 1355
 A Good Time Server could not be located.
................. domain.org failed test LocatorCheck

Ran AD Replication Status Tool, shows no errors, says operations completed successfully. 

DNS & DHCP servers are on S2. S1 's DNS pointing at S2. 

Cutting very close to 21 grace period. Any help is appreciated. 

C:\> repadmin /showrepl

Default-First-Site-Name\S2
DSA Options: IS_GC
Site Options: <none>

=== INBOUND NEIGHBORS ================
DC=domain, DC=org
 Defualt-First-Site-Name\S1 via RPC
    DSA object GUID: ##########################
    Last attempt was successful.

CN=Configuration, DC=domain,DC=org
 Defualt-First-Site-Name\S1 via RPC
    DSA object GUID: ##########################
    Last attempt was successful.

DC=DomainDnsZones, DC=domain,DC=org
 Defualt-First-Site-Name\S1 via RPC
    DSA object GUID: ##########################
    Last attempt was successful.

CN=ForestDnsZones, DC=domain,DC=org
 Defualt-First-Site-Name\S1 via RPC
    DSA object GUID: ##########################
    Last attempt was successful.

I have a client with 3 servers in different cities.  One server is Windows Server 2012 Essentials, one 2012 R2, and the other 2008 R2.  I set up windows server backup on all three.  The Essentials server will run a scheduled backup once after reboot, then does not run it again.

It WILL backup if I run a backup once, and backs up all the folders that are selected.  Using the command line it runs once but not more than that.

The logs show successful backups whenever the backup runs, whether scheduled or manual.  However any other time there is nothing in the log to indicate the backup started. 

I have removed the Windows Backup feature and deleted all files related to it, then rebooted, and re-added the feature, recreating the schedule.  It backed up once as scheduled, then did not run after that.  Whenever I reboot the server the backup runs that night but does not run after that.

I am at a loss to figure this out.  The other servers backup as scheduled every day with no issue.

If someone can point me in the right direction I would greatly appreciate it.

We have a number of clients that have Windows Server Essentials 2012 and 2012R2 networks.  The client workstations are all Windows 7 Professional.  This combination has worked very well for everyone.  However, with the "free" Windows 10 upgrade soon-to-expire, we are getting questions about upgrading the client OS to Windows 10 Pro (and/or adding new Windows 10 computers to the existing network).  One reason we have held off on this is that I know there have been problems with Windows 10 and Server Essentials 2012.

Here is my question:  Does Windows 10 now work properly with Essentials, the connector software, etc.?  Or are there still issues/problems with this combination?  Understandably, I'd rather know about any looming potential obstacles prior to implementing the client OS upgrade.

Thanks very much.

John

I'm trying to upgrade my server and software at the same time. I've got Essentials up and running and need to move my data from my old Windows Home Server to the new.

I figured I would just pull out the old data drive and insert in the new server and start copying files over. Not the case as everyone has a great laugh. I did too when I realized how that just seemed to easy with encrypted and password projected files.

Question is, how do you perform a migration like this? If I could get the drive to log me in, that would be simple right. Admin, password and such. Any guidance that has done this same task?

Joe Stewart

I have a 256gb ssd for my system disk. Currently, 224GB is listed as used with 13.4GB free. The thing is, when I look at the properties of the folders I see on the drive (including the hidden program data folder), I come up with 28.025 GB in use. FTW, big time.  Comments on what might be going on and tools that are safe for the server to deal with it would be appreciated.

Thanks!

Initially, I had integrated Office 365 with Server 2012R2 so we could sync the passwords. This worked fine until recently. In the Windows Server Essentials Dashboard, all online accounts were shown as 'unknown', and when I tried to import online users (or do anything that required the online services) I got an error saying: "Cannot connect to Microsoft online services".

So, I thought I could remove the integration, and try to re-integrate it again. I removed the Azure Active Directory, and Office 365 integration. Which worked fine. However, when I want to integrate with Office 365 again, I get the error I used to get. To integrate Office 365, I took the following steps:

-Open the Windows Server Essentials Dashboard

-In Home, under Services, I went to "Integrate with Microsoft Office 365", and clicked on "Integrate with Microsoft Office 365".

-In the wizard I checked "I already have a subscription" and clicked next.

-I entered a valid user name/password combination and clicked next.

-I checked that I understand that the password policy will be set to strong and clicked next.

-Then a progress bar appears for a short while, and then I get the "Cannot connect to Microsoft online services" error again.

Does anybody know how I can resolve this?

I'm getting a continuous error when trying to enrol 2 xdifferent Windows 10 machines to the 2012 Essentials Server.

I have used the Server Troubleshooting tool and fixed a few issues with binding default web services. Ihave had the client ina few different domain-enrolled and workgoup scenarios. I have the DNS clients pointing to the essentials DNS service. I have tried various accounts with admin and non admin privileges.

When installing the connector from http://server-name/connect, the Server is located correctly, then I start the Wizrd, it checks for .NET4.5,asks for a username and password from the domain to use - if I put in the wrong account it fails here as expected, but Iput in valid accounts and it continues. Ihave tried Netbios\username and just username - I get prompted that the account is an admin when it is, so far so good. But immediately after this i get "The Server is not available. Try connecting this computer again, or for more information, see Troubleshooting connecting computers to the server".

I checked some of that troubleshooting. Time on the clients and the servers is accurate within the second. Just about all other troubleshooting steps I comply with. I found somone with a refernce to the 1603 error below was due to an issue with bindings on the WSS Certificate Web Service running on port 65500, but it is fine, The server has been rebooted a couple of times 'just in case'.

I toyed with the registry key on the client that stops domainenrolment - but that had no effect. I noticed one of the regkey values that had been left behind by the failed client install, that the account in there is 'administrator' (HKLM/SOFTWARE/Microsoft/Windows Server/ServerAdminUserName), which I had disabled, so enabled to test but no good. I tried cleaning out that folder and tried again, no good.  Since my DHCP gives my DNS suffix as the FQDN, I tried a manual DNS suffix change to .workgroup, nased on some other troubleshooting steps I'd seen. No good.

Looking at the logs on the failed clients, they both get the same errors. Logs were found in c:\programdata\Microsoft\Windows Server\Logs.

From CLientDeploy log:

[10496] 170123.120010.8235: ClientSetup: Running Task with Id=ClientDeploy.GetStandardUsers

[10496] 170123.120013.2472: ClientSetup: Could not get domain user list, exception: System.DirectoryServices.DirectoryServicesCOMException (0x8007052E): The user name or password is incorrect.

   at System.DirectoryServices.DirectoryEntry.Bind(Boolean throwIfFail)

   at System.DirectoryServices.DirectoryEntry.Bind()
   at System.DirectoryServices.DirectoryEntry.get_AdsObject()
   at System.DirectoryServices.PropertyValueCollection.PopulateList()
   at System.DirectoryServices.PropertyValueCollection..ctor(DirectoryEntry entry, String propertyName)
   at System.DirectoryServices.PropertyCollection.get_Item(String propertyName)
   at System.DirectoryServices.AccountManagement.PrincipalContext.DoLDAPDirectoryInitNoContainer()
   at System.DirectoryServices.AccountManagement.PrincipalContext.DoDomainInit()
   at System.DirectoryServices.AccountManagement.PrincipalContext.Initialize()
   at System.DirectoryServices.AccountManagement.PrincipalContext.get_QueryCtx()
   at System.DirectoryServices.AccountManagement.Principal.FindByIdentityWithTypeHelper(PrincipalContext context, Type principalType, Nullable`1 identityType, String identityValue, DateTime refDate)
   at System.DirectoryServices.AccountManagement.Principal.FindByIdentityWithType(PrincipalContext context, Type principalType, IdentityType identityType, String identityValue)
   at System.DirectoryServices.AccountManagement.UserPrincipal.FindByIdentity(PrincipalContext context, IdentityType identityType, String identityValue)
   at Microsoft.WindowsServerSolutions.ClientSetup.ActiveDirectoryUser.GetUserInfoCollection(String serverName, String domainNetbiosName, String userName, String password, String[] userSids)
   at Microsoft.WindowsServerSolutions.ClientSetup.ClientDeploy.GetStandardUsersTask.Run(WizData data)
[10496] 170123.120013.2482: ClientSetup: Exiting GetStandardUsersTask.Run()
[10496] 170123.120013.2482: ClientSetup: Task with Id=ClientDeploy.GetStandardUsers has TaskStatus=Failed
[10496] 170123.120013.2482: ClientSetup: Task with Id=ClientDeploy.GetStandardUsers has RebootStatus=NoReboot
[10496] 170123.120013.2482: ClientSetup: Exting ConnectorWizardForm.RunTasks
[10920] 170123.120013.2532: ClientSetup: JoinNetwork Tasks returned TaskStatus=Failed
[10920] 170123.120015.4250: ClientSetup: Back from the Client Deployment Wizard
[10920] 170123.120015.4280: ClientSetup: Saving Wizard Data
[10920] 170123.120015.4320: ClientSetup: End of ClientDeploy: ErrorCode=1603

So the real odd behaviour here is that it accepted a valid domain username and password one step prior, but then errors out complaining of a bad username and password. This is not very intuitive to me.

Looking at all mention of the Exception error that is originally thrown when Clientsetup is called turns up a few hits, but nothing that has helped. The additional detail in the debug where we seem to fail is GetUserInfoCollection or GetStandardUsersTask - but they don't turn up any hits. Seeing the 'DoLDAPDirectoryInit' made me think it might be doing a generic ldap query, so I grabbed an ldap browser - and the accounts I use for installing the client appear to have full read access to the whole directory, so ldap is running and working fine.

So I am at an end. To me it looks like either there is an issue with the .NET 4.6 calls from my client (.NET 4.6.01586) and Server 2012 essentials responses, or there is some hidden account that is used for the Userlookup that has expired or is disabled that prevents the lookup. 

 I have 17 of 50 allowed workstations enrolled. There are a mix of XP, W7 and Windows 10 clients that have previously installed fine, are currently managed and are running backups seemingly fine. The working W10 systems were W7 systems that were upgraded. One system installed as W10 new (Surface Pro 4)does have problems with the launchpad that I have yet to troubleshoot, which may be related. It seems to still backup and function fine accorsding to the logs, but the launchpad comes up blank when started. WHen initially installed it did not do this.  So it seems an update in between, or some other inadvertent configuration,has caused this issue, and may also be the cause of my inability to install new W10 clients now.

Could someone advise if there are further troubleshooting steps that are available to me?

Luke Plaizier

After a re-boot it does this:

https://broadwave-my.sharepoint.com/personal/dwebster_broadwave_com/_layouts/15/guestaccess.aspx?docid=179cd6b96e6104724b80e31eb82c21138&authkey=AReNCCiKtWyXi4ER5J3H-WM

It will not boot into safe mode, it does the same thing as shown in the video, the video is a .mov from my iPhone, for those that don't go to the link here is what it does.

loads dell UEFI, then attempts to go into repair then almost immediately try's to boot windows and it spins a few times then goes to a blue screen where it asks me to choose an option, continue, use the device, troubleshoot, turn off your device.

Is there a way to just install the operating system's files, this has happened one other time and a reinstall fixed it but it didn't have data on it which it now does.

Any help is appreciated. :)

Duane

I have a Dell T330 server running WSE 2012 r2.  I have eight slots for sata hard drives.  One is the OS on a SSD, so not touching that.  I want to put another SSD on the second slot, but that is another priority later.  That leaves me with six slots.  They are older drives and bit of a mixed bag, but all 1GB, leaving me with roughly 6GB space for my storage.  I configured storage spaces as a two-way mirror, so that leaves me with just under 3GB of actual storage.  I only have a little over 1GB of actual usage right now.  I want to, over time, drop out the 6-1GB drives and replace them with 4-2GB drives.  I know I can retire a drive, replace it out, and swap in a new one.  I don't think the system is going to allow me to retire 2 drives, and then replace them with one.  I have the capacity and the redundancy (two-way only requires three drives at a time) to do this.  Is there a trick to making this work?

I know I could move the data elsewhere, swap out all the drives, and move it all back, but I don't have a spare server and it would be a lot more work. I can add a drive but only then can I remove one.  Anyway to remove one (two?) before adding one back in? Thoughts?

In the same Windows 10 PC Server two different configurations. Get connected and Hyper-V with the same Windows Server 2012 R2 Datacenter trial evaluation. For in Get Connected using the essential role configuration and for Hyper-V configuration utilizing a partition in Windows 10. Your recommendations are appreciated.

My question related to the Client Connector stopping during the install process. I've reviewed the various online content available and nothing I've seen is helpful. This problem started after I update to Win 10 Pro Version 1607. Since this appears to be an new issue, I thought I should see if anyone had thoughts on how to resolve. Also, I'm hopeful that this posting will bring the issue to the Microsoft, as I'm sure they want to know about this and fix it. The client machine is a Microsoft Surface Pro 4 i7 with Windows 10 Pro Version 1607 (I know I'm being redundant.)

The client deploy software appears to execute properly until the backup portion where it crashes with this dialog box that says: "Windows Server 2012 Essentials Connector Configuration Wizard has stopped working" followed by this text: "A problem caused the program to stop working correctly. Windows will close the program and notify you if a solution is available."

The most interesting line is towards the end of the log where I get this lone error message:
[5884] 170106.125100.3443: ClientSetup: !!!FATAL!!! Unhandled Exception: System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> Microsoft.WindowsServerSolutions.ClientSetup.ClientSetupException: Unexpected Error occured: DeploymentStage=ConfiguringComputer ---> System.AggregateException: One or more errors occurred. ---> Microsoft.WindowsServerSolutions.Common.ServiceNotProgressingException: The service 'WseClientMgmtSvc' failed to start. The exit code was 1067.

Seems a service fails to start, but for the life of me I can't figure out why.

I'm completely out of ideas. Any one have any thoughts? I'd welcome your help.

Here is the install log:
---------------------------------------------------------
[5884] 170106.125015.7207: ClientSetup: Start of ClientDeploy
[5884] 170106.125015.7878: General: Initializing...C:\Program Files\Windows Server\Bin\ClientDeploy.exe
[5884] 170106.125015.7878: ClientSetup: Create client deployment registry subkey if necessary
[5884] 170106.125015.8035: ClientSetup: The initial launching way:
[5884] 170106.125015.8035: ClientSetup: The initial state is set
[5884] 170106.125015.8035: ClientSetup: The initial serverName:
[5884] 170106.125015.8035: ClientSetup: Loading Wizard Data
[5884] 170106.125015.8035: ClientSetup: Saving Wizard Data
[5884] 170106.125015.8035: ClientSetup: Current DeploymentStatus=Start
[5884] 170106.125017.0902: ClientSetup: Showing the Client Deployment Wizard
[5884] 170106.125017.5906: ClientSetup: InitWizard, The currrent stage is ConnectingToServer
[5884] 170106.125017.5906: ClientSetup: Set the Deployment Sync Event
[18324] 170106.125027.5771: ClientSetup: Finish server discovery
[5884] 170106.125029.8486: ClientSetup: The selected server name is ZEKA-SERVER
[5884] 170106.125029.8486: ClientSetup: The server info: ZEKA-SERVER, System.Collections.Generic.List`1[System.Net.IPAddress]
[9276] 170106.125029.8800: ClientSetup: Entering ConnectorWizardForm.RunTasks
[9276] 170106.125029.8800: ClientSetup: Running Task with Id=ClientDeploy.PreConfiguration
[9276] 170106.125029.9113: ClientSetup: The configuration cab will be downloaded from 192.168.100.100
[9276] 170106.125029.9269: ClientSetup: Download file Setup.cab from server
[9276] 170106.125029.9269: ClientSetup: Making web request: https://192.168.100.100//connect/default.aspx?Get=Setup.cab&LanguageId=1033&64bit=1
[9276] 170106.125030.0116: ClientSetup: Failed to download Setup.cab from server: System.Net.WebException: The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel. ---> System.Security.Authentication.AuthenticationException: The remote certificate is invalid according to the validation procedure.
   at System.Net.Security.SslState.StartSendAuthResetSignal(ProtocolToken message, AsyncProtocolRequest asyncRequest, Exception exception)
   at System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.ForceAuthentication(Boolean receiveFirst, Byte[] buffer, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.ProcessAuthentication(LazyAsyncResult lazyResult)
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Net.TlsStream.ProcessAuthentication(LazyAsyncResult result)
   at System.Net.TlsStream.Write(Byte[] buffer, Int32 offset, Int32 size)
   at System.Net.ConnectStream.WriteHeaders(Boolean async)
   --- End of inner exception stack trace ---
   at System.Net.HttpWebRequest.GetResponse()
   at Microsoft.WindowsServerSolutions.ClientSetup.CSCommon.DownloadFileFromConnectSite(String outputDirectory, Uri serverUrl, String fileName, Int32 languageId, Boolean is64bit)
[9276] 170106.125030.0116: ClientSetup: Cannot get configuration file with https, will try http...
[9276] 170106.125030.0116: ClientSetup: Download file Setup.cab from server
[9276] 170106.125030.0116: ClientSetup: Making web request: http://192.168.100.100//connect/default.aspx?Get=Setup.cab&LanguageId=1033&64bit=1
[9276] 170106.125030.8511: ClientSetup: Downloaded file C:\WINDOWS\Temp\ClientDeploymentTempFiles\Setup.cab
[9276] 170106.125030.8511: ClientSetup: The configuration cab is downloaded to C:\WINDOWS\Temp\ClientDeploymentTempFiles\Setup.cab
[9276] 170106.125030.9294: ClientSetup: Adding Server Info data in the Product Registry
[9276] 170106.125035.8598: Networking:DnsEnvironmentDetector: Dns.GetHostAddresses threw exception: System.Net.Sockets.SocketException (0x80004005): No such host is known
   at System.Net.Dns.GetAddrInfo(String name)
   at System.Net.Dns.InternalGetHostByName(String hostName, Boolean includeIPv6)
   at System.Net.Dns.GetHostAddresses(String hostNameOrAddress)
   at Microsoft.WindowsServerSolutions.Networking.ServerDiscovery.DnsEnvironmentDetector.GetAddressesFromDns(String machine)
[9276] 170106.125035.8598: DnsEnvironmentDetector: No result from GetHostAddresses(), normal environment
[9276] 170106.125035.8613: ClientSetup: SkipDomainJoin hook is set, skip domain join
[9276] 170106.125035.8613: ClientSetup: Exiting PreConfigTask.Run()
[9276] 170106.125035.8613: ClientSetup: Task with Id=ClientDeploy.PreConfiguration has TaskStatus=Success
[9276] 170106.125035.8613: ClientSetup: Task with Id=ClientDeploy.PreConfiguration has RebootStatus=NoReboot
[9276] 170106.125035.8613: ClientSetup: Exiting ConnectorWizardForm.RunTasks
[18324] 170106.125043.1495: ClientSetup: Running InstallRootCert Task at WizardPage DomainUserCred
[18324] 170106.125043.1495: ClientSetup: Entering ConnectorWizardForm.RunTasks
[18324] 170106.125043.1495: ClientSetup: Running Task with Id=ClientDeploy.InstallRootCertTask
[18324] 170106.125043.1495: ClientSetup: Entering InstallRootCertTask.Run
[18324] 170106.125043.1495: ClientSetup: Install root cert to local trusted store
[18324] 170106.125043.1495: ClientSetup: Exiting InstallRootCertTask.Run
[18324] 170106.125043.1495: ClientSetup: Task with Id=ClientDeploy.InstallRootCertTask has TaskStatus=Success
[18324] 170106.125043.1495: ClientSetup: Task with Id=ClientDeploy.InstallRootCertTask has RebootStatus=NoReboot
[18324] 170106.125043.1495: ClientSetup: Exiting ConnectorWizardForm.RunTasks
[18324] 170106.125043.1495: ClientSetup: Running SetupVPNAndDA Task at WizardPage DomainUserCred
[18324] 170106.125043.1495: ClientSetup: Entering ConnectorWizardForm.RunTasks
[18324] 170106.125043.1495: ClientSetup: Running Task with Id=ClientDeploy.SetupVpnAndDATask
[18324] 170106.125043.1650: ClientSetup: Entering SetupVpnAndDATask.Run
[18324] 170106.125043.1650: ClientSetup: SkipDomainJoin hook is set, skip domain join
[18324] 170106.125043.1832: ClientSetup: Deploy VPN profile
[18324] 170106.125045.2936: ClientSetup: Exting SetupVpnAndDATask.Run
[18324] 170106.125045.2936: ClientSetup: Task with Id=ClientDeploy.SetupVpnAndDATask has TaskStatus=Success
[18324] 170106.125045.2936: ClientSetup: Task with Id=ClientDeploy.SetupVpnAndDATask has RebootStatus=NoReboot
[18324] 170106.125045.2936: ClientSetup: Exiting ConnectorWizardForm.RunTasks
[18324] 170106.125045.2936: ClientSetup: Running ValidateUser Tasks at WizardPage DomainUserCred
[18324] 170106.125045.2936: ClientSetup: Entering ConnectorWizardForm.RunTasks
[18324] 170106.125045.2936: ClientSetup: Running Task with Id=ClientDeploy.ValidateUser
[18324] 170106.125045.2936: ClientSetup: Entering ValidateUserTask.Run
[18324] 170106.125045.2936: ClientSetup: Validating User
[18324] 170106.125045.2936: ClientSetup: Call MachineIdentityManager.GetMachineStatus
[18324] 170106.125046.4463: ClientSetup: Current Machine Join Status: ActiveWithCert
[18324] 170106.125046.4463: ClientSetup: SkipDomainJoin hook is set, skip domain join
[18324] 170106.125046.4463: ClientSetup: Exiting ValidateUserTask.Run
[18324] 170106.125046.4463: ClientSetup: Task with Id=ClientDeploy.ValidateUser has TaskStatus=Success
[18324] 170106.125046.4463: ClientSetup: Task with Id=ClientDeploy.ValidateUser has RebootStatus=NoReboot
[18324] 170106.125046.4463: ClientSetup: Exiting ConnectorWizardForm.RunTasks
[18324] 170106.125046.4463: ClientSetup: Running JoinNetwork Tasks at WizardPage DomainUserCred
[18324] 170106.125046.4463: ClientSetup: SkipDomainJoin hook is set, skip domain join
[18324] 170106.125046.4463: ClientSetup: Entering ConnectorWizardForm.RunTasks
[18324] 170106.125046.4463: ClientSetup: Running Task with Id=ClientDeploy.JoinNetwork
[18324] 170106.125046.4463: ClientSetup: Entering JoinNetworkTask.Run
[18324] 170106.125046.4463: ClientSetup: Network Join Client to Server: ClientComputerName=Amiel-Surface ServerName=ZEKA-SERVER
[18324] 170106.125046.4463: ClientSetup: Maximum amount of joined machines: 50
[18324] 170106.125046.4463: ClientSetup: Current amount of joined machines: 8
[18324] 170106.125046.4463: ClientSetup: Server already contains a computer joined with Client Machine Name
[18324] 170106.125046.4463: ClientSetup: Network Join has not been forced
[18324] 170106.125046.4463: ClientSetup: Network Join will not be Run
[18324] 170106.125046.4463: ClientSetup: Exiting JoinNetworkTask.Run
[18324] 170106.125046.4463: ClientSetup: Task with Id=ClientDeploy.JoinNetwork has TaskStatus=Retry
[18324] 170106.125046.4463: ClientSetup: Task with Id=ClientDeploy.JoinNetwork has RebootStatus=NoReboot
[18324] 170106.125046.4463: ClientSetup: Exiting ConnectorWizardForm.RunTasks
[5884] 170106.125046.4463: ClientSetup: JoinNetwork Tasks returned TaskStatus=Retry
[7732] 170106.125049.3241: ClientSetup: Running JoinNetwork Tasks at WizardPage ComputerAlreadyExists
[7732] 170106.125049.3241: ClientSetup: SkipDomainJoin hook is set, skip domain join
[7732] 170106.125049.3241: ClientSetup: Entering ConnectorWizardForm.RunTasks
[7732] 170106.125049.3241: ClientSetup: Running Task with Id=ClientDeploy.JoinNetwork
[7732] 170106.125049.3241: ClientSetup: Entering JoinNetworkTask.Run
[7732] 170106.125049.3241: ClientSetup: Network Join Client to Server: ClientComputerName=Amiel-Surface ServerName=ZEKA-SERVER
[7732] 170106.125049.3241: ClientSetup: Maximum amount of joined machines: 50
[7732] 170106.125049.3241: ClientSetup: Current amount of joined machines: 8
[7732] 170106.125049.3241: ClientSetup: Server already contains a computer joined with Client Machine Name
[7732] 170106.125049.3241: ClientSetup: Network Join has been forced
[7732] 170106.125049.3241: ClientSetup: Running Network Join
[7732] 170106.125049.3241: ClientSetup: Call MachineIdentity.GetCert
[6536] 170106.125049.4705: IDENTITY: GenerateCSR using the names: Amiel-Surface AMIEL-SURFACE
[7732] 170106.125050.6880: ClientSetup: Exiting JoinNetworkTask.Run
[7732] 170106.125050.6880: ClientSetup: Task with Id=ClientDeploy.JoinNetwork has TaskStatus=Success
[7732] 170106.125050.6880: ClientSetup: Task with Id=ClientDeploy.JoinNetwork has RebootStatus=NoReboot
[7732] 170106.125050.6880: ClientSetup: Exiting ConnectorWizardForm.RunTasks
[5884] 170106.125050.6880: ClientSetup: JoinNetwork Tasks returned TaskStatus=Success
[5884] 170106.125050.6880: ClientSetup: SkipDomainJoin hook is set, skip domain join
[5884] 170106.125050.6880: ClientSetup: SkipDomainJoin hook is set, skip domain join
[9276] 170106.125055.7723: ClientSetup: Running Tasks for Wizard Page ConfiguringComputer
[9276] 170106.125055.7723: ClientSetup: Entering ConnectorWizardForm.RunTasks
[9276] 170106.125055.7723: ClientSetup: Running Task with Id=ClientDeploy.PrepareClient
[9276] 170106.125055.7879: ClientSetup: Entering PrepareClientTask.Run
[9276] 170106.125055.7879: ClientSetup: Ensuring that ServiceName=NetTcpPortSharing is Running
[9276] 170106.125055.8413: WssgCommon: Information: [0] : NetTcpPortSharing is already in the desired state.
[9276] 170106.125055.8413: ClientSetup: Ensuring that ServiceName=SSDPSRV is Running
[9276] 170106.125055.8413: WssgCommon: Information: [0] : SSDPSRV is already in the desired state.
[9276] 170106.125055.8413: ClientSetup: SkipDomainJoin hook is set, skip domain join
[9276] 170106.125055.8413: ClientSetup: Setting ACL of the Log and Data Directory.
[9276] 170106.125055.8568: ClientSetup: Enabling Compression on the Log Directory.
[9276] 170106.125055.9037: ClientSetup: Exiting PrepareClientTask.Run
[9276] 170106.125055.9037: ClientSetup: Task with Id=ClientDeploy.PrepareClient has TaskStatus=Success
[9276] 170106.125055.9037: ClientSetup: Task with Id=ClientDeploy.PrepareClient has RebootStatus=NoReboot
[9276] 170106.125055.9037: ClientSetup: Running Task with Id=ClientDeploy.AddUserRoles
[9276] 170106.125055.9037: ClientSetup: Entering AddUserRolesTask.Run
[9276] 170106.125055.9037: ClientSetup: Exiting AddUserRolesTask.Run
[9276] 170106.125055.9037: ClientSetup: Task with Id=ClientDeploy.AddUserRoles has TaskStatus=Success
[9276] 170106.125055.9037: ClientSetup: Task with Id=ClientDeploy.AddUserRoles has RebootStatus=NoReboot
[9276] 170106.125055.9037: ClientSetup: Running Task with Id=ClientDeploy.ConfigureComputer
[9276] 170106.125055.9037: ClientSetup: Ensuring that ServiceName=ServiceProviderRegistry to be stopped
[18324] 170106.125055.9037: ClientSetup: Ensuring that ServiceName=WseNtfSvc to be stopped
[18324] 170106.125055.9203: WssgCommon: Information: [0] : WseNtfSvc is already in the desired state.
[9276] 170106.125055.9208: WssgCommon: Information: [0] : ServiceProviderRegistry is already in the desired state.
[18324] 170106.125055.9208: ClientSetup: Ensuring that ServiceName=WseNtfSvc to be disabled
[9276] 170106.125055.9208: ClientSetup: Ensuring that ServiceName=ServiceProviderRegistry to be disabled
[18324] 170106.125055.9213: ClientSetup: Ensuring that ServiceName=WseHealthSvc to be stopped
[9276] 170106.125055.9213: ClientSetup: Ensuring that ServiceName=WseClientMgmtSvc to be stopped
[18324] 170106.125055.9218: WssgCommon: Information: [0] : WseHealthSvc is already in the desired state.
[18324] 170106.125055.9218: ClientSetup: Ensuring that ServiceName=WseHealthSvc to be disabled
[9276] 170106.125055.9223: WssgCommon: Information: [0] : WseClientMgmtSvc is already in the desired state.
[9276] 170106.125055.9223: ClientSetup: Ensuring that ServiceName=WseClientMgmtSvc to be disabled
[18324] 170106.125055.9228: ClientSetup: Ensuring that ServiceName=WseClientMonitorSvc to be stopped
[18324] 170106.125055.9233: WssgCommon: Information: [0] : WseClientMonitorSvc is already in the desired state.
[18324] 170106.125055.9233: ClientSetup: Ensuring that ServiceName=WseClientMonitorSvc to be disabled
[9276] 170106.125055.9258: ClientSetup: IsSwitchingToNewServer is false, so skip setting configured once to false
[9276] 170106.125055.9258: ClientSetup: ClientServices.EnsureStarted
[9276] 170106.125055.9415: ClientSetup: Ensuring that ServiceName=ServiceProviderRegistry is DemandStart
[19380] 170106.125055.9415: ClientSetup: Ensuring that ServiceName=WseNtfSvc is DemandStart
[9276] 170106.125055.9415: ClientSetup: Ensuring that ServiceName=WseHealthSvc is DemandStart
[19380] 170106.125055.9415: ClientSetup: Ensuring that ServiceName=WseClientMgmtSvc is DemandStart
[9276] 170106.125055.9415: ClientSetup: Ensuring that ServiceName=WseClientMonitorSvc is DemandStart
[9276] 170106.125055.9415: ClientSetup: Ensuring that ServiceName=WseClientMgmtSvc is Running
[7732] 170106.125055.9415: ClientSetup: Ensuring that ServiceName=WseClientMonitorSvc is Running
[9276] 170106.125100.3286: ClientSetup: Fail to configure the computer, exception: System.AggregateException: One or more errors occurred. ---> Microsoft.WindowsServerSolutions.Common.ServiceNotProgressingException: The service 'WseClientMgmtSvc' failed to start. The exit code was 1067.
   at Microsoft.WindowsServerSolutions.Common.ServiceUtility.NotifyServiceStatusChange(ServiceController svc, ServiceNotifications notifyMask, DateTime utcDeadline)
   at Microsoft.WindowsServerSolutions.Common.ServiceUtility.WaitForMultipleStatus(ServiceController objSvc, DateTime utcDeadline, ServiceControllerStatus[] statusArray)
   at Microsoft.WindowsServerSolutions.Common.ServiceUtility.WaitForStatus(ServiceController objSvc, DateTime utcDeadline, ServiceControllerStatus finalStatus)
   at Microsoft.WindowsServerSolutions.Common.ServiceUtility.ChangeObjectState(Methods method, ServiceController svc, DateTime utcDeadline)
   at Microsoft.WindowsServerSolutions.Common.ServiceUtility.EnsureStarted(ServiceController svc, Int32 timeout)
   at Microsoft.WindowsServerSolutions.Common.ServiceUtility.EnsureStarted(String serviceName, Int32 timeout)
   at System.Threading.Tasks.Parallel.<>c__DisplayClass17_0`1.<ForWorker>b__1()
   at System.Threading.Tasks.Task.InnerInvokeWithArg(Task childTask)
   at System.Threading.Tasks.Task.<>c__DisplayClass176_0.<ExecuteSelfReplicating>b__0(Object )
   --- End of inner exception stack trace ---
   at System.Threading.Tasks.Task.ThrowIfExceptional(Boolean includeTaskCanceledExceptions)
   at System.Threading.Tasks.Task.Wait(Int32 millisecondsTimeout, CancellationToken cancellationToken)
   at System.Threading.Tasks.Parallel.ForWorker[TLocal](Int32 fromInclusive, Int32 toExclusive, ParallelOptions parallelOptions, Action`1 body, Action`2 bodyWithState, Func`4 bodyWithLocal, Func`1 localInit, Action`1 localFinally)
   at System.Threading.Tasks.Parallel.ForEachWorker[TSource,TLocal](IEnumerable`1 source, ParallelOptions parallelOptions, Action`1 body, Action`2 bodyWithState, Action`3 bodyWithStateAndIndex, Func`4 bodyWithStateAndLocal, Func`5 bodyWithEverything, Func`1 localInit, Action`1 localFinally)
   at System.Threading.Tasks.Parallel.ForEach[TSource](IEnumerable`1 source, Action`1 body)
   at Microsoft.WindowsServerSolutions.ClientSetup.ClientServices.<>c.<EnsureStarted>b__1_0()
   at Microsoft.WindowsServerSolutions.ClientSetup.ClientServices.ServiceActionWrapper(Action serviceAction)
   at Microsoft.WindowsServerSolutions.ClientSetup.ClientDeploy.ConfigureComputerTask.Run(WizData data)
---> (Inner Exception #0) Microsoft.WindowsServerSolutions.Common.ServiceNotProgressingException: The service 'WseClientMgmtSvc' failed to start. The exit code was 1067.
   at Microsoft.WindowsServerSolutions.Common.ServiceUtility.NotifyServiceStatusChange(ServiceController svc, ServiceNotifications notifyMask, DateTime utcDeadline)
   at Microsoft.WindowsServerSolutions.Common.ServiceUtility.WaitForMultipleStatus(ServiceController objSvc, DateTime utcDeadline, ServiceControllerStatus[] statusArray)
   at Microsoft.WindowsServerSolutions.Common.ServiceUtility.WaitForStatus(ServiceController objSvc, DateTime utcDeadline, ServiceControllerStatus finalStatus)
   at Microsoft.WindowsServerSolutions.Common.ServiceUtility.ChangeObjectState(Methods method, ServiceController svc, DateTime utcDeadline)
   at Microsoft.WindowsServerSolutions.Common.ServiceUtility.EnsureStarted(ServiceController svc, Int32 timeout)
   at Microsoft.WindowsServerSolutions.Common.ServiceUtility.EnsureStarted(String serviceName, Int32 timeout)
   at System.Threading.Tasks.Parallel.<>c__DisplayClass17_0`1.<ForWorker>b__1()
   at System.Threading.Tasks.Task.InnerInvokeWithArg(Task childTask)
   at System.Threading.Tasks.Task.<>c__DisplayClass176_0.<ExecuteSelfReplicating>b__0(Object )<---

[9276] 170106.125100.3286: ClientSetup: Exiting ConfigureComputerTask.Run()
[5884] 170106.125100.3443: ClientSetup: !!!FATAL!!! Unhandled Exception: System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> Microsoft.WindowsServerSolutions.ClientSetup.ClientSetupException: Unexpected Error occured: DeploymentStage=ConfiguringComputer ---> System.AggregateException: One or more errors occurred. ---> Microsoft.WindowsServerSolutions.Common.ServiceNotProgressingException: The service 'WseClientMgmtSvc' failed to start. The exit code was 1067.
   at Microsoft.WindowsServerSolutions.Common.ServiceUtility.NotifyServiceStatusChange(ServiceController svc, ServiceNotifications notifyMask, DateTime utcDeadline)
   at Microsoft.WindowsServerSolutions.Common.ServiceUtility.WaitForMultipleStatus(ServiceController objSvc, DateTime utcDeadline, ServiceControllerStatus[] statusArray)
   at Microsoft.WindowsServerSolutions.Common.ServiceUtility.WaitForStatus(ServiceController objSvc, DateTime utcDeadline, ServiceControllerStatus finalStatus)
   at Microsoft.WindowsServerSolutions.Common.ServiceUtility.ChangeObjectState(Methods method, ServiceController svc, DateTime utcDeadline)
   at Microsoft.WindowsServerSolutions.Common.ServiceUtility.EnsureStarted(ServiceController svc, Int32 timeout)
   at Microsoft.WindowsServerSolutions.Common.ServiceUtility.EnsureStarted(String serviceName, Int32 timeout)
   at System.Threading.Tasks.Parallel.<>c__DisplayClass17_0`1.<ForWorker>b__1()
   at System.Threading.Tasks.Task.InnerInvokeWithArg(Task childTask)
   at System.Threading.Tasks.Task.<>c__DisplayClass176_0.<ExecuteSelfReplicating>b__0(Object )
   --- End of inner exception stack trace ---
   at Microsoft.WindowsServerSolutions.ClientSetup.ClientDeploy.ConfigureComputerTask.Run(WizData data)
   at Microsoft.WindowsServerSolutions.ClientSetup.ClientDeploy.ConnectorWizardForm.RunTasks(Object sender, DoWorkEventArgs workEventArgs)
   at System.ComponentModel.BackgroundWorker.OnDoWork(DoWorkEventArgs e)
   at System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument)
   --- End of inner exception stack trace ---
   at Microsoft.WindowsServerSolutions.ClientSetup.ClientDeploy.ConnectorWizardForm.<>c__DisplayClass45_0.<m_wizardPageConfiguringComputer_PageEnter>b__2(Object worker, RunWorkerCompletedEventArgs completedEventArgs)
   at System.ComponentModel.BackgroundWorker.OnRunWorkerCompleted(RunWorkerCompletedEventArgs e)
   --- End of inner exception stack trace ---
   at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
   at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments)
   at System.Delegate.DynamicInvokeImpl(Object[] args)
   at System.Windows.Forms.Control.InvokeMarshaledCallbackDo(ThreadMethodEntry tme)
   at System.Windows.Forms.Control.InvokeMarshaledCallbackHelper(Object obj)
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Windows.Forms.Control.InvokeMarshaledCallback(ThreadMethodEntry tme)
   at System.Windows.Forms.Control.InvokeMarshaledCallbacks()
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.DebuggableCallback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
   at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg)
   at System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(IntPtr dwComponentID, Int32 reason, Int32 pvLoopData)
   at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)
   at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)
   at System.Windows.Forms.Form.ShowDialog(IWin32Window owner)
   at Microsoft.WindowsServerSolutions.ClientSetup.ClientDeploy.Program.Main()
[5884] 170106.125147.8885: ServerDiscovery:HostsFileUpdater: Removing hosts file entry: ZEKA-SERVER

Just after installing and whitelisting an SSD in my Sentinel DS5100, my clients stopped backing up. The server reports:

So I dutifully went to Client Computer Backup Tasks and chose Tools: Repair Backups. This allegedly completed properly, reporting:

but one of my clients (this happens to be my personal machine) reports as "Incomplete":

and if I inspect that one machine, I see this:

If I attempt to start a Manual Backup on _any_ of my clients, it fails with that same "Errors in the backup database."

I've repaired the backups 4 times now, and each time it says it's completed the repairs, but backups still don't work.

Hi

This was working fine, until I tried to install a trusted certificate to allow remote web access. Now the default website will not start and the configuration wizard fails. When I try to manually start the default website, I get an error stating that the process cannot access the file because it is being used by another process with HRESULT 0x80070020.

I must get this working quickly as my client cannot access their server based applications.

Any suggestions would be appreciated.

Tony Harvey

I have been having an issue completing the installation of the Connector on my new Surface Pro 4 running Windows 10 Pro. I have been successful installing the same connector on my other laptop running Windows 10 Pro and can't seem to solve this issue on the Surface. Hoping someone here would have some advice.

First off, both the server (Windows Server 2012 R2 Essentials) and the client are current on all updates, except for one on the server (Update for Security Essentials KB3205972, just can't get this to work but I'll work on that another day).

I am able to get to the point where you enter the login and password, then a blue circle runs for a bit and the following error comes up "Cannot connect this computer to the network. The server is not available. Try connecting this computer again.".

I've tried some tips from other posts such as installing KB updates, which were either rejected by the client or server as not being applicable to the system or for already being installed. I've setup a new profile to run the connector install as well which was not successful.

Any help or tips is appreciated.

Thanks.

Update 01/08/2016

Thought that the pending update for Security Essentials might has caused the error after reading similar posts about this issue, so I removed it. Error still persists.