WECCNET MESSAGING SYSTEM CLIENT DOCUMENTATION

Transcription

1 TABLE OF CONTENTS WECCNET Messaging System Client Documentation WECCNET MESSAGING SYSTEM CLIENT DOCUMENTATION March 3 rd, 2015 SUPPORT CONTACTS... 2 CLIENT REQUIREMENTS... 2 CLIENT PRECONFIGURATION... 3 FIREWALL SETTINGS (REQUIRED)... 3 SUPPORT DOWNLOADS... 3 HOSTS FILE (REQUIRED)... 4 CERTIFICATE TRUST (REQUIRED)... 5 SECURITY SETTINGS (REQUIRED)... 7 ANTI-VIRUS (OPTIONAL)... 8 PATCH MANAGEMENT (OPTIONAL) TIME SYNCHRONZIATION (OPTIONAL) CLIENT CONFIGURATION OUTLOOK 2007/ OUTLOOK WEB ACCESS FAILOVER PROCESS DEFINITIONS OUTLOOK 2007/ CONTROLLED FAILOVER CATASTROPHIC FAILOVER OUTLOOK WEB ACCESS CONTROLLED FAILOVER CATASTROPHIC FAILOVER Page 1 of 22

2 SUPPORT CONTACTS Technical support for the WECCNet Messaging System is provided by Peak Reliability IT department. WECCNet Messaging System customers are encouraged to first contact local IT support before contacting Peak Reliability IT department. Local IT support will be able to solve most common issues with greater rapidity then Peak Reliability IT department will be able to. Requests for access to the WECCNet Messaging System, as well as recovery of historical messages, are also supported by the Peak Reliability IT support team. Within the WECCNet Messaging System, you can send an to WECCNet- Support. Outside the WECCNet Messaging System, you can use the following contacts: TECHNICAL SUPPORT CLIENT REQUIREMENTS WECCNet Messaging System supports the Outlook 2007 and newer clients on Windows 7 or higher operating systems. Windows XP is not supported. Outlook Web Access (OWA) is supported using the Internet Explorer 11 or later web browsers. Anti-virus software is required on all WECCNet Messaging terminals. Organizations are free to use an anti-virus product of the organization s choice. Peak Reliability provides an anti-virus solution for clients that do not have the infrastructure to support an anti-virus client on isolated WECCNet Messaging terminals. Page 2 of 22

3 CLIENT PRECONFIGURATION FIREWALL SETTINGS (REQUIRED) DESTINATION HOSTS WECCNET Messaging System Client Documentation CORE SERVICES (REQUIRED) PORT/PROTOCOL 80/tcp (HTTP for autodiscover and OWA) 443/tcp (HTTPS for autodiscover and OWA) 135/tcp (RPC Endpoint Mapper) 40000/tcp (Exchange SA) 40002/tcp (Exchange NSPI Proxy) 40004/tcp (Exchange IS) 40006/tcp (NTDS) DESTINATION HOST AUXILARY SERVICES (OPTIONAL) PORT/PROTOCOL 80/tcp (HTTP for Windows update services) 123/udp (NTP for time synchronization) 8530/tcp (HTTP port for Windows update services) 4158/tcp (HTTP port for anti-virus updates) SUPPORT DOWNLOADS The necessary configuration scripts, software and files can be downloaded from the Peak Reliability support website at: Page 3 of 22

4 HOSTS FILE (REQUIRED) WECCNET Messaging System Client Documentation 1. Replace the client computer s HOSTS file with the WECCNet Messaging HOSTS file. a. The HOSTS file is included in the support download (see Support Downloads section). b. Rename the existing HOSTS file from C:\Windows\System32\Drivers\etc\HOSTS to C:\Windows\System32\Drivers\etc\HOSTS.OLD c. Extract the WECCNet Messaging HOSTS file from the downloaded ZIP archive and copy the file to the C:\Windows\System32\Drivers\etc\ folder. d. Test the HOSTS file by opening a command prompt and typing ping vancouver-a. If the result returns an IP address of , the HOSTS file is working properly. Page 4 of 22

