9.3 Installing and Starting the GroupWise Windows Client

The GroupWise Windows client software is available in both the Windows version and the Linux version of the downloaded GroupWise 2012 software image. A simple installation of the GroupWise Windows client helps you test your GroupWise system as you are setting it up.

If you want, you can burn the GroupWise 2012 software image to DVDs for distribution to Windows client users. Advanced, system-wide rollout methods for the GroupWise Windows client are also available, as described in Distributing the GroupWise Windows Client in Client in the GroupWise 2012 Administration Guide.

9.3.1 GroupWise Windows Client Workstation Requirements

  • x86-32 processor or x86-64 processor

    On a 64-bit processor, GroupWise still runs as a 32-bit application.

  • Any of the following Windows versions:

    • Windows XP on a 300 MHz or higher workstation with at least 128 MB of RAM

    • Windows Vista on a 1 GHz or higher workstation with at least 1 GB of RAM

    • Windows 7 on a 1 GHz or higher workstation with at least 1 GB of RAM

    • Windows 8 on a 1 GHz or higher workstation with at least 1 GB of RAM

  • Approximately 200 MB of free disk space to install the GroupWise Windows client

9.3.2 Installing the GroupWise Windows Client from the Windows GroupWise 2012 Software Image

Install the Windows client on a Windows workstation that meets the system requirements listed in Section 2.2, GroupWise User Requirements.

  1. Run setup.exe from the root of the downloaded GroupWise 2012 software image.

    or

    If you have already copied the Windows client software to a Windows software distribution directory, run setup.exe from the root of the software distribution directory to start the GroupWise Installation program.

    In order to install from the software distribution directory, users need a drive mapped to the software distribution directory. Users also require Read and File Scan rights to the drive:\grpwise\software directory to start the GroupWise Installation program and to the drive:\grpwise\software\client\win32 directory to run the Windows Client Setup program.

  2. Select the language in which you want to run the GroupWise Installation program, then click OK.

    All available languages are included in the multilanguage version of the downloaded GroupWise 2012 software image, but you can select which languages you want to install for the GroupWise Windows client.

    The main GroupWise System Installation page appears.

    GroupWise Installation program main page
  3. Click Install More Components > Install GroupWise Client to start the client Setup program.

  4. Select the language in which you want to run the client Setup program, then click OK.

  5. Click Next to display the Setup Type dialog box.

    Setup Type page
  6. Select one of the following options:

    Typical: Installs the most commonly used components in the standard installation directory of c:\Program Files\Novell\Groupwise without prompting for further information. By default, this installs the software integration and Internet browser mail integration. A GroupWise icon is added to your desktop as well as to the Quick Launch area. However, Notify is not added to your Startup folder. This means that Notify does not run when Windows starts.

    Custom: Allows you to customize the following GroupWise Windows client functionality:

    • Languages (select as needed)

    • Software Integrations (enabled by default)

    • Internet Browser Mail Integration (enabled by default)

    • Program Folder (Novell GroupWise by default)

    • Add GroupWise to the Desktop (selected by default)

    • Add GroupWise to Quick Launch (selected by default)

    • Add Notify to the Startup folder (disabled by default)

    See Using GroupWise Windows Client Custom Installation Options in Client in the GroupWise 2012 Administration Guide for more information about installing the GroupWise Windows client.

  7. Click Next.

  8. (Conditional) If you selected Typical or Upgrade:

    1. Click Install to install the client files.

      When the client Setup program has completed, a shortcut to run GroupWise appears on your desktop and in the Quick Launch area.

    2. Click Finish to exit the GroupWise Installation program.

  9. (Conditional) If you selected Custom:

    1. Make sure each component you want to install is selected.

      Languages: Select which languages to install.

      Software Integrations: Select the applications for integration with GroupWise Document Management Services for saving and retrieving files from GroupWise libraries.

      Internet Browser Mail Integration: Sets GroupWise to be the default email program on the workstation, so that whenever the user clicks an email link on a Web page or chooses the Mail command in the browser, GroupWise starts.

    2. Click Next.

    3. Select the Program folder where you want to add the GroupWise icons.

      The default is Novell GroupWise.

    4. Select if you want the GroupWise icon added to your Desktop and Quick Launch.

    5. Select if you want Notify added to the Startup folder. This starts Notify when Windows starts.

      You can also choose to start Notify when GroupWise starts, as described in Starting Notify When GroupWise Starts in Notify in the GroupWise 2012 Windows Client User Guide.

    6. Click Next.

    7. Click Install to install the client files.

      When the client Setup program has completed, a shortcut to run GroupWise appears on your desktop.

    8. Click Finish to exit the GroupWise Installation program.

