Transcript ZENworks For Servers 1.0 Technical

ZENworks for Servers
Presenter Name
Title
Directory-Enabled Management
• Novell is a leader in Directory-Enabled
Workstation management, and we are now
becoming a leader in Server and Network
Management
• Leadership and involvement in DEN and
DMTF groups
• ZENworks for Desktops, Servers, and
Networks gives us a complete solution
Policy Management REQUIRES a
directory!
• Without a directory, you can’t relate the
user and the device to the policy.
• Novell has the best directory, therefore we
are best positioned to deliver directoryenabled management
• ZENworks for Desktops, Servers, and
Networks delivers an end-to-end solution
that only Novell can give you
Open Standards means multivendor support
• Novell is committed to the DMI, WBEM, and
DEN standards to provide the ability to
manage many desktops, switches and
routers, and takes advantage of built in
desktop management interfaces.
Our management products
• ZENworks for Desktops 2.0
• The best desktop management and software distribution product
for Win32 desktops.
• ZENworks for Optimized Networks
• The first vendor-independent DEN-enabled network device
management product. Shipping Q1 ‘00.
• ManageWise
• Server and Network Monitoring.
• ZENworks for Servers
• Policy Management and Software Distribution for NetWare.
ZENworks for Servers 1.0
• Policy-based management
• Policies automate and enforce procedures or actions a server
takes in response to an event, or on a set schedule
• Server software packages
• Groups of files packaged together for distribution, can also
contain applications with installation automation
• Tiered Electronic Distribution (TED)
• Scaleable server-to-server using proxies to increase efficiency
and reduce bandwidth utilization
Can ZENworks for Servers help
you?
• Could you benefit from automated server management?
• Do you need to reduce the time it takes to manage each
individual server on the network?
• Do you currently manually distribute files or software to
multiple servers using batch files or other primitive methods?
• Do you need a solution for automating and managing the
deployment of server applications to any point on the
network?
• Do you plan on growing or changing your servers to meet
business needs in the near future?
Minimum Requirements
• NetWare 4.11, 4.2, 5.0, 5.1
•
•
•
•
•
TCP/IP Stack on each server
Service Pack 8 for NW4.x, SP4 for NW5.0
128 MB RAM
135 MB Free disk space
200 MHz Pentium processor
• JVM & Java Class Libraries installed (on
the ZfS CD)
• ConsoleOne (uses 1.2b19)
Server Policies contain:
• Set commands
• Down server
• Schedule
down/restart
• Load/run
• NLM, Java
• Script Run
• Netbasic, NCF, Perl
• SNMP agent
configuration:
• Trap target
• Community strings
• Text File
processing
Policy management
Looks and
feels much like
ZENworks for
Desktops
SET parameter policy
• Set Parameter Policy
- Standard server configuration
- Queries a single server for Set Parameter
template
- Policy maintains set parameter configuration
- Run on schedule to enforce settings
- Can run reports to identify servers that were not
already in compliance
Server Down Policy
• Automate steps used in server down process
• Ensures compliance with procedures
• Provides down override conditions based on files,
processes, users etc.
• Sets time to delay before the server goes down
• Disables Login
• Send Down Alerts via email, snmp
• Sends broadcast messages to logged in users
• Automates sequential application unload
Load/Run Policy
• Load or Unload NLM’s
• Load or Unload Java processes
• Scheduled by time, frequency, date, or run
immediately
Script Run policy
• Run NCF files
• Run Netbasic scripts
• Run Perl scripts
SNMP Agent configuration
• Configure Trap Targets
• Configure Community strings
Text File policy
• Configure NCF and any other text file
•
•
•
•
•
Append to end
Prepend to beginning
Search and Replace
Create new files
Delete files
Tiered Electronic Distribution
Distributor
Proxy/
Proxy
Subscriber
Subscriber
Subscriber
Subscriber
Subscriber
Subscriber
Proxy
Subscriber
Use Proxies to save bandwidth
Tiered Electronic Distribution
• Distributor
• Provides Server Software Packages to a proxy or a Subscriber
• Proxy
• Takes Server Software Packages from a Distributor, mirrors
them, and provides them to a Subscriber
• Subscriber
• Takes Server Software Packages from a Distributor or a Proxy
and applies them to its own file system
• A single server can run as a Distributor, Proxy, and
Subscriber, they are individual Java processes on
the server
Tiered Electronic Distribution
• Channels
• A channel is how the distributor gets the data to
the proxy or subscriber.
• A distributor defines a channel, and proxies and
subscribers subscribe to the channel.
• A distributor can host multiple channels, so you
could have an accounting channel, a human
resources channel, etc… to apply different
packages to different servers.
Server Software Packages
Very similar to
a ZENworks
for Desktops
Application
Object
Server Software Package
Requirements
• Set pre-conditions that must be met before
a distribution will occur
•
OS version
•
Physical Memory
•
Free Disk Space
•
Set Parameters
•
NetWare Server Registry Settings
•
File existence, non-existence
•
Products.dat entries
Pre-Install Automation
• Before running the file distribution,
you can:
•
•
•
•
•
Load/Unload NLM’s
Load/Unload Java Processes
Run NCF’s
Run Netbasic scripts
Run PERL script
File Copy
• In your distribution, you can
• Copy files to arbitrary directories/volumes
• Set copy-over rules (copy if exists, if does not
exist, if newer, etc…)
• Set attributes on the files
• Set retry behavior if the file is locked
SET parameter
• In your distribution, you can:
• Update and change any arbitrary SET
parameters, based on an sample server’s set
parameters, or set your own arbitrary set
parameters.
Registry Settings
• In your distribution, you can:
• Update and change the Novell server registry
(similar to a Windows registry, exists on every
NetWare server)
PRODUCTS.DAT changes
• In your distribution, you can:
• Update and change the PRODUCTS.DAT file
(the Novell server-based database which stores
information on every product and service pack
installed to the server)
Post-Install Automation
• After running the file distribution, you
can:
•
•
•
•
•
•
Load/Unload NLM’s
Load/Unload Java Processes
Run NCF’s
Run Netbasic scripts
Run PERL script
Down, restart or reboot the server
Why do you need ZENworks for
Servers?
• You have multiple servers in multiple
locations
• You would rather be doing real work than
going server-to-server-to-server-to-serverto-server and doing updates
• You need scalable software distribution
Sample ROI calculation
Assumption
• You pay your admin $50,000 per year
• Assuming 2000 work hours per year, that’s
$25.00 per hour
• You have 50 servers
• Applying a patch to each server would take
two hours per server
• Applying a patch to each server using ZfS
takes two hours total.
Sample ROI calculation
• So, ZfS takes two hours, versus 100 hours
for the manual method
• 98 hours saved * $25.00 per hour =
$2,450.00 saved on just one single patch.
• Your mileage may vary, but you can
certainly see that it takes less time and
resources to do something once rather than
do it many times.
Futures
• NT Support
• Additional policies
• Server and Network monitoring capabilities