Tuesday, August 28, 2007
ZenCM (a.k.a. Zen 10)
We're taking a look at ZenCM right now, as it's the Zen that supports Vista. I saw quite a lot about it back at Brainshare, so I have some expectations. Now that it is out, there is a manual out. We like manuals. They tell us what to expect.
Some quick hits on differences that'll cause us to do things differently from previous Zen versions:
There is also internal disgruntlement about the abandonment of edir as the policy repository, but I understand the sound business reasons for it. The loss of the ability to have NetWare be the file-source for application installs is also something that is causing grumbling, as that's the infrastructure that's well built for large scale deployments. The fact that we need yet another server for this is also causing grumbling, though in the end we'll be using the server that was slated to be the real server for the Zen Asset Inventory, as its beefy enough to handle it (we think).
And then the imaging question... we've not been using Zen's imaging because we've been using another product. However, that other product plays hobb with Workstation Import, and from the sounds of it that'll still be a problem with ZenCM. So, no device-based policies for us.
All in all, we'll end up going with it because 1) it's free to us, and 2) we've always been using it. That said, there will be a push to use the built-in AD tools as they are perceived to be less clunky. No agent to install, that sort of thing.
Some quick hits on differences that'll cause us to do things differently from previous Zen versions:
- No NetWare support, so we'll need at least one new server to drive this thing.
- Application deployment won't work with NetWare as a file source, so all those MSI's will have to be hosted on Windows somewhere (no Linux support yet, though that's probably SP1 stuff).
- Inventory has been rolled into the central product, so no need for a separate Inventory server like the past (the past product was the Inventory side of Zen Asset Management. ZAM now is just Asset Management).
- No AXT-based installs, just MSI and Simple Application.
- The MSI installs will FORCE us to start looking at ApplicationStudio, whether we like it or not.
- Introduces a single point of failure for Zen policy, as it no longer uses eDir for a policy repository, and instead uses the ZenCM server. Which in our case will be a single server, as we're not $$$ enough for two, nor do our users segregate into large chunks well.
There is also internal disgruntlement about the abandonment of edir as the policy repository, but I understand the sound business reasons for it. The loss of the ability to have NetWare be the file-source for application installs is also something that is causing grumbling, as that's the infrastructure that's well built for large scale deployments. The fact that we need yet another server for this is also causing grumbling, though in the end we'll be using the server that was slated to be the real server for the Zen Asset Inventory, as its beefy enough to handle it (we think).
And then the imaging question... we've not been using Zen's imaging because we've been using another product. However, that other product plays hobb with Workstation Import, and from the sounds of it that'll still be a problem with ZenCM. So, no device-based policies for us.
All in all, we'll end up going with it because 1) it's free to us, and 2) we've always been using it. That said, there will be a push to use the built-in AD tools as they are perceived to be less clunky. No agent to install, that sort of thing.
<permalink> posted by riedesg : 8/28/2007 10:51:00 AM
