Cool Solutions

GroupWise: Distribute Windows Client using ZENworks


August 13, 2010 10:20 am





Many of our customers have hundreds or even thousands of desktops to keep up to date. They rely on tools like ZENworks to distribute the very latest GroupWise clients to these desktops and to their users. As part of GroupWise 8.0.2, our Integration Testing Team took some time to determine the best ways to configure, distribute and install on a variety of Windows platforms.

Here are a few pointers…

Windows Client Distribution Using ZENworks

To successfully distribute the GroupWise Windows client using ZENworks, some .msi files must be distributed in advance of the GroupWise software. These .msi files are part of the standard client installation, but they are not successfully installed when you perform a ZENworks silent installation using the /qb or /qn switches. (The /qn switch is used by default.)

For ZENworks 10, the following .msi files must be distributed before the GroupWise client software:

  • wse3.msi
  • mxsml.msi

To successfully distribute the GroupWise Windows client software using ZENworks 10:

  1. Create a ZENworks bundle for each .msi file:
    1. In the ZENworks Control Center, click Bundles, then click New > Bundle.
    2. Select Windows Bundle, then click Next.
    3. Select MSI Application, then click Next.
    4. Specify a name for the bundle such as WSE3, MSXML, or GroupWise Windows Client, then click Next.
    5. Select the .msi file for each bundle:
      1. In the Upload .msi file for normal install field, browse to and select each .msi file in your GroupWise software distribution directory: \grpwise\software\client\win32
      2. (Conditional) For the wse3.msi and msxml.msi files, do not select Include all files in and below the directory of this file. or (Conditional) For the groupwise.msi file, select Include all files in and below the directory of this file. This includes all the contents of the win32 subdirectory, which is the GroupWise client software.
      3. Click OK.
    6. Click Next.
    7. Finish creating each bundle as usual.
  2. After you create all three bundles, set the executable security level for each bundle:
    1. Click each bundle name, then click the Actions tab.
    2. Click the Install tab, then click Install MSI.
    3. Click More Options.
    4. Set Executable security level to Run as dynamic administration, then click OK.
  3. Assign each bundle to the appropriate GroupWise users.
  4. Create a launch schedule for each bundle so that the bundles launch in the following order:
    • wse3.msi
    • msxml.msi
    • groupwise.msi

ZENworks 7 Desktop Management

For ZENworks 7, the following files must be distributed before the GroupWise client software:

  • dotnetfx.exe (if .NET 2.0 or later is not already installed on workstations)
  • wse3.msi
  • mxsml.msi

To successfully distribute the GroupWise Windows client software using ZENworks 7:

  1. Copy the GroupWise client installation directory from the GroupWise software distribution directory: \grpwise\software\client\win32 to a convenient location on the ZENworks server or other network location.
  2. Create a NAL Application object for each file:
    1. In ConsoleOne, right-click the container where you want to create the NAL Application object, then click New > Object > Application.
    2. (Conditional) When you are installing dotnetfx.exe, select A simple application, then click Next. or (Conditional) For a .msi file, select An application that has an .MSI file.
    3. Click Next.
    4. Specify the path to the file, then click Next.
    5. Specify the name for the NAL Application object, such as DOTNETFX, WSE3, MSXML, or GroupWise Windows Client, then click Next.
    6. Finish creating each NAL Application object as usual.
  3. (Conditional) When you are installing dotnetfx.exe:
    1. Right-click the DOTNETFX NAL Application object that you created in Step 2.b, then click Properties.
    2. Click the Run Options tab, then click Application.
    3. In the Parameters field, specify: /q:a /c:”install /q”
    4. Click OK.
  4. Select Force Cache for each NAL Application object.
  5. Assign each NAL Application object to the appropriate GroupWise users.
  6. Create a schedule for each NAL Application object so that the applications are installed in the following order:
    • dotnetfx.exe
    • wse3.msi
    • msxml.msi
    • groupwise.msi

There continue to be challenges as Microsoft introduces and changes their desktop security options and ZENworks is enhanced to accommodate new options and configurations. Novell GroupWise has several dependent components that can also present another layer of difficulty. We will continue to work with Microsoft, the ZEN team and our own engineering team to further enhance this capability.

Please refer back to the official documentation and TIDs for updates and the most up-to-date information and advice.

GroupWise 8 Interoperability Guide >



Editor’s Note: When it comes to Windows 7 Migration projects, ZENworks can be your new best friend. Check it out.

2 votes, average: 5.00 out of 52 votes, average: 5.00 out of 52 votes, average: 5.00 out of 52 votes, average: 5.00 out of 52 votes, average: 5.00 out of 5 (2 votes, average: 5.00 out of 5)
You need to be a registered member to rate this post.

