Nicole, I recently had to do this. You have all the correct reg locations. Make sure that each of the archive servers and clients are restarted. Also, this is important, if any of the clients had their local view installed as "This user only" instead of "All users" then the registry location on the clients are in a different location (Under "HKEY_CURRENT_USER") The best thing to do is run a search in the registry for the old SQL server name and replace it.
Thank you VERY much for the feedback.
We took the old SQL server offline, restarted the services, and rebooted the new server.
I did a search for the IP address through the entire registry to ensure I had them all. (IP addresses are how ours is setup)
I believe that the client was done as "all users" but we did "current user" registry change while we were in there.
Are you getting any messages, errors, any entries in client log, archive server log, or even in Windows Server Application log?
The EPDM Archive and Database server services are using a SQL login name to access the database. Did you make sure you updated these services with a new name and password, or did you make sure to create the same username and same access rights on the new SQL server, as you had on the previous?
We did another dry run last night and turns out that IT was using a SQL login that they didn't realize they were. I was using what they said it was yet that wasn't it.
Thank you all VERY much for your suggestions!!!