Web Client Installation - Missing Options...

[98Converter]

I've installed the Web Client R3 on a W2K3 Server running IIS6.0. But I don't have these (2) components:

Modular Messaging Web Client Users gain access to this interface by logging on to their
mailboxes through the URL for the Web Client server:

Modular Messaging Web Client Administration and Maintenance tools
Administrators use this interface to configure and maintain the Web Client server. For
more information about this interface, see Completing initial administration on page 24, the
online Help system contained within the administration interface, or Modular Messaging
Web Client Administration and Maintenance on the Modular Messaging Web Client
software CD-ROM.

When I do a start programs Avaya MM Web Client Tools, the only things listed are:

Connectivity
Install Verify Test - Ivy
MMLogViewer
Reset Web Server
Start Web Server
Stop Web Server

Should I see the other options??? If not, how do I add the MSS and MAS servers...?

Thanks,
CJH
S8720
MM 3.0
MSS/MAS



We are what we repeatedly do. Excellence, then, is not an act but a habit. ARISTOTLE 384-322 B.C.

 

[twix79]

You do the administration through the web. For admin go to

http://yourwebserverIPaddress/webmsg/admin.

I think the login is "admin" and password is "admin1". Once you have done that, go to

http://yourwebserverIPaddress/webmsg/scripts/start.asp

to log into your mailbox.

 

[KenMeans]

you need to setup the web service. go to servername/webmsg/admin

The pasword is admin and admin1 then add the mss in as the message store.

Then just go to servername/webmsg and it wiill ask you for the mb number and password.

Ken Means

http://www.tel-is.com

"I find that the harder I work, the more luck I seem to have."
- Thomas Jefferson (1743-1826)

 

[98Converter]

I've tried that - but the page doesn't load. Our web admin looked at the server, and mentioned it looks correct. He can get it to run as it's own webpage, using different ports, but the Admin Features are not available.

More news to follow early in the week.

Thanks,
CJH


We are what we repeatedly do. Excellence, then, is not an act but a habit. ARISTOTLE 384-322 B.C.

 

[KenMeans]

Have you installed the patch for the web server? And i assume you loaded this on a non mas server so how did you install the software? using the customer povided server instructions or other?

Ken Means

http://www.tel-is.com

"I find that the harder I work, the more luck I seem to have."
- Thomas Jefferson (1743-1826)

 

[98Converter]

I installed it on a stand-alone W2K3 box from the CD Modular Messaging Web Client Release 3 Disk 1 of 1 (CD). I did not install a patch? Which patch is that?

Thanks,
CJH

We are what we repeatedly do. Excellence, then, is not an act but a habit. ARISTOTLE 384-322 B.C.

 

[KenMeans]

INTRODUCTION

There is a new version (3.0.0.43) of the Modular Messaging (MM) 3.0 Web Client Server available for download.

In this version of the Web Client, the following issues are resolved:

* If there are multiple subscribers with the same last four digits of the numeric address, sometimes, the wrong name is displayed.
* A Web Client memory leak causes IIS to reset and reduces the number of supported sessions to 500. NOTE: With this version, 3.0.0.43, 1000 sessions are supported.
* New Message Notification is being displayed when a user logs in to the Web Client
* When a message is addressed to a networked machine, an error of "invalid address" could be received even though the address is valid.

The MM Web Client Server supports access to client mailboxes on the MSS. The server provides this access through the corporate LAN. The Web Client also supports access to messages stored on an email server that is compatible with IMAP4.

The Web Client can reside on the same server as the one being used for Web Subscriber Options. However, the Web Client cannot be installed on an MAS.

Information on the hardware and software requirements for the Web Client Server can be found in "Chapter 2: Perquisites" of the "Avaya Modular Messaging Web Client Release 3 Server Installation and Upgrades" document.

The Web Client Server zip file can be downloaded, extracted and copied to a CD.

Additionally, the Web Client Server zip file can be downloaded, extracted and copied to the Web Client Server. To begin the installation if the files are copied directly to the Web Client Server, open the DEFAULT.HTM file.

The installation instructions can be found in the "Avaya Modular Messaging Web Client Release 3 Server Installation and Upgrades" document.
The document can be found on support.avaya.com and is also included in the Documents directory in the zip file.

BASE RELEASE

This software update is only intended to be installed against the following release(s) of Modular Messaging Web Client:

* MM Web Client 3.0

CHANGES SPECIFIC TO THIS SOFTWARE UPDATE

For detailed information on the changes included in this version and the known issues please refer to the Release Notes - Release Notes for Modular Messaging 3.0 Web Client Server - 3.0.0.43

To download version 3.0.0.43 select the Download link.
The download file size is 51.4 MB.

Visit the Download Center to download the software.

Ken Means

http://www.tel-is.com

"I find that the harder I work, the more luck I seem to have."
- Thomas Jefferson (1743-1826)

 

[KenMeans]

You may want to try using port 82 i think it said something about that but i can't find it right now. But the more i think about it i think that was to talk to the MAS's. Also i assume you are using an MSS right?

Ken Means

http://www.tel-is.com

"I find that the harder I work, the more luck I seem to have."
- Thomas Jefferson (1743-1826)

 

[twix79]

I know that when I originally installed the web client on the Win2k3 server, by default our IIS was set up to not serve certain types of files, ASP being one of them. You may need to make some configuration changes if you are able to view some pages but not others. I don't remember all of the specific entries, but your web admin should be able to help with that.

 

[KenMeans]

Installing Web Client server software
Note:
Note: If you have a previous version of Modular Messaging Web Client installed on a
server and want to upgrade to Web Client Release 3, follow the procedures in
Chapter 4: Upgrades on page 29.
To start the installation:
1. Insert the Modular Messaging Web Client software CD-ROM into your server. The system
displays a screen with the following options:
? Avaya Modular Messaging Web Client 3.0 Install. Use this option for installing the
Web Client Release 3 software. Go to Step 2 of this procedure.
? Uninstall Avaya Modular Messaging Web Client 3.0 (Data will be retained). Use
this option when you want to uninstall the the server software but retain the directory of
administered Web Client data. For more information, see Uninstalling Web Client
server software on page 26.
? Remove Avaya Modular Messaging Web Client 3.0 (All data will be lost). Use this
option when you want to remove the server software and the directory of administered
Web Client data. For more information, see Removing Web Client server software on
page 27.
? Avaya Modular Messaging Web Client 3.0 Installation Guide (Requires Adobe
Acrobat Reader). Use this option to view this installation guide.
? Avaya Modular Messaging Web Client 3.0 Administration Guide (Requires
Adobe Acrobat Reader). Use this option to view information about administering the
Chapter 3: Installation
20 Web Client for Modular Messaging Release 3 Server Installation and Upgrades April 2006
Web Client server. For more information, see Completing initial administration on
page 24.
Note:
Note: If the Autorun does not run, browse to the setup.exe file on the CD-ROM and
double-click the file.
2. Select Avaya Modular Messaging Web Client 3.0 Install.
The rest of the installation process is described in the following table. In this table, each row
relates to a particular dialog box you see as the installation progresses. The information in each
row describes how to complete the fields in that dialog box and then proceed to the next dialog
box.
Use the following table to complete the Install dialog boxes.
Dialog box Required action Notes
Read Me file Click Continue. ???
Avaya Modular
Messaging Web Client
Installation (Welcome
dialog box)
Click Next. ???
Software License
Agreement
Click I Agree. ???
Modular Messaging
Web Client Installation
(Tell Me About dialog
box)
1. Review any topics of interest.
2. In the body of the dialog box,
click Next.
3. Select Continue With Install.
4. At the bottom of the dialog box,
click Next.
You can view information
about the
documentation, or you
can continue the
installation.
Modular Messaging
Web Client Installation
(Select Destination
Directory dialog box)
1. Accept the default destination
folder on the C: drive, or navigate
to a different location.
2. Click Next.
Modular Messaging
Web Client Installation
(Backup Replaced
Files? dialog box)
Select Yes, and click Next. Avaya recommends that
you complete a system
backup before starting
the installation.
Select Program Group Leave the default as is, and click
Next.
???
Modular Messaging
Web Client Installation
(Ready to Install dialog
box)
Click Next. ???
Verifying the installation
Web Client for Modular Messaging Release 3 Server Installation and Upgrades April 2006 21
Verifying the installation
This section includes the following topics:
? Verifying Web Client components on page 21
? Running Install Verify Test (Ivy) on page 22
? Verifying port settings on page 24
Verifying Web Client components
When you installed Modular Messaging Web Client, the system installed all the components
needed to run, configure, and monitor the use of the application, including:
? Modular Messaging Web Client. Users gain access to this interface by logging on to their
mailboxes through the URL for the Web Client server:

http://<server

name>/webmsg
Note:
Note: Users of this interface can select the language in which they want the interface to
display.
Installing Wait for the system to display the
next dialog box.
Caution: If you see any messages
asking whether you want to
overwrite newer files, click No.
???
Modular Messaging
Web Client Installation
(Installation
Completed! screen)
1. Click Finish.
2. To restart the server, click OK.
3. After the restart completes, log
on again to the server.
The system registers several
Web Client files. Wait for file
registration to complete.
???
Dialog box Required action Notes
Chapter 3: Installation
22 Web Client for Modular Messaging Release 3 Server Installation and Upgrades April 2006
? Modular Messaging Web Client Administration and Maintenance tools.
Administrators use this interface to configure and maintain the Web Client server. For
more information about this interface, see Completing initial administration on page 24, the
online Help system contained within the administration interface, or Modular Messaging
Web Client Administration and Maintenance on the Modular Messaging Web Client
software CD-ROM.
Note:
Note: The administration interface is available in English only.
? Modular Messaging Web Client Tools program group. You can use these tools to verify
the installation and connectivity of the Web Client server and to maintain the server. You
can access these tools from the Start menu of the Web Client server by clicking Programs
> Avaya Modular Messaging Web Client Tools. Tools include the following:
? Connectivity Test. You can use this tool to verify connectivity between message
servers and the Web server, after you have added message servers. For more
information, see Configuring and verifying the message servers on page 25.
? Install Verify Test - Ivy. You can use this test to verify and diagnose the installation of
the Web Client server. For more information, see Running Install Verify Test (Ivy) on
page 22.
? Reset Web Server. If you reset the Web server, the server stops and then re-starts.
This might be required, for example, if you are having problems with IIS.
Note:
Note: You can also test for IIS problems and reset the Web server through the Web
Client Administration pages. For more information, see the online Help system
contained within the administration interface or Modular Messaging Web Client
Administration and Maintenance on the Modular Messaging Web Client software
CD-ROM.
? Start Web Server. You can start the Web server after you complete any needed
system maintenance.
? Stop Web Server. You can stop the Web server to perform system maintenance.
? UMLog Viewer. Technical support representatives can use this log viewer to
troubleshoot problems with your system.
Running Install Verify Test (Ivy)
About Ivy
Use the Install Verify Test (Ivy) to verify and diagnose the Modular Messaging Web Client
installation. Ivy uses system data to create a report in plain ASCII format. You can do the
following:
? Save and print the Ivy report.
Verifying the installation
Web Client for Modular Messaging Release 3 Server Installation and Upgrades April 2006 23
? Send the Ivy report as an e-mail attachment, for example to technical support
representatives.
? Change the filter for viewing data.
? Create different baselines for comparisons.
When you open Ivy from the Modular Messaging Web Client Tools program group, the tool
starts automatically. The tool checks each Modular Messaging Web Client file against the
database for the following:
? File name
? Location
? Size
? Date
? Version
? Windows registry entry
About the Ivy report
The status bar in the Install Verify window displays each file name as that file is being checked.
When the verification is complete, the window displays the Ivy report. The default is to create a
report that shows only errors and warnings. You can change the information that is shown by
clicking the stoplights on the toolbar. Red shows only errors, yellow is the default that shows
both errors and warnings, and green shows all files. Errors appear against a red background,
and warnings appear against a yellow background.
The Ivy report is made up of a row of tabs. If you enable the default that shows both errors and
warnings and the fields of a selected tab are empty, no errors or warnings are present.
The tool displays the information contained in the Ivy database on the first line for each file and
the information found on the Web server on the second line. The tool displays only information
that differs from one database to another. A blank column on the second line indicates that the
information matches.
When you review a report, you might notice some warnings for differences that you do not need
to address. For example, a newer version of a system file present on the server is usually not
replaced with an older version, but the Ivy report displays the difference. You can exclude these
differences from future Ivy reports when you set the baseline. You should address all errors that
the system displays in a report.
You can create a baseline of the Ivy report either from the Tools menu or from the magnifying
glass icon on the toolbar. A baseline file contains information about the Ivy database and
system differences at the time the baseline was created.
Chapter 3: Installation
24 Web Client for Modular Messaging Release 3 Server Installation and Upgrades April 2006
Establishing a baseline report
To establish a baseline report:
1. On the Web Client server, click Start > Programs > Avaya Modular Messaging > Web
Client Tools > Install Verify Test - Ivy.
The system checks the program files. The process might take a few minutes.
2. Click each tab in the Ivy window, and verify that no errors exist. Errors appear in red.
3. On the Tools menu, click Make Baseline.
4. Specify saving the file to the default folder, and click Save.
5. In the Select Output dialog box, select All Entries, and click OK.
6. When you are ready to close Ivy, click File > Exit.
The baseline file is not used automatically when Ivy creates future reports. To view the
differences between an Ivy report and the baseline, on the Tools menu, click Compare to
Baseline. The system displays a new report that shows only the errors and warnings that are
not in the baseline file.
Verifying port settings
The Web Client installation process creates the virtual Web directory webmsg under the Default
Web Site of Internet Information Services (IIS). The Default Web Site uses port 80 as the default
Transmission Control Port (TCP) port. If you are using the default port and port 80 is closed on
the Web server, you must open port 80 on the Web server. To open port 80 on the Web server:
1. Click Start > Run, and type secpol.msc.
The system launches the Local Security Policy snap-in.
2. In the left pane, under Security Settings, click IP Security Policies on Local Computer.
3. Right-click Block TCP 80 Filter, and click unassign.
The Policy Assign column displays no.
Completing initial administration
After you successfully install the Web Client server and verify the installation, you can complete
basic administration tasks from the Web Client administration interface.
Note:
Note: Before you administer the Modular Messaging Web Client server, the server must
be installed on the network at the customer site.
Completing initial administration
Web Client for Modular Messaging Release 3 Server Installation and Upgrades April 2006 25
To log on to the administration interface:
1. In Microsoft Internet Explorer, enter the following URL:

http://<server

name>/webmsg/admin
(for example,

http://uccweb.rnd.avaya.com/webmsg/admin).

The system displays the Administration and Maintenance logon page.
2. In the Log On field, type admin, and type the default password, admin1.
3. Click Log On.
The system displays the Administration and Maintenance page.
Initial administration tasks that you should complete include the following:
? Configuring and verifying the message servers on page 25
? Configuring Web Client options and settings on page 26
For more information about administration and maintenance tasks completed within the Web
Client administration interface, see the online Help system contained within the administration
interface or Modular Messaging Web Client Administration and Maintenance on the Modular
Messaging Web Client software CD-ROM.
Configuring and verifying the message servers
From the Message Servers page of the Web Client administration interface, you must configure
the message servers that will communicate with the Web Client server. To configure message
servers, follow the instructions in "Message Servers page" in the administration online Help
system or in Modular Messaging Web Client Administration and Maintenance on the Modular
Messaging Web Client software CD-ROM.
You can use the Connectivity Test to verify the connectivity between the Web Client server and
the message servers that you administered for the Web Client. The Connectivity Test verifies
the name and IP address of the Web Client server and where the Web Client resides. The test
also checks the following criteria:
? The Web Client server is configured for network access.
? Internet Information Services (IIS) is running on the Web server.
? A connection to the message servers exists.
To run the Connectivity Test:
1. On the Web Client server, click Start >Programs > Avaya Modular Messaging Web
Client Tools > Connectivity Test.
2. To test all the message servers that you configured for the Web Client, click Test All.
The tool automatically tests connectivity to each server.
Chapter 3: Installation
26 Web Client for Modular Messaging Release 3 Server Installation and Upgrades April 2006
Configuring Web Client options and settings
From the Options and Settings page of the Web Client administration interface, you can
configure the following parameters that affect how subscribers use the Web Client:
? Web server timeout
? Corporate logo
? Web Link Control
? Voice player
? Subject edit
? New message notification
? Message of the day
? IMAP4 server
For more information about these parameters and how to configure them, see the "Options and
Settings page" section in the administration online Help or in Modular Messaging Web Client
Administration and Maintenance on the Modular Messaging Web Client software CD-ROM.


Ken Means

http://www.tel-is.com

"I find that the harder I work, the more luck I seem to have."
- Thomas Jefferson (1743-1826)

 

[98Converter]

Thanks for the info. That is what I followed on the install. We are using MSS. We also enabled our server to accept .ASP files, and to no avail.

Our release is 3.0.0.39. Not sure if the upgrade to .43 will help this issue. I'll have to get if from our BP...

Thanks,
CJH





We are what we repeatedly do. Excellence, then, is not an act but a habit. ARISTOTLE 384-322 B.C.

 

[KenMeans]

This may not be it but we had trouble with the time on the system. It must be less than a min off of the time on mas 1

But if you can't configure it then it would not know about mas 1

Ken Means

http://www.tel-is.com

"I find that the harder I work, the more luck I seem to have."
- Thomas Jefferson (1743-1826)

 

[98Converter]

The time was about 2 minutes off. I changed them to the same time. Would a reboot be required? If so, on which box?

Thanks,
CJH

We are what we repeatedly do. Excellence, then, is not an act but a habit. ARISTOTLE 384-322 B.C.

 

[KenMeans]

a reboot should not be required

Ken Means

http://www.tel-is.com

"I find that the harder I work, the more luck I seem to have."
- Thomas Jefferson (1743-1826)