What gives you an equal headache to subnet masking without a subnet calculator? Well, probably a server migration of any size with considerable changes in technology, licensing and options. Then finally gaining enough confidence to place the order based on what you know and forecast what you will need.
Today I finally placed such an order with Dell. The last time I made such decision to place a large purchase with them was years ago when I first arrived here and had to do a PC Rollout, man those days were hectic.
For the past several years I had been informing superiors about the need to get a new primary server and for years it kept being put on the back burner for financial reasons or simply, "let's see how it goes." Fortunately the "let's see how it goes," approach got us through several years, of course I was under the server's hood constantly making sure it remained optimal and maintained so any major disasters would be avoided. This preventative maintenance and care paid off and yet this server we are currently running on is still kicking like a 90 yr. old man talking about the olden days in his death bed. Or maybe the analogy of Moses would be better, his 'eye has not grown dim or his vital force did not flee him.' That's how I feel this server is operating right now. It is still very useful for our environment but we are limited in what we can do with it. We are flying up but hitting the ceiling. Also, we are no longer supported with both hardware and software, for over several years now, which is not good in IT. Either way, it has
served its purpose and it needs to be retired, thus the dawn of a new primary server.
I must admit, I am not as seasoned as many other vets in the field, but I do no how to do my job and manage a network. I didn't start as a network admin in a small business
taking an old UNIX guy's job for failing at Windows because I looked cute on a computer. I "acquired" it because I was worth a shot and had some crazy motivation to excel in this field and still do--though some priorities have changed.
Anyway, enough AdminAlive Lore™, that's a subject for another time and has already been slightly covered elsewhere (for those that knew the old me). Let's talk about the process and many other details I had to become familiar with before becoming comfortable with this purchase.
Information Gathering, Presales
To start out with, I really began the process (on and off) in June of this year. As I do with most bigger purchases, I decided roughly what solution I needed and requested a quote to find the price ranges I was looking at and what could be either changed in the configuration or what could be left out all together. Usually though before even requesting a quote from our Dell rep, I normally configure a machine or server on their website to get an even clearer understanding of what hardware is currently available and also an even more rougher price range. Then I shortly send a general spec request for quote and go from there.
The first quote I received was a good price and was lower than I expected it to be. It was on a PowerEdge R710. Here are the general specs, Xeon E5520 x1, RAID 1/5, SBS 2008, 4GB RAM, 146GB HDD and 300GB HDD (RAID 5) with SBS 2008 Std OEM.
Though I really wasn't looking to purchase at that time, I needed something to base my meetings with managers for pricing, technology and so forth--it's always good to be prepared.
Signs of The Times
Between then and November, we had several meetings regarding the future of our network and more on this new server and of course I brought what little I knew on pricing and hardware to the discussion. A lot revolved around, "well do we really need to upgrade? the server is working fine right now." One thing to remember, while it is good to know your technical reasons for certain things in a network, it often does
very little in convincing the guys that sign your check that a certain move is a good idea. After going in circles for a few times in various meetings I dropped my case even though I had compelling reasons to upgrade or at least set a day to do it.
It wasn't until about a month or two ago that we had a server crash that affected the network, and yes it was our primary server. It was due to the OS drives filling up with different Exchange logs, BadMail files and other accumulated data. So I wrote a script to take care of the BadMail files regularly (daily). I changed some settings on the Exchange logs management and moved some folders around. I literally began to rob Paul to pay Peter on the server's HDDs (or was it Peter I'm robbing?) I was able to free up enough space to continue operating and while the crash made the executives go D: it soon wore off and were more than happy to know that we are "good" again. Though now at this time knowing I had to keep a closer watch on the storage I kept having to make room to avoid another server crash due to no disk space. Long story short, it finally moved them to make a final okay to order a server around in the middle of November I believe.
Where's the Server?
We finally had our last meeting regarding this purchase and decided to go with it, I was asked, "so when can we expect this server purchase?" I said clearly, "probably mid December, it's been a while since I looked at the hardware and I need to do more research, plus they will probably have better deals so close to the close of the quarter."
Additionally what I wanted to also do was wait for the SBS 2008 Trial to come in the mail which I had ordered along with a fat SBS 2008 Unleashed book. I had a new OS coming and I had a lot to learn about it. I'm a 2K and XP admin, a lot has changed even though a lot has not changed. So therefore I had planned on installing it on a VM and playing with it there to get more comfortable with it, but of course it turned from one extreme to the other. Multiple times I got asked: "is it here yet?" "Well I don't see it, did you order it?" "Where is it?" "Why the wait?"
Seriously! Did I not say mid December? I thought to myself.
At this point (even after explaining over again 'why the wait' it was not stopping the badgering) I decided to say screw it. I put aside my hopes of running the trial version and began focusing on making a purchase based on an informed choice.
Let's Go All Out Decisions
I again followed my same procedure at this point as discussed before, but this time I decided not to be scared of optimizing the server. I remembered the time I did the PC Rollout and I skimped out on a lot of good upgrades at the time of purchase trying to make an appealing price to the CEO. An appealing price is what I got him and we ended up with what we paid for. The main reason we got a good "bang for the buck" was because compared to what this network was running on, it was a drastically huge improvement even if they
were running on 256MB of RAM when 512 - 1GB was normal. That is the reason I went "scalable" knowing we would probably outgrow the post-purchase specs in a year--at least I'd be able to upgrade them little by little.
By now though, I have quite a bit of purchasing and decision power in this company that I have a lot more say so in this area which I'm grateful for. To make this part of the story shorter, I ended up perhaps quadrupling the specs of the same PowerEdge R710 server for probably a few hundred dollars difference. Seriously, I'm talking about from UDIMM to RDIMM memory, from 4GB to 12GB, Single to Multi-CPU, from 4MB Cache to 8MB Cache, Enterprise consoles etc. It is a beast for this company and it didn't really cost that much more than the original gimp server configuration. How? Well as I had predicted, there would be better deals come December, 40% in fact for us plus whatever business discount we received saved us a ton and gained us a lot more. I was well below our anticipated cost that I even went for the better APC UPS, this baby here:
120V SmartUPS.
However it wasn't as easy as it may have seemed. I was actually pretty intimidated by the lack of experience with certain technologies and something new I had not had to deal with before, Microsoft Open Licensing.
Dell Server Technologies, and Vagueness
Let's first talk about the hardware aspect of this. As per the Dell quote (if you're familiar with their format) the Excel looking formatted quote form can be confusing. Mainly because the rows are labeled for certain hardware parts but the description columns are totally different hardware. So if it says Video Card the column where the hardware is specified will say something like "Intel Dual NIC (23423-234234234)". I actually became irritated at that and sent an email to one of the Dell reps, he explained that their system has not yet been 'updated' to the new format so some of the information does not match. Sounded like a generic excuse to me.
Aside from that confusing aspect, the hardware listed is usually incredibly vague save the CPU and perhaps the OS selection. So before actually making my decision based on the quote and general specs specified, I went line by line on the Dell configuration website to find out what each part was. Let me tell you, if you are not familiar with the Dell hardware setups and vague terms, it can really prove challenging or just plain "wtf?".
Hopefully the following information will prove useful to someone, those that may find themselves here:
The "Customize" button appeals to all of us, but if you are not sure what each configuration does or means, it may prove a pain in the bollocks.
So here I'll try to do my best not to burden this post further than I already have, but it's my blog, I'll be as wordy as I want! ;-)
PowerEdge R710, What do the Dell Configuration Options Mean?
I actually asked myself that question a few times on certain configuration menus and had to find out through their people, well here hopefully is a documented record of what they mean to save you the hassle. Mind you, a lot of the information is based on what multiple Dell representatives told me with their actual mouth, if it's incorrect, blame them and don't kill the messenger.
- Does choosing an 4, 6, 8 HDD chassis change the dimensions of the PowerEdge R710? No it doesn't, according to Dell, the "inside changed" but the outside remains the same, so yes it will stay a 2U even up to an 8 HDD chassis.
- What is PERC? PowerEdge RAID Controller. It is just a RAID controller for PowerEdge server's, that are able to utilize SAS.
- SBS 2008 options does not specify if it is 32 or 64 bit, which am I getting? You are getting 64 bit, because SBS 2008 only comes in 64 bit, because of Exchange.
- Does the SBS 2008 Std option come with 5 CALs? Yes.
- How are the OS Partitions options setup, how do they differ? If you choose a partitioned configuration it will automatically be done on your RAID 1 set array. So yes, if you have a 146GB RAID 1, it will be partitioned to 40 or 80GB, and you will have the left over as an additional partition (eww.) The other two options, "Maximum Microsoft OS Partition Override, GPT Enabled" and "Maximum Partition Size Override for Microsoft Windows Factory" are basically the same thing according to Dell. They use the entire disk to install your Server OS (OEM). I could not get a straight answer what GPT was, so I joked with him and said, "GIANT PARTITION TABLE maybe?" He did not respond, but on a more serious note, it may be for a Terabyte OS drive?
- Will the Dell configuration page warn me if I need a bigger power supply unit? Unfortunately, no. So since it only gives you two options, a 570w or a 870w PSU, I'd go with the 870w PSU if you do more than a few upgrades away from the default configuration.
- What is Broadcom's TOE? It is TCP/IP Offload Engine (PDF), sort of like what SCSI does for the CPU.
That is most of what I gathered, if anything else was left out I probably chose "No Option" and didn't bother with it because I knew I didn't need it.
Microsoft Open Licensing, Open Business Licensing, Open Value, Open Orifice?
(Disclaimer: I am not a Microsoft Licensing Specialist nor do I want to be, all information should be verified before making business decisions or I'll AdminSlap™ you. This information is here to simply share personal net admin experiences. That's right, in OG Courier font.)
I think one of the more problematic road blocks I came across was Microsoft's licensing programs and options and requirements. If you have not looked at the newer options, maybe you should, because it's confusing. Seriously, I spoke with a "Microsoft Licensing Specialist" twice and was still confused. Then I spoke with a reseller and he explained it a bit better than the specialist did. Then I again went back to Microsoft's licensing website and was further confused. One of the more confusing things is when all the licensing terms begin to sound the same.
So here I will attempt to give you accurate information--and as simple as I can possibly put it. Ready?
Pirate their software.
I'm kidding! While that may actually simplify things, you're bound to get pegged one day with a fat audit fine. Really it all depends on the size of your organization and how much money you have to spend. Options are split into two sections, ones you can pay in three split payments and ones you
must pay upfront, each have their advantages depending on what you need and what you want to spend.
Here are a few basics:
- Software Assurance is basically a common maintenance agreement as you probably have with many other vendors. It insures you get free upgrades to the newest software during your term, discounts, support, possible certifications and classes (all depending on what SA you choose.)
- Open Business Licensing is actually not very easy to find by simple Google searches (also known as MOB, Microsoft Open Business) and why, I do not know. In fact it doesn't even appear on the Microsoft website under that name, except for some obscure link to the Microsoft Australia division. But both Dell and a few other vendors offered that package to me in those exact words, "Open Business Licensing." However with a little bit of comparing, it seems to be the same as what Microsoft has listed as "Microsoft Open Licensing." From what I learned, this is the most basic and probably the one you may really be looking for. What it is, is a 2 yr renewable agreement that requires you to buy 5 licenses of any Microsoft product (for registration or renewal) that grants you rights to the respective software. However, you are only buying the software license and not any media. Therefore you save a small percentage per license since you are not buying media or retail boxing. Keep in mind, this is NOT OEM. That means you do the installations, you acquire the software by downloading it off Microsoft's site or using your own copy. All licensing tracking and keys are done online. This is an excellent solution for any business in my opinion. It eliminates the hassle of handling paper licenses and certificates etc. It also gives you the right to transfer licensees between computers and hardware, unlike OEM licenses that are only legible for the hardware it came with. There is no complicated forecasting or points system required either. This option also allows you to add the Software Assurance agreement if you wish or decline it as well (which is good, because it can become expensive with SA.) So case in point, MOB is a renewable agreement that gives you electronic licenses, no more paper.
- Open Value Licensing, is the other common option. According to Dell, it offers a 6-10% discount per license. However, every license you purchase automatically comes with Software Assurance for 3 yrs., which may spike your pricing right off the bat. But this option lets you spread the total payments across the 3 yrs. And yes, Software Assurance is paid for every single license, it is not a single package that blankets all licenses as you normally encounter in regular "maintenance agreements." The Microsoft website also has one with "Subscription" appended to it, the big difference that I saw was 1 or 3 yr. agreement with a few variations.
There are plenty of other options that Microsoft offers, while I don't really consider them options but more like legalistic management, MOB seems to be perhaps the cheapest and most effective option for smaller businesses, unless you upgrade a lot and like having the latest software versions--then go with a Value subscription, you'll save money in the long run. But in most cases, smaller businesses will efficiently use software well into their life cycle for highest ROI.
Now Let's Talk Microsoft's COW$
I mean, let's talk about Microsoft CALs. I already knew CALs were implemented and tracked different since the Win2k days, but I just wasn't quite clear on how they worked and what really changed. Do you remember
Per Seat and Per Server licensing? Even more, do you recall Small Business Server 2000
enforced CAL? If you're coming from that era still (don't be ashamed, I know people still running Windows 98SE, no joke!), it may take a little getting used to the new methods of CAL deployment.
Now they are divided into two categories, USER CAL and DEVICE CAL, no more Server CAL, well not like the old way at least. Additionally, it is again, not enforced in Windows 20008 (even in SBS 2008). So knowing this, you must know, there is room for either abuse or error involving remaining "legit" with your Microsoft Licensing. I say error because if you purchase a certain amount of CALs and you think you are all set, the server will not tell you that you're out of CALs or perhaps using the software illegitimately, it will work just fine regardless. Heck you can have 0 CALs with 1,000 users and it still won't tell you. But if you get audited, this error may cost you, so therefore it is important you understand how Windows Server 2008 'counts CALs.'
I had studied up a bit on current CAL methods and options and came across a common description of both types:
- DEVICE CALs: recommended for networks that contain devices that are used by multiple people, for example a company that runs shifts. Say you have 75 employees and 25 computers, but you run 3 shifts, 25 employees a shift. Device CALs in this case will save you money, you simply license the 25 computers/devices than all 75 employees. Using USER CALs in this scenario would be unnecessarily expensive, having to purchase 75 CALs.
- USER CALs: recommended for networks that contain users that use multiple devices, for example roaming/mobile users and PDA/Smartphone users. Say you have again 25 computers, and 25 employees that use them. At first glance you could probably choose either option and probably be okay. But let's throw in a PDA/Smart Phone and a laptop for every user. That easily turns into 75 devices, and now it matters which CAL you choose. As before, you end up paying more for the same services by choosing the wrong CAL, thus in this scenario you'd choose USER CALs, 25 of them and they are covered on all 75 devices.
Now these are the typical scenarios often cited in books and Microsoft websites, but for people new to this method and perhaps with lingering remnants of the older method may become confused or have some questions on how to 'count CALs' that most documentation on CALs doesn't explain. I had these very questions, and as stupid as they may be to some, the 3 - 4 people I spoke with could not give me a straight answer or simply did not know. However I finally got a Microsoft representative to answer my questions regarding how they are counted. The following were the questions I wondered about, was it just me complicating the matter further? Probably, but still good to know, here is a summarized version of what the dialogue went like between Microsoft and myself:
- How are CALs counted? "What do you mean counted?"
- Let me rephrase that, are CAL licenses 'counted' by simply counting how many computers are accessing the server or by active connections? Windows 2008 does not activate CALs based on connections, but on the quantity of devices accessing the server, one per device.
- So does that mean that DEVICE CALs that are not "active" or in use can be used by a different device logically, say a remote machine? ". . .what do you mean, a CAL 'not in use'?"
- A device/computer not being used is technically not using a CAL (this is a remnant of the old way of doing it by concurrent connections), but what if the same employee that is not using that device because he is at home, but chooses to VPN, can that CAL license apply to that remote machine? "No! He would need a CAL too, all CALs are always active."
- What if I choose USER CALs, do I count the amount of user names in Active Directory, does every single user name require a USER CAL? "No! CAL Licensing is in no way tied to Active Directory. You can have 100 user accounts and only 5 USER CALs and it will still operate and you'd still be licensed, provided only 5 employees are using the network."
- So the amount of user accounts is totally unrelated? "Yes! To decide how many USER CALs you need, just count how many humans, real people are using your network. *voice face palm.*"
Seriously, this dude although he was able to provide me answers, he had a crazy tone with me. But you cannot fault me or anyone else that may have wondered the same things, because there
are software programs that
do base their licenses on Active Directory and user accounts. There
are program licenses that pool their 'device' licenses (i.e. SBS 2000) or by concurrent connections.
After getting answers to these questions, then and only then I felt more confident in the type of CALs I was going to purchase. Originally, Dell had quoted me for DEVICE CALs--which they in fact configured, I wasn't asked which type I wanted. Good thing I became better informed, because in reality, DEVICE CALs in this case would have been a poor decision for us. Where in most SMBs, DEVICE CALs may be enough, it is not so in our company. We actually have more devices than we do employees due to servers, service workstations, production workstations, manufacturing machines that run Windows, PDAs, laptops and several other networked nodes that require user access, it would have simply been foolish and expensive to go DEVICE CAL. But the even far more worse thing is, I was only being quoted for a certain amount of CALs, a number matching how many users we have, because no one asked, 'do you have more devices than users?' So while everything would have worked fine and dandy from an operational level, we would have been illegally operating on a Terms of Service level, over words and technicality. So once I realized this, I quickly informed our Dell representative and had the configuration changed. An additional thing that was changed in the CALs is that you can now purchase single CALs! No more of this having more than you need crap. If you need 47 CALs, 47 is what you get. If you need 8, 8 is what you get. That alone saved us a nice chunk of change, the price of 2 CALs to be exact. Since now we are using USER CALs, (as soon as it is implemented) we can rest assured we are legit for all mobile and remote users.
Admin Nesting Phase™
Since now I am simply awaiting the arrival of my new progeny, I have began to "nest." These past several weeks have been quite stressful, managing a network, managing users, managing myself that my server room which unfortunately is my office as well has been neglected. I need to clean! I have papers, quotes, licensing information, CDs, DVDs, retail packaging, Cokes, empty shipping boxes, cables, computer guts and all sorts of clutter laying around. I need to make way for this new server and start reorganizing stuff again and start documenting key configurations etc. I feel like a woman well into her 5th month of pregnancy frantically cleaning and wanting to keep everything in an unreasonable 'ready' condition.
Anyway, time to snip this excessively long trail of words spewing from my finger tips. I hope some of this information helps a fellow admin out there somewhere either technically or just for a laugh, "wow that dude is crazy lol. . ."
