When working through the connector software - having already set up "Michael Smith" as an account on the Win 2012 server with the Domain-name "HomeServer", my local account is now converted to "HomeServer.Michael Smith" or "Michael Smith.Homeserver", with a separate entry under the local boot-disk folder "Users".īut I need to know how I can migrate everything from my local account to the new domain account. In other words, I started out with a local account - call it "Michael Smith" with the password "BonzaiDuck". But how do I migrate my desktop, settings and everything else to the new account? Now I can go forward again, and get this client workstation PC to rejoin the Domain. I was in a panic about this, so (praise Jee-sus) I have a great backup system on the Win 10 flagship system, and I restored the boot drive to what it was this morning.
Now I've figured out how to install the connector so that my local account name and password are used in the domain, but it creates a new desktop as if this were a new 'local" account. So installing the server connector software on the flagship gives me access to all the files on the server alright, but the system doesn't back up to the server as the others do. And when I finally upgraded one of our Win 7 systems to Win 10 so that it absorbed my software and settings and desktop and everything else, it too was being backed up - but my original Win 10 flagship system would never back up successfully.Ī little investigation helped me discover that the laptop and the formerly Win 7 system upgraded to Win 10 were somehow configured under a domain, while my sig system was still set up with a local account in "Workgroup" mode.
So when I acquired a new laptop last summer, I was mystified and confused how it just joined our network so easily and was being backed up by our server. I DIDN'T have TIME to troubleshoot this, as I took over caring form my 97-year-old Moms five years ago.
Now I've discovered why Win 2012 was backing up our Windows 7 computers just fine, but wouldn't back up my Windows 10 flagship system. Someone discovered a simple hack so you could access your server without joining its domain. Win 2012 R2 wants your computers to be in a Domain, and many of us hesitated. We had always organized our home computer systems in the WORKGROUP paradigm, then "Home Group" under Win Svr 2011. The last server I built was configured with Windows 2012 Essentials R2, upgrading from Windows Home Server 2011. I've fallen behind in my reading, because I have big burdens at home. Somebody should know the answer to my question.