Moving TS server between networks?

Hi all,

We're thinking about moving one of our TS servers (TS501SP1) from one network to another (different physical networks, different domains etc) Has anyone any experience in doing this? What are the key things to consider? How much time does it take?

Thanks in advance,
Hakan

Hakan

Hakan

Find more posts tagged with

Comments

Migrateduser

Is this server a windows server or a unix server? You will most likely need to modify your iw.cfg for most of the things that you need to change. You will also need to regenerate you TS license key with

If this is windows then things get a lot more complicated since changing NT domains adds a whole other layer of complexity. Some of this is made a little easier to deal with in TS5.5.x (since it has tools to change SID mappings in the backing store). The biggest problem would be if the domains that all of your users belong to needs to change at the same time (but again this is only windows).

Other things to look for would be any special preview servers or external database servers that you are using in conjunction with TeamSite (these might need to be adjusted as well). Other things that might need to change would be your OD configurations.

tvaughan

IP Changes can result in end-user confusion. Here's a support site KB about ways to help users if there are any problems with windows after your migration:

Solaris: Users Cannot login After Changing Hostname and ip address on Existing TS Server
Synopsis
The following will show you how to change the hostname & ip address for Solaris and reconfigure TeamSite to recognize the change:
Details
I. Changing the Hostname and ip address on Solaris OS (Solaris 8):

> Run /usr/sbin/sys-unconfig to change the hostname, IP address of the machine. (use DNS and domain where previously no domain and no DNS were declared)

> Reboot system

> For TeamSite (version 5.0.1) modify /etc/iw.cfg, changing the following section keys to the new host name (just hostname - not fully qualifed host name)

[iwcgi]
launchpad_hostname=< hostname>

[teamsite_servlet_ui]
servlet_host=< hostname>

[iwwebd]
host=< hostname>

[iwproxy]
iwproxy_host=< hostname>
customer_webserver_host=< hostname>

After changing the ip address and the hostname of the solaris box, users will *not* be able to login to teamsite anymore, with the following representative error message:

Invalid login: username=john, domain=null, role=master

Note: At this point, running the CLT 'iwauthen' to verify the above master user "john" will report "YES".

II. To complete your reconfiguration of TeamSite, modify openapi.cfg to reflect hostname changes and fix invalid login error.

> Change the following entries in the
< iw-home>/iwopenapi/openapi.cfg file to allow user login:

Access.host: < newhostname>
FileSys.host: < newhostname>
FileSys.shortHost: < newhostname>

> Reboot the TeamSite server - users will now be able to login to TeamSite.

Good luck,
Tom