My company is running SBS2008/SBS2011/Essentials, but it has grown to the point where this no longer meets our needs (We have too many employees!) and/or the software is going out of extended support. What is the migration path off of SBS/Essentials?
I'm setting up Windows Server 2012 R2 Essentials for the first time. I'm able to backup a test client which runs Windows 7 Ultimate. All available Microsoft Updates have been applied to both client and server.
When I attempt to restore from a backup using the Windows Server Essentials Dashboard on the client machine I get an error stating the restore has stopped working.
I'm also seeing two errors in the event log.
Error #1
Application: MountBackupWizard.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: Microsoft.WindowsServerSolutions.DataProtection.PCBackup.ObjectModel.PCBackupClientProviderException
Server stack trace:
at Microsoft.WindowsServerSolutions.DataProtection.PCBackup.ObjectModel.PCBackupClientManager.CallSyncOperation(Action`1 operation)
at Microsoft.WindowsServerSolutions.DataProtection.PCBackup.ObjectModel.PCBackupClientManager.StartMountBackup(String user, Byte[] password, String machineSid, Int32 jobIndex, Guid volumeGuid)
at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Object[]& outArgs)
at System.Runtime.Remoting.Messaging.StackBuilderSink.AsyncProcessMessage(IMessage msg, IMessageSink replySink)
at System.Runtime.Remoting.Proxies.RealProxy.EndInvokeHelper(System.Runtime.Remoting.Messaging.Message, Boolean)
at System.Runtime.Remoting.Proxies.RemotingProxy.Invoke(System.Object, System.Runtime.Remoting.Proxies.MessageData ByRef)
at Microsoft.WindowsServerSolutions.DataProtection.PCBackup.ObjectModel.PCBackupClientManager+StartMountBackupWorkerEventHandler.EndInvoke(System.IAsyncResult)
at Microsoft.WindowsServerSolutions.DataProtection.PCBackup.ObjectModel.PCBackupClientManager.StartMountBackupAsyncDone(System.IAsyncResult)
Exception Info: System.Reflection.TargetInvocationException
at Microsoft.WindowsServerSolutions.DataProtection.UI.MountBackupWizard.backupClientManager_StartMountBackupAsyncCompleted(System.Object, System.ComponentModel.AsyncCompletedEventArgs)
at Microsoft.WindowsServerSolutions.DataProtection.PCBackup.ObjectModel.PCBackupClientManager+<>c__DisplayClass2f.<StartMountBackupAsyncDone>b__2e(System.Object)
Exception Info: System.Reflection.TargetInvocationException
at System.RuntimeMethodHandle.InvokeMethod(System.Object, System.Object[], System.Signature, Boolean)
at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(System.Object, System.Object[], System.Object[])
at System.Delegate.DynamicInvokeImpl(System.Object[])
at System.Windows.Forms.Control.InvokeMarshaledCallbackDo(ThreadMethodEntry)
at System.Windows.Forms.Control.InvokeMarshaledCallbackHelper(System.Object)
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
at System.Windows.Forms.Control.InvokeMarshaledCallback(ThreadMethodEntry)
at System.Windows.Forms.Control.InvokeMarshaledCallbacks()
at System.Windows.Forms.Control.WndProc(System.Windows.Forms.Message ByRef)
at System.Windows.Forms.Control+ControlNativeWindow.OnMessage(System.Windows.Forms.Message ByRef)
at System.Windows.Forms.Control+ControlNativeWindow.WndProc(System.Windows.Forms.Message ByRef)
at System.Windows.Forms.NativeWindow.DebuggableCallback(IntPtr, Int32, IntPtr, IntPtr)
at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG ByRef)
at System.Windows.Forms.Application+ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(IntPtr, Int32, Int32)
at System.Windows.Forms.Application+ThreadContext.RunMessageLoopInner(Int32, System.Windows.Forms.ApplicationContext)
at System.Windows.Forms.Application+ThreadContext.RunMessageLoop(Int32, System.Windows.Forms.ApplicationContext)
at System.Windows.Forms.Application.Run(System.Windows.Forms.Form)
at Microsoft.WindowsServerSolutions.DataProtection.UI.Program.Main(System.String[])
Error #2
Faulting application name: MountBackupWizard.exe, version: 6.3.9600.16384, time stamp: 0x52156f60
Faulting module name: KERNELBASE.dll, version: 6.1.7601.23392, time stamp: 0x56eb2fb9
Exception code: 0xe0434352
Fault offset: 0x0000845d
Faulting process id: 0xbfc
Faulting application start time: 0x01d1bcf8214eedba
Faulting application path: C:\Windows\System32\Essentials\MountBackupWizard.exe
Faulting module path: C:\Windows\system32\KERNELBASE.dll
Report Id: 658061e9-28eb-11e6-85e2-00155da01813
I found some old reports from last year stating windows update KB3023562 was the problem, but there was no change after uninstalling the patch. I also tried turning off the firewall on the client and server, but that changed nothing. I have done a repair on the backup database and no errors were found.
I've never successfully mounted a backup, so I'm not sure what the problem could be.
A time ago i had to configure a W2012 R2 essentials server with storage spaces and 2 virtual disks. As the real disk count and the disks itself where not final at that time, i had to resort to the powershell way of configuring the virtual disks. The purpose was to create 2 virtual disks, one with parity and 3 columns, and one with a mirror layout (no special requirements - created with server manager), both thin provisioned.
In the final setup there would be 5 disks 2*8T, 1*4T and 2*3T. At the time of creating the first virtual disk, the 2*8T, 1*4T and 3 other disks (smaller disks that should be removed later) where available.
Because i thought i knew that 3 columns would give me the largest space (2* the 8T and the 3rd the rest of the disks), i specified the powershell command to use 3 columns and the 3 first disks to use (default storage spaces would use as many columns as it possibly can, which would restrict expanding later - more disks to add before picking up).
Everything seemed to work fine, however after removing the smaller disks and adding the 2*3T disks, they where picked up by the mirror virtual disk, but not by the parity virtual disk.
As a side note, i have another W2012 R2 server where a similar setup is made, but the 3 column parity disk was created (by the default tools - not powershell) when there where only 3 disks in the pool (2 larger and 1 small disk). I added later 1 extra disk, which was directly picked up by the virtual disk expanding its space significantly.
The questions:
What is limiting the usage of the 2 3T disks in the virtual disk, is it because the virtual disk was created by the powershell command specifying the 3 disks at that moment to use, or is it because i need another disk to fulfill the 3 column constraint (note the previous paragraph where this seems not the case)?
Are there powershell commands or other tools that can solve my problem (if it is possible without recreating the disk) to get a 3 column parity disk with each column at least 8T (8T - 8T - 4+3+3T)?
Edit 20160606: I did some other tests creating a new virtual disk in powershell with 3 columns, without specifying the disks to use, and as I expected the software dit not choose wisely regarding future expansion: it selected the 2 smallest disks and one of the larger disks probably limiting the expansion later on with the available disks (I could replace disks, but enclosure space and available Sata ports are the current limits to the amount of disks that can be connected)
When a Client Backup starts on my 2012 Server Essentials, it fails and I receive the following error in my System log:
Logical drive 1 of array controller B120i [Embedded] returned a fatal error during
a read/write request from/to the volume.
Logical block address 3573083600, block count 248 and command 32 were taken from the
failed logical I/O request.
Array controller B120i [Embedded] is also reporting that the last physical drive to report
a fatal error condition (associated with this logical request), is located
in bay 0 of box 0 connected to port ??.
The message is cryptic as it doesn't seem to know which physical drive the problem is on.
A disk did recently fail in my RAID 1 setup(Two 2TB Disks), but I replaced it and it rebuilt absolutely fine.
Every diagnostic I have run on the disk come back fine. I have used "HP Smart Array Configuration Utility", "HP Array Diagnostics and SmartSSD Wear Gauge Utility", and the "HP Insight Diagnostics Utility", all of them report both drives as being healthy. Yet windows still reports bad blocks when trying to run a Client Backup.
Is there anything else I can do resolve this issue(or at least tracking down where the issue is)?
I'm setting up some brand new Dell laptops that have come with Windows 10 Pro preinstalled. I need to connect them to a server that is running Windows Server 2012 R2 Essentials.
From what I can make out online, Windows 10 has been supported since about November 2015 and I should just proceed as normal, by pointing the client's browser to http://server-address/connect
The connector wizard loads and asks me for my username and password, then after a bit of a delay says
An unexpected error has occurred
Right, very helpful, thanks Microsoft ;-)
I've spent maybe a couple of hours googling and found a lot of out-of-date stuff about manually installing the connector; I think that advice is obsolete now.
What's the knack to getting this to work?