2007

Longhorn Virtual Labs

Great find by David, Microsoft Technet has a few new Longhorn virtual labs. These labs are free and are a great way to explore the new technology that you may not be familiar with. For the low low price of $0 you get to download a Word document that serves as your guide through the lab. It tells you what to click on, what to do, what different things mean and you can follow them point by point or go exploring on your own.

Note: Toy labs are not a good substitute for deploying, configuring and managing a proper lab network. However, for the first look and specific task training, they are more than enough.

Managing Windows Longhorn Server and Windows Vista using Group Policy

Managing Windows Vista and Windows Server Longhorn Network Bandwidth with Policy-based Quality of Service

Windows Server Longhorn Beta 2 Server Core

Windows Server Longhorn Beta 2 Server Manager

Microsoft Windows Server "Longhorn" Beta 2 Terminal Services Gateway and Remote Programs/p>

If you’re in the MonkeyForce check out the IIS 7 virtual labs as well.

Breaking down the Microsoft vs. Linux Patent Scare

(not a rant, hey there is first time for everything)

By now you’ve surely seen at least a dozen articles on how, depending on the source, Microsoft is ready to eliminate Linux from existence or collect royalties or sue “them” into oblivion. It’s a juicy topic because it’s about a lot of money, emotion, business with a great protagonist and so on. Everyone from Scoble down to the guy with a rock standing in front of a copyright billboard has chimed in. What’s it really about and why will it never happen?

It’s about Microsoft trying to put the Interop picture together for Longhorn.

Because nobody likes Microsoft already, and suing will only make it worse while admitting failure.

Point 1: It’s not about Linux.

Many bloggers will pull stories and anecdotes about how this is about a huge company that is seemingly falling apart (while making 14 billion dollars a quarter) exerting it’s power to eliminate competition. They then transition to the conspiracy theories that SCO lawsuits were funded by Microsoft. Then they support that by a dozen or so articles in which Microsoft lost the patent lawsuit and had to part with a mountain of cash. And, for the cherry on top, they sprinkle something about Microsoft stealing from Apple for 25 years, how any offending code would be rewritten/removed within hours, etc. But in a nutshell, the take of nearly every article is about an evil Microsoft trying to kill off the little Linux.

Meanwhile at the ranch Microsoft is working at perhaps the most significant software release in it’s history, Longhorn Server, which will set it miles apart from any other server suite available just like it’s done with it’s Office suite. And if you see where Microsoft actually makes money you realize that selling Microsoft’s next server into the enterprise involves having a decent interop story for the customer. Whether Microsoft likes it or not, the business reality is that more and more ISV’s are writing software and delivering it on Linux servers – so for Longhorn to be a sell it has to be able to prove it can play nicely. Thats all there is to all this: Microsoft is trying to build up it’s glossy orange flyer with Linux distribution vendors who have signed interoperability agreements so Microsoft can go to the customer and say “Look, you run Redhat, Novell, Ubuntu and Debian and we have interop agreements with those folks to make sure the application you just purchased will be compatible with the middleware you have running on Windows Server” – and how do you coerce the distribution vendors into siding with you and working on Interop? By sprinkling a little patent doubt in the air which you (Microsoft) know full well you won’t be pursuing.

 

Point 2: Enough people already hate Microsoft

There are 800 lawyers at Microsoft, likely 780 of them are there to deal with continuous lawsuits stemming from inappropriate behavior that happened ten years ago. But read the blogs and you’re left with the impression that those 800 lawyers are just there to do recruiting to get more lawyers to sue FOSS out of existence.

It’s not difficult to find people that hate Microsoft, be it a developer a customer or partner. When you’re big you’re bound to screw people. Heck, even a one man shop has managed to make enemies for itself. Just the nature of business.

So let me clue you in to a little thing about Microsoft that I’ve learned about their culture through working with them for the past 10 years or so. Microsoft guys, be it in sales, development, even executive levels truly believe, beyond a shadow of doubt, that they are the best. Absolutely, without question, Microsoft BOB in one hand and Windows ME in the other, 640K ought to be enough for everyone – the best. Whether they are right or not, Microsoft, by culture, believes they are the best, with the best value, best technology. How? Through innovation.

Going into extended patent lawsuits would make it pretty clear to its shareholders and employees that Microsoft is no longer a business built on innovation and expertise, but one that barely survives on the very thing they have been widely accused for years – FUD. Which is why you’ll never see the lawsuits. It would be ridiculously expensive and highly demotivating for the company culture and what Microsoft stands for.

