Forcing GroupWise to Start in caching mode

This started out as an attempt to disable the ‘online’ mailbox as an option.

I couldn’t find out how to do that, but if you make your GroupWise shortcut point to the .vbs script below it will force GroupWise to start in caching mode. Regardless of what the user last selected.

To create a script file, enter the text below into a new .txt file. Then rename the extension to .vbs.


Set WshShell = WScript.CreateObject("WScript.Shell")

Key = ""

Path = WshShell.RegRead("HKCU\Software\Novell\Groupwise\Login Parameters\path to cache\" & Key)

wshShell.Run("c:\novell\groupwise\grpwise.exe /pc-" & path)


Some of you may need to edit lines 3 and 4 depending on where your info is stored/where you have installed GroupWise.

What the script does is use Windows Scripting Host, first to read the path to the caching directory from the Current Users registry keys. Then it runs GroupWise using the ‘pc-‘ switch command with the cache path stuck on the end to start GroupWise in caching mode.

If there is no caching directory set GroupWise just starts up in online mode.



How To-Best Practice
Comment List
  • in reply to MigrationDeletedUser
    We deploy our client via NAL. During the install we create the folder that we want the caching mailbox stored. We then put in this registry entry-

    [HKEY_CURRENT_USER\Software\Novell\GroupWise\Login Parameters\Path To Cache]

    When they create their caching mailbox, all they need to do is select the defaults.

    I know this is not exactly what you want, but it at least gives them a default location.
  • in reply to MigrationDeletedUser

    we get the same thing here. Example calls :

    "my email is asking me to create a 'cashing'? double-you tee eff?"

    you could perhaps have the script watch the process list for the prompts appearing then send the answers you need - but then it would not be so simple a solution.

    The issue is that Groupwise often wont let you make any changes to a users options unless you are logged in as the user.

    If i get anywhere with it i'll post it for sure.

  • sounds great...
    ...we have the intention too, to force our users to use caching rather than online mode, to lighten server's load!
    what we are looking for is a way, that we don't need to bother the user with the store-path-questions when we force him to use caching mode and he first time logs in...

    unfortunately there seems to be no way to pre-configure the chaching-mode-related options via client options!!

    any suggestions on that? tnx!