Novell ZENworks
Lua error in package.lua at line 80: module 'strict' not found.
| Developer(s) | Novell |
|---|---|
| Stable release | 11 Support Pack 4[1] / 30 July 2015 |
| Operating system | Cross-platform |
| Type | Systems management |
| License | Proprietary |
| Website | www |
Novell ZENworks, a suite of software products developed and maintained by Novell, Inc. for computer systems management, aims to manage the entire life cycle of servers, of desktop PCs (Windows or Linux), of laptops, and of handheld devices such as personal digital assistants (PDAs). As of 2011[update] Novell planned to include full disk encryption functionality within ZENworks.[2] ZENworks supports multiple server platforms and multiple directory services.[3]
Contents
Elements of the ZENworks Suite
In July 2015 the ZENworks Suite consists of seven individual products:
| ZENworks Suite / Platform | Product | |
|---|---|---|
| ZENworks Suite | ZENworks 11 Platform | ZENworks Asset Management |
| ZENworks Configuration Management | ||
| ZENworks Endpoint Security Management | ||
| ZENworks Full Disk Encryption | ||
| ZENworks Patch Management | ||
| ZENworks Application Virtualization | ||
| Novell Service Desk (Incident Management Edition) | ||
As of July 2015 the product „ZENworks Mobile Management" is not yet an element of the Suite. Additionally, Novell offers an ITIL version of „Novell Service Desk". This version is ITIL certified by PinkVERIFY and supports ten ITIL v3 processes. E.g. Change, Incident, Problem and Service Level Management.[4]
Customers can buy the whole suite or choose between individual elements.
History
Kevin Hopton, a corporate systems engineer at Novell, first conceived of the software which later became NAL (Novell Application Launcher) in 1993. The original concept involved using the Novell Directory Services (NDS) directory as a namespace and storage engine. NDS, in concert with a client console program, would perform just-in-time application-configuration. The directory namespace - global, unambiguous and outside the influence of end users - provided a highly reliable mechanism for ensuring that expert staff could define the methods invoked for launching an application (app).
The prototype consisted of a demonstration app named "Magic Windows" due to the automatic correction of configuration errors after the double-click and before the launch. Kevin Hopton, the primary architect and developer of Magic Windows, received important assistance from JD Marymee in the writing of AppWare objects that enabled directory access. Hopton produced a second version, written in Delphi and with UI assistance from Eric Burkholder. That version added representation for users and several other object classes.
Once the demonstration application proved a hit with customers, Novell's software-engineering organization took over the code and rewrote it from scratch in C. Key engineers and architects for this official version (named Novell Application Launcher or NAL) included Damon Janis, Kelly Sonderegger, Matt Brooks and Calvin Gaisford. Sandy Marymee handled marketing. The network-administrator community responded favorably to NAL, and its use and adoption quickly grew.[citation needed]
The success of NAL led to a desire to expand its functionality. Notably, Kent Prows lobbied for adding software-distribution capabilities, Samm DiStasio came up with the name "ZENworks" (for "Zero Effort Networking") with Allen Tietjen driving the bundle.[5] The "Novell Application Launcher" service and executable program-names with the .nal file extension persist within ZENworks.
Novell later wrote a version that diversified the managed object class to include users. That solution (based on the second iteration of Magic Windows, engineered primarily by Damon Janis), "UserNet", appeared at the Novell Brainshare conference in 1994.
Kelly Sonderegger had done prior work relating to NDS as a shared Windows registry; that work significantly influenced the design of the official versions of NAL and ZENworks.
The new name, "ZENworks", first appeared as "Z.E.N.works" in 1998 with ZENworks 1.0[6] and with ZENworks Starter Pack - a limited version of ZENworks 1.0 that came bundled with NetWare 5.0 (1998). Novell added server-management functionality, and the product grew into a suite consisting of:
- "ZENworks for Desktops" (ZfD)
- "ZENworks for Servers" (ZfS)
Novell has continued to add components to the suite, which it sells under the consolidated name "ZENworks Suite".
The "ZENworks 11 Support Pack 4" was released on 30 July 2015.[1]
Implementation
- The ZENworks Agent (also known as the "ZENworks Management Daemon" or "zmd") installs, updates and removes software.[7]
- ZENworks Configuration Management (ZCM) addresses patching, endpoint security, asset management and provisioning.[8]
See also
Further reading
- Lua error in package.lua at line 80: module 'strict' not found.
- Lua error in package.lua at line 80: module 'strict' not found.
- Lua error in package.lua at line 80: module 'strict' not found.
- Lua error in package.lua at line 80: module 'strict' not found.
- Lua error in package.lua at line 80: module 'strict' not found.
References
- ↑ 1.0 1.1 Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Compare Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
