How to Export Zenworks Object Properites from ConsoleOne

Hello All,

I am looking for a utility that can export Zenworks ojbect properties to a excel or cvs sheet. Does anyone know a solution?

Thanks,
Tareef
TareefAAsked:
Who is Participating?
 
ShineOnCommented:
As to your question, there's a bit of freeware that might help you in your endeavors, called "DSReport."  It's a free download by Wolfgang Schreiber: http://www.WolfgangSchreiber.de  He has written some really nifty tools - a lot of what you find in the Novell CoolSolutions "Cool Tools" links are by him.

DSReport can query the entire tree for whatever attributes you choose to select, and dump it into pretty-much whatever format you want - including directly to an Excel file.
0
 
alextoftCommented:
What kind of Zen object are you referring to? Policy package? Workstation? Application?

You can export Zen apps to an axt (text) file, but I'm not aware of anything much more than that. Could I perhaps ask what it is you wish to achieve from doing this?
0
 
TareefAAuthor Commented:
Hello Alextoft,

I want the extract the properties of Zenworks Application Objects. I am doing an assessment of a customer's Novell environment and need to validate the Source, Target, and Executable Paths. That's why a CSV file would work good for me.

Any suggestions?

Thanks,
Tareef
0
Cloud Class® Course: CompTIA Cloud+

The CompTIA Cloud+ Basic training course will teach you about cloud concepts and models, data storage, networking, and network infrastructure.

 
dotENGCommented:
Well not CSV but everything you asked, give it a try:

NLIST App:Application SHOW "App:Path", "App:Macros" /CO ".base context to search from" /S /C > text_file.txt


0
 
TareefAAuthor Commented:
dotENG,

Thanks for the reply. Do you know of a way to perform a bulk export on a container? I have a lot of applications to export.

Thanks,
Tareef
0
 
ShineOnCommented:
TareefA,

Just so you're aware - there's a lot - a LOT - of different ways a ZEN app can be built, and what you're planning to do might cover a tenth of what you need to cover to analyze the situation.  In addition to source, target and executable paths, there are little things to consider like registry entries, INI files, MSI/MST files if you're doing MSI-based distribution, variable macros, folders, icons, shortcuts, target machine architecture... the list goes on and on.

If this is a company that's planning to migrate from NetWare and all other Novell products to all-Microsoft-all-the-time, then my recommendation is - DON'T.  Sure, migrate off NetWare if you must, but ZEN does not require NetWare.  It can run on Windoze or Linux (yes, you can manage your Windows desktops from Linux) just fine.  To migrate everything from ZEN to, say, SMS2000, could be a major project all by itself.  I know, 'cause I have to plan something similar here.
0
 
TareefAAuthor Commented:
ShineOn,

I would be nice to stay with ZenWorks, but it is not an option, everything Novell is going. We already migrated one division of the agency off of Zenworks. I am using ConsoleOne to export to an axt file, that we will make MSIs out of. But I need a tool for documentation aide.


Thanks,
Tareef
0
 
ShineOnCommented:
Have you checked at http://www.novell.com/coolsolutions to see what kind of cool tools there might be?  For example, something like NALalyze: http://www.novell.com/coolsolutions/tools/14352.html - "Quickly sanity check, document, search & report on ZENworks NAL objects."
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.