Hi all, 

 We want to rename our SLXQA machine to a different name. We have Full SLX(7.5.2) along with web server and reporting server installed in this machine also with sql server 2008 on the same machine.

 If we rename this machine name. Will this affect our slx application? 

If Yes, Please kindly let me know what are the precautions to take care of 

Thanks,

Mark

Yes it will affect your SLX systems.

1. SLX OLE DB Provider connection repointed. Don't forget to APPLY the edit to the connection and reset the name of the PingServer in the SLX Database SystemInfo table.

2. Data Connections on each machine changed to the SLX OLE DB Provider connection machine.

3. SLX Administrator program, ADMIN user, adjust Windows Authentication webdll user if not using an Active Directory User.

4. make sure websites are pointing at the right machine names.....

5. make sure web deployments are pointing at the right machine names (localhost not an issue of course).

6. Speed Search?

7. Web Reporting?

8. don't forget to check sData (well, you're on 7.5.2 probably not a big deal compared to a 7.5.4 system with SLXMobile deployed).

Basically go through the ENTIRE install check list without actually reinstalling the software.

Hi RJ - hate to disagree but:

1) Changing the connection is enough - it will automatically repoint pingserver. This doesn't need to be done manually.
2) No, the data connection doesn't chnage. The Connection gets it's servername off of the SLX Server (which it knows by ConnMgr) - so this is the SLX Server - not the physical DBServer
3) WinAuth isn't affected (unless this is a DC but then I suspect not)
4) Agreed - and siad this via community post
5) As above
6) Controlled via connname
7) As per community post (scrub the web.config for the name)
8) Agreed

Cheers, Mike!

Actually we're not disagreeing....

If the name of the SLX OLE DB Provider Server (the 'App' Server) changes from MikesServer to AARDVARK you'll have to change every LAN DataLink to point at the new AppServer Name. 500 clients, 500 changes.

And Mike, you've been doing this for 12+ years, if you have a way to change the Data Connection through a non-manual process (i.e. without keyboard or mouse clicks) we are ALL ears. I didn't state you had to change the pingserver name through SQL, and yes, you must manually click on the yes button with that god-awful 2" tall message box which has the new pingserver name automagically changed on the database systeminfo table.  So a couple of mouse clicks to 'non-manually' change the pingserver name. (BTW, mouse clicks are manual in my manual). I've had clients that clicked on YES (that would be manually) and actually converted the Corporate LAN Database pingserver to their LAPTOP.....this while installing a remote client on their laptop. And yes, when they packed up for the night Synch was broken and LAN user's were hosed. (I hope she's long gone and the customer enjoying SFDC at significantly more expense than SLX).

But you still have to change do this manually (i.e. mouse clicks....)

Yep, you are right - I was thinking about leaving the SLXServer in place but swapping out the SQL Server. Doh!

*BUT, to avoid the manual clicks - all of this is in the registry so could have been sent out with "just a few clicks". I'm fairly sure we've not got to Star Trek days yet where it can be done without *ANY* mouse clicks or keyboard clicks But, a forced AD update would have done the trick in your case, rather than manual.