Microsoft doing a patent suit over innovation is similar in experience to the blind test of which soda you prefer. If you don’t win do you turn around and say “Wow, I’ve been a jackass for 20 years, thank you, thank you for pointing out what I’d like drinking better” or do you walk away in resentment that you picked incorrectly?

Same for the Microsoft customers. Their customers already dislike the business practices that Microsoft has. They outright hate the licensing. Developers and partners aren’t far behind. And we’re ALL buying software and hardware from other companies. So is Microsoft going to pour gasoline on that fire by telling us, to our face, that we’re thieves as we have already purchased solutions based on non-Microsoft products? Or will they just try to build a better story about how this new thing they have coming will play nicely with that third party stuff we already bought?

Personal note:

As you’ve seen on this blog, I talk a fair amount of smack against Microsoft. Yes, they deserve it. I also run more Microsoft software than any sane person ought to be allowed to. I’ve been awarded a Microsoft MVP award for two years in a row. I send large checks to Microsoft, on monthly basis, all while bitching about how Microsoft is putting me in the early grave with lack of patch QC. I write about problems and solutions for Microsoft software, all while leading ITPRO groups focusing on Microsoft software. I develop software for the Microsoft platform. And on daily basis I am asked if I love or hate Microsoft, if I’m pro or con Microsoft, if, if if. Everyone wants a fanboy.

The key thing to understand here is that when it comes to business there are many shades of grey, many circumstances, many compromises that have to be made as you go on. Thats what makes people successful, realizing that there are tradeoffs to every position. The alternative, as you’ve seen in the blog posts on this subject, is to take black vs. white approach to it all, cite historical references and dollar figures and adopt a faith-based view on business management by which you accept a single fundamental truth while ignoring every shred of concrete evidence that smashes it to pieces. Try to see the bigger picture here or come to terms with having to move to rural Mississippi.

Shockey Monkey - New Web Site, Consulting Best Practice

As Shockey Monkey project grows, and let’s face it, as there are many of you out there using it and making your living on it the need for a serious site grows. I have worked very hard today to make ShockeyMonkey.com a better home for all Shockey Monkey information.

The new site has the long desired roadmap, updated FAQ, and something I think many of you will really enjoy even if you have no intent to ever use Shockey Monkey. I’ve spoken to well over a thousand of you over the last year of the Shockey Monkey development and through that process identified a lot of best practices, pitfalls and challenges an IT solution shop faces. While my long term vision of Shockey Monkey is to help lessen some of the pains, I am taking to writing down some of those consulting best practices and management tips in form of documentation on the site.

Consulting best practices & Shockey Monkey Documentation

Find out how to shape your IT practice through best practices. 

What’s the big idea? You can figure out what to put in for the email branding screen or what an announcement is. But what you might want to learn is what makes an effective announcement, what to say, what to avoid, what works and what doesn’t.

That, I believe, is the overall value of Shockey Monkey, the collective intelligence of SMB IT community put to work for your business.

Coming up this week: Customer-facing documentation and video to help train the customers, Shockey Monkey discussion group/list, documentation and videos on managing tickets and a few more developments on ticket management workflow implementation.

The Seventh Monkey of The Seventh Monkey

(those of you that picked up on the Iron Maiden reverence, you rock!)

Exciting Saturday night of coding and Shockey Monkey deployments. Big thanks to Armen Varjabedian of PropelNet, Robert Muir of Practical IT Services, Ken Edwards of Maverick Mesa and Garett Chipman of TVG Consulting who wasted their Saturday night to help deploy the new Shockey Monkey management engine. This is the backend management code that actually creates portals: creating the user accounts, copying files from cvs, setting up httpd.conf virtual servers, copying over caching includes, initializing the database, etc. For all it does it’s actually quite a slim piece of code, only 124 lines most of which are for error handling. It does run one monster SQL query that 341 lines to setup the db schema for your portal.

Why is this cool? (take it with a grain of salt, it’s 1AM Sunday and I’m excited about the evening of coding I just wrapped) It’s cool because this backend system allows me to manipulate data over the entire Shockey Monkey enterprise. For example, I can drop a single file or execute a single SQL query over 2,000 isolated virtual servers on demand. I can also link and team them together, relocate them (when Shockey Monkey grows it will have geographical locations which at this point look to include UK and Australia in addition to USA Dallas / LA.)

But, it’s not all good news. First, my management of these activations blows. The documentation blows. I’ve had to ask people to go look at 20 minutes worth of video 3 times so they would get the single 5 word sentance I said somewhere in the middle of it and didn’t highlight it enough. The process for registering/signing up for Shockey Monkey blows – you have 3 sites, 2 hoops, and two other places to deal with before you can even sign in. The process can take hours, days – or if you’re POM trying to get an SSL certificate with a .AU domain… well, prepare to wait. I aim to address all of these issues today, along with a web site, a single signup, single activation and more accountable activation process.