5 CERTIFICATE TRUST (REQUIRED) WECCNET Messaging System Client Documentation 1. Install the WECCNet Root CA certificate as a trusted root certificate authority. a. The certificate file is included in the support download (see Support Downloads section). b. Double-click the certificate to open it. In the Certificate window, select Install Certificate. c. When prompted to select a Certificate Store, select Place all certificates in the following store. Click the Browse button, and choose Trusted Root Certification Authorities. Page 5 of 22

6 d. When prompted with a Security Warning, verify the certificate and select Yes to install the certificate. Windows XP clients require Windows XP SP3 to validate SHA-2 certificates. Thumbprint (sha1): c34749c5 ccefee d29 84b87e faae e. Use the Certificates MMC snap-in to verify that the WECCNet Root CA certificate was installed in the Trusted Root Certification Authorities store. Page 6 of 22

7 SECURITY SETTINGS (REQUIRED) WECCNET Messaging System Client Documentation 1. Modify the LAN Manager Authentication Level supported by the computer. a. Open the Local Security Settings tool (located in the Control Panel under Administration Tools ) and browse to Security Settings \ Local Policies \ Security Options. b. Change the value of Network security: LAN Manager Authentication Level to Send NTLMv2 response only\refuse LM & NTLM. Page 7 of 22

8 ANTI-VIRUS (OPTIONAL) WECCNET Messaging System Client Documentation 1. Uninstall any existing anti-virus products. Refer to the existing product documentation for additional instructions. 2. The anti-virus installation package is included in the support download (see Support Downloads section). 3. Extract the anti-virus installation package to a temporary folder (for example, C:\Install). 4. Open a command prompt and change to the directory you extracted the anti-virus installation files to. Launch the anti-virus installer by executing the command AvgSetup.cmd. 5. When the setup is complete, double-click the AVG icon in the system tray to open the AVG management console. Click Update Now to verify that AVG can connect to the update server. Page 8 of 22

9 6. If your connection is successful, you will see a prompt to download and install definition and program updates. Page 9 of 22

10 PATCH MANAGEMENT (OPTIONAL) WECCNET Messaging System Client Documentation 1. The registry file to configure a Windows system to use the WECC patch management server is included in the support download (see Support Downloads section). 2. From the support download, extract and double-click WSUS.reg. 3. You will be prompted to verify that you want to add the information in the WSUS.reg file to the registry. Select Yes. 4. Check for updates: a. For Windows XP clients: Execute the command wuauclt.exe /detectnow from a command prompt. b. For Windows Vista and later clients: Open the Windows Update tool from the control panel and click Check for updates 5. Check the status of the Windows Update client by reviewing the log file (%systemroot%\windowsupdate.log). Verify that the Windows Update client has the Server URL configured for the IP address Page 10 of 22

11 TIME SYNCHRONZIATION (OPTIONAL) WECCNET Messaging System Client Documentation 1. Uninstall any third-party time synchronization or NTP time service products installed on the system. Refer to the existing product documentation for additional instructions. 2. The time synchronization script is included in the support download (see Support Downloads section). 3. Execute the TimeSync.cmd file from the support download archive. 4. Check the System event log. You should find an entry for source W32Time, stating that The time service is now synchronizing the system time with the time source Page 11 of 22

12 CLIENT CONFIGURATION OUTLOOK 2007/ Open the Control Panel and double-click the Mail icon. 2. In the Mail Setup Outlook window, click the Show Profiles button. Page 12 of 22

13 3. Click on the Add button to create a new profile. Name it WECCNet Messaging. Click OK to launch the Accounts wizard. 4. In the Add New Account wizard, provide the following: a. In the Your Name field, enter your login name. b. In the Address field, enter your login name followed For example, if your login name is WXYZ1, your address would be WXYZ1@weccrc.net. c. In the Password and Retype Password fields, enter in your password. Page 13 of 22

14 5. Based on the information you provided, Outlook will automatically discover your server settings. NOTE: If you are prompted with a Security Alert, the certificate trust pre-configuration step was not completed successfully. 6. When prompted for your user name and password, enter WECCNET\(USERNAME) for the user name and your password. Page 14 of 22

