Moving dynamics from 1 sql 2000 server to another sql 2000 server

[Luvsql]

The steps are pretty straight forwad on article ID 878449. The part that has me very concerned is step 11 where the sql logins are created. It states that if the new server does not have the same name as the old server (which is impossible when the 2 servers are on the same domain) passwords for the users will no longer be valid and they recommend logging in as sa and resetting all the users' passwords.

We have over 50 users! As well, how are the user's database access granted? This script only adds the sql login. We also have 15 companies. If we have to manually reset each password and grant access to each company, I might as well do it all by scratch.

Why is this so difficult? We are running sql 2000 with GP 9. All our other applications are a piece of cake to move over.

 

[RobertC22]

Hello Luvsql,

The sql login has the password encrypted based on the SERVERNAME\INSTANCE contained in the ODBC DSN used to access the database.

In December I had to move our Great Plains database from one server to another.
After migrating the sql logins, I then allocated new passwords (grabbed from a dictionary) for the 400 user accounts. (using sp_password)
In conjunction with the user name, these were mail merged and emailed to each user individually.
When the user then connected for the first time to Great Plains after the move they were prompted for to enter a new password.

As long as the uid is maintained, you do not have to re-grant access to each company. (We have 28 )

Unfortunately, the way Great Plains now wants to encrypt the password and will not accept a password that has not been encrypted the dexterity way before access is granted, you WILL be changing all 50 users passwords.

The script created to 'reset' passwords is now part of the DR (disaster recovery) plan, should the server have to be replaced.
------
Robert

 

[Luvsql]

I used the script from Dynamics' knowledge base article titled "How to transfer an existing Microsoft Dynamics GP...to a new server.." It has a script that captures each user's ID and password which can be run on the new server to recreate them.

I have done so, but the users do not have any databases checked in the security setup. When I restored the databases, the user will be setup as a database user, but they will not be able to login due to the security setup not being linked. I would then have to remove the database user, then mark access to the database. This would take forever with over 50 users and 15 companies.