I’ve managed to create all this, yet it took doing it wrong 2,300 times to finally realize how to do it right. I might as well move to India. 

VladCast Episode 5

VladCast 5, the SMB ITPRO world condensed into a loud 5 minute podcast:

– Less than two weeks left to get to SBS Migration Conference
– Interested in Cougar? Ask your SBS group leader for a beta invite.
– Changes with Longhorn
– Susan’s Patch-week: WSUS3, WSUS v2 Client
– Contest: Post the authors name, book title and why you’d read it!

Play VladCast: [audio:http://www.vladville.com/media/VladCast5.mp3]

Add feed to iTunes  / File Attachment: VladCast5.mp3 (1883 KB)

HP Mobility Misses Again: No WM6 upgrade for iPaq

The more Carly changes, the more they HP the same.

While iMate is well on its way to provide the third OS upgrade to their iMate JasJar PocketPC (from 2003 to WM5 and now to WM6) the HP strikes again – denying updates to their entire customer base. And while all the WM5 devices can be easilly upgraded to WM6 because it’s the same underlying operating system (WindowsCE 5.0/5.2), HP yet again leaves it’s customers with fairly pricey paperweights.

The message: Ignore HP.

While I got burned by HP years ago, I still do not have Vista x64 drivers for any of the printers we use. HP continues to sell equipment with outdated technology while pricing it at a premium. Are consumers dumb enough not to notice the difference? Apparently, yes.

Shockey Monkey - Development Center Added

The next time you login to Shockey Monkey support portal at OWN you’ll notice a new tab. Development.

The Development tab is a bug and feature wishlist tracker that will allow us to take public feedback on features you are looking for. It will also provide you with the ability to report any bugs that you may encounter and allow others that are experiencing the same bug to see if it was opened already (known problem). Feature wishlist, as the name implies, let’s you request features you think our software should have. Just like the bug tracker, each wishlist is open for public updates allowing anyone in the system to comment on the bug or on the feature, giving our entire customer base an input into the type of software and features we develop. Anotherwords, we won’t R2 you – you’ll see exactly what type of a customer we’re developing solutions for because the name of the person will be printed on it.

Please allow me to point out the message here that is far bigger than Shockey Monkey:

We are doing this not just for Shockey Monkey, but for our entire software and service portfolio. That means no more “there was no interest”, no more “I’ve never seen that before” or “this is only happening to you”

Is this the kind of message you are sending to your customers and partners? If not, do you understand why you need to have a customer-facing portal thats more than just trouble ticket junk and shiny charts? So if you don’t have Shockey Monkey, maybe you should.

-Vlad

P.S. This is what I’ve been up to this week, so if you didn’t get your Shockey Monkey turned up since weekend ended, now you know why

Microsoft starts dropping Longhorn features

Microsoft has announced that several cool virtualization features will be dropped from what was promised for Longhorn release. Bink quotes a seemingly angry quote complaining about the lack of live migration, no hot-adding of resources, CPU core limitations, etc.

I’m sure there are many that will be very disappointed about this move.

I am not one of them.

Even though my business is based on the Microsoft virtualization platform (not Vmware) from a customer and partner scenario I am not looking forward to Longhorn’s virtualization feature set. That is not what I find exciting about the new server.

What I am particularly excited about is the new IIS 7 modular configuration and management, the new Longhorn Core Server free of the usual junk. Given the past year or so, I’d just like a reliable platform that Longhorn promises and they can release all the “cool” features when they feel they are ready.

Mailing List Recommendations - Help!

This worked really well for the SBS Show but as I put more and more stuff out directly here on Vladville I’m finally starting to give in to the constant requests for a mailing list – again. The reason Vladville came to life in the first place was because I was tired of managing the mailing list with a few hundred replies every time I sent a piece out. But there is a high demand and let’s face it, a large majority of you (80%) is not reading this blog via RSS.

So, would anyone care to recommend a mailing list service? I’m a little opposed to freebies (no Google, no Yahoo) because of their terms of service so is there anything out there that is competitive with Constant Contact?

Is that another Radhakrishna on your QC team?

Second month in a row without a major Microsoft patch incident – patches apply properly, systems reboot as intended, no BSoD’s, no application incompatibilities. Just like it’s supposed to work.

Are we starting to see a trend in improved patch release management at Microsoft?