I have the Server portion of the software installed on a server. I want to install that server portion on another server. The client is running on a different server and that's staying the same. So I just need to install the server side software of SalesLogix. Is there a trick to this or any crazy configuration? Thanks!

Can you give a little detail what the end result of having two SLX servers is?  Is one production and the other for testing/development?

John

I just wish to have it on one server. Once it's on the new server I am removing the current server.

And you have only 1 client? Is this a Citrix install?

I don't know the environment and this might not matter.  Is the database sitting on a different server altogether?

I think all you need to do once the new server is completed is disconnect the old server from the network to prevent any issue.  Then open the Connection Manager on the new server and create the connection(s) to the database either named the same or new names.  I'm not sure if using the same name as was used on the old server will cause an issue, but changing the name will definitely required the client to be reconfigured for the new connection.  If you have just one client then this really isn't a problem.  If there are multiple clients then a new name will definitely require more time and inconvience.

John

The Client is not moving. there is one client and it's all good. Just moving the Server-side software. I'm going to move it to the server that also hosts the SQL db. The current Server software is on it's own server. So yeah, all I want to do is install the SLX Server software on the same box as the SQL db. then I will shut down the existing SLX Server. So I am just trying to find out what configuring I'll need to do. THANKS SO MUCH EVERYONE. 

Quote: Originally posted by John Gundrum I don't know the environment and this might not matter.  Is the database sitting on a different server altogether? I think all you need to do once the new server is completed is disconnect the old server from the network to prevent any issue.  Then open the Connection Manager on the new server and create the connection(s) to the database either named the same or new names.  I'm not sure if using the same name as was used on the old server will cause an issue, but changing the name will definitely required the client to be reconfigured for the new connection.  If you have just one client then this really isn't a problem.  If there are multiple clients then a new name will definitely require more time and inconvience. John

Hmm, there's more to it than that. The documents and library files need to be moved - and new logging paths set on the new server. I'm assuming there's no sync, given that there's one client.

Any other systems which access SLX via the SLXOLEDB provider will need to be reconfigured. Any integration with any other systems needs to be looked at, just to check.

The documents are already residing on the client server. So that's good to go.

I was going on just the SalesLogix server application being moved.  Not the sync folders.  Not knowing the environment doesn't lend itself well to complete answers.

I believe there is some terminology issues happening here.  Please describe what a "client server" is?  To me "client" and "server" are two different animals not used to describe a single entity.  A "client" is used to describe a user who runs the SLX "client" application.  A "server" is the box (or boxes) that reside in a data center.  The "client" accesses "servers" for data in support of the application.

Where is the Sync Logs folder located?

John

Hi. Client. I said Client Server cuz it's a terminal Server. But we can just refer to client as client. My bad.

So yeah, client is good to go. Sync Docuemnts Folder is on the Client box.

I just wanna move SLX Server to a new server and was hoping there wasn't some crazy config.

Mike

Yeah! Turned out to be an easier job than expected. Our Sync Docs were already on the Client so that didn't have to change. So we just installed express server on a new box and used the Configuration Manager and it found it. We powered the other one down and it's all good. Thanks for all the answers.