talksr Posted June 17, 2021 Posted June 17, 2021 Hi there, We have a second DC server which runs: WSUS Paxton PaperCut Backup Exec WDS WSUS is constantly running the server out of space. Today, as an example, I am unable to image any computers as I need to add the NIC driver to Deployment Workbench, but I can't as there is 3mb spare on the server hard disk. I am thinking about removing WSUS from the server, installing Windows Server 2016/19 onto a new desktop computer with a big 6tb drive and making this desktop the new WSUS server. Does this sound like a good idea? Most of the other roles on the current second server would be a pain to move where as WSUS will just be a case of installing on a desktop and updating my WSUS GPO with a new server location. Would be grateful of any suggestions. Was thinking of going for an HP ProDesk 400 G7 Microtower with i5 or if not available, i7 P.S. I have already gone through WSUS and deselected options we don't need. I also run the cleanup wizard every week and it is not helping. It is using just under 1tb. The server is too old to upgrade or add any additional storage to. All bays are full and already raided.
3s-gtech Posted June 17, 2021 Posted June 17, 2021 The roles do want separating - WSUS is a space monster if unchecked. It'll run on a desktop - it's not exactly a service that needs massive redundancy or reliability. I would personally still use multiple disks - if not in RAID, then with OS and data separation (OS on SSD) as it'll be faster and wear less. WSUS is borderline unusable without https://www.ajtek.ca/cart/ - though I think this has been rather cynically commercialised now. 1
talksr Posted June 17, 2021 Author Posted June 17, 2021 The roles do want separating - WSUS is a space monster if unchecked. It'll run on a desktop - it's not exactly a service that needs massive redundancy or reliability. I would personally still use multiple disks - if not in RAID, then with OS and data separation (OS on SSD) as it'll be faster and wear less. WSUS is borderline unusable without https://www.ajtek.ca/cart/ - though I think this has been rather cynically commercialised now. Thanks, yes this is exactly my plan. OS on SSD and WSUS files on a 6tb secondary drive.
jthompson Posted June 17, 2021 Posted June 17, 2021 +1 for the suggestion to store WSUS data on a separate drive to the OS. 1
mavhc Posted June 17, 2021 Posted June 17, 2021 Work towards getting rid of WSUS, Microsoft don't care about it. Enable P2P sharing, setup Update Compliance for free 2
DGardiner Posted June 17, 2021 Posted June 17, 2021 Work towards getting rid of WSUS, Microsoft don't care about it. Enable P2P sharing, setup Update Compliance for free just did the same, Binned WSUS enabled WUFB with a 7 day install deadline. Id rather fix the odd computer that goes tits up than deal with wsus these days 1
mavhc Posted June 17, 2021 Posted June 17, 2021 I wrote about it here http://www.edugeek.net/forums/windows-10/207846-update-compliance.html 1
MatthewL Posted June 18, 2021 Posted June 18, 2021 Hi there, We have a second DC server which runs: WSUS Paxton PaperCut Backup Exec WDS WSUS is constantly running the server out of space. Today, as an example, I am unable to image any computers as I need to add the NIC driver to Deployment Workbench, but I can't as there is 3mb spare on the server hard disk. Each of the above want their own server really, also if any issues then it only affects said server and you do not take down multiple things for 1 issue.
Oaktech Posted June 18, 2021 Posted June 18, 2021 Bin WSUS as mentioned above, or get a cheap a*s microserver with a tiny SSD for the OS and big a*s spinner for the Space Monster. I have a 'utility server' which hosts VA, WSUS, WDS/MDT and a file share with device drivers on it. Something I can drop and nobody will notice.
fredesq Posted June 18, 2021 Posted June 18, 2021 Been trialling P2P win10 updates here, far more efficient and absolutely no issues. Definately not going back!
slugshead Posted June 20, 2021 Posted June 20, 2021 Three servers 1, WSUS 2, SCCM (recently deployed 2103 and I'm super happy with it) 3, SQL (Important not to use WID for WSUS when using in conjunction with SCCM). WSUS and SCCM Need plenty of space but will give you the control you need, auto updates from wsus still work then with SCCM the ability to "push" updates with deadlines etc...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now