sizing C: drive for Windows Server 2008 future winsxs growth

Posted on 2009-02-20
Last Modified: 2012-08-13
I am setting up a Windows Server 2008 x64 server. I am concerned about future growth of the Windows SxS directory (%System Root%\winsxs), which will permanently store all updates that are ever applied to the server. For example see

Nowhere can I find a rule of thumb for sizing a C: drive on a WS2008 server, so that we can survive for up to 5 years of updates without running out of space. What would you recommend? This particular server will be used to run SCCM 2007 and SQL Server 2008, but we have a lot more servers coming that will be running a variety of stuff.
Question by:DscpTech
    LVL 8

    Accepted Solution

    i would think if you set aside 2.5X installed operating system size for that purpose it would be sufficient.

    LVL 58

    Assisted Solution


    Personally, all my Server 2008 systems are configured with very little space on any of their hard disk volumes. This is because you then keep the majority of the free space available for allocation at a moment's notice later on. Any volume bar the C: drive can be Extended while Windows is running, and it's only a case of using GParted to allocate additional space to the C: drive where necessary.

    I would recommend against allocating all your hard disk space when you initially install the server. Changing requirements may mean that what is suitable today is not suitable in 6 months time.

    LVL 58

    Expert Comment

    That said, you should aim to put at least 40GB of space minimum on the C: drive from the outset, then add more as and when required.


    Author Comment

    I'd rather not expand as required. Our standard practice is to allocate at the beginning of the server's life. Also we don't want to have to come back later to add more drives, there might not be physical space for them. We're also considering upgrading some Windows Server 2003 boxes that only have 80GB or even 40GB drive C's and are not real confident that they will survive winsxs growth.

    Write Comment

    Please enter a first name

    Please enter a last name

    We will never share this with anyone.

    Featured Post

    Threat Intelligence Starter Resources

    Integrating threat intelligence can be challenging, and not all companies are ready. These resources can help you build awareness and prepare for defense.

    We recently had an issue where out of nowhere, end users started indicating that their logins to our terminal server were just showing a "blank screen." After checking the usual suspects -- profiles, shell=explorer.exe in the registry, userinit.exe,…
    If you migrate a Terminal Server licenses server inside the 2008 server family, you can takte advantage of the build-in migration tool. If you like to migrate an older 2003 Server (and the installed client CALs) to a 2008 R2 server for example, you …
    This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles to another domain controller. Log onto the new domain controller with a user account t…
    This tutorial will walk an individual through setting the global and backup job media overwrite and protection periods in Backup Exec 2012. Log onto the Backup Exec Central Administration Server. Examine the services. If all or most of them are stop…

    759 members asked questions and received personalized solutions in the past 7 days.

    Join the community of 500,000 technology professionals and ask your questions.

    Join & Ask a Question

    Need Help in Real-Time?

    Connect with top rated Experts

    12 Experts available now in Live!

    Get 1:1 Help Now