Technorati Tags:
SBS 2008,
licensing,
CALs
So today we are performing our first SBS 2008 production installation. I’d like to say this has gone smoothly without any glitches and for the most part so far it has.
We were all prepared to complete a migration using the technet provided resources but unfortunately the clients already flaky server decided to give up the ghost completely so we have had to resort to a brand new install. We were able to get all the clients data off a current backup including their Exchange data so after importing all the data and running through the to-do list we were ready to install the Client Access Licences (CALs)
After 20 minutes of 4 of us searching trying to find some kind of licensing console and doing some searching on the ‘net it finally dawned on us that there is in fact no licensing console and no licensing enforcement - yep, you heard that right - NO LICENSING CONSOLE AND NO LICENSING ENFORCEMENT!!!
So what does this say about Microsoft? Other software vendors are able (and do) lock out users of their software if the number of licences is exceeded - so why don’t Microsoft? In SBS 2003 via the licensing console we had a basic way of telling how many licences were installed and the maximum usage of those licences since the last reboot - admittedly this wasn’t foolproof but it was better than nothing! Now not only do we have to change our policies to record how many licences a client has, but it is also harder to track how many users/devices they have connected to their server - that’s what I call a huge step backwards!
I would really love someone from Microsoft to provide a single good reason for removing licence enforcement, I really would. In one fell swoop not only have MS made our lives more difficult from a technical/admin point of view, they’ve also made it (even) easier for unscrupulous partners and customers to ignore licensing issues - Come on Microsoft, you need to be sharper than this!
Technorati Tags:
SBS 2008,
Licensing,
CALs