I’m no MS fan. If I was in charge of our migration I would’ve explored some sort of hybrid system, using MS to serve up directory services and OES or Linux to serve up files.
I would’ve stuck with ZCM for at least another year, and really put v11 through its paces.
We where lucky to have 11 people to help out… 4 are network admins, one is a supervisor, and one was a temp we brought in. Everyone rolled up their sleeves to get this done – all while doing “emergency projects” and people still got to take vacation and sick leave during the process – effectively I’d say we had about 8.5 guys working on this at any given time.
When all was said and done our Zenworks replacement cost us over $100K to get into for the first year, which cost us more than our OES+ZCM+Groupwise yearly cost. We also had a HUGE learning curve in learning a new desktop management tool along with all the “new stuff” that we stepped into with windows.
In the end, we don’t have fewer problems… just different problems.
Are we better off? I sure don’t see it.
]]>Most of the organisations I mention in the article don’t have 11 staff to handle these migrations. Most of them have to make do with 2-4. I also want to clarify that I’m not “suggesting” these timelines – they’ve been reported to me by these customers. I’m not making this up!
Yes, ZCM 10 was buggy, but by 10.3 was stable and we had great success with it. Now at 11.2, it is very stable and customers are very happy.
I’m glad your migration went well, and that you saved your job. I also appreciate the candid comments about your experiences with Windows vs. Novell.
Thanks!
]]>It’s been one of the hardest things to get across for us as a partner: that Novell is more than the old NetWare, that they have modern, relevant solutions that run natively in Microsoft/AD. Those customers that have been open-minded enough to listen and try have been very surprised and impressed (ZENworks is a perfect example of this!). Too many customers, however, have drunk the blue Kool-Aid and now have a purely blue-tinted view of IT. If it ain’t stamped with the Microsoft logo, it couldn’t possibly be good!
And I agree with you – OES and GroupWise are rock-solid!
]]>We just transitioned from Novell to MS this past summer. The change involved touching some 4000 workstations and a couple of dozen servers.. and we got it done in just a few short months with a crew of 11 – so I don’t really buy the migration timeline that the author is suggesting.
Finding a replacement for Netstorage wasn’t an easy task – but our new product is far superior to Novell’s offerings. Its WebDAV even works with modern desktop OSes like Windows Vista and 7.. there’s none of that “Just use a 3rd party WebDAV” nonsense.
I REALLY would’ve like to keep ZCM – but ZCM 10 was so buggy that nobody wanted to give it another chance. Sorry Novell…
There was no way we where going down the Exchange path.. and we raised a few eyebrows when we openly laughed at people who suggested that because we where migrating to MS we just “need Exchange”. Nope.. we went Google – and I’m really surprised about how well it’s going.
After running MS servers for almost a year here are my findings from the trench
* the biggest thing I miss is how well Novell provided file services. It just worked… and it worked well. NTFS’s ACLs are embedded into every file and directory, so when you make a change the client has to molest every part of the path.. it’s slow and inefficient. Move a file or directory and the ACLs are stuck to it, resulting in some weirdness that’s described as a feature. WTH??
* eDir is still superior to mAD.
* Novell/OES File services are better than MS
* Groupwise is just another email system
* ZCM suffers from a history of bugs – v10 was really v1.0