Moving components to different servers

[dbowman]

My 3.5 setup (upgraded from 3.2) is currently running fine on a test environment
One server is hosting web and sql while the lansweeper service is running on a different computer

Now I'm trying to move everything to the production environment, a different server for each componet, but...

1)
I tried to install the service only on a new computer: it asks for the SQL server, I choose the current SQL 2005 test setup, and I get the error "The Lansweeper database is not installed on .. Server!"
This is not true but I understand that probably the name of the database is changed from lansweeper32 to lansweeperdb

How can I overcome this?

2)
I also want to move the current db to the production SQL server. Only problem is that the test environment is SQL 2005 and the production is SQL 2000.
Obviously I could reinstall everything from scratch but I don't want to miss all the gathered data

3)
I still haven't tried but can I foresee any problem in installing the web component alone?
Is there a suggested path for migration (I haven't found any in the forum)

Thanks

[Hemoco]

There are 2 config files:
web.config -> website
lansweeperservice.exe.config -> service

In these files you have a "connectionstring"

If you point these to the database with the correct username/password it should work.

[Hemoco]

1) The database need to exist first.
You can detach the database and attach again using a different name.
2) I don't think you can downgrade your database from 2005 to 2000
3) to install the service and website you need a working database lansweeperdb to point to first.

[dbowman]

Lansweeper wrote:
1) The database need to exist first.
You can detach the database and attach again using a different name.

I originally discarded this solution because I thought this could be a problem for the application (web or service). I guess that the db name is stored under some configuration file (maybe web.config).
Are you confirming that the db name is not referenced anywhere?

My guess is that your solution works if you move everything at the same time: if you change the db name and later you only move the application then the web service is not working anymore until you reinstall it on the final server since it loses the reference to the db

Thanks