• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Upgrading_to_GroupWi..
 

Upgrading_to_GroupWi..

on

  • 501 views

 

Statistics

Views

Total Views
501
Views on SlideShare
501
Embed Views
0

Actions

Likes
0
Downloads
1
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    Upgrading_to_GroupWi.. Upgrading_to_GroupWi.. Presentation Transcript

    • Upgrading to GroupWise 7 Timothy King Premium Support Engineer Novell ANZ
    • Outline
      • This session is about upgrading complex GroupWise systems, focusing on minimizing:
        • Risk of failure or damage
        • Disruption to Services
        • Cost – Out of hours work
      • This session is not about the Upgrade Wizard
        • The Upgrade Wizard is suitable for small, LAN based GroupWise systems, but it is an inefficient way to upgrade complex, WAN based systems.
    • Agenda
        • GroupWise 7 System Requirements
          • Server
          • Administration
          • Client
        • Preparing for the Upgrade
          • eDirectory
          • GroupWise
        • Performing the Upgrade
          • Domains
          • Post Offices
          • Gateways
          • Clients
        • Review and implement new features.
        • 32-bit/x86 processor
        • eDirectory 8.7 or later, plus the latest Support Pack
        • NetWare
          • NetWare 5.1, NetWare 6.0, NetWare 6.5 or OES
        • Linux
          • SuSE Linux Enterprise Server 9
          • Novell Open Enterprise Server (OES)
        • Windows
          • Windows 2000 Server, Windows 2003 Server
        • Approximately 25 MB of free disk space (varies by platform)
      System Requirements - Server
    • System Requirements - Administration
        • ConsoleOne 1.3.6 or later
        • Windows
          • Windows 2000/XP/2003
          • the Novell Client for Windows
        • Linux
          • X Window System version X11R6 or later
          • Java Virtual Machine (JVM) 1.4.2
        • Windows
          • 2000 on a PII 200 or higher with at least 128 MB of RAM
          • XP Pro on a PIII 300 or higher with at least 128 MB of RAM
          • 2003 on a PIII 350 or higher with at least 256 MB of RAM
          • 200 MB of free disk space to install the Windows client
        • Linux
          • Novell Linux Desktop, plus the KDE or GNOME desktop
          • Red Hat* Desktop 4 or Red Hat Enterprise Linux WS 4, plus the GNOME desktop
          • Java Virtual Machine (JVM) 1.4.2 or later (1.5 or later for GW 7.0.1)
          • 200 MB of free disk space to install the Cross-Platform client
      System Requirements - Client
        • Macintosh
          • OS X 10.3 or 10.4 or Mac OS X for Intel (GW 7.0.1)
          • Java Virtual Machine (JVM) 1.4.2 or later
          • 75 MB of free disk space to install the Cross-Platform client
        • WebAccess
          • Linux and UNIX: Mozilla Firefox
          • Windows: Microsoft Internet Explorer 6.0 or later; Mozilla Firefox
          • Macintosh: The latest version of Safari for your Mac OS; Mozilla Firefox
      System Requirements - Client
    • Preparing for the Upgrade
      • Preparation is the key to a successful and trouble free upgrade.
        • eDir
          • Complete a health check
        • GroupWise
          • Review system design
          • Complete a Top Down Rebuild
        • Check and clear upgrade “Show-Stoppers”
          • Closed Links
          • Pending Operations
          • Stalled User Move Operations
          • Damaged Databases
          • Hardware problems
          • Client Access problems
      • A healthy eDir tree is essential to achieve a trouble free upgrade.
        • Confirm that eDir is healthy
          • TID 10060600 provides the recommended eDir health check procedure.
        • Do not proceed any further until your tree is healthy.
        • Check eDir schema sync status across all servers in the tree.
        • Do not proceed any further until your tree’s schema is healthy .
      Preparing eDirectory
      • Take some time to review the existing system before upgrading.
        • Remove redundant system components
          • This task should be done before the upgrade so that we don’t do any unnecessary domain upgrades, and to minimise the replication time frame as changes are made during the upgrade.
        • Standardize workstation time zone configuration
          • GroupWise 7 post offices are multi-time zone capable. The GroupWise 7 client uses the workstation’s time zone configuration for timestamps and scheduling appointment times. Incorrect workstation time zone configurations result in inconsistent time stamping and incorrectly scheduled appointments.
      Preparing GroupWise
      • A healthy GroupWise system is essential to achieve a trouble free upgrade.
        • Complete a top down rebuild of the GroupWise system as described in TID10070541.
          • NOTE: This step is optional. A top down rebuild is not a mandatory part of the upgrade procedure, however it does help minimise the risk of errors occurring during the upgrade.
          • Duplicate entries and damaged GUID's can prevent the upgrade from completing the recovery of the domain database, so at the very least you should rebuild the primary domain database to confirm whether such damage is present.
      Preparing GroupWise
        • Pre-Upgrade tasks minimize service outages and overtime required for the upgrade.
        • Build and distribute a Domain and Post Office upgrade package
        • Upgrade Sequence
          • Domains
          • Post Offices
          • Gateways
          • Clients
      Performing the Upgrade
      • Before upgrading any components:
        • Backup
        • Run the GroupWise 7 installation to extend the eDir Schema
          • This task should be done several days before the upgrade takes place.
        • Check eDir schema sync status across all servers in the tree.
          • Do not proceed until your tree’s schema is synchronized.
        • Install and distribute the GroupWise 7 SDD
          • Don't update an existing SDD assigned to a post offices, create a new one.
        • Create a Domain and Post Office upgrade package.
        • Run the GroupWise 7 installation to install the C1 snapins.
          • Ensure you have ConsoleOne ver 1.3.6d or later.
        • Prepare for client distribution.
      Pre-Upgrade Tasks
      • An upgrade package contains all the files needed to upgrade domains and post offices.
        • To include the Agents (MTA and POA) for NetWare in the package run the GW7 installation to install them
          • Set the install path to an upgrade package directory, i.e. sys:systemgw7
            • Do not select domains or post offices when prompted
        • Agents for Windows or Linux servers must be installed by running the Agents install program
          • Copy the Agent startup files to the upgrade package
        • From the SDD copy the following directories to the upgrade package directory
          • clientwin32ofviewswin, domain and po
        • Distribute the package to all domain or post office servers
          • Be sure to include all cluster nodes that load a local copy of the agents
        • Configure agent startup files in the upgrade package.
      Building an Upgrade Package
        • To upgrade the MTA and POA on a NetWare server
          • Copy the files in the root of sys:systemgw7 and the sys:systemgw7help directory to sys:system
          • Be sure to include all cluster nodes that load a local copy of the agents
        • To upgrade Windows or Linux Agents run the install program
        • To upgrade a domain
          • Unload the MTA
          • copy the files in sys:systemgw7domain to the domain directory
          • copy the ngwguard.dc file from sys:systemgw7domain to <domain>wpoffice directory
          • Load the MTA
        • To upgrade a post office
          • Unload the POA
          • copy the files in sys:systemgw7po to the post office directory
          • copy the files in sys:systemgw7clientwin32ofviewswin to <post office>ofviewswin
          • Load the POA
      Using an Upgrade Package
      • The upgrade should be done in the following sequence:
        • Backup
        • Primary domain first
          • This is enforced
        • Secondary domains
        • Post Offices
          • The domain that hosts a post office must be upgraded before the post office
        • Gateways
          • The domain that hosts a gateway must be upgraded before the gateway
        • Clients
          • A users post office must be upgraded before they can use the new client
      Upgrade Sequence
        • The primary domain must be upgraded first.
          • If you don't want your production primary domain to be the first one upgraded, then either:
            • Promote another domain to be the primary or
            • Create a new domain for the upgrade process and promote it to primary.
          • Backup
          • Unload the MTA
          • Ensure exclusive access to the domain
            • No ConsoleOne connections
            • Gateways hosted by the primary domain should be down
          • Ensure POA's are up while their owning domain is being upgraded.
          • Either copy the files from the upgrade package to the domain or run the Agent installation program for the server OS.
          • Load the MTA
            • Recovers the wpdomain.db, applying the new schema from the DC file
          • Verify the database version in ConsoleOne
        • Secondary domains.
          • Repeat the procedure above, starting with the backup step.
      Upgrading Domains
        • Backup
        • Unload the POA
        • Ensure exclusive access to the WPHOST.DB
        • Either copy the files from the upgrade package to the post office or run the Agent installation program for the server OS.
        • Load the POA
          • Recovers the wphost.db, applying the new schema from the DC file
        • Verify the Post Office version in ConsoleOne
        • Connect with a v7.0 Client
      Upgrading Post Offices
        • Unload GWIA and backup the GWIA.CFG file
        • Install GWIA
          • <SDD>internetgwiainstall.exe /copyonly
          • NOTE: MTP port is a new method for MTA's to connect to GWIA. The port you specify must be unique on this host or leave as 0 for a UNC connection
        • Load, unload and reload GWIA
          • See TID10099640 if you experience problems with this step
      Upgrading GWIA
        • The WebAccess Agent and Application can be updated independently of each other:
          • The GW7 Agent cannot access pre-GW7 domains and post offices.
          • Agents older than ver 5.5EPSP3 cannot access GW7 domains and post offices.
          • The GW7 Agent can communicate with ver 5.5 or newer Applications.
          • The GW7 Application can communicate with ver 5.5EP SP3 or newer Agents.
        • Unload WebAccess
        • Install the GW7 WebAccess Agent and Application/s
          • You will be prompted to unload other GW agents, the web server and Java on the server.
          • Check the WebAccess and Document Viewer Agents configuration
        • Load the WebAccess Agent and Web Server
        • Login to confirm successful upgrade.
      Upgrading WebAccess
      • Common methods of updating the GW client:
        • ZENWorks is the most common method for deploying the Client
          • The GroupWise 7 Client is an MSI deployment
        • Distribute a new SOE image that includes the GroupWise 7 Client
          • The Client is installed using it's setup.exe
        • Distribution to individual workstations via
          • SetupIP
          • Automatic update
        • The cross-platform client for Linux is upgraded by installing the RPM packages.
        • The cross-platform client for OS X is upgraded by copying the groupwise.app file from groupwise.dmg package to the Applications folder.
      Upgrading Clients
      • Ensure that your organization benefits from the upgrade.
        • If you don't implement new features your organization will not get the full benefit of the upgrade.
          • Review the system design with a view to consolidating post offices to benefit from increased scalability.
          • Use GWIA's new MTP capability to simplify routing of internet mail
        • There are many productivity enhancing new features in the GroupWise 7 Client.
          • The new client interface is very different, and users will probably need training to take full advantage of it's features.
        • Take a fresh look at Caching mode
          • Enforces mailbox size limits
          • Address Book delta updates
          • Reduces network traffic and POA load
          • Introduces fault tolerance to the Client
      Review and implement new features
    • References
        • GroupWise 7 Upgrade Guide
          • by Danita Zanrè and Eric Raff
          • http://www.caledonia.net/gw7upg.html
        • Consultants Corner: Tips for Upgrading to GroupWise 7
          • by Gregg Hinchman
          • http://www.novell.com/coolsolutions/feature/15709.html
    •  
      • Unpublished Work of Novell, Inc. All Rights Reserved.
      • This work is an unpublished work and contains confidential, proprietary, and trade secret information of Novell, Inc. Access to this work is restricted to Novell employees who have a need to know to perform tasks within the scope of their assignments. No part of this work may be practiced, performed, copied, distributed, revised, modified, translated, abridged, condensed, expanded, collected, or adapted without the prior written consent of Novell, Inc. Any use or exploitation of this work without authorization could subject the perpetrator to criminal and civil liability.
      • General Disclaimer
      • This document is not to be construed as a promise by any participating company to develop, deliver, or market a product. Novell, Inc., makes no representations or warranties with respect to the contents of this document, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc., reserves the right to revise this document and to make changes to its content, at any time, without obligation to notify any person or entity of such revisions or changes. All Novell marks referenced in this presentation are trademarks or registered trademarks of Novell, Inc. in the United States and other countries. All third-party trademarks are the property of their respective owners.