Announcements
Hello
I will refer to my company as companyb and the company that acquired us as companya.
We have an executive who is pressing us to do a move of Great Plains without adding users into the companyb Great Plains instance. My first question….is this even supported? Make user boorpd = H012345 'old to new.
I was able to accomplish this with limited testing but that doesn't mean it will work. across Great Plains and Management Reporter I updated SY60100, SY01400, SY10550. I also did what would be necessary to replace boorpd to H012345. This was enough to get the user logged into Great Plains. A very limited test.
The problem is there are many tables that contain userid in GP tables. I found roughly 80 tables across Dynamics, Management Reporter an TLI(Our main DB).
Does Microsoft support a process or is there a document that describes such a migration strategy? I suggested adding the new users to companyb which would make the migration a no brainer.
Thanks,
Patrick
Management Reporter uses windows credentials. You will need to install MR on the second server and then add users that match what is on the first server. On the first server you will need to export the MR building blocks and then import these building blocks on the second server. As far as GP goes remember the GP passwords are hashed so you will to set them using GP not SQL.
You should be able to create the user records in the target system and add the companies and add the company access records.
Are there any duplicate users or companies (ie. same ID used in both)?
I can't answer about Management Reporter as I have never used it.... I am a developer (and ex Microsoft Escalation Engineer), but have not implemented or directly supported the accounting side of GP.
The GPPT Portal is http://WinthropDC.com/GPPT Check out the Benefits Presentation.
A current Microsoft Support engineer should be able to clarify the best approach better.
Regards
David
David, thank you for your reply. I will take a look at GP Power Tools. I am not worried about keeping the passwords in sync. As long as I can get on with SA on the destination server, there will be no issues.
My biggest worry here, is updating Dynamics and the company DB. Management Reporter is also in play. I can find all of the tables with userid. What matters most to me is that this would be supported. Are there other tables would need to be updated?
If it is not supported, I would prefer to have that documented and present that to the Business.
Again, thank you for your attention.
I have seen two instances of GP Combined. You can add the company databases from once instance to another instance of the Dynamics Database and restore the company databases into the newly created blank companies.
There is some post processing needed such as updating the Next Note Index in the SY_Company_MSTR table.
Some pre-checks will also be needed to confirm what the account framework (chart of accounts structure in the tables) is. They will need to match to be able to join the systems. See SY003001 and SY00302 tables in the Dynamics DB.
You will also want to confirm that the SQL Collation on the two systems matches.
Regards
David
Thank you for your reply. The executive wants this done with SQL without GP Intervention. I would have to do this in SQL across all of the tables in Dynamics and our company DB. That is the question. Is it supported? We will not have a licensing issue as only one will be live production.
I would suggest running GP Power Tools Database Validation to recreate all the SQL Logins and Database Users once you have updated the GP tables.
This is much more reliable than the CaptureLogins methods as it can create encrypted passwords and even email users with their temporary password to be changed on next login.
You cannot keep the same passwords as the encrypted passwords have the SQL Server ID as part of the encryption algorithm.
Regards
David
Please refer to KB878449 for server move instructions. Some of this is a licensing question. Are you planning on using the same instance of GP on two servers in production? If so, that is not allowed. You will find a CaptureLogins script in this KB. What it will do is create the users on the new SQL instance. You will need to drop those users and create new ones and assign security using GP.
André Arnaud de Cal... 291,359 Super User 2024 Season 2
Martin Dráb 230,370 Most Valuable Professional
nmaenpaa 101,156