--- Sjoerd Hooft's InFormation Technology ---

User Tools

Site Tools



Would you like to sponsor this site?
Or buy me a beer?:

Recently Changed Pages:

View All Pages
View All Q Pages

View All Tags

Sign up for Q to post comments.

WIKI Disclaimer: As with most other things on the Internet, the content on this wiki is not supported. It was contributed by me and is published “as is”. It has worked for me, and might work for you.
Also note that any view or statement expressed anywhere on this site are strictly mine and not the opinions or views of my employer.

Terms And Conditions for Q users

Pages with comments

2019/05/01 14:08 2 Comments
2019/03/15 16:02 1 Comment
2019/03/15 16:02 1 Comment
2019/03/15 16:02 3 Comments
2017/04/20 15:28 1 Comment
2017/04/20 15:23 1 Comment
2017/04/19 14:44 1 Comment
2017/04/17 20:10 1 Comment
2017/04/17 20:07 1 Comment
2017/04/17 19:58 1 Comment
2017/04/17 19:52 1 Comment

View All Comments



This is a page about ConsoleOne. These topics will be discussed:

  • ConsoleOne and ZENworks Configuration Management 7
  • ConsoleOne and Windows 7
  • ConsoleOne parameters

ConsoleOne and ZENworks Configuration Management 7


ConsoleOne is an application which does not have to be installed in the traditional meaning of the word. All you need is the application files to be in the correct file hierarchy. In other words, to run ConsoleOne locally all you need to do is to copy the files to your local hard drive. This was already possible in ZENworks 7, and it is still possible to do that in ZENworks 10, also known as ZENworks Configuration Management. You start by creating a new bundle:
Then select the 'Copy Directory' option:
Fill in the bundle name, make it descriptive and if you want, add an description:
Now you must select the directory to copy from and the directory to copy to. The destination directory does not already have to exist. I selected the 'Copy Option' 'Copy if Different' to make sure only changes are copied after incrementing the file bundle version number (see later on this page for more information about that):
Select the 'Define Additional Properties' and click next:
After creating the file bundle you can change the file bundle to fit your needs. I changed these settings:

  • Display Name
  • ZENworks Explorer Folder Path
  • Show Bundle Activity Also, don't forget to increment the version.
    You have now created a file bundle which will copy the files to the local disk drive. Although it's possible to add another action to the bundle to launch ConsoleOne I decided to create another bundle to start ConsoleOne. == Startup == So we want to create a Windows Bundle which will simply start the correct executable:
    Select simple application:
    Fill in the bundle name, make it descriptive and if you want, add an description:
    Now, provide the executable that has to be started. As you can read in this page you need to select 'consoleonedos.exe' if you're providing Windows 7 with ConsoleOne so make sure to provide the correct executable:
    Select the 'Define Additional Properties' and click next:
    Now in the system requirements add a requirement that the install bundle has been installed before ConsoleOne can be launched:
    After setting the requirement for the Windows bundle you can change it to fit your needs. I changed these settings:
  • Display Name
  • ZENworks Explorer Folder Path Also, don't forget to increment the version:

ConsoleOne and Windows 7

When you try to start ConsoleOne in Windows 7 you'll probably get a message like this:

You have Novell Client version lower than 4.91 installed.
For the proper functioning of ConsoleOne, Novell Client Version 4.91 or higher version is required.

You can work around this issue by starting the 'ConsoleOneDos.exe' executable in stead of 'ConsoleOne.exe'. You can find both executables in the 'bin' directory under the ConsoleOne root directory. The parameters described in this article work for both executables.

ConsoleOne Parameters

ConsoleOne has a few parameters you can use for specific purposes: If you have an environment with really large containers or a lot of objects you could start ConsoleOne with more memory and a higher limit of objects it reads per container:

-JXmx512m -vboundary 20000

If you have synchronization issues you could force ConsoleOne to use the Master of the replica you're working in:


If you have issues regarding hidden objects you can make them visible by starting ConsoleOne with this parameter:


If you need to debug plugins or ConsoleOne you can start it with these debug options:

-debug -windowout
You could leave a comment if you were logged in.
consoleone.txt · Last modified: 2013/05/04 14:33 by sjoerd