The IT GroupWise system has been updated with the latest patch from Novell and updated desktop clients are available from the IT Download site. If you are seeing “odd” behavior with GroupWise, try installing the updated version first.

The Build Number (Help > About GroupWise) is 92614.

There will be a scheduled outage of the main campus GroupWise system on Sunday March 13, 2011 from 8:00 AM – Noon. We’ll be expanding the files system to accommodate system growth. Expect the system to be unavailable for most of the maintenance window.

From IT Alerts:

The GroupWise Mailbox Size display, which became disabled after a recent upgrade, will be
re-enabled for all main campus GroupWise users starting Wednesday, March 9. Mailbox Size
will again be shown in the bottom right of the GroupWise Windows desktop client or as a
bar graph displayed in the upper right of GroupWise Web Access. There is no Mailbox Size
display in the GroupWise Mac client.

For more information, see the IT GroupWise Support Page (http://it.unm.edu/groupwise) or
contact the main campus GroupWise administrator at gw8@unm.edu or
GroupWise Instant Messenger contact gw8.

Due to all the spam that gets posted or attempts to get posted here (for some reason) the comments have been pretty much disabled. We’re looking into move to a bulletin board system.

Make a rule in GroupWise to automatically reply mis-addressed email. Using the GroupWise Windows client, go to Tools menu, Rules item:

Click New… button. New Rule window opens.

Rule Name (can be any text)
When event is set to New Item and activate Recived check box.
If conditions are activate Mail checkbox and click Define Conditions… button. Define Contiditions dialog window opens.

Include Entries where…
To = (Matches)
@salud.unm.edu
Click OK

Then actions are area

click Add Action button, choose Reply … from menu. Reply dialog window opens.

Active Reply to sender dot (default)
Activate Include message received from sender. Click OK. Reply dialog window opens

Type appropriate message. Click OK

In New Rule window, click Save

In Rules Window, be sure the new rule is active (check mark) and click Close.

We’re always getting calls about problems with managing meetings and appointments. Because of all the possible options that the user may or may not recall following it is almost impossible to say why any specific meeting hasn’t behaved as anticipated once the action has been taken. Searches through system log files may reveal what might have happened but isn’t efficient use of limited resources to reveal particular issues of usage rather then errors in the application.

Instead we ask the user to attempt to replicate the issue and document the steps followed. This will often reveal mis-understanding or mis-usage that can be resolved by a visit to the Help menu or the IT Groupwise Support page. If the issue can be replicated consistently then an Incident Management report should be opened.

Here’s some tips for troubleshooting:

Novell uses the term Appointment to refer to item you create (Post) for your self and Meeting (Send) for single or recurring event that include other users or resources.

If you create and send a Meeting, you are that event’s owner. If you receive a meeting from someone else, you are an invitee.

Meetings can be modified directly on the calendar by right clicking on it to see the context menu or even dragging to change the time. If you don’t see the meeting on the calendar then look in your Sent Items folder. (Of course, only meetings that you’ve sent will be in your Sent Items.)

An invitee can decline, delete, delegate and move a meeting but only for themselves. Any change an invitee makes will only be reflected on their own calendar.

Both owners and invitees can delegate a meeting to another user. Add the delegated invitee to any field of the compose meeting view that is presented. Only the new invitee will receive a notification.

Right click and choose Open to see who owns the meeting as the From: address.

A meeting owner can modify a meeting in several ways from the context menu. If these options are not on right click menu it means you don’t own the meeting and can’t modify it for other users.

• They can delete meeting with the option withdraw it from every invitee’s calendar and/or every instance of a recurring meeting. If the withdraw option is presented then you don’t own the meeting. An notification will be sent to all the invitees.
• If the details of the meeting, for instance the title, notes, or location, need to be changed, use the Resend item. The meeting create view will be presented and any of the fields can be edited. When the Send icon is clicked GroupWise will ask if the original item should be retracted. In most cases the answer will be Yes unless some tracking or history of the event is required. A notice with the changes will be send to all invitees.
• If more invitees need to be added to an existing meeting, the owner can use the Modify Recipients item. This will present a dialog that you can add invitees to To:, CC:, and BC:. Notification is sent only to the new invitees.

UPDATE: This issue has been resolved by a setting change applied on 11/08.

Issue: GroupWise user is sending to non-GroupWise user, the non-user’s NetID matches a GroupWise account name in the newly expanded address book. Auto complete finds the GroupWise user and the messages is delivered to that Mailbox instead of going out of GroupWise.

Issue: GroupWise address auto complete now finds a Salud address for an UNM Net ID.

Problem: The GroupWise user is mis-addressing their message and need to type in <NetID@smtp.unm.edu> and or add that to Frequent Contacts or other personal address book. This was an unannounced usage change not revealed in testing.

For More information:

Adding a contact (Windows)

https://unm.custhelp.com/cgi-bin/unm.cfg/php/enduser/std_adp.php?p_faqid=5893

Adding a contact (Mac)

https://unm.custhelp.com/cgi-bin/unm.cfg/php/enduser/std_adp.php?p_faqid=2765

Address book, auto complete, and troubleshooting

https://unm.custhelp.com/cgi-bin/unm.cfg/php/enduser/std_adp.php?p_faqid=3467

Also the GroupWise Help menu > Help Topics will have information on using personal address books.

.

IT GroupWise users may have seen some UNMH or UNM-HSC announcements this morning. This was in error and is being corrected.

Workaround: If the user answers ‘No’ to the upgrade question, IM will work normally but the user will be asked to upgrade on each login.

Upgrade: If the user can’t answer Yes, the installation executable can be downloaded from http://gwim.unm.edu:8300. I’m getting the IT GWIM page updated now. The latest version is 2.1 and is called Novell Messenger now. My guess is that it will install in C:\Novell\Messenger by default in and upgrade or C:\Program Files\Novell in a fresh install.

Settings: Be sure the login (click the advanced button at the login screen) is set to the host name gwim.unm.edu and not an IP address.

See other posts for login issues.

User of Pidgin are reporting they have to delete and re-add their accounts.

I’ll post about new and outstanding eDirectory merge issues by here, with updates as needed. Feel free to pass this url around as needed.

If using an IMAP connection in GroupWise to access folder to a non-GroupWise system such as UNM Webmail, the password used by GroupWise to login to that system isn’t updated automatically. It has to be changed by the user when ever the password is changed.When using an IMAP connection in GroupWise to access folder to a non-GroupWise system such as UNM Webmail, the password used by GroupWise to login to that system isn’t updated automatically. It has to be changed by the user when ever the password is changed.

In GroupWise:

1. Go Accounts menu, Account Options item.
2. In Accounts window, highlight IMAP account, click Properties button.
3. In Account Properties window, select Server tab.
4. Change Password in the Incoming mail server (IMAP4) section.
5. Click OK, then Close to return to GroupWise main window.
6. Go Account menu, Send/Retrieve item to test.

Sometime, the GroupWise IMAP account becomes corrupted and must be recreated to restore functionality. This can be done with out affecting messages on the IMAP server.

If an identical account name (NetID) for the Salud system is in the IT-GroupWise address book, then neither user will not be able to log in to GroupWise Webaccess. The workaround is use a fully qualified GroupWise user name in the account name field to force a login against the users own domain. Use the following form:

DOMAIN.POSTOFFICE.accountname

Example:

If the account name (NetID) is gw8, then enter  UNMDOM.GWPO1.gw8

Several users have asked about this after switching to GW8.  When you reply to an email, the compose field is often blank. This is because the person is either selecting part of the text in the original email (and only that text is included in the reply) or selecting a space by accident and the email is blank when replying.

This is default behavior and not user configurable in the current release (8.0.1 HP1).

Dean Lythgow, Director of GroupWise Engineering for Novell, wrote in his blog.

New to GroupWise 8 is the capability to select some text in a message you are readying and when you hit ‘Reply/Forward’, ONLY that text is included in the new message. Some users have found this new feature to be one of the most ‘productive’ features in all of GroupWise 8. While others have told us that this is the ‘dumbest’ feature in the entire product. Sometimes you just can’t win!!

Some users struggle because they did not realize or did not remember that they had selected text when they hit ‘Reply/Forward’. Then when the new message appeared and not all of the text was included, they become very frustrated.

This is another feature that is included in most of our competitor’s products. This feature was included because it was requested by many customers and end-users. It was a relatively easy feature to implement and therefore became a feature that we have highlighted and advertised as one ‘we’ really like.

GroupWise Windows client seems to prefer a rather old version of the mapi library files, which it installs. If those .dlls get corrupted or Window Messaging Service gets uninstalled from the Control Panel the user will see error messages referring to mapi or experience general addresses look up failures when composing messages and adding proxies or shares.

The Fix is to re-install the .dlls using wms.exe. This executable comes with the GroupWise Window client install files  (\win3232\wms\nt\us\wms.exe) or I put a copy on my GW8 support page (http://www.unm.edu/~gw8). The system must be restarted after wms.exe is run.

Note: Running wms.exe will install a GroupWise compatible  mapi profile that the user may get prompted to use if they launch Outlook. The default profile can be set in Outlook or the Mail control panel.

In the process of moving users to new post offices, we’ve seen where the account that has received proxy lose access to some accounts. The general rules for fixing proxy problems apply:

1. Remove the problem account (including any duplicates) from the proxy recipients list on File > Proxy… Close, then relaunch GroupWise. Re-add the account in File > Proxy… Click OK and you should be put in that account automatically.

2. In some cases, the Proxy source has to remove their offer (Tools>Options>Security icon>Proxy tab). Restart and re-offer the proxy. Be sure to use the same Access rights. The user the account was offered to should remove the account from their list before and re-add it after the offer is remade.

3. Use the GroupWise 8 client. There are some bug fixes and improvements in the Proxy features.

For some lists and views (but not everything), GroupWise picks up the text font and size from Windows. If it is not to your liking it can be changed by modifying the Appearance settings.

Note: Changing themes, or logging into a workstation using an account that uses a different theme can result in text appearance changes in GroupWise.

Modifying appearance is a somewhat different process depending on Windows Version:

XP

1. Right-click the desktop, choose Properties from context menu. Opens Display Properties dialog.
2. Click Appearance tab, then Advanced button. Opens Advanced Appearance dialog.
3. In the Item field, choose Message Box.
4. Change the Font and Size parameters to taste.
5. Click OK
6. Click OK to return to desktop.

Vista

1. Right-click the desktop, choose Personalize from Context menu to open Personalization window.
2. At the top of the Personalization options, choose Window Color & Appearance link. Appearance dialog opens.
3. In the Window Color and Appearance dialog, choose Advanced appearance settings…
4. In the Item field, choose Message Box.
5. Change the Font and Size parameters to taste.
6. Click OK
7. Click OK
8. Close Personalization window to return to desktop.

Windows 7

1. Right-click the desktop, choose Personalize from Context menu to open Personalization window.
2. At the bottom-center of the Personalization dialog, choose Window Color.
3. In the Window Color and Appearance dialog, choose Advanced appearance settings.
4. In the Item field, choose Message Box.
5. Change the Font and Size parameters to taste.
6. Click OK
7. Click OK
8. Close Personalization window to return to desktop.

A friend, who really has nothing to hide, asked “What’s with the GW IM saving the entire history of previous conversations even when I say I don’t want them saved?

In GWIM, the dialog when logging out is to save a plain text transcript of the conversation.

The local, on your computer history (both the file and the “scroll back”) are as ephemeral as you set them in Tool>Options>History category. There is no central archive of chats in the IT GWIM system. The Salud GWIM is archived.

I just tested this with my iPod Touch (aka. iPad mini). You must use Lobo-Sec wireless network to have access to the correct data ports. As far as I know, you’d need to use Lobo-Sec wireless network to make an IMAP connection to UNM Webmail, too.

The latest iPhone OS seems to be pretty good about this, but you might want to re-start the device before begining.

Start by going to Settings>WiFi and picking the Lobo-Sec. Assuming you are in range, it will connect and then ask for a password, which can be gotten from the IT Downloads page in the wifi-passphrase.txt file. Note that this phrase may change over time and will have to be re-entered. Once the password has been accepted, (if not, use the Forget this Network button and re-try) then open Safari to any page and attempt to go to or refresh a web page. This should redirect to the UNM Wireless Authentication page. Enter your current UNM NetID and password and click the Login button. If successful, Safari will show an acknowledgment page then automatically take you on to your page. Only now are you able to use the Lobo-Sec wireless network. Now go to the Settings>Mail,Contacts,Calendar and set up your account. Use gwdomain.unm.edu as the incoming server and smtp.unm.edu as the outgoing with your regular UNM email address, NetID, and current password. The OS will discover the correct SSL settings automagically.

The device will remember the passphrase, but the user must go through the browser re-direct every time they connect or reconnect in a new wireless zone.

This rule will prevent anybody but a principal person (and other users they choose) from putting appointment on their calendar. If another user sends an invitation, it is declined immediately and a notification is returned with information on how or who to contact to request a meeting. Because GroupWise rules can only use one account name per conditional, multiple rules have to be created and evaluated in order. The Stop Rule Processing action is vital for assuring this rule will work as anticipated. All these rules go in the principle person’s account. Go Tool>Rules>New… button to start.

First, make a rule that delete/declines any appointment request not from that person.Rule names can be any text

1. Rule name: can be any text.
2. When event is: Set pull down to New Item.
3. And Items are: check Received.
4. Click the Define Conditions button. In the Define Conditions dialog box, use From, ‘! Not Equal to’, and principal persons full name as it appears in the GroupWise address book. This will make it so they and their proxy can schedule meetings but the rule is applied to everyone else. Click OK to return to the Edit Rule Window.
5. Under Then Add Actions, click Add Action from the pull down and choose Reply if you want the the person who attempted to schedule the appointment to receive an email response. This is where the alternative contact information goes. Add the response to the second dialog that appears and click OK.
6. Click Add Actions pull down and choose Delete/Decline. Optionally enter a word or two that the person who attempted to schedule the appointment will receive as in Notification or in the properties of their meeting sent item.
7. Click Save to save the rule and return to the new rule window.

You could stop here if all meeting are scheduled from the principal user’s account.

Now create another rule for any other users who will be setting appointment for the principle person.

1. Rule name: can be any text.
2. When event is: Set pull down to New Item.
3. And Items are: check Received.
4. Click the Define Conditions button. In the Define Conditions box, use From, ‘= Matches’ conditional, and schedulers full name as it appears in the GroupWise address book. Do NOT use the [] contains conditional.  Click OK to return to the Edit Rule Window.
5. Under Then Add Actions, choose Accept and optionally enter a message.
6. Under Add Actions, choose Stop Rule Processing.
7. Click Save to save the rule and return to the new rule window.

You can use the Copy… command in the Rules window to create rules for additional schedulers.

Once all the rules have been created, be sure they are in the proper order in the Rules window. The schedulers rules must be above the rule that tests for the principal’s name.  Any forward or opt-out rules should be at the very top of the list.  Use the Move up or Move Down buttons to reorder the rules. Click Close and test.

Here is my version of the clean install using what is on our download page. There are more and less thorough versions of what needs to be done, but this seem to fix most systems.

If GroupWise gives Window errors like “Client has encountered a problem and needs to close” a clean reinstall will usually be required.  Have the user attempt a login on another computer to be sure the problem is specific their computer.

Clean re-install of GroupWise Windows client.

1. Download GroupWise client software .zip file from ITS Download site.

http://it.unm.edu/download

2. Extract .zip to known location. C:\TEMP\Novell recommended.

3. Go to Add/Remove Programs. Not all of these will be present in every installation.

Remove Windows Messaging

Remove GroupWise Tip of the Day C3PO

Remove GroupWise Internet Browser Mail Integration

Remove GroupWise

4. Go to the extracted GroupWise installer folder and run Cleanit.exe (a GroupWise specific Registry cleaner). Use the program defaults unless GWIM is installed. It runs quickly and quits automatically.

UPDATE: Some users report using the Windows Installer CleanUp Utility to remove residual GroupWise installer files. The link at Microsoft is: http://support.microsoft.com/kb/290301

5. Delete these the files in the C:\Windows\Temp directory if present.

Setup IP folder and contents

copyip*.*

gw*.*

5. Restart the computer.

6. Go to the extracted GroupWise installer folder and run the UNM-ITS SETUP file (or go to /win32/setup.exe). The client must be installed with Administrator privileges, but can be run at other privilege levels.