If you’ve been thinking about deploying an alternative groupware platform to Exchange, but don’t want to abandon Windows 2000, you’re in luck. Older versions of GroupWise were a NetWare-only affair. With recent versions, not only will GroupWise run on Windows, but you can also install it without having a NetWare server on the network. Here’s what you’ll face installing the newest version of GroupWise—version 6.5—on a Windows 2000 server.
My Windows 2000 server, win2kgw, is running as a stand-alone machine—not part of an Active Directory domain. I've installed eDirectory 8.7 for Windows 2000 on this server. My NDS tree is named NDS-2K. GroupWise requires an eDirectory installation in order to operate. For instructions on installing eDirectory on Windows 2000, see the Daily Drill Down "Expand Windows 2000 server options with Novell's eDirectory." Installing GroupWise on a Windows 2000 server or a NetWare server is a similar process. For more information about installing GroupWise 6.5 on NetWare, see the Daily Drill Down "Preparation is key when installing GroupWise 6.5."
To begin the installation, insert the GroupWise Admin CD into the CD ROM drive of the server on which you wish to install it. If Autorun is enabled on the server, you will see a GroupWise 6.5 installation menu. If the installation menu doesn’t appear, browse to the root of the Admin CD and double-click Setup.exe.
As with most Windows Setup wizards, the first screen of the installation contains a license agreement. Read the license to make sure you can abide by it. You must agree to it before you can continue the product installation.
Setup will then check the version of eDirectory running on your Windows 2000 server to see if you’ve previously installed a copy of GroupWise on your server. If you’ve never installed GroupWise, Setup will create a new system and extend the NDS schema to add support for the GroupWise fields. Setup will also install administration files and create a software distribution directory. This directory will later be used to install GroupWise agents and clients.
The first decision that you need to make is to determine the NDS tree in which to install GroupWise. You’ll do this on the Select Tree screen shown in Figure A. Since I want to install this system into my Windows 2000 NDS tree—NDS-2K—I will select that tree name from the list. Once selected, the installer will check to see whether or not the tree has been previously extended to support GroupWise 6.5. If it has not, the installer will do so.
|The Select Tree screen offers options for choosing the NDS tree.|
With an extended NDS, you need to add support for the new fields in ConsoleOne. This is accomplished by extending ConsoleOne with GroupWise Administrator files. Setup needs to know the location for ConsoleOne and will ask for it in the next step of the installation. For my Windows 2000 server, ConsoleOne is located in C:\Novell\ConsoleOne\1.2. ConsoleOne 1.3.4 or later is required for GroupWise.
Setup requires a location in which to put the GroupWise files related to agent and client installation files. When you see the Software Distribution Directory screen shown in Figure B, you’ll specify this location. For my installation, I put these files in C:\Grpwise\Software and will specify this information in the next step of the installation.
|Provide a location for the software distribution directory.|
After you click Next, you’ll see the Select Software screen shown in Figure C. Here you specify the GroupWise components you want to install. Among the options are the agent files, the client software, and ConsoleOne Snap-ins. For the purposes of this Daily Drill Down, I will select all of these options.
|What should go in the software distribution directory?|
When you click Next, Setup will begin to copy files to your server. This step will take quite some time as Setup checks your server for previous versions of software before files are finally copied.
After all of the files are copied, you determine whether this will be a new system or an upgrade of an existing system. Since I do not have a GroupWise system in this tree, I will choose to create a new GroupWise system. This will launch ConsoleOne, which is used for the remainder of the system configuration. If you’ve gone through the NetWare installation from my previous article, this process will be very familiar because directory names are the only significant change.
When Setup finishes copying all of the files, there's still some work to do, but this time it’s from within ConsoleOne.
The ConsoleOne GroupWise system creation wizard
The GroupWise Setup wizard should start ConsoleOne automatically. If it doesn’t, start ConsoleOne on your server. ConsoleOne will start with another GroupWise System Setup wizard that will walk you through the steps needed to get your GroupWise system up and running.
The first screen you’ll see is the Software Distribution Directory screen shown in Figure D. Here you’ll enter the directory that you provided earlier specifying the location of the software distribution directory. For my demonstration, this is C:\Grpwise\Software. This location will need to be used by administrators and clients alike.
|Specify the location of the software distribution directory.|
When you click Next, you must provide the name of the NDS tree in which you wish to create your new GroupWise system. As mentioned before, my tree name is NDS-2K. Enter that information where requested and move on.
You’ll then see the System Name screen shown in Figure E. The system name is used to describe your overall GroupWise system. It organizes your various domains. For my example, I'll name this system Scotts GW System.
|I have named my GroupWise system Scotts GW System.|
Then, you’ll see the Primary Domain screen shown in Figure F. Don’t confuse a GroupWise domain with your Windows 2000 domain. The GroupWise domain organizes post offices and represents physical locations. Enter the name of your domain in the Domain Name field. For my example, I entered lab as the name of my first domain.
|In the Domain Name field, I entered lab.|
After you’ve specified the domain name, you must tell GroupWise where to store the domain files. You’ll do so on the Domain Directory screen shown in Figure G. I like to keep a subdirectory for each domain under a master directory. Therefore, my first domain will reside in C:\Gw\Lab.
|My domain directory location is indicated on the Domain Directory screen.|
Setup then asks some basic NDS questions. You must specify the name of the container in your NDS tree where you want to store GroupWise objects. You must also specify the language you want to use and the time zone for your server.
After you’ve specified the NDS information, you must name your Post Office. You’ll do so on the Post Office Name screen shown in Figure H. I entered home as the name of my first post office, which is contained inside the Lab domain of Scotts GW System.
|My first post office is named Home.|
Like the domain, the post office has files and directories specific to it that need a home. However, the location cannot be the same as the domain. You’ll specify these locations in the Post Office Directory screen shown in Figure I. Therefore, I will use C:\Gw\Lab\Home for this purpose.
|Post office file location is indicated on the Post Office Directory screen.|
As with the GroupWise domain, you must specify the container in your NDS tree where you want to store Post Office information. The NDS objects will be located in the same container as the domain files—lab.nds-2k. Post Office objects will also use the same language and time zone you specified.
Your Message Transfer Agent and Post Office Agent have two ways that they can communicate: TCP/IP or direct access to the files. You’ll specify how GroupWise communicates on the Post Office Link screen shown in Figure J. I recommend choosing TCP/IP as the default communication mechanism and setting up the appropriate parameters on the next screen of the installer.
|Choose TCP/IP for interprocess communication.|
Finally, you get a choice to add GroupWise mailboxes for your users. I will skip this step for now and create mailboxes later.
The next few screens of the installer verify the information provided during the steps and then carry out your instructions. During the final process, you are asked for which type of system you wish to install—NetWare or Windows. Choosing Windows results in additional steps in the wizard.
First, you’ll see the Installation Path screen shown in Figure K. Here, you need to decide where you want Setup to install the GroupWise agents. This path will allow you to run the agents directly from the server. I will use the default of C:\Grpwise for this example.
|Install the agents as Windows services in C:\Grpwise.|
When GroupWise starts on your Windows 2000 server, it runs as a service. When a service is run on Windows, it can be run as the local system or as a specific user. On the Windows Service Information screen shown in Figure L you can specify the account that GroupWise uses to run. For this example, I will allow the agents to run in the context of the local system account and to start up automatically. You can select Use This Windows Account to specify a different user.
|System service configuration is shown on the Windows Service Information screen.|
At the end of the process you are notified that everything was installed. Click the Finish button to start the agents.
To create users in your new GroupWise system and give them mailboxes, go through the normal user creation process in ConsoleOne. Once you have provided the necessary parameters, such as a login name and surname, click the GroupWise tab and provide the name of a post office for the user’s mailbox, as shown in Figure M.
Not just for NetWare anymore
GroupWise installs and runs as easily on Windows 2000 as it does on NetWare. If you want an alternative to Exchange, but don’t want to run a different operating system, you’ve got a proven solution from a reliable company.