9.3.3 Installing the GroupWise Windows Client from the Linux GroupWise 2012 Software Image

Install the Windows client on a Windows workstation that meets the system requirements listed in Section 2.2, GroupWise User Requirements. The Linux GroupWise 2012 software image includes the Windows client software.

  1. On the Linux server where the Windows client software is located, set up a Samba share to provide access to the Windows client software.

    If you need assistance with this task, follow the instructions for your version of Linux

  2. On the Windows workstation where you want to install the WIndows client software, map a drive to the Samba share that you created in Step 1

    If you need assistance with this task, follow the instructions for your version of Linux:

  3. Change to the win32 subdirectory through the Samba share on the Linux server, then run setup.exe.

    Windows client Setup program
  4. Click Next to begin the installation.

  5. Skip to Step 4 in Section 9.3.2, Installing the GroupWise Windows Client from the Windows GroupWise 2012 Software Image to continue with the standard Windows client installation process.

Setting up Samba on OES Linux

In order to access the Windows client software on a Linux server, you can set up a Samba share to the client directory, either in the downloaded GroupWise 2012 software image or in the software distribution directory, if you have created one on the Linux server.

Configuring NetWare Core Protocol (NCP)
  1. In a terminal window on the OES Linux server, become root by entering su - and the root password.

  2. Enter the following command to create the NCP volume:

    ncpcon create volume volume_name /directory
    
    1. Replace volume_name with a unique name for the location of the Windows client software

    2. Replace directory with the full path to the Windows client software, for example:

      /opt/novell/groupwise/software/client
      
  3. Verify that the volume has been created:

    more /etc/opt/novell/ncpserv.conf
    

    The new volume should be listed at the end of the NCP server configuration file.

  4. Restart the Novell eDirectory daemon:

    rcndsd restart
    
  5. Continue with Installing Samba.

Installing Samba

If you installed Samba when you installed OES Linux, skip to Logging In to iManager.

If you did not install Samba when you installed OES Linux, install it now:

  1. Start YaST.

  2. Under Groups, click Open Enterprise Server, then click OES Install and Configuration.

  3. Under OES Services, select Novell Samba, then click Accept.

  4. Follow the prompts to install Novell Samba.

  5. Continue with Logging In to iManager.

Logging In to iManager
  1. Access the following URL:

    https://ip_address/nps/servlet/webacc?taskid=fw Startup
    

    Replace ip_address with the IP address of the OES Linux server.

  2. Specify the eDirectory administrator user name, such as admin.users.novell, the password for the user name, and the IP address of the eDirectory tree, then click Login.

  3. Continue with Creating a User to Manage the Samba Share.

Creating a User to Manage the Samba Share
  1. In iManager, click Users > Create User.

  2. In the Username field, specify a unique user name for accessing the Samba share from Windows, such as gwclient.

  3. In the Last name field, provide a last name because it is a required field.

  4. In the Context field, browse to and client the eDirectory context where you want to create the new User object.

  5. Type, then retype the password for the new user.

    IMPORTANT:Any users who map a drive to the Samba share need to know this user name and password in order to map the drive.

  6. Click OK to create the Samba user for the Windows client Samba share.

  7. Click Users to close the Users menu.

  8. Continue with Configuring the eDirectory Universal Password for Samba.

