Want to win a PS4? Go Premium and enter to win our High-Tech Treats giveaway. Enter to Win

x
?
Solved

Increasing WinSXS folder size on SBS 2008 causing problems

Posted on 2009-07-01
6
Medium Priority
?
6,804 Views
Last Modified: 2012-06-27
A few months back we supplied a SBS 2008 machine with a 60Gb C: partition which at the time we thought was too much. Now we are getting continuous problems with the partition running low on space and stopping Exchange from receiving emails. The server keeps throwing the well-known "The Microsoft Exchange Transport service is rejecting message submissions because the available disk space has dropped below the configured threshold" and if we restart the server it fixes it for a couple of hours.

WSUS downloaded content, users shared data and all company data is all on D:, as is most of the pagefile, yet C: still only has 2Gb free space.

I've used SpaceMonger to show me the biggest folders on the disk. The WinSXS folder is 8Gb in size and the remainder of the windows folder is 6Gb - C:\windows\assembly is 2gb and SysWOW64 is 1.4Gb approx.

 I've done a lot of reading and there is one source that has shown me how to move winsxs but it is very fiddly and has too many steps that could possibly go wrong, especially on a server.

The only other large file is SUSDB.mdf at 2.5Gb but I'm not able to log into the SQL instance containing this database to be able to move it.

Any suggestions - shrinking winsxs, moving susdb.mdf, anything would be appreciated. I'm not overly keen on re-partitioning a server in case it goes wrong half-way through.
0
Comment
Question by:smickell
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
  • 3
6 Comments
 
LVL 27

Expert Comment

by:shauncroucher
ID: 24753242
I wouldn't look to do anything for the Winsxs folder. It is a particularly important system folder that will hold versioning for many updated components. Its not a good one to fiddle with.

So of 60GB partition you have accounted for 19.9 in your post

Perhaps moving the pagefile to a non-system partition may give you some more room. It seems like a pretty big system partition to me.

Shaun
0
 

Author Comment

by:smickell
ID: 24753408
Only 1Gb of the pagefile exists on C:
Trend Micro server component takes up 2Gb. In hindsight this should have been installed to d:\program files. But again at the time we didn't think space was ever going to be an issue.
I've found a 750Mb folder full of logiles in c:inetpub\logs\logfiles\W3SVC1372222313 which I've moved off.
Most of the remaining folders are 1Gb approx but all essential un-movable folders like exchange\bin or update services\selfupdate.
Just been fiddling around as I've wrote this and now brought the free space up to 4.4Gb.

Moving SUSDB.mdf would be ideal now. When I open SQL management studio and browse for instances, it doesn't show up, I've tried logging onto servername\wsus and still nothing. Should I just uninstall WSUS and lock the 10 client machines to download updates from the web instead?
0
 
LVL 27

Accepted Solution

by:
shauncroucher earned 1200 total points
ID: 24753491
That is an option. I tend not to use WSUS for small sites unless they have specific needs to manage the application of certain updates / stop certain updates from being applied.

With larger sites it makes sense to use WSUS as there are obvious benefits with manageability, control and conserving bandwidth.

If the 10 PC's can be set to download all updates direct from Microsoft, then you can remove the WSUS and you may then find that space is freed. I believe there is a WSUSContent directory where the updates for WSUS are installed, is this on C: ?

Shaun
0
Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

 

Author Comment

by:smickell
ID: 24755439
No the wsuscontent was set to d: from the outset (as was everything else where the option was available), it is just the SQL .mdf file.
Would still like to figure out the SUSDB.mdf move, even if just for future reference.
0
 
LVL 27

Expert Comment

by:shauncroucher
ID: 24755483
0
 

Author Closing Comment

by:smickell
ID: 31598725
Thanks for the quick replies.
0

Featured Post

What is SQL Server and how does it work?

The purpose of this paper is to provide you background on SQL Server. It’s your self-study guide for learning fundamentals. It includes both the history of SQL and its technical basics. Concepts and definitions will form the solid foundation of your future DBA expertise.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Know the reasons and solutions to move/import EDB to New Exchange Server. Also, find out how to recover an Exchange .edb file and to restore the file back.
With so many activities to perform, Exchange administrators are always busy in organizations. If everything, including Exchange Servers, Outlook clients, and Office 365 accounts work without any issues, they can sit and relax. But unfortunately, it…
In this video we show how to create an Accepted Domain in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Mail Flow >> Ac…
Exchange organizations may use the Journaling Agent of the Transport Service to archive messages going through Exchange. However, if the Transport Service is integrated with some email content management application (such as an antispam), the admini…

609 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