kennysarmy Posted October 8, 2012 Posted October 8, 2012 I have a situation where our WSUS has been running fine for several years. It's running on a VM Server 2003 R2 and the WSUS store is on the servers D:\ drive. It is a 50gb drive which now has only 300MB free. The WSUS Server Cleanup Wizard has made little or no difference to the free disk space. I tried removing Server 2003 and Office 2003/2007 from the products and classifications and running the wizard again - but again no space it reclaimed. At a loss now.... What will WSUS make of a drive store that is running out of space?
SHimmer45 Posted October 8, 2012 Posted October 8, 2012 you need to manually remove the packages which you dont need, i think you can use the cleanup wizard if that doesnt work try using wsusutil.exe, i havent used it for a LONG time so would suggest reading the options for it 1st
Michael Posted October 8, 2012 Author Posted October 8, 2012 There's nothing to stop you properly uninstalling WSUS and deleting its database, then starting again. Typically (to give you an idea), setting it up using my guide and selecting 2003 Server, 2008 R2 and Office 2010 takes up approx. 15GB-20GB.
sted Posted October 8, 2012 Posted October 8, 2012 yeah wipe n reload of wsus saves a lot more space than the cleanup wizzard
kennysarmy Posted October 9, 2012 Posted October 9, 2012 My bad! This helped Clean Your WSUS Server - Spiceworks I had nt declined the superceded updates for a while...I now have reclaimed about 20 Gb
gmonks Posted October 9, 2012 Posted October 9, 2012 My bad! This helped Clean Your WSUS Server - Spiceworks I had nt declined the superceded updates for a while...I now have reclaimed about 20 Gb We had this problem at my old school, we just started again and managed to have it set up by the end of the day.
Michael Posted January 23, 2013 Author Posted January 23, 2013 How to uninstall a broken WSUS install on 2008 R2 If you're running WSUS on 2008 R2 and like me you don't bother backing up WSUS data (as it can be re-downloaded), you're then left with a broken WSUS install as the files, database and logs are missing when you have a hard disk/RAID failure. Navigate to the registry: HKLM\Software\Microsoft\Update Services\Server\Setup Change the wYukonInstalled entry from 1 to 0 Download WSUS x64 from here, do not tick any boxes and WSUS will uninstall correctly, hurray! Re-install WSUS by re-downloading it a second time (the link above) to perform a full re-install.
TForsdyke-SHS Posted January 25, 2013 Posted January 25, 2013 I am having serious problems with WSUS,I am having serious problems with WSUS, I set it up on a virtual machine running a fully updated fresh install of server 2008 R2, and followed the 2008 R2 guide by Michael on page 1, the only area in which I did not precisely follow the guide is where it says to choose full install including console, I was at no stage given that option. XP and Windows 7 clients in a test OU linked to the WSUS GPO are listed on the computers page in the WSUS console but are not receiving any updates and there status shows 0% not yet reported. This is my third attempt to setup WSUS, and each attempt has got to this same stage which I have been unable to pass. I have consulted with a technician working at another school, who has given up trying to install WSUS after experiencing the same problem. I have been unable to find any forums or guides to resolve this. Any help, hints or advice you can offer would be greatly appreciated.
ajs Posted February 17, 2013 Posted February 17, 2013 If you look at the Windowsupdate.log file on a station that isn't updating, what are the most recent date entries present?
newpersn Posted February 17, 2013 Posted February 17, 2013 May be worth checking the gpo and giving the said computer a gpupdate force. Ive had this and it was the gpo playing up. I created a new gpo with the update settings on.
TechSupp Posted January 16, 2014 Posted January 16, 2014 Having a few issues here and looking for inspiration! I have a WSUS up and running on our 2003 server, clients are all listed in it, all moved into their groups, updates downloaded and ready to install, clients just say not reported in yet! On a client tried the update, stop service, detect now etc etc but nothing. Looked at the windowsupdatelog and it says: 2014-01-16 10:19:59:167 1024 fd4 PT Initializing simple targeting cookie, clientId = 13d9ae16-d66a-4fd7-b9f7-bfc2a95adea2, target group = , DNS name = pc_250.hexthorpe.local 2014-01-16 10:19:59:167 1024 fd4 PT Server URL = http://hpserver/SimpleAuthWebService/SimpleAuth.asmx 2014-01-16 10:19:59:183 1024 fd4 PT WARNING: GetCookie failure, error = 0x8024400D, soap client error = 7, soap error code = 300, HTTP status code = 200 2014-01-16 10:19:59:183 1024 fd4 PT WARNING: SOAP Fault: 0x00012c 2014-01-16 10:19:59:183 1024 fd4 PT WARNING: faultstring:Fault occurred 2014-01-16 10:19:59:183 1024 fd4 PT WARNING: ErrorCode:ServerChanged(4) 2014-01-16 10:19:59:183 1024 fd4 PT WARNING: Message:Server rolled back since last call to GetCookie 2014-01-16 10:19:59:183 1024 fd4 PT WARNING: Method:"http://www.microsoft.com/SoftwareDistribution/Server/ClientWebService/GetCookie" 2014-01-16 10:19:59:183 1024 fd4 PT WARNING: ID:60db9986-1c22-4d34-b815-7393239cd6c6 2014-01-16 10:19:59:183 1024 fd4 PT WARNING: PTError: 0x80244015 2014-01-16 10:19:59:183 1024 fd4 PT WARNING: GetCookie_WithRecovery failed : 0x80244015 2014-01-16 10:19:59:183 1024 fd4 PT WARNING: RefreshCookie failed: 0x80244015 2014-01-16 10:19:59:183 1024 fd4 PT WARNING: RefreshPTState failed: 0x80244015 2014-01-16 10:19:59:198 1024 fd4 PT WARNING: Cached cookie has expired or new PID is available 2014-01-16 10:19:59:198 1024 fd4 PT Initializing simple targeting cookie, clientId = 13d9ae16-d66a-4fd7-b9f7-bfc2a95adea2, target group = , DNS name = pc_250.hexthorpe.local 2014-01-16 10:19:59:198 1024 fd4 PT Server URL = http://hpserver/SimpleAuthWebService/SimpleAuth.asmx 2014-01-16 10:19:59:229 1024 fd4 PT WARNING: No updates found from server; serverID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} 2014-01-16 10:19:59:261 1024 fd4 Report Uploading 2 events using cached cookie, reporting URL = http://hpserver/ReportingWebService/ReportingWebService.asmx 2014-01-16 10:19:59:261 1024 fd4 Report Reporter successfully uploaded 2 events. What am I looking at and what do I need to check? I can see its failing but from what!
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