So you don't have to reinvent the wheel.
The last few months, I've noticed brand new clean Windows 7 installs have a hard time updating for the first time. Doesn't matter if they are updating from the original Microsoft update service of from a WSUS server, the time until the first update sometimes can be hours.
This update is supposed to fix that. I haven't tried it myself yet:
https://support.microsoft.com/en-us/kb/3161608
(No Ratings Yet)
Loading..."c:\Program Files\Microsoft SQL Server\90\Tools\binn\SQLCMD.EXE" -E -S np:\\.\pipe\MSSQL$MICROSOFT##SSEE\sql\query -Q "BACKUP DATABASE [SUSDB] TO DISK = N'C:\backups\SUSDB.BAK' WITH NOFORMAT, INIT, NAME = N'WSUS Database Backup', SKIP,NOREWIND, NOUNLOAD, STATS = 10"
c:\backups must be writable by the user that is running the database. In my case, I believe this is user "NETWORK SERVICE".
© GeekLabInfo Backup your WSUS database is a post from GeekLab.info. You are free to copy materials from GeekLab.info, but you are required to link back to http://www.geeklab.info (No Ratings Yet)Loading...The virtual machine running my WSUS got a little stuffed. So I decided to move the WSUS data to a fileserver, where the price per MB is a lot lower.
To move:
"C:\Program Files\Update Services\Tools\wsusutil.exe" movecontent [newpath] [logfile]
For example:
"C:\Program Files\Update Services\Tools\wsusutil.exe" movecontent \\fileserver\wsusdata$\ c:\wsusmove.txt
Of course this very same method can be used to move from c: to d: or something.
To move the WSUS database (meta data stored in mssql), visit this page.
© GeekLabInfo Move your WSUS contents is a post from GeekLab.info. You are free to copy materials from GeekLab.info, but you are required to link back to http://www.geeklab.info (No Ratings Yet)Loading...WSUS 3 by default stores its metadata in the "Windows Internal Database". According to wikipedia, this is an embedded version of SQL Express, which ships with Win2k8, Sharepoint Services and WSUS.
As with a regular SQL Server datastore, you can detach and move the database.
I got the tools from the microsoft website. I downloaded sqlncli.msi and SQLServer2005_SQLCMD.msi
The following services must be stopped to be able to detach the database: IIS Admin Service and Update Services (Not Windows Update Service!). To do this, run:
net stop "update services"
net stop w3svc
1. Detach the database
"c:\Program Files\Microsoft SQL Server\90\Tools\binn\SQLCMD.EXE" -E -S np:\\.\pipe\MSSQL$MICROSOFT##SSEE\sql\query -Q "sp_detach_db 'SUSDB'"
2. Now move the SUSDB.mdf and SUSDB.ldf to their new location. In the example below, we use E:\WSUSDB\. Use explorer to move the files to the path you'd like.
3. Then we reattach the database:
"c:\Program Files\Microsoft SQL Server\90\Tools\binn\SQLCMD.EXE" -E -S np:\\.\pipe\MSSQL$MICROSOFT##SSEE\sql\query -Q "sp_attach_db @dbname=N'SUSDB',@filename1=N'E:\WSUSDB\SUSDB.mdf', @filename2=N'E:\WSUSDB\SUSDB_log.ldf'"
Restart the services we stopped before. To do this, run:
net start "update services"
net start w3svc
If you want to move the WSUS data itself as well, please see this page
© GeekLabInfo How to move your SUSDB (WSUS) is a post from GeekLab.info. You are free to copy materials from GeekLab.info, but you are required to link back to http://www.geeklab.info
(8 votes, average: 4.63 out of 5)Loading...(This article is an update to this original page from march.)
I recently installed a new Microsoft WSUS server. Most of it went just fine. Except for a few updates that weren't needed according to windowsupdate.com, but were required according to WSUS.
Especially KB974417 was pretty annoying. I tried installing it a dozen times, but after each reboot, WAU came back telling the update was ready to install. I checked out the eventvwr, and got the following useless message:
Event Type: Error
Event Source: HotFixInstaller
Event Category: None
Event ID: 5000
Date: 3/16/2010
Time: 3:06:25 PM
User: N/A
Computer: PC1
Description:
EventType visualstudio8setup, P1 microsoft .net framework 2.0-kb974417, P2 1033, P3 1642, P4 msi, P5 f, P6 9.0.40302.0, P7 install, P8 x86, P9 w2k3r2, P10 0.
I downloaded the file from the Microsoft website, to find that the update itself thought itwasn't needed as well: None of the products that are addressed by this software update are installed on this computer. Click Cancel to exit setup.
So what I did:
© GeekLabInfo KB974417 install fails - working solution! - updated is a post from GeekLab.info. You are free to copy materials from GeekLab.info, but you are required to link back to http://www.geeklab.info (2 votes, average: 5.00 out of 5)Loading...In order to keep my users from getting windows update messages, I try to install any client updates at night. I have a few tricks to make this possible:
Most computers can boot up automatically at night, using Wake-On-LAN. If your computer or its NIC does not support WOL, you can use the bios' power management to boot at night.
Don't start all computers at the exact same time, as this will result in a power peak - better spread it, like 5 computers per minute.
© GeekLabInfo Windows update: Install at night is a post from GeekLab.info. You are free to copy materials from GeekLab.info, but you are required to link back to http://www.geeklab.info (2 votes, average: 2.50 out of 5)Loading...I just described that KB974417 fails to install on a few of my clients. Well, so does KB953297.
Unforunately, I don't have error messages for this update. But I can tell how I fixed it:
Trying to install NDP1.1sp1-KB953297-X86.exe, I got the message that the software we're updating is not installed. It most definitely was. I just downloaded NDP1.1sp1-KB867460-X86.exe and installed it right over the existing installation. After that, KB953297 was successfully deployed.
© GeekLabInfo KB953297 installation fails - working solution! is a post from GeekLab.info. You are free to copy materials from GeekLab.info, but you are required to link back to http://www.geeklab.info (No Ratings Yet)Loading...