tinkererguy

FYI, that DNS thing might haunt you again, since a service called "Windows Server LAN Configuration" is running that might get you back into a pickle. See my write up about this with details on disabling the service here:

Windows Server 2012 Essentials remote client loses its Internet connection, here’s your DNS-related fix

Interesting article:
http://support.micro...5?wa=wsignin1.0

Excerpt below:

Update adds Windows 8 and Windows Server 2012 support to Forefront Endpoint Protection 2010 clients

Article ID: 2758685

 

This article describes an update that adds Microsoft Forefront Endpoint Protection 2010 client support to Windows 8 and Windows Server 2012.

After you install this update, you can install the Forefront Endpoint Protection 2010 client on a computer that is running Windows 8 or Windows Server 2012.

So far, so good, removal of the Domain went well, and it sure isn't looking very hack-like, which could be good, now with screenshots added:
http://tinkertry.com...domain-removal/

Next up is testing for any side-effects.  But if this all works out, then moving data from old WHS2011 to new WS2012E should be as simple as copying folders from old shares to new shares, just like I did when moving from WHSv1 to WHS2011.

As Chris Courney kindly pointed out to me during the recent Google Hangout:
http://tinkertry.com...e-spaces-media/
removing the client from the domain and putting it back on the workgroup seems to work just fine, no side effects, able to login to the Dashboard as well.  After a reboot, autologin could be set with netplwiz.exe again, and backups proceeded as usual.

Next steps, recording a sweet and simple video showing all this.  But yeah, things are looking good, the overhead of managing a domain (painful for VPN/ certificate stuff for Direct Access (VPN)
http://blogs.technet...what-s-new.aspx
is on the sysadmin of the home server.

But at least it looks like none of that will be visible to the backup clients in any meaningful way.  Well, they may notice their CPU spike as a backup finishes very quickly ;-)
(whereas WHS2011 plodded along with >5% of CPU and disk resources, but also took forever).

New, related article out now:
http://www.winsupers...ver-2012-143644
which ends like this:

Looking ahead, there are some other questions. For example, although last week’s announcement included no mention of Storage Server, I’m told that this product line will continue forward in some capacity (ahem), perhaps with a 2012-based follow-up to Storage Server Essentials.
More soon.