The requirements for the CPU stated in Terry's book can be checked by running Sysinternals 'coreinfo' which is a free download from MS TechNet.
I used this to check my own server hardware before I made the move from WHS2011 to Windows 10. In my own (and admittedly limited) experience hardware performs slightly better with Windows 10 than with WHS2011.
Well, I have finally bitten the bullet and started to decommission my WHS V1 server. It's a bit sad really as WHS has served me well for a number of years just sitting in the corner quietly doing it's thing. But the inability to recognise drives larger than 2TB and it's inability to backup the more recent OSes, while not an issue now as my PCs are still all Win7, will become a problem in the foreseeable future.
So, with a heavy heart I have commenced building the replacement.
Due to cost considerations, I have decide to go with Win10 as the replacement. Running the OS on a SSD and using a pool of HDDs for data storage.
I wanted as much as possible to emulate the functionality of WHS, so I am using StableBit Drive Pool to pool the disks and run file duplication, and Veeam Endpoint to back up my clients on a regular basis.
There is a small app offered on the Veeam forums that one of their users developed to report on backup success/failure, so I will be playing with that to keep tabs on the backups.
I've just commenced putting this together, so I'll let you know how it goes.
Windows 10 clients are updated.
I ran chkdsk on SSD boot drives (errors fixed - this seems to be a reoccurring problem that may be related)
I ran SFC /scannow to fix and windows issues.
WSE dashboard see's clients as offline and reports Windows updates needed and restart needed. I've done both.
No client backups for 55 days now. Not good.
ncarty & Shidoshi,
I am planning on doing the same thing (no domain setup) with my setup. I have one question though. If I do join my clients to the domain, can they log back onto their local accounts if they choose to?