• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 415
  • Last Modified:

Dynamics v8 transfer to another server

I have a problem with an "old" server that is dying. Windows Server SBS 2003, Dynamics 8, SQL 2000. We DO NOT have any money to go out and buy all new software and hardware. However when we bought these Dell 2800's we got two of them--one for production and another for a hardware backup, After 10 years we will hope to get a use of the backup. So my question is if I install Server 2003 SBS and then install Dynamics and SQL can I then "simply" copy the Dynamics install from the old server to the new install? If I  setup SQL to store the databases in the same place so that when Dynamics starts it is setup on the "same" hardware albeit it different hardware, will that work? Or is the Dynamics install much too complicated to do it like this? Or will have I have to export registry settings and/or something else to get this functioning. We do not have the money to hire a Dynamics expert to do this transfer for us, so I was hoping this "simple" process might work--will it? Thanks!
0
Lionel MM
Asked:
Lionel MM
  • 4
  • 2
1 Solution
 
Chinmay PatelEnterprise ArchitectCommented:
Hi lionelmm,

I don't think that will work.  I am not  an expert in this area so you might want to wait for other experts to  respond.

Regards,
Chinmay.
0
 
Lionel MMSmall Business IT ConsultantAuthor Commented:
Thank you.
0
 
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
This seems to have been posted quite a long time ago, but thought I'd respond anyhow.

If you are going to move your exact installation to another identical server then you can simply backup and restore.  The easiest way to do this would be to use a full image backup such as Acronis, but the built-in SBS backup should do the trick.

Just follow the documentation:
http://www.microsoft.com/en-us/download/details.aspx?id=1215

Jeff
TechSoEasy
0
Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

 
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
I would point out that all of your software is beyond the general support life-cycle, so you will really be stuck should you have any problems in the future.  Best to get it upgraded, or look at alternative cloud-based solutions which do not require such a large investment.

Jeff
TechSoEasy
0
 
Lionel MMSmall Business IT ConsultantAuthor Commented:
Thanks for that but in the question I did note that we do not have any money for this--we have to make do with what we have, and cannot upgrade--even to cloud based solution. Worst case we will do a ASR to the backup server--that will be our fail back, last option solution but since we are going to do this I wanted to do a fresh install of Windows Server and then of SQL and then of Dynamics. After 10 years of use all operating systems have their issues and so I wanted to find out how best to proceed to move an existing SQL/Dynamics from one server to another. Since posting this Q I have found several helpful postings and it is possible--do you have any experience doing this? I have actually started the process, having put together a server of spare parts for testing purposes and have SQL in the same sate as the old server, same updates, same service packs--first requirement. Next is to create databases in the same order as the original--trying to find out that order from their IDs--stuck here for now.
0
 
Lionel MMSmall Business IT ConsultantAuthor Commented:
After much searching I found this and it works--these are just the basic outlines, there are details and links to other resources missing because it is so much. Not easy to do but possible, MS Dynamics Customer Source Support
How to transfer an existing Microsoft Dynamics GP, Microsoft Small Business Financials, or Microsoft Small Business Manager installation to a new server that is running Microsoft SQL Server
1.      On the old server, copy the following Capture_Logins.sql script to the local hard disk. Click the following link to obtain the Capture_Logins.sql script:
2.      On the old server, run the Capture_Logins.sql script to capture all SQL Server logins and password information.
3.      Make a full backup of the DYNAMICS database and all company databases on the old server.
4.      On the old server, generate a SQL script for each SQL Server Agent Job that is currently scheduled and for each SQL Server Agent Operator that is currently set up.
5.      In Windows Explorer, copy the SQLLOGINS.sql script that you created in step 2, the backup files that you created in step 3, and the SQL Server Agent Job and SQL Server Agent Operator scripts that you created in step 4 from the old server to the hard disk on the new server.
6.      Install SQL Server on the new server if it is not already installed.
Notes Make sure that you use the same sort order that was used on the old server. To obtain the sort order that was used on the old server, run the following script against the master database in the SQL Server Management Studio, in Query Analyzer, or in the Support Administrator Console:
7.      On the new server, restore the DYNAMICS database from the backup file that you created in step 3. Follow these steps, based on the SQL Server tools that you use.
8.      Repeat step 7 for each company database.
9.      Create an Open Database Connectivity (ODBC) connection at the new server and at all client workstations that use the financial application.
10.      On the new computer, install a Server and Client installation of the financial application. Then, install any third-party products or additional products that you use on the new server. Verify that the third-party and additional products are functional.
11.      Run the SQLLOGINS.sql script that you created in step 2 to create all the SQL Server logins. You can use SQL Server Management Studio or Query Analyzer to run the script.
12.      Run the scripts that you created in step 4 to create the SQL Server Agent jobs and the SQL Server Agent Operators on the new server.
13.      Obtain the Dex_Req.sql script and the Grant.sql script, and then run the scripts.
14.      Run the following script against each financial application database to set the database owner to DYNSA.
15.      If the Reports and Forms dictionary files are shared on the old server, copy the files to the new server.
16.      If the OLE Notes files are shared on the old server, copy the files to the new server.
17.      If the Automatic Updates feature has been used and has entries that point to a share on the old server, the files must be copied to a share on the new server. The entries in the SYUPDATE table in the System DYNAMICS database needed to be adjusted.
18.      If you're moving your Microsoft Dynamics GP 2010 databases and you use the drilldown functionality in the SQL Server Reporting Services or Excel integrated reports you need to do the following to update your server links so the drilldowns work after the server move--NA
0
 
Lionel MMSmall Business IT ConsultantAuthor Commented:
Did not get any help from anyone on this question--I had to find the answer myself.
0

Featured Post

Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 4
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now