Urg. Early mornings. Up early for a 7 am partner breakfast. Roadmap, vision, feedback and comments from our reseller and channel partners.
The most common request – “give us early access to code” – we’re working on it right now.
Also gave my first session of the week – ZENworks Linux Management Best Practices – seems like this is the week of AV problems – one of the video feeds failed on me.
Writing this sitting in the tech lab with Naresh and Jose from the ZLM engineering team – talking about the keynote.
It’s almost 9pm – and we’ve hopefully done the final run for the Wednesday Keynote.
The keynote was a success – our demos worked well and my photo even got on the official Novell press kit. We had a minor glitch with the AV feed – the word is that the splitter box power failed. Typical!
Reports have it that the scooter was on one wheel as I cornered – it certainly felt as if I was about to run over a couple of Novell VPs 🙂 Nice to see the photos posted on novell.com
Much of the rest of the day spent giving press interviews – including Dave Kearns – then more preperation and rehearsal for the Wednesday keynote.
Sunday morning – and I’m in Monday keynote rehersals. BrainShare is about to start.
I will be posting photos and comments from BrainShare during the week.
The scooter came plastered with a strong warning (clicky for big):
1. Read the all manual carefully before operations.
2. Easily slide forward brakingin high speed
3. Centerof gravity should be retrusive when downgrade.
4. Center of gravity should be retrusive when braking and riders are better to went down.
5. Center of gravity should be moving rightwards when turn righ t, and moveing leftwards when turn left.
It was a late night. Lots of rehearsals and testing for the keynote.
Downtown SLC looks great – lots of Novell BrainShare banners everywhere; it’s also starting to fill up with people.
I’m putting together an article about building the BrainShare keynote demos. I’ll include information on ‘what and how’
Here are the screen shots from Monday:
Demo building is fun 🙂
I’ve been locked in our PM war room all day building servers and demos with Mark Schouls – one of the smartest guys around when it comes to systems management.
As always the demos are being built on code so fresh you can still smell the paint. We’ve found some interesting things for our engineers to look at – and as always time is short.
I’ll add more as we get closer to the keynote demos.
Another cross posting on Microsofts own internal discussions on software distribution to my team blog
Hmm.. This seems like a missing feature. I really only want to write this once and post to two blogs. That and trackback would be great.
 – I originally had multiple blogs – I moved from Blogspot to self-hosted WordPress; now consolidated to a single blog.
It has been claimed by some that:
Microsoft Active Directory along with Group Policy Object support for software distribution is everything a customer needs to manage workstations.
Here we will discuss that further.
I posted a lot of the previously internal ZENworks Linux Management/Red Carpet Enterprise configuration documentation. I dated it for December 2004 – which was when I posted it internally at Novell. Some day I must go back and clean up the formatting – it’s a raw cut and paste from the ZENworks internal wiki.
I was hunting around for some information on Mono dependancies when I found this article by Kevin Shockey:
I mailed Kevin:
I’ve just read your article from the end of last year – http://www.oreillynet.com/pub/wlg/6123 – and I thought it was particularly interesting.
One thing to note – did you know that the ZENworks Linux Management client components – also known as Red Carpet – are 100% open source and available without downloading ZENworks Linux Management?
We have the RPMs for many platforms at ftp://ftp.ximian.com/pub/redcarpet2 – certainly fast and easy.
Also we have the public Red Carpet server http://red-carpet.ximian.com which provides community updates – including those for Mono.
Finally we have another open source project – Open Carpet – which lets developers host their updates to be consumed by the Red Carpet/ZLM client components – http://opencarpet.org
Let me know if I can be of any further help – and please feel free to reference this data in the future.
Let’s see if this gets a response. I’m keen to evangelise the benefits of OpenCarpet for developers and hacker teams.