One of the big questions when installing a new Windows server is whether or not to install eDirectory on the server itself. This really depends on your GroupWise infrastructure. The simple fact is GroupWise needs eDirectory. Somewhere. This does not necessarily mean that each GroupWise server needs eDirectory. If you are a NetWare Administrator, you know that every NetWare server runs eDirectory, and each server is installed “into” the tree. Not every NetWare server needs to have an eDirectory partition on it though. This is the same for GroupWise servers. While you CAN install eDirectory onto every Windows server that houses GroupWise components, it is not a requirement. As long as there is one eDirectory server in the network to manage eDirectory authentication, then GroupWise will work.
If you are planning on migrating entirely to Windows, then you will need to install eDirectory on at least one GroupWise server. Plan on putting a Windows eDirectory server everywhere that you would normally place an eDirectory replica for the most part.
Rather than reinventing the wheel, we point you to a very good App Note on installing eDirectory on Windows. If you are in a situation where you need eDirectory on your Windows server (i.e., you will have no NetWare or OES2 Linux servers in your network), then use this guide to get eDirectory installed on your Windows server:
NOTE: While these instructions are for 8.7.3, the 8.8 installation is very similar, and preferred for Windows and Linux servers.
You will need to install the Novell Client for Windows on any Windows server that will install and run GroupWise agents. If you do not have the Novell Client installed on your server, you can download it from http://download.novell.com.
While it is not explicitly required that ConsoleOne be installed on the Windows server (ConsoleOne can be run from workstations of course), it is convenient to have it there. We will install ConsoleOne on the Windows server.
Click on the file name to go go the download window (in our example this is ConsoleOne 1.3.6h). At the next screen, be sure to choose to download ConsoleOne for Windows. After the file is downloaded, run c1.exe to install ConsoleOne.
Most of the questions you are asked should be self-explanatory. When asked which snapins to install, we typically choose “all” just in case we ever need these snapins.
NOTE: You will not see the GroupWise Administration snapins listed here. Those are installed in the GroupWise installation below.
GroupWise Administration Snapins
Once ConsoleOne has been properly installed, we will move on to installing some GroupWise files.
To install the GroupWise ConsoleOne snapins, download the Windows software for the version of GroupWise you have. You should be able to find the GroupWise distribution for your version at http://download.novell.com. See Figure 2-2 for downloading software from the Novell download site.
Extract the files into a directory of your choosing. This can be the location which you intend to serve as your Software Distribution Directory on this server. After the files are extracted to a location accessible from the Windows server, run the setup.exe found in the root of the extracted software directory. Our installation here is using GroupWise 8.0. Your agent installation may vary slightly. When you run this program, you see the Window in Figure 2-3.
- Click on Install GroupWise System.
- Click Yes on the next screen to accept the license agreement.
- Click Next on the next screen to do a standard install. You will see the window in Figure 2-4.
- Install Wizard – GroupWise Components
- Choose GroupWise Administration and click Next.
- At the next screen, check only the Install administration files option.
- You will then verify the location of ConsoleOne on your Windows server.
- The snapins will install.
If you will be moving a post office to a Windows server, you will want to have access to Novell’s DBCopy utility. This is found in the \admin\utility directory of your software distribution. You can copy the DBCopy files to another directory on your Windows server, or simply run the program from the directory in the software distribution.
With these additional programs installed, we can now start our GroupWise components move. We will begin with a domain move in the next chapter.
Throughout this Section on moving to a new Windows server, we will be discussing three different types of servers: NetWare, Linux and Windows. Unless the information is specific to a particular server OS, we will simply reference the “Source” server. So, no matter where you are “coming from” you will be able to get your GroupWise components moved to a new Windows server.
First, let’s look at some of the reasons why you might be moving your GroupWise components to a new Windows server, and point out which chapters of this section will be for you!
- Your GroupWise components are already on Windows, but you are upgrading to new hardware, reconfiguring your network, or any other myriad of reasons why you might need to relocate GroupWise.
- Everything is moving to a new Windows server. If you are moving all of your GroupWise system to a new Windows server, and you have a small system, you may be moving your domain, gateways and post office together to Windows in a very short period of time. If you are moving a domain that has no gateways (for example, a primary routing domain, or a domain that only owns post offices), we will discuss how to do this in “Moving a Domain with No Gateways – Windows”.
- You wish to move your GWIA to Windows. As you probably know, Novell’s Best Practices for GroupWise highly discourages the idea of having a gateway on a server remote from its domain. Any time we put a gateway on a server, we need to have a domain there. So, if you wish to move your GWIA to Windows, you will need to move the domain that owns that GWIA as well. For some sites, moving the domain and GWIA together is quite simple, and we will go through the steps for this in the chapter “Moving a GWIA – Windows”. For others, you might need to create a new domain and effectively install a new GWIA, rather than actually “moving” the domain and existing GWIA. We will discuss how to do this in the “Creating a New Domain on Windows to Relocate a Gateway” chapter.
- You wish to move your WebAccess Agent to Windows. Again, we do not want to have the WebAccess Agent on a server that is remote from its domain. We will move a domain and WebAccess Agent to Windows in the chapter entitled “Moving WebAccess – Windows”.
- You wish to move a Post Office to Windows for deployment in a remote office.
As we move through this section on Windows, we will address each of these ways to move a GroupWise components to a new Windows server.