When it asks for User, use your SiteAdmin login even though it says it isn't

Log onto each workstation with its local Administrator account, and run the usual server/connect from browser (make sure they have the same date and time).

You may have to check folder access for users and groups later, when the data is allĥ. You can set up groups now if you use them. Create a SiteAdmin user account with Administrator privileges.Ĭreate any desired data folders other than default and start copying the saved data into them.Īdd all the user accounts in the Dashboard of the new server that you use on the old server. Get it stable and updated and seeing the Internet. But don't ever plug the old server back into this network. Unplug the old server from the network, repower routers and switches, and do setup of the new one on the network (static IP). Any non-default settings such asĭNS Server (and DHCP Server unless your router does that) will need to be recorded and set on the new server.ģ. If QuickBooks, do a backup from within QB (don't use their 'Move my QB to another computer', it is no good). Save all the data you want from the old server somewhere off that server. If user name and password and everything else are the same, and would normally create a new empty profile ('I've lost everything') - but we have a workaround below. Realize that the new server will ignore the existing user account (profile) even

But first: make sure you have the ability to log onto a local Administrator account for each PC.Īnd know the user name and user folder currently in use, since you will need to migrate that profile back to that PC later (use the 'set' command from Command Prompt). In general: System Properties/ Computer Name/ Change/ WORKGROUP).

Remove all of the workstations from the 2012 domain (Look it up.

Windows server essentials 2019