Categories: GroupWise Blog


Disclaimer: This content is not supported by Micro Focus. It was contributed by a community member and is published "as is." It seems to have worked for at least one person, and might work for you. But please be sure to test it thoroughly before using it in a production environment.


  1. By:hajo68


    We are using roaming profile and to avoid roaming of My Documents and also make sure that our user save their documents on a network share we have changed the target for My Documents to a mapped network drive (users home directory, in our case G:\). The problem is when I try to run wse.msi as dynamic administrator I get the error: “Error 1327 Invalid Drive G:\”. If I run it as logged in user I get the error: “You do not have sufficent privileges to complete this installation…..”. Most of our user belongs to the users group in windows.

    I have not found any solution to distribute (upgrade) the groupwise client to users that are not local admins yet.

    Any ideas?

    John Hallberg
    Jonkoping University

  2. By:dlythgoe

    Try this out… Information provided by Paul – a member of the engineering team.


    I suspect that the main issue is that because the package is running as a dynamic admin that the G:\ drive hasn’t been mapped at that stage or that it’s mapped and now the package is running in a different user session than the drive was first mapped in.

    You can try using a UNC path in the registry key instead of a named mapping. The regkey is HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folder\Personal. Ttypically this is set to %USERPROFILE%\My Documents, in this case I suspect it’s set to G:\ for the roaming profile.

    A better solution is to create a transform for the WSE3.MSI package and delete the PersonalFolder property. As far as I can see WSE3.MSI doesn’t actually install anything into the PersonalFolder (My Documents), however it is still used in the disk space calculation functions (CostFinalize) that Windows Installer provides. This is where the actual error 1327 occurs.

    I duplicated the issue by changing my regkey to x:\xxx then installing WSE3.MSI and the same error occurred. I created a transform, deleted the PersonalFolder property and installed with the transform and the package installed fine.

    When troubleshooting MSI packages, install the package with msiexec and create a verbose log file – this really is the key to seeing why those mysterious errors appear. If one is using roaming profiles, try doing this on a machine without roaming profile set (or change the above reg key) and compare the log output.
    eg: msiexec /l*vx c:\wse3install.log


    Let us know if this information helped you and we will create a TID.


    • By:hajo68


      This information helped me a lot. I created mst:s where I removed MyPicturesFolder and PersonalFolder in the Directory table. Then the install worked when running as dynamic administrator even if the user belonged to the Users group.

      I also found another solution: before running the msi install i used the command “subst G: C:\Temp”. Then I don’t have to create the mst.

      It’s enough to create one bundle that runs all three msi install one after another. My bundle consists of four Install actions:
      – subst G: C:\temp (secure system user)
      – install wse (dynamic administrator)
      – install msxml (dynamic administrator)
      – install Groupwise (dynamic administrator)


  3. By:jskelton

    How do you pass the custom settings like LDAP search servers?
    I have tried this in the past with a mst but it only propagated the settings to the logged in user.
    I also noticed that if i ran the exe install with the ini file for these settings, all users now show the ldap entries.


  4. By:woutervantil

    I looked on Microsoft sites to see what the relation between GroupWise 8 client and MSXML and WSE could be but didn’t become any further.
    Can you please tell me the use of MSXML and WSE?

  5. By:kwhite

    Novell, better yet make a MSI that includes everything that we need and WORKS!

    • By:dlythgoe

      It sounds like a simple request. The issue is that each installation using ZEN is usually customized. A generic MSI that includes everything – also includes too much for people who are not using ZEN or who do not need to configure as much as others.

      I guess we could provide multiple MSI. I guess the next blog would be to answer the question – which MSI should I use and why do you guys have so many? 🙂

      Sometimes you just can’t win…


  6. By:Tessnow

    Whats up with the included vcredist_x86.exe?
    Do I need to install this “Microsoft Visuall C++ 2005 Redistributable” on a fresh machine or is it not needed for the GroupWise Client?

    • By:dlythgoe

      This is needed. Most ‘fresh’ machines do not include the DLLs and system modules that are used/required by the Windows Client and that can be found in this redistributable.

      If they are not installed/present on the machine – the GroupWise Windows Client will not run.

      So – YES…required to be there.


  7. By:box

    Here is what I did which works perfectly (so far on about 60 workstations):

    One single bundle with the following (in this order):

    1. Run script: subst U:\ C:\Windows\temp
    MORE OPTIONS LINK: Priority: Normal; Run as: Administrator

    2. Upload WSE3.MSI; include a transform (MST) which removed PersonalFolder and MyPicturesFolder. (Used Tuner in Admin Studio to do this).
    MORE OPTIONS LINK: Run as Dymanic Administrator

    3. Upload MSXML.MSI.
    MORE OPTIONS LINK: Run as Dymanic Administrator

    4. Upload GROUPWISE.MSI; include transform (MST) which removed the desktop icon. (Used Tuner in Admin Studio to do this).
    MORE OPTIONS LINK: Run as Dymanic Administrator

    5. Registry Edit to disable document integratiions (imported this string from exported key): HKCU\Software\Novell\GroupWise\Client\Library\Integrations – String Data: Disabled; Registry Operation: Create Always.
    ADVANCED SETTINGS TAB: Check the box: “Apply HKEY_CURRENT_USER changes to the logged in user’s have instead of .DEFAULT

    Depending on the hardware of the workstation, the installation process takes up to 10 minutes.

    Hope this helps out!


  8. By:shutchinson

    I am using ZCM 10.1.3 to install GW 8.0.2 onto a PC running:
    – Windows XP SP3
    – ZCM Client 10.1.3
    – Novell Client 4.91 SP4

    I used the GWTuner which came with GW 8.0.2 and built a .MST

    I built the bundle as described in the article (except I put all 3 .MSIs into the same Bundle, taking care to keep them in the right order). I included the custom .MST file.

    When I run the bundle, I get the following results:

    1 – ZENworks says the installation completed successfully
    2 – The Start Menu “email” icon has been changed to GroupWise, with the teal circle.
    3 – GroupWise seems to work when launched from the link at the top of the start Menu.
    4 – There is no GroupWise folder in Start->”All Programs”
    5 – There is no GroupWise Shortcut on the Desktop (even though I specified to put it there in GWTuner)
    6 – There is no GroupWise on the Add/Remove Programs screen

    What am I doing wrong?


  9. By:shutchinson

    this is adding to my previous comment (which I just posted and can’t see yet):

    It occurred to me to look in the Desktop and Start Menu for the Dynamic Administrator – and I found the Shortcuts.

    Now I guess I need to figure out how to move those shortcuts to “All Users” (since this is not an option in GWTuner)

    But even this does not explain why GroupWise does not appear on the All/Remove Programs screen.


    • By:dlythgoe


      I have asked NTS to reach out to you and see if they can help figure out what is going on. Once that is figured out, we will post the solution here as a response to your post.



      • By:shutchinson

        I found that if I run it as “Normal” (logged in user) but check the “Temporarily elevate user to an Administrator” box, it seemed to work, when I was testing with an Administrative Windows login.

        When I tested the bundle logged in as a non-admin user which had no password, it asked for the Windows Password (but would not accept blank or Administrator’s password), then failed to elevate the user because it could not obtain the Windows password.

        So I look forward to hearding from NTS.


  10. By:fpatterson

    AutoIT is a scripting tool that allows you to install as an existing administrator on the box. If your boxes have been imaged with the same administrator across all workstations, then you can choose to install it as an existing administrator.

    The AutoIt Site:

    The Downloads: – This is the AutoIt program itself – This is the recommended editor which includes tight AutoIt integration. (Great for Non-AutoIt stuff too.)

    A Sample AutoIt Script to do what is required could be a single line as shown below:

    RunAs(“bob”,@ComputerName,”secret”,1,”notepad.exe readme.txt”)

    Simply Change “bob” to be the local administrative account on the PC.

    Change “secret” to be the password.

    @ComputerName is a “Variable” that would be left the same and simply tells the script that the account is on the local PC.

    “notepad.exe readme.txt” could be changed to match any command that is desired. For example it may be “msiexec /i c:\gw8install\groupwise8.msi /qb+ ”

    As a Reminder, with zenworks 7, the Distribution Tab will be required to download the install files locally, this “RunAs” user will not have any network access rights.

    Example script that worked for my customer:
    ; Fill in the username and password appropriate for your system.

    Local $sUserName = “Administrator”
    Local $sPassword = “Novell”

    ; Run a command prompt as the other user.

    RunAs($sUserName, @ComputerName, $sPassword, 1, “msiexec /i c:\temp\client\win32\groupwise.msi /T=groupwise.mst /qb- /norestart ALLUSERS=1”)

    ;change gb- to passive to only see the progress bar

    • By:wdewey

      Having a script with a clear text username and password in it is a very big security risk especially if the local admin password is the same across all desktops. If users have access to run a script then they have access to view it, so I would consider if I wanted to share a password like that with any random user that happens to be curious and have a little knowledge.