Slashdot Log In
Microsoft Recalls Small Business Server
Posted by
ScuttleMonkey
on Mon Aug 21, 2006 07:23 AM
from the another-day-another-delay dept.
from the another-day-another-delay dept.
dasButcher writes to tell us VarBusiness is reporting that hot on the heels of many other delays, Microsoft has recalled their Small Business Server 2003 R2. The operating system started shipping to OEMs, distributors, and systems builders in July but was immediately recalled after a recent audit.
This discussion has been archived.
No new comments can be posted.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
Full
Abbreviated
Hidden
Loading... please wait.
Huh - did it explode in a fireball? (Score:5, Funny)
Therac 25 (Score:5, Informative)
Parent
Sinclair ZX81 ads of the 1980s (Score:4, Funny)
Parent
Re:Sinclair ZX81 ads of the 1980s (Score:4, Informative)
a PLC tends to have memory in the 1 - 4k range and racks full of IO cards. If I remember correctly the z80 cpu could address 64k of address's as I/O or memory.
1 bit is all it takes to operate a valve or a motor or read a sensor.
8-16 bits for an analog input or output.
while the ad's seem far fetched in reality the PLC's actually being used will not be that far removed from a ZX81.
for further reading try googling for words like wonderware allen bradley omron SCADA.
simple PLC's run most of the worlds automated processes.
Parent
Re:Huh - did it explode in a fireball? (Score:5, Funny)
Parent
At least they caught it (Score:4, Informative)
Re:where did you read that? (Score:5, Informative)
Parent
Re:where did you read that? (Score:5, Insightful)
No it doesn't actually say *no* end users it says *most* and most does not equate to all. You should realize that most PR statements don't actually mean what the words mean.
"it basically said that in the part you left out:" - kjart
"None went to end users" - dreamchaser
The actual words are:
"Most of Microsoft's voluminous partner base did not have copies of SBS 2003 R2 in hand yet"
In other words some of Microsoft's voluminous partner base did have it. And seeing its a PR statement out of Redmond we can assume the reality is a lot more than a few got copies got out.
This fella seems to think he bought a new server that has the R2 edition on it.
http://snipurl.com/v9i1 [snipurl.com]
http://groups.google.com/group/microsoft.public.w
No one has still replied to my request for an explanation of what non-final core components mean. Is this the same as bugs?
Parent
Re: (Score:3, Informative)
Yeah, as he already said, it basically said that in the part you left out:
Re:At least they caught it (Score:4, Insightful)
Parent
Re:At least they caught it (Score:4, Insightful)
Parent
Re:At least they caught it (Score:5, Funny)
Yeah, monopolies are pretty cozy. Those Exxon/BP/Shell/Total guys have not released a new product in 50 years but still haul in record profits.
Parent
Why was it recalled? (Score:4, Informative)
"This routine check of the initial software on the manufacturing line found that it contained portions of code deemed "non-final," according to Microsoft... Microsoft plans to swap in the 'final' code, then reissue Small Business Server 2003 R2 to its manufacturing partners,"
Non-final? (Score:4, Funny)
New patent application in the works? (Score:5, Funny)
1. Ship your non-ready product on the stipulated date.
2. Tell your customers your product has not met your enormously high quality standards *giggles violently*.
3. Use the time gained to make the product ready for shipping.
4. If its not ready in time see # 1.
Re:New patent application in the works? (Score:4, Insightful)
5. Profit!
Parent
SBS made me quit my job... (Score:5, Interesting)
I feel your pain (Score:5, Insightful)
Parent
Re:SBS made me quit my job... (Score:4, Insightful)
It's too expensive to buy multiple boxes and too complicated (for these places where the controller/accountant does double-duty as IT guy). Don't even get me started on Linux. I'm sure it's great if you happen to have an open source guru around, but it's just not a viable option for setting up a back-end where no one has any serious tech experience. Then of course they could always just be a Mac shop - if they want to double or triple their IT infrastructure costs (ha!). Not to mention the prevalence of MS Access in small business areas.
I think you've got to hand it to MS. For about $400 you get all the software you need to run your business server, and it pretty much works out of the box. It's a whole lot better than not having anything, and as companies grow they will eventually build out the infrastructure and implement more redundancy. The "all eggs in one basket" isn't unique to just Windows SBS - it pretty much characterizes how small business works.
-stormin
Parent
Re:SBS made me quit my job... (Score:5, Interesting)
You would have to streamline everything a lot though:
- The customer isn't expected to do anything with the server. That's the support companies job (this isn't a million miles away from how a lot of these places work anyhow, so that's not a big deal).
- Installation is nailed down to "insert CD, turn system on". All the configuration is pre-done by the support company, and every customer gets the same configuration. The customer doesn't do the install anyhow, the company sends someone to site if necessary, but the fact that everything is already nailed down means that you could get away with shaving a chimpanzee, putting them in a shirt and tie and sending them out to site.
- Server hardware is specified (and usually supplied by) the support company.
- Desktops aren't heavily locked down, but are locked down enough to minimise the likelihood of someone completely hosing their system. Combine that with Ghost, and running as much as possible from the server, and the desktop support overhead almost evaporates.
You could easily charge £a few thousand per company per annum doing this - for the customer, it's a lot cheaper than paying a fulltime IT person when they probably only need a couple of man days a month, and gives them peace of mind.
Parent
Re:SBS made me quit my job... (Score:5, Insightful)
No it doesn't. For a lot of uses, it just needs to be easy enough, and customisable enough that a company with the right expertise can seriously consider offering services based on it.
Parent
Re:SBS made me quit my job... (Score:4, Informative)
The eggs-in-one-basket thing is inevitable in small business. As has been said before, many small businesses do not have the budget to support multiple boxes and IT/support staff. The wizards in SBS2003 make administration nearly a snap, and the rest of the process can be handled with clever automation. SBS can be the foundation of a multi-server environment -- at one site we have three, the SBS server, a TS server, and a WebServer for
First off, DO NOT RUN A SERVER ON A SINGLE HARD DRIVE. Read that again several times, repeat it, write it on a chalk board a hundred times, spell it out in your Alphabits. Even RAID1 is better than nothing.
Secondly, have a good and reliable backup solution. Tapes are great, and there are several well-priced alternatives which can provide reliability and durability. I prefer tapes, and for large installations an AIT or DLT-V4 drive is great, while smaller installations can handle DAT72.
Secondly-and-a-half, keep an up-to-date ASR tape and floppy on hand! I keep one of these for each customer locked in a fire-resistant and water-resistant media vault.
Thirdly, TEST your backup solution. Build another box, do an install and restore the backup. Make sure your plan works, lest you be caught with your pants down when it counts. VirtualPC, VMWare, etc. are great for this if you do not have extra hardware lying around. You *do* have the Action Pack, right??
Fourthly, have an action plan in place in case one of your clients (or your own site) suffers a catastrophic failure. Be ready to order new equipment, test and restore backups, and spend a day or more on-site getting things back up and running. Fire, frost, or frippery can and do happen.
Fifthly, have recovery software available. I purchased RTools a while back, with FAT, NTFS, and RAID recovery tools. Some people prefer OnTrack or some other tools. I have had great results with RTools. While not the Alpha-Omega of site recovery, such software can prove invaluable in the process. But it early, learn how to use it, and be prepared.
BTW: In reference to the issue of new hardware, REMEMBER MS LICENSING. If you build systems, STAY AWAY FROM OEM SOFTWARE. But it is cheaper, right? Yeah, until your motherboard dies and, technically, so does your OEM licensing. Buying canned systems is not so much of a problem since you can (generally) rely upon the OEM to provide an exact replacement. But if you build your own or order a custom system, things change VERY rapidly, and your favorite Socket AM motherboard may not be available for long after AM2 comes out. (Ran into this problem with a PIV 1.7 rig with the original socket. UGH!)
Attend your local InfraGard general meetings, consider becoming a member. These meetings are often very interesting, especially when they cover topics such as this. You will have a chance to learn from the processes and mistakes of your brethren in the industry. I like to hear tales of state agencies who learned lessons the hard way
In essense, you have to be a tech Boy Scout and always be prepared. I always kinda liked the term "Technology Samurai." I cannot say that I am ready for every possible disaster, but I like to think that at this point I have a good start.
Parent
Re:SBS made me quit my job... (Score:4, Interesting)
- SMTP
- POP
- DNS
- Apache (hosting mediawiki, mantis, dotproject, phpMyAdmin)
- MySQL (for the mentioned web apps)
- A SAMBA fileserver
- DHCP
The only thing that's not in that server is the firewall... which I kept in a different machine with no services running whatsoever, except those that handle our aDSL connection (pppoe, and sshd to connect from inside the LAN).
Our setup is not great on redundancy... but we can afford a couple of days of downtime (we had to, once or twice over the years) more than we can afford doubling our setup. Our services are used by a small number of employees (six, actually) and none are critical.
If Microsoft wants to pull us away from Linux they'd have to offer a Windows Server with all they usual servers (like those you mentioned), even if they're somewhat limited to prevent being used in a large corporation (max database size, max number of clients, etc.), priced appropiately for the use we'd give it. This product sounds like what we'd need... despite some companies misusing it for some reason.
Parent
Re:SBS made me quit my job... (Score:4, Insightful)
How do you define a small business ?
I think you can consider a business with only one person a small business, but where do you draw the line ? 5 people ? 10 people ? 20 people ?
I ask, because I worked for a business of twenty people as the full-time IT staff, from 1997 to 1998.
We had a WANG VS system, running our own custom software, based upon the PACE RDBMS.
The support costs every year where about 25000EUR/year I think, but this computer system never failed.
Peripherals, like line printers and terminals needed some replacements and service every year, but that was included in the support costs.
The database consisted of about 350 tables for the operational work, 180 tables for financial reporting, and in addition to that the bookkeeping software.
I could spend about 95% of my time programming and enhancing the system.
Why do I tell all this ?
Because I think that a system like SBS, with all its different features, cannot be optimally used by a company which does not have a good IT staff.
What I mean is that from a certain size you should be able to also hire a good programmer, which is able to service the SBS and start making use of features of SBS specifically tailored to the business.
If you cannot afford such a person, then SBS is no use to a business (except maybe in a bragging 'me too' way), because only the easiest and simplest features will be used.
Parent
Another recall or /. just slow? (Score:4, Informative)
http://news.softpedia.com/news/Microsoft-Recalls-