15 7. When the automatic configuration is complete, you will receive the message Your account is successfully configured to use Microsoft Exchange. Click Finish to continue. 8. Confirm that the WECCNet Messaging entry has been added to the Mail properties window. Select the option to Always use this profile, and select WECCNet Messaging from the drop-down menu. Page 15 of 22

16 9. Launch Outlook. Please note, you must specify WECCNET\ in front of your username when launching Outlook to connect to the WECCNet Messaging System. 10. Once Outlook has launched, confirm the configuration by checking the connection status of your client: Page 16 of 22

17 OUTLOOK WEB ACCESS WECCNET Messaging System Client Documentation 1. Right-click the desktop and select the New -> Shortcut option. 2. In the Create Shortcut wizard, enter in in the Type the location of the item: field and click Next. 3. In the Select a Title for the Program window, type in loveland-a and click Finish. Page 17 of 22

18 4. Perform steps 2-4 again three times. Each time, on step 3 and step 4, change Loveland-A to Loveland-B, Vancouver-A and Vancouver- B. When all four shortcuts have been created, proceed to the next step. 5. Launch any one of the four shortcuts. You will be presented with the Office Outlook Web Access logon screen. a. Select the option This is a private computer. Do not select the Use Outlook Web Access Light option. b. Enter in your user name and password in the appropriate boxes. Your password is identical to your user name. Passwords are case-sensitive and use all capital letters. 6. On your first login using Outlook Web Access, you will be presented with a configuration menu. Set the time zone you wish to use, and click OK to continue. Page 18 of 22

19 7. You will enter the Outlook Web Access interface for your mailbox. Page 19 of 22

20 FAILOVER PROCESS All notifications of a scheduled controlled failover will be sent via the WECCNet Messaging System. A notification for a controlled failover will be sent a minimum of 72 hours before the failover is scheduled to take place, and will include the specific date and time of the failover event. DEFINITIONS CONTROLLED FAILOVER: A controlled failover is the planned and communicated failover of mail services from the primary mail server to one of the three redundant mail servers. CATASTROPHIC FAILOVER: An unplanned failover of mail services, where the primary mail server has failed in an unrecoverable manner. If the primary mail server is recoverable in any fashion, a catastrophic failover will not be required. The average recovery time from a catastrophic failover is 60 minutes and all messages up to the point of the failover will be recovered. In a worst-case scenario, recovery from a catastrophic failover should take no more than four hours, and may result in a loss of the messages sent through the system for a maximum of twelve hours prior to the catastrophic failure. Page 20 of 22

21 OUTLOOK 2007/2010 CONTROLLED FAILOVER Outlook 2007/2010 will alert the user with a notification message stating that you must restart Outlook. Closing and re-opening Outlook will automatically re-connect the client to the correct mail server. This behavior is consistent regardless of failover type. CATASTROPHIC FAILOVER Failing over an Outlook 2007/2010 client during a catastrophic failover uses the same process that Outlook uses for a controlled failover. Outlook will alert the user with a notification message stating that you must restart Outlook. Closing and re-opening Outlook will automatically re-connect the client to the correct mail server. This behavior is consistent regardless of failover type. Page 21 of 22

22 OUTLOOK WEB ACCESS CONTROLLED FAILOVER WECCNET Messaging System Client Documentation During a controlled failover, Outlook Web Access clients will be required to shut down Outlook Web Access and re-open it. During the migration process, OWA clients might also encounter one of the following messages. Both indicate that the OWA client should be closed and re-opened. CATASTROPHIC FAILOVER There are several indicators that a catastrophic failure has occurred. If you see one of these messages, please contact WECCNet Support for immediate assistance to determine if a catastrophic failure has occurred. If you have contacted WECCNet Messaging Support, and if support has indicated that a catastrophic failure has occurred, use the following process to re-establish connectivity to WECCNet Messaging: 1. Close all open instances of Internet Explorer, including Outlook Web Access. 2. Launch Outlook Web Access using one of the three alternative shortcuts on your desktop. If the alternative shortcut fails, continue attempting to connect the remaining shortcuts. Contact WECCNet Messaging Support if you continue to experience issues. Page 22 of 22