Consultant's Corner: Bonsai's Connection to the Administrator

"Adventure. Heh! Excitement. Heh! A Jedi craves not these things." Yoda

As a GroupWise administrator or consultant or otherwise, I am going to lay odds you do not seek adventure or excitement with GroupWise, usually because that means problems. Not that working with GroupWise is boring – quite the opposite. But who really seeks problems?

In this installment, I will go through some of the new things in Bonsai that are "administrator facing," meaning that they are for the administrators to use. When managing GroupWise, as you know, ConsoleOne is the utility. There are several places an administrator can go to configure GroupWise: the first on the list is Tools > GroupWise System Operations. This provides a large list of system settings.

Figure 1: GroupWise System Operations -New items

System Preferences

First on the GroupWise System Operations list is System Preferences. This is the place where administrators can set various items that make administering GroupWise easier, such as a default password for new accounts, Nickname Settings when moving mailboxes, and Admin Lockout Settings that allow the administrator to keep some people's “light sabers” off the GroupWise system. New to this list are Archive Service Settings and Calendar Publishing Settings.

Archive Service Settings allows the administrator to link an Archive Trusted Application as a default setting. This system preference is directly linked to those Trusted Applications you have set up in the GroupWise System Operations > Trusted Application location. The Calendar Publishing Settings feature turns on published calenders. Once Web Calendaring Hosting is set up an administrator can set system-wide availability of the published calendars. This feature can be set at the domain and post office levels as well - it's off by default. See the figures below.

Figure 2: System Preferences -Archive Service Settings

Figure 3: System Preferences -Calendar Publishing Settings

Internet Addressing

One would think that Internet Addressing cannot change much, but it did. First, the developers changed the presentation. Instead of the good old single page, there are now three pages: Internet Domains, Addressing Formats, and Publish to eDirectory.

Internet Domain page – has the information you are use to seeing, such as Internet domains and default GWIA for outbound SMTP. This page is where new Internet domains are created, edited, deleted, or set as the system default.

Addressing Formats page – where Preferred Address Format is set, along with other allowable email address formats.

Publish to eDirectory page – brand spanking new. This new feature is used to keep email addresses in GroupWise and eDirectory in sync. But it goes a step further, and offers the administrator the option to post various email addresses from the Allowable email addresses list, Nickname email addresses and Gateway Alias email addresses into the eDirectory user object General Tab, Email Address property. See the figures below.

Figure 4: Internet Addressing -Internet Domains

Figure 5: Internet Addressing-Addressing Formats

Figure 6: Internet Addressing-Publish to eDirectory

Figure 7: eDirectory User Properties-General Tab-Email Address Property

Web Calendar Publishing Host

Meanwhile, the Web Calendar Publishing Hosts allows the administrator to set hosts (web servers) that can be used by those in/not in the GroupWise system for accessing user calendars across the Internet. Web Calendar Publishing is a new feature for users with Bonsai. Those accessing a user's published calendar can do busy searches and view those calendars available to them. In setting up a Host, a web server is needed that already has WebAccess set up on it with the new Calendar Publishing. Then the administrator can point to that web server and give the Web Calendar Publishing Host a URL for users, which can be tied to an IP address and port. Of course, for the security-conscious, SSL is available. I mean really, it's GroupWise – of course there is SSL security. See the figures below.

Figure 8: Web Calendar Publishing Host

Figure 9: Web Calendar Publishing Host-Configuration

GroupWise Utilities

OK, I will confess: this is not a new feature in Bonsai. But there is a new tie-in to Bonsai. In Tools > GroupWise Utilities is a relatively new feature that showed up around the time of the GroupWise 7 SP 1 . It's called Gateway Alias Migration, and it's a great utility to help administrators look at their (usually) SMTP gateway aliases.

So what is a gateway alias? Well, the best definition I can give is that it's an alternate email address, assigned at the GWIA, for non-GroupWise format systems. For example: You create an External domain in your GroupWise system that holds user names and ties those user names to or email accounts. The point? These users are not members of the GroupWise system, but you want their names/email accounts to appear in the GroupWise address book for your users.

There are other examples as well. Take a user in the GroupWise system that wants to be known as a different email address. Say John Smith ( wants to be known as . These are some are valid reasons for having a Gateway Alias, but I have found that the vast majority of customers have Gateway Aliases and are not sure why.

Enter the dragon! Oh, sorry – wrong movie theme – Attack of the Clones (or Gateway Alias Migration Utility). The Gateway Alias Migration utility will help the administrator go through the aliases and convert them to proper Preferred email addresses. Why do you want to do this? Well think of it this way: if the Gateway Alias is set up in the old style in order to give someone a Preferred Email address at the GWIA versus the system default, then you have to manage email addresses in two locations. Using the utility, you can convert those Gateway Aliases (that are really Preferred Email Addresses) to Preferred Email Addresses, which are seen in the User Properties > GroupWise > Internet Addressing window. Huh?

OK, I know it's a bit confusing, so let's go back to John Smith. Let's say in the old days of GroupWise a Gateway Alias was set up for John as . But today, you have that option in the System Operations > Internet Addressing, so there's no need to have the Gateway Alias. Use the utility, and you can convert John's email account to Preferred – or really, in this case, a system-available email address. Now let's take a look:

Figure 10: GroupWise Utilities-Gateway Alias Migration

Once you open the Gateway Alias Migration Utility, it will search the system for all Gateway Aliases and show you both the alias and the object ID. You can then decide to migrate or not.

Figure 11: GroupWise Utilities-Gateway Alias Migration

Here comes the Bonsai tie-in. In the Properties of the User under the GroupWise tab, on the Internet Addressing Tab, is a new View Email Addresses button. OMG! This might be the best new feature for GroupWise administrators yet! With this little button you can now see all email addresses (formats) tied to the user, including Nickname and Gateway Aliases! Tell me this does not break your Jedi resolve and make you excited! OK, deep breath and focus ...

Back to the previous example. In the figure below you can see that I have a '' Gateway Alias, which is a duplicate of the Allowed Email Address ''. Say it with me – “Duplicate”! Obviously, this Gateway Alias is not needed and is just clogging up the GroupWise system and confusing administrators. You can set the Preferred Email Address or just delete the Gateway Alias.

Figure 12: User Properties-Internet Addressing-View Email Addresses


Well, this little adventure is at an end. As you can see, there are quite a few new features that will make GroupWise administrators' lives easier, as well as help them clean up an older GroupWise system. It's quite obvious that Bonsai will allow administrators to connect to their upgraded systems. It's a wrap! I hope the excitement did not 'Force push' you too far. “Mind what you have learned. Save you it can!”

Got comments or article ideas? Need help with GroupWise? Drop me a line at: “The Force is strong in this one.”


How To-Best Practice
Comment List