Jeremy Davis
Sitecore, C# and web development
I found a fun new variation on the "Windows Server Essentials client can be tricky to install" problems I've had in the past recently. To help me remember for next time, here's the issue I saw this time...
The other day I realised that my home server hadn't sent me it's daily "Health Report" email. Having done the usual simple test of "is the server up?" and "what happens if I reboot it?", I ended up digging through the Event Log and Google to work out what was wrong. In case this happens to me again, or happens to you, here's what I found:
A while back I blogged about some of the issues of having Windows 10 computers using Windows Server Essentials as their backup target. Recently I installed the first major update for Windows 10, and this caused me more issues, which I figured I should document.
Like many people around the internet, I've upgraded my computer to Windows 10 this weekend. So far I'm reasonably happy with the upgrade – most of my stuff has continued to work fine, and the few installation issues I hit were already well documented by the internet community. I will admit to a bit of "who moved my cheese" style frustration at some of the changes though – but I'm sure that will pass as I get used to them...
But I also came across one issue I wasn't expecting which I had a bit more trouble finding the answer to: What happens if your PC was connected to a Windows Server Essentials domain for backup and then you try to upgrade?
