Cool Solutions

Virtualizing ConsoleOne 1.3.6h for Windows 7



By:

May 19, 2011 11:16 am

Reads:1,097

Comments:4

Score:5

One of the more tricky hurdles our team had to overcome in our migration from Windows XP to Windows 7 in a ZENworks environment was to figure out how we were going to get ConsoleOne working on our Windows 7 workstations.

Until we came across the solution, we were running XP VM’s for the sole purpose of running ConsoleOne. With no clear instructions on how to accomplish this task, I took a four day long stab at trying to virtualize the application. Finally, after some face-to-keyboard contact and much trial and error, I found success!

Before you Begin:

  • Start with a fresh, barebones Windows XP workstation or VM.
  • Install Novell ZAV 8.0
  • Copy the files from an existing Windows XP workstation with a fully functional install of ConsoleOne (Typically located at C:\novell\consoleone) and place them on the Desktop of the ZAV machine you have just created.
  • Copy over the ConsoleOne setup executable.
  • Install Novell Client 4.91 SP5 for Windows. Reboot your machine.
  • Beginner’s Tip: If you’re frequently building and virtualizing applications, you may want to create a VM and utilize the snapshot feature so that starting from scratch is only a short ‘revert’ away.

The Fun Part:

  • After the reboot, do not log into your Novell network. Log in workstation only. I used the administrator account.
  • Launch ZAV. To keep things easy, we are going to use the Configuration Wizard. Choose ‘Virtualize a third-party application or component’.
  • Ensure all other programs and processes have been shut down. Capture the ‘before’ snapshot. This is a good time to grab a coffee.
  • When the snapshot is complete, proceed with running the ConsoleOne setup to your liking. Do not launch the software when the install has completed.
  • Take the ConsoleOne files that you copied to the Desktop earlier and paste these overtop of what you just installed. By default, ConsoleOne installs to C:\novell\consoleone. This will copy over your snap-ins, configuration, etc.
  • Take the ‘after’ snapshot.
  • Ensure that the Startup File points to the proper executable. If you let it install to its default directory, this field should be pointing to C:\novell\consoleone\1.2\bin\consoleone.exe.
  • Build the application.

Before you Deploy:

  • Please make the following registry change on the Windows 7 PC prior to running ConsoleOne (or, build this into the virtualized application itself — I chose not to so that it could be used on various flavours of Windows):

    [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Novell\NetWareWorkstation\
    CurrentVersion] > “MinorVersion”=dword:0000005b

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.
Loading ... Loading ...

Tags: , , ,
Categories: Technical, ZENworks, ZENworks Application Virtualization

Disclaimer: This content is not supported by Novell. 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.

4 Comments

  1. By:smflood

    No need to do all of the above as the latest version of ConsoleOne will run on Windows 7.

    The trick is getting the latest version – you want 1.3.6h as included in the latest available version of GroupWise 8.0 (currently SP2 HP2 – see http://download.novell.com/Download?buildid=HJuDB3wNoeM~ )

    Note that ConsoleOne is now only supported by the GroupWise team specifically to manage GroupWise although you can still use it to manage other things.

    • By:jrands

      We’ve attempted to use the latest version several times, but there’s a lot of work to be done in getting it configured properly in our environment with our current settings/snap-ins. It just wasn’t working.

      Not to mention to get it to display properly, you have to switch back to the Windows 7 ‘Basic’ theme. There’s not enough contrast to clearly read the icons, and the color is pretty much unprofessional without loads of customization that we weren’t prepared to spend our time on configuring.

      Virtualizing the application was the most appropriate approach for us in our organization.

  2. By:sisml

    I was able to run up an older version of ConsoleOne yesterday – 1.3.6e – by copying across the files that were installed on an XP machine and setting consoleone.exe to run in XP compatability mode. Also set it to “Disable visual themes” but not really sure if that had much effect.
    As jrands mentions, if an aero theme is being used it doesn’t display too well but appears to be functional.
    1.3.6e probably isn’t supported by Novell to do any administration, but seems to work for us to do what we need.

  3. By:whitea

    I followed the instructions. When I run the virtualized ConsoleOne application the following message appears.
    “consoleone.exe – Ordinal Not Found The Ordinal 689 could not be located in dynamic link library CALWIN32.DLL
    Any help would be appreciated.

Comment

RSS