Comments on: Hey Microsoft… UP YOURS! http://mike.crute.org/blog/2006/02/28/hey-microsoft-up-yours/ import random; return random.shuffle(mike_crute.thoughts) Tue, 07 Oct 2008 00:51:25 +0000 http://wordpress.org/?v=2.5.1 By: Jeffrey B. Kane http://mike.crute.org/blog/2006/02/28/hey-microsoft-up-yours/#comment-177 Jeffrey B. Kane Tue, 11 Jul 2006 04:22:59 +0000 http://mike.crute.org/blog/2006/02/28/hey-microsoft-up-yours/#comment-177 Mike, SBS is not targeted at you so why would you care what it has or does!?! It's not bogus licensing... it's actually a pretty well balanced science. Consider that with standard Windows Servers, you would never put your Exchange Server on a Domain Controller. You'd never put your SQL server on a Domain Controller. Etc, etc, etc. The fact is that there are tons of businesses that have less than 20 users and a single server is PLENTY for them. Most of them didn't even have a server before SBS, so you aren't going to get Mr. Smallbusinessperson to start spending tons of money on hardware and maintenance etc, when he thought that his Win98 machines were doing just fine. Most of all though, the end-users of this product don't want to know any more than they already do about operating systems... they are experts in whatever field they are in, and SBS will help them do those jobs better. Simply. So they arenh't going to buy "boxes". Just a box. Mike,

SBS is not targeted at you so why would you care what it has or does!?! It’s not bogus licensing… it’s actually a pretty well balanced science.

Consider that with standard Windows Servers, you would never put your Exchange Server on a Domain Controller. You’d never put your SQL server on a Domain Controller. Etc, etc, etc.

The fact is that there are tons of businesses that have less than 20 users and a single server is PLENTY for them. Most of them didn’t even have a server before SBS, so you aren’t going to get Mr. Smallbusinessperson to start spending tons of money on hardware and maintenance etc, when he thought that his Win98 machines were doing just fine.

Most of all though, the end-users of this product don’t want to know any more than they already do about operating systems… they are experts in whatever field they are in, and SBS will help them do those jobs better. Simply. So they arenh’t going to buy “boxes”. Just a box.

]]> By: Mike Crute http://mike.crute.org/blog/2006/02/28/hey-microsoft-up-yours/#comment-12 Mike Crute Thu, 02 Mar 2006 16:50:00 +0000 http://mike.crute.org/blog/2006/02/28/hey-microsoft-up-yours/#comment-12 Don't get me wrong I actually find Windows server nice when I have to maintain a whole organization full of Windows PCs, Active Directory implemented properly makes this a snap. But for any real tasks such as email, web, file, database, etc... serving I use a real OS on my boxes. Same goes for all my network routing equiptment. None of that is the point here, what is really ticking me off is the bogus licensing restrictions they put on their software. In my situation we have an existing AD implementation to which I can not join a SBS server because of those stupid licensing restrictions. Another sidenote, we are using piloting opensource web based groupware. Exchange sucks and I don't want to run anything but AD on the Windows boxes. Don’t get me wrong I actually find Windows server nice when I have to maintain a whole organization full of Windows PCs, Active Directory implemented properly makes this a snap. But for any real tasks such as email, web, file, database, etc… serving I use a real OS on my boxes. Same goes for all my network routing equiptment.

None of that is the point here, what is really ticking me off is the bogus licensing restrictions they put on their software. In my situation we have an existing AD implementation to which I can not join a SBS server because of those stupid licensing restrictions.

Another sidenote, we are using piloting opensource web based groupware. Exchange sucks and I don’t want to run anything but AD on the Windows boxes.

]]> By: Paul Donley http://mike.crute.org/blog/2006/02/28/hey-microsoft-up-yours/#comment-11 Paul Donley Wed, 01 Mar 2006 21:53:20 +0000 http://mike.crute.org/blog/2006/02/28/hey-microsoft-up-yours/#comment-11 Hey Crute, read a little further along willya? First, you can have a backup domain controller (BDC) -- a copy of your domain for a rollover when main box crashes. Second, you can configure a server for Exchange. It's even recommended if you're running more than 20 active systems on the network. Third, you can have any number of file servers on the network. Fourth, you can have a Linux box anywhere on your network. One of the best uses for it would be as a DMZ controller or firewall. The idea of having other servers take up an SBS CAL suddenly makes sense, if they're Microsoft boxes. If you use Linux on the servers, you don't have to worry about the CAL usually. You use up the CALs for a machine, whatever your use of the machine. One of the most common examples is having a local fax/printer on the main desk. It only uses up one CAL on the network, but the faxes can go out over SBS (as email through Exchange) or through the fax modem. I love Linux. It's easy to configure, inexpensive if you know what you're doing with it, and frankly gives you the sense that you know what you're doing since you're not working through tiny peepholes in the GUI (often obscured even more by confusing MS documentation.) But give SBS its due. It's a great system for a small business because it integrates the management capabilities of SharePoint and the power of Exchange. If you don't like Exchange, join the club. The team that designed that mess was high on drugs designed specially for them. SharePoint and SBS 2003, on the other hand, are great products that bridge much of the gap between the black box server and a real application to help manage a business. Take a good look at SharePoint, then compare it with other CMS. If your people like to surf the web and still want to feel like they're working, SharePoint is for them! --Paul Hey Crute, read a little further along willya?
First, you can have a backup domain controller (BDC) — a copy of your domain for a rollover when main box crashes.
Second, you can configure a server for Exchange. It’s even recommended if you’re running more than 20 active systems on the network.
Third, you can have any number of file servers on the network.
Fourth, you can have a Linux box anywhere on your network. One of the best uses for it would be as a DMZ controller or firewall.

The idea of having other servers take up an SBS CAL suddenly makes sense, if they’re Microsoft boxes. If you use Linux on the servers, you don’t have to worry about the CAL usually.
You use up the CALs for a machine, whatever your use of the machine. One of the most common examples is having a local fax/printer on the main desk. It only uses up one CAL on the network, but the faxes can go out over SBS (as email through Exchange) or through the fax modem.

I love Linux. It’s easy to configure, inexpensive if you know what you’re doing with it, and frankly gives you the sense that you know what you’re doing since you’re not working through tiny peepholes in the GUI (often obscured even more by confusing MS documentation.)
But give SBS its due. It’s a great system for a small business because it integrates the management capabilities of SharePoint and the power of Exchange.
If you don’t like Exchange, join the club. The team that designed that mess was high on drugs designed specially for them.

SharePoint and SBS 2003, on the other hand, are great products that bridge much of the gap between the black box server and a real application to help manage a business.
Take a good look at SharePoint, then compare it with other CMS. If your people like to surf the web and still want to feel like they’re working, SharePoint is for them!

–Paul

]]>