This tip explains on how to run ConsoleOne 1.3.6f on Windows Vista Business Edition, at least until Novell comes with versions of the Novell Client and Console that support Vista.
Here's the typical problem you will encounter:
1. Install Java 6 Runtime. You can find it here: http://www.java.com/en/download/windows_manual2.jsp
2. Install the Novell Client, version: 1.0 Build 20070125
Vista Compatibility: The beta version of the Novell client for Windows Vista works with Vista.
Vendor Support: Officially supported. The beta client is available from the Novell Downloads (http://download.novell.com/Download?buildid=yIEJzwGwlu0~) site.
3. Install ConsoleOne (C1.exe) like normal. You can find it here: http://download.novell.com/Download?buildid=brBWU2uxSiM~
If you start ConsoleOne 1.3.6.f from the icon it creates on the desktop, you will get this error:
(and yes, the Client was installed when I took this snapshot ...)
This error occurs when you try to start ConsoleOne.exe, obviously because of the "New Client."
To get around this problem,
1. Go to the directory C:\novell\consoleone\1.2\bin
2. Double-click run.bat, or create a new icon on the desktop of the same run.bat and execute it. You can also use ConsoleOneDos.exe, like run.bat.
Vista will change to the basic theme while ConsoleOne runs.
Note: This solution can have some trouble with different ConsoleOne plugins, allthough I have been able to get the GroupWise 7.01 plugins running fine. The only trouble is that I have to go to the Domain eDirectory objects and choose "connect" to make it work. If I choose Tools in the menu to select the Domain, I get errors in the running DOS window.
So, this is only a temporary workaround until there is a solution from Novell, but at least it's usable. This way I don't need an XP machine running VMWare to have ConsoleOne there.
Disclaimer: As with everything else at Cool Solutions, this content is definitely not supported by Novell (so don't even think of calling Support if you try something and it blows up).
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, test, test before you do anything drastic with it.