SCCS + Web server name change STEPS REQUIRED

[HUGWideBoy]

Symposium server version 5
Symposium web server 4.5

The Symposium server had a name and site change.
System seems to be working routing calls ok.

Now the one thing that wasn't checked, was the symposium web server.

The graphic displays don't work.
Theres references to the old site name.

As usual the few PDF's that nortel allow us to download aren't much help.

Hopfully you guys have an idea...otherwise it's format C: and reinstall time.

And just for todays RANT...."when will Nortel realise that there customer support/help must be the worst in the world...why can't they look at the way cisco, microsoft, Dell look after there customer?"

(granted MS does need lots of support)

 

[spanton]

Ok, Is the web server at the same location? if not then you will need to make sure you switches are setup to forward multicast traffic.

If you sign up on Nortel website take a look for the following doc: 297-2183-117

 

[sandyml]

Here's an excerpt from that NTP that spanton recommended to you. It is pretty detailed, start by going to the Troubleshooting chapter, Application Server section.

Do you need to change the computer name of the application server?
Problem:
You need to change the computer name of the application server, and you need
to know when it is best to do so, and whether there are any special procedures
that you must perform afterward.
Solution:
The tips for changing the computer name and suggested post-change tasks vary
based on the operating system installed on the server (Windows 2000 Server/
Advanced Server or Windows Server 2003).
See the appropriate scenario below for the solution:
You need to change the computer name of a server that is running
on Windows 2000 Server/Advanced Server
If you need to change the computer name that you choose when installing the
operating system, you must only do so before you install Active Directory and
Symposium Web Client.
You cannot change the computer name that you choose during the Windows
2000 Server/Advanced Server installation at a later date without disrupting the
operations of both Symposium Web Client and Active Directory. Both
applications require the computer name to be identified on the network.
When Symposium Web Client runs on a Windows 2000 Server/Advanced Server
platform, the application server must be a domain controller. If you need to
change the computer name after Active Directory and Symposium Web Client
are installed, then you must demote the server from being a domain controller,
and in doing so, you will lose all Active Directory data (Symposium Web Client
data).
You need to change the computer name of a standalone or
coresident server that is running on Windows Server 2003
When you change the computer name on a Windows Server 2003 platform after
you install Symposium Web Client, there are several procedures that you must
perform to reset the name so that Symposium Web Client (and, on coresident
servers, Symposium Call Center Server and TAPI) function properly.
1. On a coresident server, an administrator must run the Symposium Call
Center Server Computer Name Sync utility. For details, see the Symposium
Call Center Server Installation and Maintenance Guide.
2. On either a standalone or coresident application server, an administrator
must reset the IUSR_SWC account to reflect the new computer name. For
details, see “To reset the IUSR_SWC account to reflect a new computer
name” on page 1022.
3. After you change the computer name, some SOAP processes will not
function properly (because they still refer to the old computer name). On
either a standalone or coresident application server, an administrator or
support technician must run the Symposium Web Client ChangeSOAPSrv
utility to reset the SOAP files to reflect the new computer name. For details,
see “To run the ChangeSOAPSrv utility” on page 1053.

Also -- you did not mention whether this is a coresident server or not.

Here is another wording from Nortel's solution site:

Fix:
Run the ChangeSOAPSrv utility to update WSDL files. Refer to the Troubleshooting section in the SWC Installation Guide, publication number: 297-2183-117, which states the following:

When you change the computer name on a Windows Server 2003 platform after you install Symposium Web Client, there are several procedures that you must perform to reset the name so that Symposium Web Client (and, on coresident servers, Symposium Call Center Server and TAPI) function properly.
1. On a coresident server, an administrator must run the Symposium Call Center Server Computer Name Sync utility. For details, see the Symposium
Call Center Server Installation and Maintenance Guide.

2. On either a standalone or coresident application server, an administrator must reset the IUSR_SWC account to reflect the new computer name. For details, see - To reset the IUSR_SWC account to reflect a new computer name - on page 1022.

3. After you change the computer name, some SOAP processes will not function properly (because they still refer to the old computer name). On either a standalone or coresident application server, an administrator or support technician must run the Symposium Web Client ChangeSOAPSrv utility to reset the SOAP files to reflect the new computer name. For details, see - To run the ChangeSOAPSrv utility - on page 1053.

 

[Milesprower]

If the name/ip of the SCCS is all that changed: Follow the post from Sparrow and verify that Multicast is enabled between the two servers. Also, make sure your DNS settings are updated with the new SCCS name and IP. You need to be able to resolve the server name from the IP address and vice versa.

Then, log into SWCS, go to configuration, click on green box next to your server name. On the right side of the window, your server properties will be displayed.

I do not believe you can edit the server name. I think you will have to add a new server. Click on SERVER and ADD SERVER from the drop down menu. Enter the new server name and tab to IP address. The IP should automatically populate if the DNS settings have been updated.

After adding the new server, check things out, especially Access and Partition Management. If all is ok, Delete the old server name.