SBS 2008 Promises More but Delivers Less

I admit that I was more than just a little apprehensive moving a client to Small Business Server 2008.  I had minimal time to play  with it and learn its finer points.  Documentation is sketchy and sometimes incorrect since there were last minute changes to the final release.  Microsoft is rapidly addressing the issue.

I was pleased to learn that server migration had been greatly improved; disappointed to learn that there is no direct migration path from server 2000 to SBS 2008.   For more specific details on my migration see How to Migrate SBS 2008 from Server 2000. 

Once in the GUI, I began familiarizing myself with all the new menus and wizards.  I give Microsoft props on more wizard driven functions, but I despise their insistence in changing names and locations of certain features.  These are the same frustrations you’ve come to know going from XP to Vista.  Specifically networking and Exchange has some new terminology, sometimes for no apparent reason to this author.

Here’s where the less comes in:  

  1. There is no client installable Outlook 2007 included in the client apps folder.  I’ve heard the MS explanation but it doesn’t change the fact that your clients will have to pay for it and most are perfectly happy with their Microsoft Office 2003 suite with the 2007 compatibility pack installed.  I give Microsoft a big thumbs down on this move. 
  2. I defy any IT savvy person not affiliated with Microsoft to defend the built in backup solution for SBS 2008.  One word:  Sucks Royally! Ok, that’s two words but one wasn’t enough to describe the disappointment.  Simply put, it’s less customizable, has less features for backing up Exchange than expected, and  compatible with fewer backup solutions (eg. tapes)  Its more proprietary as well, making it harder to hookup to any old workstation to restore data to a temporary machine.  I would love to get a reply from someone that has gotten ntbackup to work on SBS 2008.
  3. The system requirements for SBS 2008 is much higher than SBS 2003 and Server 2008 standard.  Running only on a 64 bit platform, it is a major memory hog with 4GB being the minimum.  Equate 4GB in SBS 2008 to 256MB in XP.  I am running 8GB and it seems to work well, but I’m thinking of doubling that in the future.  Couple that with the CPU and storage requirements, and you better be prepared to lay some dollars down for good hardware.  This isn’t necessarily a bad thing but it your bottom line will be higher.

Considering the above stripped out and dumbed down features, you might have noticed that the total cost of implementation is more expensive than with SBS 2003.  Factor in no Outlook licensing, the steep hardware requirements and the additional “familiarity” time, and you start scratching your head wondering if SBS 2008 is really worth the money.  I couldn’t help but wonder if Steve Balmer and Ashton Kutcher were going to bust into the server room and announce I had been punk’d.


