by ezs | Feb 24, 2006 | blogging, evilzenscientist, Novell BrainShare, Uncategorized, ZENworks
We’re in the home straight; final testing for the new Novell Cool Blogs.
I’ve been hitting the test system hard in the last week – making suggestions to the Novell team that are making this happen. There are two main updates – the plan is now to use WordPress for the blog infrastucture; second launch is due ‘next week’.
The internal test system looks really great; all Novell branded and look and feel – but with live blog content. All of your favourite features should be there – comments, trackback, pings – as well as some unique blog posts from Novell’s strongest personalities.
I’ll leave it until announcement time so as not to spoil the surprise – but watch out – this is going to be big!
Special kudos to Mr Jared Nyland from Novell’s web team; he’s been awesome.
by ezs | Feb 21, 2006 | blogging, evilzenscientist, podcast, Uncategorized, ZENworks
At last – the flood of community content I’ve blogged about for the last month or so is starting to appear.
First out of the gates is Novell OpenAudio – Podcasts for the broad Novell Community.
I’ll not spoil the suprise – but I recorded a series of four podcasts with Erin Quill about a month ago. Watch out for them to show up.
by ezs | Feb 16, 2006 | blogging, evilzenscientist, Uncategorized, ZENworks
Guy Kawasaki has a great post tonight on Building a Community.
I’m not going to post it here – but take a read.
We’re right in the middle of getting the Novell CoolBlogs kicked off – this is great timely reading.
[Edit: this also got picked up by Robert Scoble; who added ‘go visit your community’. My comment back was this was great for well funded evangelists. What I also meant to add was that it also only works if you have clusters of community members in places you go.]
by ezs | Feb 8, 2006 | blogging, Evangelism, evilzenscientist, Novell BrainShare, Uncategorized, ZENworks
More updates on BrainShare 2006.
I am in Provo, UT all week – working with Mark Schouls – on our BrainShare session and demo:
Session Title: |
|
ZENworks Design, and the Lifecycle Management Framework |
Length: |
|
2 Hours |
Level: |
|
Advanced |
Abstract: |
|
Over the past number of years Novell has presented the ZENworks Lifecycle Management diagram in many of the ZENworks related sessions. This session will focus squarly on how to design a rock solid ZENworks infrastructure and put lifecycle management into practice. Join this session to learn how to fully leverage your ZENworks architecture, take advantage of best practices, and see a live lifecycle management demonstration. This session is a combination of both theory and live demonstration. |
Speaker: |
|
Mark Schouls
ZENworks Product Manager
Novell, Inc.
Martin Buckley
Director of Product Management – Resource Management
Novell, Inc.
|
Should be good fun. We’re working on the ‘minimal slides, maximum demo’ approach.
So far I am documenting how to build a successful ZENworks demo/workshop/lab – I will get that posted to the (soon to be launched) Novell Cool Blogs community.
The summary of the session describes the life of an employee – presented in a two hour session. From day zero (hire) to when the employee leaves for pastures new – the session and demo will describe how ZENworks, Novell Identity Manager and other solutions can control the lifecycle of the user and their hardware.
I’ll post more in the next week or so – but I’m saving the bulk of the information for the new Cool Blogs!
by ezs | Jan 19, 2006 | Evangelism, evilzenscientist, Linux, Novell BrainShare, patching, podcast, Uncategorized, ZENworks
I recorded a series of podcasts today for the new Novell Communities site.
Usual delays – see posts below – but should be up and posted in mid-February.
Topics for discussion: ZENworks 7, ZENworks Asset Management, Patching and BrainShare 2006.
Cool.
by ezs | Jan 18, 2006 | Evangelism, evilzenscientist, Uncategorized, ZENworks
I wrote a few days ago on how a few Novell people are going to start blogging on CoolSolutions.
This is delayed. Sigh.
End of quarter IT lockdown is the reason. Means that our internal IT people do not touch IT systems during quarter and year end periods.
Looks like another month of waiting.. I’m still collecting the requests for the first post 🙂
Recent Comments