Transcript Advanced ZENworks Management

Advanced ZENworks
Management
Ryan Radschlag
Network Manager
Hartford Joint #1 School District
[email protected]
Whaddya Wanna Do?
•
Imaging - How to make ZCM make you look like you’re working
•
Bundle Conquering - Combating educational “software”
•
Policies - Unleash your inner Network Nazi
•
Best Practices - according to $variable
Imaging The Ronco Way!
•
Automated imaging can be your saving grace with limited time and
resources
o
•
Easily deploy new machines without starting from scratch
o
•
Quit troubleshooting pointless windows/user errors
Banish golden images
Image machines without leaving your desk
o
AKA...go golf 9 while you image your entire district
The Imaging Process
Phase 1
Build Setup
Phase 2
ZENworks
Imaging
Environment
autoImage Script
Driver
Installation
Phase 3
ZENworks
Agent
Installation
Customize
Machine “Profile”
Phase 4
Operating
System
Build
Bundle
Installation
Drivers
Build Process
Naming
Convention
Build Type
Phase 5
Build
Process
Cleanup
- Import necessary
registry keys from ZIE.reg
- Set build run on start
- Drivers for machine
downloaded in addon
image.
- dpinst run to install
drivers for hardware
- ZENworks Agent silently
installed
- “-x -q -k” command line
arguments to perform
silent install & registration
- Bundle specified by
registry key is installed
-Reboot after bundle
install completes
- Build files are deleted
from machine
-Other cleanup tasks can
also be run in this process
ZENworks PXE Menu
autoImage Script
Simple Prompt Driven Imaging Script
1. Choose OS
2. Choose Building/Context
3. Choose Build Type
4. Enter Room #
5. Name is auto generated by CONTEXT(1)-ROOM(max 5)-SERIAL(7)
Imaging File paths are auto-generated by OS/Context/Type
•
Code for clientless: case $opt in
“Clientless”)
projbase=${os}-clientless/
•
projimg=${LONGCONTEXT}-${os}-clientless.zmg
If Windows 8 is chosen for a clientless machine in Building A, the project image would be win8-pro-x64clientless/BUILDINGA-win8-pro-clientless.zmg
autoImage Script (cont’d)
•
Add-on images deployed
o
o
buildprocess.zmg

contains build-AMD64.exe & build-x86.exe

build-%PROCESSOR_ARCHITECTURE% called on first login (configured in
unattend.xml)
zenagent-AMD64/x86

o
contains the full ZENworks Agent installer
(CONTEXT)-(OS)-(buildtype).zmg

contains registry and batch files used to customize the machine throughout the
build process
Build Types
•
•
•
Clientless
o
No Novell Client/Domain Membership
o
Only local users
Clientless DLU
o
No Novell Client/Domain Membership
o
ZCM logins via DLU from LDAP source
Full/Domain Client
o
Novell Client/Domain Membership
o
Logins passively passed to ZCM if valid
In A Nutshell
1. PXE Boot into ZENworks imaging
environment
2. Choose the build options
3. Walk away - go take a nap
Becoming a Bundle Master
1. Think
2. Think a little harder
3. Click Around
4. Execute
5. Test
6. Set them free
Think
•
What do you want to do?
o
o
o
o
o
Install a program?
Launch a program?
Both?
Have a user launch a program?
Install a kitten wallpaper on your District
Administrators computer?
Think A Little Harder
•
How are you going to do it?
o
o
o
o
o
MSI
EXE
Some registry tweaks here and there
BOB←Your friend
Requirements
Click Around
•
Go create a skeleton bundle
o
•
If you want to “categorize” it according to what
you thought a little harder about, fine
Gather your supplies
Download installers
o Export registry settings
o Copy program XML settings
o
EXECUTE!!!!
•
•
If you wanted to install something
o
Start creating INSTALL actions
If you wanted to launch something
o
Start creating LAUNCH actions
TIP: The more organized you are in naming
conventions and action labeling the easier it
will be to maintain your bundles
Test
•
•
Recommended to get used to Snapshot
bundles
o
Allows you to test without committing (like dating)
Virtual test machine
o
o
Snapshotting can save you tons of time when it
comes to bundle testing
Clean slate to start with each time
Deploy
•
•
Publish the bundle and start assigning it to
things
Do not under any circumstances schedule
bundles to deploy “NOW”
Using Requirements
•
•
•
Bundle action requirements allow you to
make 1 bundle for all deployment scenarios
Keep your bundles working for you instead
of against
Action requirements keep your database
size under control in comparison to bundle
requirements
Policies
•
Many different types of policies
o
o
o
o
Windows Group Policies
Patch Policies (for ZPM users)
Firewall/Device/Security Policies (for ZESM users)
Many more
Policies - KISS
•
•
•
•
Be selective in assigning policies to
users/devices
Plan a clean policy organization before
rolling them out
The less settings that need to be deployed
to the user when they login the better
Don’t be a total Nazi, the illusion of
freedom is a powerful thing
Best Practices - Primary Servers
•
Novell
Recommends
o
o
o
Dual Core Processor
2GB-4GB RAM
30GB Hard Disk
•
Real World
o
o
o
Quad Core Processor
8-16GB RAM
HDD depends on how
many bundles you
intend to create.
Primary Servers Tuning
•
•
•
Tuning the primary server to your
environment is a must
Allocate more RAM to the zenserver and
zenloader services
Increase the CPU thread count for HTTP/S
services
Primary Servers Layout & Design
•
•
•
•
•
Recommend starting with 3 Primary Servers
o 2 Internal for redundancy
o 1 DMZ for external clients & Join Proxy
Spread across your virtual cluster if you have one
Create closest server rules or use a L4 switch for load
balancing
Locate them as close to your database as possible
I would recommend 1 primary based on your favorite
server software and the rest can be appliances
Database Considerations
•
•
ZPM users should consider MSSQL due to the
database heavy workload
Always use an external DB
o
•
o
Room for future growth
Don’t put all your eggs in one basket
Follow Novell guides for tuning and
database maintenance
o
HAPPY DB=HAPPY ZONE
Satellite Devices
•
•
•
Only use them if necessary
o
Slow links between sites
Satellite Devices are NOT meant to reduce
the load to the Primary Servers
The purpose of a Satellite Device is to
reduce network load
Summary
1. Plan your zone out
2. Plan your policies structure
3. Plan your bundle rollout
4. Create a working imaging environment
5. Start deployment
6. Monitor and test your future changes
Novell Resources
•
•
•
Primary Server Tuning
• http://www.novell.com/documentation/zenworks11/zen11_
cm_deployment_bp/data/bi5t8rz.html
Database Tuning
• http://www.novell.com/documentation/zenworks11/zen11_
cm_deployment_bp/data/bi5tm7r.html
Database Performance Optimization
• http://www.novell.com/support/kb/doc.php?id=7005560