Configuring the eDirectory Universal Password for Samba
  1. Click Passwords > Password Policies.

  2. Click Samba Default Password Policy.

  3. On the Policy Assignment tab, browse to and click the name of the Samba User object that you created in Creating a User to Manage the Samba Share, then click OK to add the user to the list.

  4. Click OK to complete the process.

  5. Continue with Setting the eDirectory Universal Password for the Samba Administrator User.

Setting the eDirectory Universal Password for the Samba Administrator User
  1. Under Passwords, click Set Universal Password.

  2. Browse to and click the name of the Samba User object, then click OK.

  3. Specify the password for the Samba user, retype the password for confirmation, then click OK.

  4. Click Passwords to close the Passwords menu.

  5. Continue with Creating a Samba Share.

Creating a Samba Share
  1. Click File Protocols, then click Samba.

  2. Browse to and click the name of the Server object where you are setting up the Samba share.

  3. On the Shares tab, create a new Samba share for the client directory on the Linux server:

    1. Click New.

    2. Specify a unique name for the Samba share, such as gwclient.

    3. Specify the full path name to the client directory on the Linux server, for example:

      /opt/novell/groupwise/software/client
      
    4. Select Read-Only.

      Write access is not required in order to install the Windows client software from the Linux server.

    5. Click OK to add the location to the list of Samba shares, then click Close.

    6. Click File Protocols to close the File Protocols menu.

  4. Continue with Setting the eDirectory Rights for the Samba Share.

Setting the eDirectory Rights for the Samba Share
  1. Click Files and Folders, then click Properties.

  2. Browse to and click the name of the Linux partition or directory where you created the new share, then click OK.

  3. Click Rights.

  4. In the Add Trustee field, browse to and click the name of the Samba User object, then click OK.

  5. Under Inherited Rights Filter, select Read, then click OK.

  6. Continue with Testing Samba on the OES Linux Server.

Testing Samba on the OES Linux Server
  1. Double-click the Home Directory icon on the Linux desktop.

  2. Click Windows client Setup program

  3. In the Location field, type smb://user_name@ip_address

    1. Replace user_name with the user name of the Samba administrator user.

    2. Replace ip_address with the IP address of the Linux server.

      The File Browser should display all Samba shares, including the new one that you created for the Windows client software.

  4. Return to Step 2 in Section 9.3.3, Installing the GroupWise Windows Client from the Linux GroupWise 2012 Software Image

Mapping a Drive to a Samba Share on an OES Linux Server

  1. On the Windows server, right-click Windows client Setup program on the Windows taskbar, then click Novell Map Network Drive.

  2. Select the drive letter to map to the NCP volume on the OES Linux server.

  3. Specify the network path to the NCP volume in the following format:

    \\linux_hostname\ncp_volume
    
    1. Replace linux_hostname with the hostname of the OES Linux server.

    2. Replace ncp_volume with the name of the NCP volume that you just created.

  4. For the network user name, specify the fully qualified Samba user name for eDirectory., such as gwclient.users.novell.

  5. Click Map.

  6. Click OK.

    The mapped drive to the OES Linux server opens in Windows Explorer and can now be accessed from Windows.

  7. Return to Step 3 in Section 9.3.3, Installing the GroupWise Windows Client from the Linux GroupWise 2012 Software Image.

Setting Up Samba on SLES

In order to access the Windows client software on a Linux server, you can set up a Samba share on the Linux server to the client directory, either in the downloaded GroupWise 2012 software image or in the software distribution directory, if you have created one on the Linux server.

Preparing Your Firewall to Allow Samba Connections
  1. In YaST, click Firewall, then click Interfaces.

  2. Click Change, select Internal Zone, then click OK.

  3. Click Next to view the summary, then click Finish.

  4. Continue with Configuring the Samba Server.

