Hello,
We are having a new GP 2013 server set up and eventually it will be moved from one vSphere cluster to another vSphere cluster.
This entails a new internal IP address and a completely new domain.
I believe I can keep the sql service account name the same.
Are there any other gotchas or issues to watch for vis-a-vis Great Plains OR SQL Server??
Thank you, Tom
*This post is locked for comments
The workstations per se aren't moving -- the client will get re-installed to a new RDSH setup and told to connect to the newly moved server...that should not be any issue. Thanks again for all your help.
Thank you, Tom
As long as all you are doing is moving that virtual image from one domain to another you should be all set. Are the workstations moving as well? As long as they can see the SQL instance you should be fine.
Thanks again Richard...Yes, I know the domain admin account used to install SQL, since I did this install.
I can look up that domain admin account's current properties (sysadmin, dbo, etc.) and reproduce them after the server is moved.
The consultant can get MS support to help out if necessary, so everything here is a good start.
Thank you again, Tom
Do you know when SQL was installed of the domain admin account was added to SQL? If not, once the move is complete, you can go into SSMS and make the new domain admin account a sysadmin in SQL or whatever service account you chose. You do not assign domain accounts to sql login accounts. Since you are using mixed mode SQL authentication you will have your SQL accounts created by GP and then whatever domain accounts you add to SQL.
Hi Richard...
Only one domain account is used for all the SQL Services -- greatpains@domain.local..
We should be good to go by making a new account with the same name in the new domain and re-assigning it?? -- what SQL login accounts must the domain account be assigned to?? (it's done automatically I think, I don't think I've even done it manually...)
Thank you, Tom
The biggest 'gotcha' I see here will be the service accounts you are using to start the SQL Services. These accounts will now be part of a new domain and will need to be assigned to the login accounts used to start these services. If the server name will be staying the same you should not need to worry about the GP passwords since the SQL instance name will be remaining the same.
It doesn't exactly help. The *entire* virtual server containing GP 2013 AND SQL Server 2012/14 will be moved to new IP and domain.
It's not moving GP to a new SQL Server I'm asking about, it's moving the complete virtual server which already contains GP and SQL.
Thank you, Tom
Please follow the instructions mentioned from below Microsoft KB article.
support.microsoft.com/.../878449
Hope this helps!!!
#1
André Arnaud de Cal...
292,516
Super User 2025 Season 1
#2
Martin Dráb
231,399
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (
