Hint - For local systems only (serves running the tracing server service there is nothing to configure except the printer mentioned below) no ODBC configuration is necessary.
Local systems, servers running the tracing service:
When using the reporting tool for the first time you must set a default printer under the reporting tool, even if no printer exists to fake out the system. May or may not be necessary to do more than once for different logins. Reports should then run.
Operational History Viewer should work.
To run OpHist and Reports on other servers you must share out both the Tracing folder and the Reports folder from the server running the MM tracing service.
C:\Program Files\Avaya Modular Messaging\Tracing
C:\Program Files\Avaya Modular Messaging\Tools\Diag\Reports
Remote systems, servers not running the tracing service:
On remote MAS (servers not running the MM tracing service) - This is where you have to do some ODBC configuration.
Under the ODBC you will have to map drives to files (be sure to check Reconnect at logon) in both the shared Tracing folder and the shared Reports folder.
Be careful with the instruction links below, I think the administration documentation is more than a little confusing but they show how to map the drives on the remote servers and point to the correct data source.
Hint – If under the System DSN if a source OperationHistory, TrxDB, or ReportsDB already exists (and they should) then you do not need to create or add them you simply need to configure (map a drive to the remote folder and point to the correct file) them.
Hint - Under the reporting admin you will have to configure the TrxDB and the ReportDB (the instructions do not mention the ReportDB and that is why I write these things).
So for Operation History, you configure and map OperationHistory (DSN) to the OpHist.mdb file (tracing folder) on the remote tracing server. 1 - thing to configure only.
And for Reports you configure the TrxDB (DSN) mapped to the TrxDB.mdb file (tracing folder) and you must also configure ReportDB (DSN) mapped to the reports.mdb (Reports folder). 2 - things to configure here.
http://support.avaya.com/elmodocs2/mm/r3_1_doc/CD_Master/a_mss_mas/MASAd-OHV-Und-Dat.html
http://support.avaya.com/elmodocs2/mm/r_4_0_doc/cd_frontend/a_mss_mas/MASAd-RT-Und-Dat.html
This sharing is login specific so mapping the data sources will have to be repeated for every login that is being used if they want the Reporting tool and Operation History to function.
Sunday, August 3, 2008
Thursday, February 7, 2008
Enabling Offline Access
Currently no offline access configured under VMSC -> Messaging
If you want to enable this feature in 3.1 - On the C: drive of which ever server you are going to use as the remote store create a folder called "remotestore" and share it. Under permissions and also under security (these are two places not one) I would add the everyone account, domain admins, and the local computer accounts (all computers in the VMD) with full contoll for all, adding the tech support and customer accounts are optional but not necessary.
Then and only then map the path to this folder and allow subscriber to access messages using the TUI.
Under the VMSC -> Messaging - I always browse to the folder because if you can not browse to it then it is not shared properly!
After browsing to the folder the path will look like this -
"\\Servername\remotestore"
When you are done leave a few test messages for any subscriber, folders should start accumulating in that “remotestore” folder if that happens then you are GOLD!
If you want to enable this feature in 3.1 - On the C: drive of which ever server you are going to use as the remote store create a folder called "remotestore" and share it. Under permissions and also under security (these are two places not one) I would add the everyone account, domain admins, and the local computer accounts (all computers in the VMD) with full contoll for all, adding the tech support and customer accounts are optional but not necessary.
Then and only then map the path to this folder and allow subscriber to access messages using the TUI.
Under the VMSC -> Messaging - I always browse to the folder because if you can not browse to it then it is not shared properly!
After browsing to the folder the path will look like this -
"\\Servername\remotestore"
When you are done leave a few test messages for any subscriber, folders should start accumulating in that “remotestore” folder if that happens then you are GOLD!
Friday, July 20, 2007
New Install Modem Issues
Symptoms: Modems answers and drops immediately; modem is RNA.
1. Start -> Programs -> Administrative Tools -> (click/open) Routing and Remote Access
2. Right click "server name" -> Disable Routing and Remote Access -> minimize window but leave open.
3. Start -> Settings -> Control Panel -> (click/open) Phone and Modem Options
Go to the tab "Modems"
Highlight the modem and then remove
After
Add -> Add Hardware Wizard -> Next -> Allow Windows to detect modem -> Welcome to the Found New Hardware Wizard -> select - No, not this time -> select - Install the software automatically {Recommended} -> Hardware Installation - Pop-up - select - Continue Anyway -> Click "Finish" -> Click "Finish"
Close the Control Panel
Routing and Remote Access
Highlight and Right click "server name" - > click - Configure and Enable Routing and Remote Access -> Wizard - next -> bottom - Custom configuration - next -> Dial-up access - next -> "Finish" - > Do you want to start the service? - Yes
Now you can configure the service per page 103 of the Modular Messaging 3.1 install guide.
1. Start -> Programs -> Administrative Tools -> (click/open) Routing and Remote Access
2. Right click "server name" -> Disable Routing and Remote Access -> minimize window but leave open.
3. Start -> Settings -> Control Panel -> (click/open) Phone and Modem Options
Go to the tab "Modems"
Highlight the modem and then remove
After
Add -> Add Hardware Wizard -> Next -> Allow Windows to detect modem -> Welcome to the Found New Hardware Wizard -> select - No, not this time -> select - Install the software automatically {Recommended} -> Hardware Installation - Pop-up - select - Continue Anyway -> Click "Finish" -> Click "Finish"
Close the Control Panel
Routing and Remote Access
Highlight and Right click "server name" - > click - Configure and Enable Routing and Remote Access -> Wizard - next -> bottom - Custom configuration - next -> Dial-up access - next -> "Finish" - > Do you want to start the service? - Yes
Now you can configure the service per page 103 of the Modular Messaging 3.1 install guide.
3.1 MSS - DCT Issues / MAS Installation issues
1. If the corporate LAN is not yet in place, do not have the tool attempt to use the corporate LAN as part of the install process. Open the DCT file -> Networking -> Corporate network -> select – Do not connect MM to the corporate network – Complete and overwrite the existing file
2. In the private hub or an administered private VLAN – Connect the MAS’ to that private connection ONE AT A TIME as you install. DO NOT JAM ALL OF THE MAS SERVERS INTO THE CONNECTION AT THE SAME TIME.
This means when installing the first MAS only MAS1 and the MSS are in that private connection, once MAS1 has been installed you then may add MAS2. So now as you install we have MSS->MAS1->MAS2-installing. This is how you install multiple servers.
3. When all servers are jammed into the private connection at once:
When all servers have been jammed into the private connection at once I have had technicians tell me that MAS1 went in just fine but that they can not install MAS2? Only to find out that while MAS1 appeared to complete we can not open up the VMSC as there was no VDM created on the MSS and when we checked the MAS server name instead of being the name specified in the DCT file it is “Generic” something or other. - I see a MAS reload in your future.
Lastly - Upgrades
Do not analyze a supplementary server. IT DOES NOT WORK.
And even if you dreamt that it worked once or a senior RSE or a Flying Monkey tells you it does work, whatever, IT DOES NOT WORK, and I just told you so!
You analyze and upgrade all of the MAS servers and add the supplementary server back in at the end. Then go through all of the servers and administer the services appropriately.
In other words if you want MWI-Call Me and the MM Monitor service as well as the Tracing service running on the supplementary server first stop and disable them if they are running some place else then start and configure them (VMSC) to run on the supplementary server.
When upgrading – do not make changes to the system using the DCT.
When upgrading – do not make changes to the system using the DCT.
When upgrading – do not make changes to the system using the DCT.
Make the change to the existing system then analyze it and do your upgrade, or upgrade the system as it is then make your changes.
When upgrading – do not make changes to the system using the DCT.
When upgrading – do not make changes to the system using the DCT.
When upgrading – do not make changes to the system using the DCT.
If you want to move a server:
Make the change to the existing system then analyze it and do your upgrade, or upgrade the system as it is then make your changes.
When upgrading – do not make changes to the system using the DCT.
When upgrading – do not make changes to the system using the DCT.
When upgrading – do not make changes to the system using the DCT.
2. In the private hub or an administered private VLAN – Connect the MAS’ to that private connection ONE AT A TIME as you install. DO NOT JAM ALL OF THE MAS SERVERS INTO THE CONNECTION AT THE SAME TIME.
This means when installing the first MAS only MAS1 and the MSS are in that private connection, once MAS1 has been installed you then may add MAS2. So now as you install we have MSS->MAS1->MAS2-installing. This is how you install multiple servers.
3. When all servers are jammed into the private connection at once:
When all servers have been jammed into the private connection at once I have had technicians tell me that MAS1 went in just fine but that they can not install MAS2? Only to find out that while MAS1 appeared to complete we can not open up the VMSC as there was no VDM created on the MSS and when we checked the MAS server name instead of being the name specified in the DCT file it is “Generic” something or other. - I see a MAS reload in your future.
Lastly - Upgrades
Do not analyze a supplementary server. IT DOES NOT WORK.
And even if you dreamt that it worked once or a senior RSE or a Flying Monkey tells you it does work, whatever, IT DOES NOT WORK, and I just told you so!
You analyze and upgrade all of the MAS servers and add the supplementary server back in at the end. Then go through all of the servers and administer the services appropriately.
In other words if you want MWI-Call Me and the MM Monitor service as well as the Tracing service running on the supplementary server first stop and disable them if they are running some place else then start and configure them (VMSC) to run on the supplementary server.
When upgrading – do not make changes to the system using the DCT.
When upgrading – do not make changes to the system using the DCT.
When upgrading – do not make changes to the system using the DCT.
Make the change to the existing system then analyze it and do your upgrade, or upgrade the system as it is then make your changes.
When upgrading – do not make changes to the system using the DCT.
When upgrading – do not make changes to the system using the DCT.
When upgrading – do not make changes to the system using the DCT.
If you want to move a server:
Make the change to the existing system then analyze it and do your upgrade, or upgrade the system as it is then make your changes.
When upgrading – do not make changes to the system using the DCT.
When upgrading – do not make changes to the system using the DCT.
When upgrading – do not make changes to the system using the DCT.
3.1 MSS - Link speed and duplex / Network Media Type
This seems to happen a lot with the MSS backend especially when systems are newly installed:
These speeds (Network Media Type) are changed on both the corporate and the private connections on the MSS usually to 100/F but do not get changed on the MAS servers.
This puts a powerful Whammy on the voicemail system and all manner of strange weirdness can ensue. Things such as people not being to get into their mailboxes or being able to get into their mailboxes but not able to fwd messages, and getting that oh so lovely, “I’m sorry there is a problem with the system…” And I have even seen 1 tech do this then wonder why the MISCM would not complete??? If you are going to change the NIC speeds do it after the install and then do it on all servers.
All of this goes away if you change the NIC’s speeds on the MAS to match what they have the MSS setup for. It takes seconds for the network connections to reset themselves.
These speeds (Network Media Type) are changed on both the corporate and the private connections on the MSS usually to 100/F but do not get changed on the MAS servers.
This puts a powerful Whammy on the voicemail system and all manner of strange weirdness can ensue. Things such as people not being to get into their mailboxes or being able to get into their mailboxes but not able to fwd messages, and getting that oh so lovely, “I’m sorry there is a problem with the system…” And I have even seen 1 tech do this then wonder why the MISCM would not complete??? If you are going to change the NIC speeds do it after the install and then do it on all servers.
All of this goes away if you change the NIC’s speeds on the MAS to match what they have the MSS setup for. It takes seconds for the network connections to reset themselves.
3.1 MSS - New Install MWI issue
Seen primarily on the MSS Backend –
Symptoms: MWI appears to not be working on a newly installed system
1. After, after, after you check the basic configuration under the VMSC and you determine that MWI is configured correctly:
2. Go to the server running the MWI service and -> stop the MM MWI service -> stop the MM Call Me service -> stop the MM Mailbox Monitor service
Then before starting those services back up
3. Stop and start the MM Messaging Application server service on every Call Processing MAS in the domain.
4. Then go to the server running the MWI service and -> start the MM Mailbox Monitor service (must be first) -> start MM MWI service -> start the MM Call Me service
MM is not monitoring subscribers after they have been bulk loaded to the machine until these services have been stopped and started. Yes rebooting the machines would do exactly the same thing.
Symptoms: MWI appears to not be working on a newly installed system
1. After, after, after you check the basic configuration under the VMSC and you determine that MWI is configured correctly:
2. Go to the server running the MWI service and -> stop the MM MWI service -> stop the MM Call Me service -> stop the MM Mailbox Monitor service
Then before starting those services back up
3. Stop and start the MM Messaging Application server service on every Call Processing MAS in the domain.
4. Then go to the server running the MWI service and -> start the MM Mailbox Monitor service (must be first) -> start MM MWI service -> start the MM Call Me service
MM is not monitoring subscribers after they have been bulk loaded to the machine until these services have been stopped and started. Yes rebooting the machines would do exactly the same thing.
3.1 Exchange – Pulling up a user in ADUC, wahappend?
A user writes: “When I go into a user account, I can access the MM tab and enter information. When I click the Advanced button, the screen goes away, including the ADUC screen and the user information screen.”
This is one of those dreaded “known issues” (Now known to you!) the work around is to pull the subscriber/user up manually – I know lots of fun to do in ADUC - then everything works.
If you search for the user then: “When I go into a user account, I can access the MM tab and enter information. When I click the Advanced button, the screen goes away, including the ADUC screen and the user information screen.”
This will be fixed in a “Service Pack” from the future.
This is one of those dreaded “known issues” (Now known to you!) the work around is to pull the subscriber/user up manually – I know lots of fun to do in ADUC - then everything works.
If you search for the user then: “When I go into a user account, I can access the MM tab and enter information. When I click the Advanced button, the screen goes away, including the ADUC screen and the user information screen.”
This will be fixed in a “Service Pack” from the future.
Subscribe to:
Posts (Atom)