• Visitors can check out the Forum FAQ by clicking this link. You have to register before you can post: click the REGISTER link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. View our Forum Privacy Policy.
  • Want to receive the latest contracting news and advice straight to your inbox? Sign up to the ContractorUK newsletter here. Every sign up will also be entered into a draw to WIN £100 Amazon vouchers!
Collapse

You are not logged in or you do not have permission to access this page. This could be due to one of several reasons:

  • You are not logged in. If you are already registered, fill in the form below to log in, or follow the "Sign Up" link to register a new account.
  • You may not have sufficient privileges to access this page. Are you trying to edit someone else's post, access administrative features or some other privileged system?
  • If you are trying to post, the administrator may have disabled your account, or it may be awaiting activation.

Previously on "Windows Server 2003 versus 2008"

Collapse

  • DimPrawn
    replied
    Most corporations have a "if it ain't broke, don't fix it" approach to servers.

    If it's running fine on Win 2003, and it's still a supported OS (which it is), why "upgrade" to 2008?

    So unless there's a new killer feature in 2008 that's going to make the pain of transition worthwhile, no one in their right mind is going to move over.

    Moving server OS is a pain and high risk.

    Leave a comment:


  • Clippy
    replied
    It is all the arguments you have listed magnified several fold due to the recession.

    Once the economy picks up and/or MS 'forces' corporations to move to a newer product by phasing out support of the older one then you will see and increased move away from Server 2003.

    My guess would be once SP1 of Server 2012 is released - sometime in 2013 perhaps?

    Leave a comment:


  • eek
    replied
    Originally posted by Sysman View Post
    I picked up a comment a few months ago that many large companies are still running Windows Server 2003 rather than 2008.

    Having worked in large corporations I know that things move at a glacial speed, so it wouldn't surprise me, but I am interested in knowing what the uptake of 2008 is.
    • Is this true?
    • What are the main obstacles to upgrading?
      • Cost of licences?
      • Price of migration?
      • Compatibility?
        (corporate inertia is assumed)
    • In what timescale is it likely to change?
    • Is there a corresponding lag in the upgrade from Windows 2008 Server to the R2 version?


    I've also read that there is less than the expected take-up of the Server Core versions of Server 2008. Knowing what a pig the Windows command line environment is, I can sympathise but my real question here is "Is the Core stuff worth learning?" (obviously not if nobody actually uses it).
    My guess is the need to rewrite code to work on 2008. I know of 8 internal applications at the current client that need a virtually total rewrite to work on 2008 and that is before they look at sharepoint customizations.

    Leave a comment:


  • Sysman
    started a topic Windows Server 2003 versus 2008

    Windows Server 2003 versus 2008

    I picked up a comment a few months ago that many large companies are still running Windows Server 2003 rather than 2008.

    Having worked in large corporations I know that things move at a glacial speed, so it wouldn't surprise me, but I am interested in knowing what the uptake of 2008 is.
    • Is this true?
    • What are the main obstacles to upgrading?
      • Cost of licences?
      • Price of migration?
      • Compatibility?
        (corporate inertia is assumed)
    • In what timescale is it likely to change?
    • Is there a corresponding lag in the upgrade from Windows 2008 Server to the R2 version?


    I've also read that there is less than the expected take-up of the Server Core versions of Server 2008. Knowing what a pig the Windows command line environment is, I can sympathise but my real question here is "Is the Core stuff worth learning?" (obviously not if nobody actually uses it).
Working...
X