Avoiding Common Novell ZENworks Configuration Management Implementation Pitfalls

  • 1,623 views
Uploaded on

Migrations and deployments aren't always straightforward and training and manuals don't always provide all the information needed for a successful deployment. In this session, you will learn the top …

Migrations and deployments aren't always straightforward and training and manuals don't always provide all the information needed for a successful deployment. In this session, you will learn the top 10 implementation pitfalls encountered in dozens of Novell ZENworks Configuration Management customer installations—and how to avoid them. The session will also cover deployment and ongoing maintenance tips, to enable you to do it right the first time!

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
1,623
On Slideshare
0
From Embeds
0
Number of Embeds
0

Actions

Shares
Downloads
102
Comments
0
Likes
0

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. Avoiding Common Novell ZENworks ® ® Configuration Management Implementation Pitfalls Ryan Kensrud Senior Technology Specialist Novell, Inc./rkensrud@novell.com
  • 2. Agenda Introductions Top 10 pitfalls Questions and Answers 2 © Novell, Inc. All rights reserved.
  • 3. Introduction
  • 4. Introductions • Who am I? • Reviewing those items if done correctly that make an implementation go smoothly. If they are not done correctly they present major pitfalls to a Novell ® ZENworks Configuration Management implementation. ® • Top ten list from least to most critical • Products to be talked about – ZENworks Configuration Manager, ZENworks Application ® Virtualization and ZENworks Asset Management 4 © Novell, Inc. All rights reserved.
  • 5. Top Ten Pitfalls to Avoid
  • 6. 10 - OS Choice • Your choice of OS for the ZENworks Configuration Management ® servers can affect the implementation – Choose the flavor your team has experience with – Do not use a ZCM implementation as a foray into Linux – Make sure to use a supported OS platform > Windows 2k3, 2k8 both 32 and 64 bit versions > Linux SUSE Linux Enterprise Server 10 and 11 both 32 and ® 64 bit versions, OES 2 – Look at using Virtualization for the OS 6 © Novell, Inc. All rights reserved.
  • 7. 9 - Training • Training on ZENworks Configuration Management ® is very important to the success of the implementation – Get training ahead of implementation – Use classroom or study materials – Build a lab to install ZCM in for testing and learning – Use Virtualization for Lab servers to save on costs – Match OS and Database choice to production 7 © Novell, Inc. All rights reserved.
  • 8. 8 - Certificate Choice ZENworks Configuration Management can use ® either a self signed certificates or an external certificate. There is not a bad choice with either, it just needs to be a long term choice since changing from one to the other will result in needing to install new agents to all managed devices. – Make the choice and make sure you have all parties buy in on the decision – This needs to be the long term choice 8 © Novell, Inc. All rights reserved.
  • 9. 7 - User Source Choice • LDAP user source choice – Can use eDirectory or AD ™ – Needs to be an enterprise tree to be most effective > Contains OU structure > Not flat – Look to assigning content (applications and policies) via group and folder assignments 9 © Novell, Inc. All rights reserved.
  • 10. 6 - Database Choice Make sure and use a supported Database platform – Sybase Version 10.0.1 – MS SQL 2005 – Oracle 10g Version 10.2.0.1.0 10 © Novell, Inc. All rights reserved.
  • 11. 5 - Migration Planning Important step to minimize the impact of the migration to ZENworks Configuration Management ® – Use hardware replacement as a migration point – Use new desktop OS as migration point – Abandon the current management practices with old hardware or OS – If staying with current OS do not change how locked down the OS is – Roll out in manageable groups of devices – Perform lots of testing prior to production roll outs 11 © Novell, Inc. All rights reserved.
  • 12. 4 - Executive Buy In • Get executive buy in before rolling anything out to end users – Especially true if deploying a secured desktop – Minimizes risk of end user push back – Develop success criteria as part of buy in – Use success criteria as project goals 12 © Novell, Inc. All rights reserved.
  • 13. 3 - Organizational Policies • Get the acceptable use policies in place prior to locking down desktops – Technology should be enforcing organizational policies – Examples of organizational policies > Acceptable computer use > Software installation > Remote access – Once organizational policies are in place you can use ZENworks Configuration Management and Endpoint ® management to secure the desktops – Use a change in OS as a good time to further lock down a desktop 13 © Novell, Inc. All rights reserved.
  • 14. 2 - Application Readiness • Prior to deployment the applications need to be packaged and organized for deployment – Start this process early, can be before deployment of ZENworks ® Configuration Management core infrastructure – Use inventory tools to gather information on what is currently deployed, what version, how many, and to whom – Make sure current App versions are supported on new OS if deploying ZCM on new OS – Create prioritized list for packaging – Deploy new apps in staged approach – App Virtualization can help some common app deployment hurdles 14 © Novell, Inc. All rights reserved.
  • 15. 1 - Capacity Planning • Improper capacity planning can severely impact the implementation – Understand numbers of currently deployed devices – Look to management for potential growth numbers – Critical for Database choice – Critical for server sizing and numbers – ZENworks Configuration Management can grow very easily if good ® choices made around Database in the beginning – Use DNS names for accessing your servers – Look at using Virtualization or Platespin to assist in making changes if ® not where it needs to be – Use “Best Practice and scalability doc” for guidelines 15 © Novell, Inc. All rights reserved.
  • 16. Questions and Answers
  • 17. Information Sources • Good sources of information to help plan your deployment – Documentation - http://www.novell.com/documentation/zcm10/ – Best Practices Guide - http://www.novell.com/documentation/zcm10/zcm10_deployment_bp/?page=/documentation/zcm10/zcm10_deployment_bp/data/ – App Deploy - http://www.appdeploy.com/ – Admin Studio - http://www.flexerasoftware.com/products/adminstudio/features.htm – Novell Training - http://www.novell.com/training/ ® – Novell Self Study Training - ® http://www.novell.com/training/courseware/ts_proj_info.jsp?pid=20402 17 © Novell, Inc. All rights reserved.
  • 18. Unpublished Work of Novell, Inc. All Rights Reserved. This work is an unpublished work and contains confidential, proprietary, and trade secret information of Novell, Inc. Access to this work is restricted to Novell employees who have a need to know to perform tasks within the scope of their assignments. No part of this work may be practiced, performed, copied, distributed, revised, modified, translated, abridged, condensed, expanded, collected, or adapted without the prior written consent of Novell, Inc. Any use or exploitation of this work without authorization could subject the perpetrator to criminal and civil liability. General Disclaimer This document is not to be construed as a promise by any participating company to develop, deliver, or market a product. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. Novell, Inc. makes no representations or warranties with respect to the contents of this document, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. The development, release, and timing of features or functionality described for Novell products remains at the sole discretion of Novell. Further, Novell, Inc. reserves the right to revise this document and to make changes to its content, at any time, without obligation to notify any person or entity of such revisions or changes. All Novell marks referenced in this presentation are trademarks or registered trademarks of Novell, Inc. in the United States and other countries. All third-party trademarks are the property of their respective owners.