31 thoughts on “SBS 2008 Promises More but Delivers Less

  1. Note

    Before you can configure the POP3 Connector, you must first complete the Set up your Internet address task on the Home page of the Windows SBS Console.

    You must be a network administrator to complete this procedure.
    To view or change POP3 Connector properties


    Open the Windows SBS Console.

    On the navigation bar, click Network.

    Click the Connectivity tab.

    The list view displays information about your network connections.

    In the list view, click POP3 Connector.

    In the Tasks pane, click View POP3 Connector properties. The Windows SBS POP3 Connector properties page appears.

    Click the Accounts tab. On the Accounts tab you can perform the following actions:
    * To map a new POP3 account to a mailbox on your server, click Add, and then specify the account connection information on the POP3 Mailbox Properties page.
    * To change an existing POP3 account connection, select an account in the list, click Edit, and then change the account connection information as appropriate on the POP3 Mailbox Properties page.
    * To delete an existing POP3 account connection, select an account in the list, and then click Remove.

    Click the Scheduling tab. On the Scheduling tab you can perform the following actions:
    * To retrieve POP3 messages at a specified interval, click the arrows to define the interval in hours and minutes.

    The minimum time interval that you can set for message retrieval is five minutes.
    * To retrieve POP3 messages from your Internet Service Provider (ISP) immediately, click Retrieve now.

    When you are finished adding or changing POP3 Connector properties, click OK.

  2. Thanks Susan for the correction and also the info. I couldn’t find it and googled that and came across information that it didn’t exist; so much for bad info. Apparently others did find it where expected either. More of the moving functions for no apparent reason.

  3. I’ll chime in here with my thoughts on the transition to SBS 2008. I have been a Microsoft Small Business Specialist for several years now, and have installed something like 40 SBS networks back to the SBS 2000 days. I have been extremely disappointed with SBS 2008, and have been surprised to hear so little outcry against this product to date. Here’s my current list of major ongoing problems with SBS 2008:

    1) The SBS Console crashes constantly. The crashes essentially eliminate the ability to maintain these servers. I’ve worked with Microsoft on the SBSC support boards for hours and hours, and they were never able to help me resolve the problem. I eventually found some hints in the Technet SBS 2008 Repair Guides on how to troubleshoot the constantly crashing console. I was able to identify the Security page (integrates the A/V vendor’s info into the console – a completely unnecessary and unwanted feature to begin with) as the culprit, and was able to disable the security page from loading in the console’s Safe Mode. After that, I can at least add and remove users for my customers with the console running in Safe Mode. There was finally an acknowledgement of this issue released last week on the Official SBS Blog – first reported more than 3 months ago. Unfortunately, the steps to resolve are so complex, I have not yet had time to try them on systems experiencing the problems.

    2) Two of the three SBS 2008 systems I’ve installed so far have Active Directory completely quit every 7-10 days – taking the server down for these two customers. As above, I have worked with the SBSC support boards for hours on these issues – no solution was ever found. I’ve had a “to-do” on my calendar for these two customers to log onto their systems after hours and restart the server once a week for more than two months now. Of course, hundreds of people have now reported the same problems, and Microsoft recently released a Hotfix that supposedly provides a work-around. I’m not too big on installing Hotfixes on production systems, so I’m still waiting for a permanent fix. Needless to say, Microsoft has some very angry customers over this issue.

    3) Absolutely pathetic Daily Reporting System on SBS 2008, compared to that provided with SBS 2003. First, SBS 2008 seems to be completely unable to generate and send a daily status report ON TIME! My deployed systems are set to send me a daily report by email at 6:00 am each day. That allows me to quickly review the status of the dozens of servers I support before the start of each day’s work. On average, the SBS 2008 systems manage to get the daily report generated and sent 3-5 hours later than scheduled. I’ve even tried scheduling the Report Time earlier, but that seems to have no effect. Furthermore, I fail to receive a report at all from two of the SBS 2008 systems several days a week. Again, I’ve worked with the SBSC support boards, and after hours and hours of troubleshooting, I received the statement that “this is just the way the system works”. Finally, no comment on the SBS 2008 Reporting System would be complete without referencing the incredible lack of alerting, again compared to the product it replaced. With SBS 2008, I no longer even have the option to get an alert when the server restarts! Of course, there are some reporting add-ons that have been developed by the community in response to these missing features, but I’ve not had the time or nerve to try them. I could go on, but if you’ve ever tried remotely supporting a customer running SBS 2008, you’ll understand what’s missing …

    4) The Solutions Pathway process for purchasing SBS 2008 upgrades is unacceptable. Beginning with SBS 2008, the only way to purchase a discounted upgrade for a client is to buy through Solutions Pathway. Microsoft consultants and resellers can no longer purchase upgrade SKU’s from the likes of Tech Data or Synnex. We now must set up accounts with the Solutions Pathway website and buy the product for the same price as end-users. Furthermore, at last attempt, product fulfillment takes something like 3 weeks. I don’t have room here to list all of the problems I had with purchasing from Solutions Pathway. My recommendation is to just quote your customers a full-product or OEM SKU and get on with life.

    I could also go on about the Domain Administrator being completely shut out of accessing my customer’s redirected My Documents files due to the changes in security permissions. Almost all of my clients depend on me to log on remotely and manage, move, and recover documents and settings when employees come and go. As it is now, I have to fight with UAC and forcefully give myself permission to access my client’s files for backup and transfer.

    Yes, there are many good new things about SBS 2008, but the bad is really bad.

    Andy Williams
    Professional Computing Solutions

  4. Not sure where the backup comments are coming from?

    Have there been any test runs at destroying a system and recovering again?

    Our one hiccup with the backup restore so far. And that was a BIOS getting over eager to put the USB hard disk in front of the RAID array the OS was to go on.

    From there, our experience with the built-in backup solution and recovering it to similar hardware, and soon to be tested with different hardware configurations has been excellent.

    Philip Elder
    MPECS Inc.

  5. My complaint with the backup is lack of flexibility. I appreciate the ability of it to be able to properly backup and restore a system. That should be a given by 2008 and so duly noted. The 4 biggest failures are no tape backups (for those that already have them), Being able to only tag specific folders and excluding system for specific types of backups, backup to a network drive is probably the biggest failure and not being able to take the drive to a workstation and restore individual files for emergency access.

  6. The balance between restoration abilities and securing the backup via encryption as is done in the SBS backup was a tough one for sure.

    But, I believe that the team made the right choice in tying the backup device to the server and making any other system oblivious to it. Security, especially when it comes to data exposure, trumps convenience IMNSHO.

    It also gives us the ability to provide our clients with a backup rotation service giving them ease of mind knowing they have off-site protection and for us another feature for our managed services options.

    For us, tape died the week we needed to do a full BUE based restore on an SBS server and 600GB of data via two 6 tape libraries. BUE failed us for the server recovery though we did manage to get all of the data back with the exception of a couple dozen individual files that must have rested right in the nest of bad sectors that were the beginning of the end.

    Needless to say, the person responsible for rotating the magazines went sheet white when things went sideways and we were asking for them. They had not been rotated in a long while and apparently BUE did not e-mail us as it should have to indicate that the tapes could not be overwritten due to rotation restriction timing.

    We went looking for an image based backup tied to disk and found one after that.

    Backup to network is not needed for us in the SMB market. For the cost of a SAN or whatever device, we instead set up a second server, sometimes DC, sometimes not as that introduces recovery hardship for SBS networks, that we use to live mirror the client’s data with. Now, with our clients on SA for SBS, we install the Hyper-V role and prep a cold backup setup that allows us to recover in short order.

    If the server is up, there is access to needed data pieces via the Windows Backup restore process. If the server is down, there are probably more important things to consider than a few files. Nice thing about that backup though, is if there is a hard disk or array failure, get some disks and the server is back in an hour or two depending on the volume of data and server configuration.

    I think Microsoft has done a very good job with the SBS 2008 backup setup.

    Ever bare metal recover the SBS 2003 backup?

    Philip Elder
    MPECS Inc.

  7. I am responsible for a couple of SBS2008 networks and I have to say I have had mixed results, on one domain it has caused nothing but grief with anything that could go wrong did go wrong, currently I am trying to resolve a VSS/Symantec Backup Exec issue that has been dragging on for months and is going round in a cycle, starting with rebuilding the VSS to reinstalling BUE, currently I am at the start of the cycle, time to rebuild VSS again.

    The other domain is an absolute dream, everything is ticking along as expected, all parts are working, all alerts are functioning, all I have to do with this one is remotely check in just in case, the only problem found so far is an erroneous update downloaded and pre-approved through WSUS which was swiftly rectified.

    The only difference between the two is Symantec products, on the bad domain we run Endpoint and Backup Exec which have caused nothing but headaches, I rely on Ninja, Vipre and Windows NTBackup on the good domain, both domains have Exchange 2007 but at the moment cannot backup individual mailboxes which was why BUE was chosen, I was expecting Microsoft to include Exchange friendly NTBackup options so am disappointed they didn’t.

    To summarize my personal experience with SBS2008 is fundamentally good, I would just not advise using ANY Symantec product anywhere near it until it can be soak tested in a test environment. Without them my experience is that the product is a very good step forward, I am not a major Microsoft fanboy but if their latest Windows 7 operating system is a new yardstick then I am very much looking forward to seeing what Windows MidMarket Server (MMS) looks and feels like.

  8. I’ll add another thing, or two:

    I have done three SBS 2008 setups so far. Actually I’ve done about six, because I’ve done a few dry runs on my own systems, and well as had to rebuild a system that the backup failed on. This backup failure has happened to me TWICE on two different production servers.

    And let me tell you this…once the backup in SBS 2008 breaks, IT IS PERMANENTLY BROKEN. Go ahead, flame me, tell me to provide you with details. No. I refuse to provide you with any details. I am worn out from providing details. I refuse to torture myself anymore. I just lost a client as a result of this. I lost another client a few years back to Folder Redirection “suddenly” failing out of the blue on an offsite laptop (it was “very offsite” on a remote lake in the countryside of Maine and my (ex) client was none too pleased about suddenly having no documents in his “My” Documents – I had to FedEx him a DVD – what a joke).

    But I digress. Back to SBS 2008 “Backup”: I am mentally worn out from hearing people’s different solutions. Once SBS 2008 Backup breaks, it’s broken for good. You’ll get a VSS Exchange failure with your backups and you’ll never be able to fix it. You can install all the Exchange Update Rollups you want, disable/re-enable shadow copies, install all the VSS backup service pack rollups you want, you’ll never be able to fix it. By the way, this is without Symantec products installed.

    There is serious FLAW (BUG) in the VSS implementation with Exchange 2007. This remains unacknowledged by Microsoft. In my (long) experience with Microsoft, this means that they are aware of the problem – they just have no idea how to fix it. Either that, or the fix would involve a complete rewrite of Exchange 2007 or Windows Server 2008. The best “defense” from their standpoint, is to just publicly pretend they don’t know about it.

    Have fun when this happens to you. Then you’ll have to put in another 3rd party backup solution, and that will probably break something else. But hey, give it a shot…it’s a roll of the dice anyway. Try a Symantec product if you really want to bollocks it up.

    • Just a quick response to Qmacker,

      Yes there is a fundamental bug in VSS but it is not unrepairable as I have done just that.

      In talking to several high ranking Microsoft developers one of them admitted that there is a VSS bug relating to backup that they have logged internally and they are waiting to receive more replications of it before they can get a fix out as they cannot re-create the failure in their test environments.

      Now the VSS is fixed on one production server, basically rebuilt VSS with the help of before mentioned Microsoft developers and without using a third party app, it is functioning as it should, even doing DR over a link to a network drive at another site quite happily.

      I can’t understand why Microsoft are not currently working on the fix to a problem that they do acknowledge internally just because they have not had enough people screaming at them.

  9. Peter –

    Thanks for the level-headed response to what I admit was a rant. I am entirely fed up with this nonsense though.

    How did you go about fixing the Exchange VSS issue? I’ve tried disabling/re-enabling shadow copies to no avail. the Shadow Copies run at the given intervals okay, but when the VSS writer goes to backup Exchange it bombs out with:

    “Exchange VSS Writer (instance f5b8a4c1-5cfa-4958-8ebf-d09f7c1ada83:2) has unsuccessfully completed the backup of storage group ‘First Storage Group’. No log files have been truncated for this storage group.”


    “Exchange VSS Writer (instance f5b8a4c1-5cfa-4958-8ebf-d09f7c1ada83:2) has unsuccessfully completed the backup of storage group ‘Second Storage Group’. No log files have been truncated for this storage group.”


    “Information Store (1384) Shadow copy instance 2 aborted.

    For more information, click” <– I LOVE THAT ONE!


    “The description for Event ID 517 from source Microsoft-Windows-Backup cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

    If the event originated on another computer, the display information had to be saved with the event.

    The following information was included with the event:


    The resource loader failed to find MUI file”

  10. Qmacker,

    I can fully understand the rant having experienced it myself, the way my problem was fixed is basically getting a Microsoft developer on the phone, letting him remote in and rebuilt VSS with him.

    Unfortunately just stopping and restarting/disabling and re-enabling VSS is not enough it needs to be rebuilt from the ground up which involves a fair amount of relying on said Microsoft developer to play ball and not follow the play book they all have.

    I did have a few sessions before the slip about the bug but as soon as it was admitted, we started to rebuild VSS and since then, touch wood, it has been functioning perfectly, admittedly still not exchange aware as cannot use third party app, and flat file backing up everything including exchange 2007 to a local USB as well as remote network drive.

    I wish I could be more help but the rebuilding process took several hours and admittedly there were some moments I just left him to it so don’t have the complete picture.

    The good news is it can be done, you just have to persist and insist they do it first rather than follow the script as some of the steps they were suggesting are ridiculous and cost downtime on a production server.

    Good luck Qmacker

    • Sorry quick addendum…

      save yourself some time by running the

      vssadmin list writers -and- vssadmin list providers -to prove that VSS is not working.

      Looking at your errors Qmacker, my assumption is that the list writers command will hang and list providers will work which means that the VSS is completely broken and the bug has struck again.

  11. You’re going to think I’m making this up, but…

    The Exchange VSS writer just failed on ANOTHER new server of mine. This time it’s my own server. I have it running inside a VM on ESXi. It has had no other problems up until now. This is really not cool. Guess I’d better call MS Support. I’ll probably have to suffer the indignity of paying for support as well, seeing as I’m still in the “trial” period (which I’ve extended one). I haven’t actually committed to paying for it, because I don’t trust it – because of this issue!

    • Qmacker,

      Your posts really punctuate the whole point of my “SBS 2008 Promises More but Delivers Less” article. By design, there are many things that should make SBS 2008 a great system. However, issues like this are simply not tolerable in today’s business critical computer environment.

      This smacks of the executive decision to force Vista on the market knowing full well it wasn’t ready. The Microsoft credo seems to be “Ship now, patch later”.

  12. Hi,

    After three weeks of successful backups, the VSS has crashed again…….

    The only option I have is to rebuild VSS as is a production server and the only one the client has, getting a bit fed up now going round in circles, am going to call Microsoft Developer contact and grill him a bit more.

    Will post any news.

    • Hi Peter,

      Any news on the last VSS rebuild? This worries me greatly and makes me want to continue selling server 2003 through open license. Have any patches come down the pipe since you reported to fix this problem.

      For the amount of labor involved, seems like selling the customer a copy of Acronis for $600 might be cheaper and more stable and flexible.

      • Hi Mitchell,

        Well the last rebuild went ok, two reboots on a production server which serves two sites and 300 clients aside, so far it is behaving as it should but it has not been that long yet.

        Still no joy on the hotfix/patch yet, the MS developer basically said they are still waiting for more people to report this problem as they are having difficulty replicating in house so a timeline is anybody’s guess unless lots of people start installing 2008 along with any third party backup it seems!

        We have a number of servers in the configuration stage at the moment for a number of new clients, all I can say is we are sticking to 2003 for the foreseeable future which is a shame really as I do like the potential of 2008 but cannot afford the man hours or support which we can’t really charge for.

  13. After months of review and using this OS, I completely stand by the premise of my original post “SBS 2008 Promises More but Delivers Less”.

    All of the new features are completely trumped by the fact that this OS breaks. Backup breaks, Exchange breaks, Automatic updates break it. Installing Exchange 2007 SP2 fixes things once you Google how to trick the OS into accepting it…and, why do we have to trick the OS into accepting this update?!

    Sorry MS, but true to its appearance and behavior, SBS 2008 is the Vista of Server OS’s. Its buggy and it sucks. I NEVER had any of the problems with 2003 that I have with 2008, period.

    I say, put people on a shared Google calendar, scrap exchange altogether and never use SBS again. I will definitely recommend this strategy to ALL my clients.

    • Mitchell,

      I am going to flat out disagree with you here.

      Click on the link back to our MPECS blog and you will get about 3 years worth of posts on SBS 2003 and recently SBS 2008.

      There have been no end of issues and hiccups in _both_ OSs. It is the nature of the beast that having so many components play together nicely in the same sandbox can lead to a few fits and struggles. That’s a given.

      But, to date, we have always had ways to deal with those little things on SBS going way back.

      An update that hiccupped on SBS 2003 that quickly come to mind:
      + Windows Server 2003 Service Pack 2. TCP offload changes and more.

      Philip Elder

      • I can appreciate your experience with bugs in both servers, but I have never experienced the types of issues with 2003 or 2000 for that matter as I have with 2008. When there are problems, 2003 seems much easier to fix as 2008, much like vista, acts like it’s never supposed to break therefore it’s harder to fix.

        I will say this, I never had exchange break in SBS 2003. Worst problem I ever had was a partition running out of space due to too many log files getting thrown out by Exchange.

        Between Backup and exchange breaking, I’m certainly not impressed. After all, these are probably to two most important components of SBS.

  14. I agree with Mitchell. SBS 2008 is great – when it works – but I never feel truly comfortable with it. It’s a crap shoot as to whether or not it will remain stable. In order for that to happen (and it’s still a roll of the dice)…

    1) Forget about “upgrading” an old SBS 2003 domain…you’d better do a clean install and wipe all your old workstations to a “new” domain.”

    2) Allow 100GB for your C: partition, and immediately after install, move EVERYTHING off it using the Folder Migration Tool thingy.

    3) Don’t install Forefront and OneCare. Use something else, post install.

    4) Make sure you flush out this folder:


    …on a regular basis. Otherwise, your C: drive will fill up, and the server will STOP sending and receiving mail.

    5) I’m on vacation right now, and I just had to remotely perform Step 4 (above).

    6) As I’m on vacation, I couldn’t be arsed to write more (I will another time), but wanted to led Mitchell some moral support.

    SBS 2008 is “there” in some ways, but in other ways, it is unfortunately the “Vista” of server OSs. If you know the “tricks” (which are not documented by Microsoft), then you can get it to work OK.

  15. Sorry, that last post up there on December 22nd, should have saif “qmacker” for the name. I inadvertently put in “Mitchell.” Sorry Mitchell!

  16. The reason I’m back here again, is to report….

    Last night, with great trepidation, in installed a few Windows Updates on a client’s SBS 2008 box. Every time I do, I hold my breath. This SBS 2008 install had given me no problems, until now…

    I installed the updates. I held off on doing the update, “Microsoft SQL Server 2005 Express Edition with Advanced Services Service Pack 3 (KB955706),” because it was very big, and any SQL updates always freak me out (because they often don’t work).

    AAnyway, the updates broke TS Gateway. Now i have an angry client, and angry remote users. And unfortunately for me – an emergency at a different clients. So this has ruined my day, and perhaps my weekend. 😦

    Thanks Microsoft! Well done SBS Team!

  17. The failed backup VSS issue has raised its ugly head again at one of my clients. This means the ENTIRE BACKUP bombs out and fails:

    Log Name: Application
    Source: MSExchangeIS
    Date: 4/8/2010 11:46:36 PM
    Event ID: 9782
    Task Category: Exchange VSS Writer
    Level: Error
    Keywords: Classic
    User: N/A
    Exchange VSS Writer (instance fce58730-de7d-4a9c-9072-95fc9c50af10:17) has unsuccessfully completed the backup of storage group ‘First Storage Group’. No log files have been truncated for this storage group.
    Event Xml:



    First Storage Group

  18. I just had to post this “fix” from Microsoft as well:

    My favorite par…(NOTE 2ND STEP)…BEGIN QUOTE:

    To resolve the error, follow these steps:

    * Inspect the Application log on the server that reported this event for Warning or Error events associated with the Microsoft Exchange Information Store (MSExchangeIS). The event description will indicate that the Exchange VSS Writer encountered a problem performing a specific task. Examine these events to determine the extent of the problem.

    * Contact your backup application vendor if you need help.

  19. Hi Qmacker,

    Thanks for continuing to post here. I love (actually hate) the MS fix and description you provided. Microsoft continues to treat both SBS 2008 and Vista the same way – to basically turn a blind eye and expect us to just deal with it until they offer a better solution.

    That is what Windows 7 was for vista and hopefully their will be something like that for SBS2008. Problem is my customers don’t upgrade server OS, they add or replace servers with whatever the current OS is when the time comes. The typical life of one of my customer’s servers is 8 years and I still have a few on SBS2000 that work just fine for what they are doing.

    To all those who take issue with “promises more but delivers less”, Qmacker’s posts illustrate my point perfectly. These kinds of issues are a cardinal sin in server systems. You simply CANNOT have them and they trump ALL of the nice new features that may be available in SBS2008.

    With cloud computing, especially shifts in the way email is treated, Microsoft will be vulnerable at the first good alternative that comes along.

  20. Just had to change the default e-mail send/receive sizes on an SBS2008 system. Straight after that ordeal I was having a Google around to find various opinions of whether 2008 is ‘better’ than 2003. My feeling is that it isn’t really a step forward… I’m both glad and sad to see that it’s not just me.

  21. Hi,

    There IS actually a fix for the failed Exchange consistency check / Exchange will not be availble for recovery when trying to make an online backup of exchange using SBS backup / wbadmin. Basically it it looking to the wrong shadow when running the check due to an old / corrupt extra GUID in the registry. After 8 hours with MS yesterday they now consider to have a known fix which should be made available through their KB / Online / SBS Blog within a few days.

    I hope this helps a few of you out… I has certainly solved a niggly issue we had seen for a few months!

    (It may be from a time of when the “disable backups” on SBS has been used and then set back up – leaving the old GUID in place.)

  22. James…

    You are the first persdon I have read to know of a fix for this issue. Could you possibly post the URL or describe the fix.

    I’m going krazy with this problem.

    Many thanks

  23. All the problems that I continue to see with SBS 2008 draws me back here to complain. Hotfix support sucks and you usually have to jump through some kind of registry hack to get many of them to install. it’s not quite server 2008 and it’s not quite vista, so the recommended updates, or updates you know will fix the problem often tell you that the fix is not recommended for you OS.

    The real complaint is that we are still having to perform hot fixes since a really good service pack that actually fixes things still have not happened. It’s obvious to me that Microsoft is going to pretend that nothing is wrong with SBS2008 (or 2008 in general), just like they did with Vista.

    Never mind that the same hardware on a new OS runs faster, more stable and with less bugs. Of course, after spending good money on an OS and then spending hundreds of dollars on making things work, many end users are reluctant to jump into another nightmare. And I can’t say I blame them.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s