Configuring the Samba Server
  1. In YaST, click Network Services > Samba Server.

  2. Specify a workgroup or domain name, then click Next.

    For use in your GroupWise system, the Samba server does not need to be part of a workgroup or domain, so it does not matter what you put in this field. For example, you could use GWCLIENT.

  3. Select Not a Domain Controller, then click Next.

    For use in your GroupWise system, the Samba server does not need to be a domain controller.

  4. Under Service Start, select During Boot.

    Because you prepared the firewall in Preparing Your Firewall to Allow Samba Connections, the Firewall Settings section shows that the firewall port for Samba is already open.

  5. Click OK to finish the basic configuration of the Samba server.

  6. Continue with Configuring the Samba Web Administration Tool (SWAT)

Configuring the Samba Web Administration Tool (SWAT)
  1. In YaST, click Network Services > Network Services (xinetd).

  2. Select Enable.

  3. In the Currently Available Services list, select swat, then click Toggle Status (On or Off).

    SWAT is off by default; this turns it on.

  4. Click Finish.

  5. Continue with Accessing SWAT

Accessing SWAT
  1. Display SWAT in your Web browser with the following URL:

    http://localhost:901
    
  2. Specify the root user name and password, then click OK.

  3. On the SWAT toolbar, click Status to verify that smbd and nmbd are running.

    It is not necessary for winbindd to be running.

  4. Continue with Setting the Samba User Name and Password.

Setting the Samba User Name and Password
  1. On the SWAT toolbar, click Password.

  2. In the User Name field, specify a unique user name for use when mapping a drive to the Samba share, such as gwclient.

  3. Type, then retype, the password for the new user, then click Add User.

    IMPORTANT:Any users who map a drive to the Samba share need to know this user name and password in order to map the drive.

  4. Continue with Creating a Samba Share.

Creating a Samba Share
  1. On the SWAT toolbar, click Shares.

  2. In the Create Share field, type a unique name for the share, such as gwclient, then click Create Share.

  3. In the Path field, specify the full path name to the client directory on the Linux server.

  4. Leave the Read Only field set to the default of Yes.

    Write access is not required in order to install the Windows client software from the Linux server.

  5. In the Available field, select Yes.

  6. Click Commit Changes.

    The Samba share on the Linux server is now ready for access from a Windows workstation.

  7. Return to Step 2 in Section 9.3.3, Installing the GroupWise Windows Client from the Linux GroupWise 2012 Software Image.

Mapping a Drive to a Samba Share on SLES

  1. In Windows Explorer, right-click the Computer object, then click Map network drive.

  2. In the Drive field, select the drive letter for the new Samba share.

  3. In the Folder field, specify the location of the Samba share in the following format:

    \\ip_address\share_name
    
    1. Replace ip_address with the IP address of the Linux server.

    2. Replace share_name with the name of the new Samba share where the Windows client software is available.

  4. Deselect Reconnect to logon.

  5. Select Connect using different credentials.

  6. Specify the Samba share user name and password, then click OK.

    The Samba share for the OES Linux file system opens in Windows Explorer and can now be accessed from Windows.

  7. Return to Step 3 in Section 9.3.3, Installing the GroupWise Windows Client from the Linux GroupWise 2012 Software Image.

9.3.4 Implementing System-Wide Windows Client Rollouts

For a system-wide rollout of the GroupWise client software, see Distributing the GroupWise Windows Client in Client in the GroupWise 2012 Administration Guide.

9.3.5 Starting the Windows Client

At startup, the Windows GroupWise client needs to know the location (IP address/hostname and port number) of the user’s post office. There are three ways that the client can get this information:

  • If the user is logged into eDirectory, the GroupWise client can read eDirectory for the post office’s location.

  • If the user is not logged into eDirectory, the GroupWise client can use a GroupWise name server to get the user’s post office location.

    A GroupWise name server is a DNS hostname entry that defines the IP address of the post office’s POA. During startup, the GroupWise client automatically looks for the GroupWise name server in DNS. For information about creating a GroupWise name server, see Post Office Agent in the GroupWise 2012 Administration Guide.

  • The user can provide the post office location when prompted.

To start the GroupWise Windows client for the first time:

  1. Double-click the GroupWise icon on the Windows desktop.

  2. Enter the password and post office address information, then click OK.

See also Getting Started in the GroupWise 2012 Windows Client User Guide.