WSUS
.. WSUS FAQ
.. WSUS on SBS
.. WSUS Troubleshooting
.. WSUS News Groups
.. Known WSUS Issues
.. WSUS Links
.. WSUS Wish List
WSUS Documents
.. WSUS Deployment Guide
.. WSUS Installation Guide
.. WSUS Release Notes
.. WSUS Best Practice
SUS
.. SUS FAQ
.. What Is SUS
.. SUS Troubleshooting
.. SUS Links
.. SUS Known Issues
.. SUS FAQ
.. What Is SUS
.. SUS Troubleshooting
.. SUS Links
.. SUS Known Issues
Wiki Community
.. Wiki Contributors
.. I Love WSUS
.. WSUS Wiki Diary
.. Wiki Statistics
.. To Do Page
Miscellaneous Stuff
.. Other Resources
.. Do You Know?
Terms of Use
Trademarks
Privacy Statement
Wsus Rollup Tool Sample |
Microsoft has developed a Reporting Rollup Sample which you can download, use and customise. The sample tool was created using the WSUS application programming interface (API) to demonstrate centralised monitoring and reporting for WSUS. The tool rolls up update and computer status from all the WUS servers in your WSUS implementation in a single report. Links to the rollup tool sample, and a readme file giving more information are on the WSUS downloads page. The downloaded file (WSUSRollupSample.EXE - 317kb) is a self extracting EXE that contains a MSI package. This MSI package contains the complete sample tool solution with UI, plus the source project files to customize the tool to your own/customer's needs. NB: This is a sample and is not supported by Microsoft.
The install/first run can be somewhat complex so be sure to review the readme and follow the steps:
http://download.microsoft.com/download/8/1/a/81a41962-cff5-4396-a567-0d2f87d8f67a/Readme.htm
Comments:
From paulsgagnon - 11/26/07 9:15 AM
From sigi86 - 8/16/06 4:58 AM
Hello!
I didn't d get it working! When I open the link http://<rollup-viewer-server>/WsusRollupViewer
I just get the page without any links just displaying LinkButton and I can't choose a WSUS Server!
Maybe somebody can help me ! Hopefully!
Thanks and best regards
Siegfried
From StefanH - 7/17/06 4:14 AM
Hello,
is there a tool available to clean up the SQL Database.
Reason: I have reinstalled some WSUS Server. As a result of this I have the servernames double in the WSUS Server List.
any ideas ?
From nishanth - 4/6/06 4:40 AM
Hi All.
I have configured WSUS in my organisation and seemed to have got stuck in configuration of WSUS rollupviewer...Would be very helpful if anyone can help me in configuration of the same.
My email id is Infrajini.epo@unilever.com ,plz help me
From flox - 2/10/06 3:40 AM
It works! This is what I do:
First follow all the steps in Microsft's Readme
When the database and the website is created and the WsusServer are prepaired,
I create a *.bat-file on all of the WsusServers and call it export.bat. It contains this line:
"E:\WSUS-Reporting\rollup-client-tools-dir\ExportAndUploadRollupData.cmd" "E:\WSUS-Reporting\Temp" http://WSUSSERVERNAME/WSUSAdmin \\ROLLUPSERVERNAME\WsusRollupData
Next I create a job on the WsusServers pointing to the export.bat
After the successfull uploads of all the *.cap-files to the WsusRollupServer,
I create a *.bat-file on the WsusRollupSever and call it import.bat. It contains this lines:
rem ##
rem ## First I rename the cryptic and ever changing *.cap-file to a specific name (I do the for all uploading wsus-server)
rem ##
ren 1stWsusSeverName* 1stWsusSeverName.cab
ren 2ndWsusSeverName* 2ndWsusSeverName.cab
rem ##--------------------------------------------------------------
rem ## Then I use the extract-tool, provided by Microsoft, to create an *.xml-file from the *.cap-file
rem ##
"C:\Program Files\Resource Kit\extract.exe" c:\WsusRollupSample\RollupData\1stWsusSeverName.cab c:\WsusRollupSample\RollupData\1stWsusSeverName.xml
"C:\Program Files\Resource Kit\extract.exe" c:\WsusRollupSample\RollupData\2ndWsusSeverName.cab c:\WsusRollupSample\RollupData\2ndWsusSeverName.xml
rem ##-------------------------------------------------------------
rem ## Next I delete the *.cap file
rem ##
del *.cab /q
rem ##-------------------------------------------------------------
rem ## Finaly I run the import itself
rem ##
C:\WsusRollupSample\WsusRollupImportMonitor.exe C:\WsusRollupSample\RollupData wsusrollupservername WsusRollupDatabase
In this way it worked for me.
From flox - 2/8/06 2:32 AM
since I needed several test, to get the job running, I created a *.bat file including just the command that finaly worked out fine.
I have created the job on the servers to run this *.bat.
The contennt of my export-the-data-command.bat is (written in one line):
"E:\WSUS-Reporting\rollup-client-tools-dir\ExportAndUploadRollupData.cmd" "E:\WSUS-Reporting\Temp" http://pclservice01/WSUSAdmin \\pvmwsus01\WsusRollupData
The contennt of my import-the-data-command.bat is (written in one line):
"C:\Program Files\WSUS\WSUS-Rollup-Sample\WsusRollupImport.exe" \\pvmwsus01\WsusRollupData\pclservice01.cab pvmwsus01 WsusRollupDatabase
this command genererates this error in the command-shell:
C:\Program Files\WSUS\WSUS-Rollup-Sample>"C:\Program
Files\WSUS\WSUS-Rollup-Sample\WsusRollupImport.
exe" \\pvmwsus01\WsusRollupData\pclservice01.cab pvmwsus01 WsusRollupDatabase
WsusRollupToolImport failed with the below exception!
System.Xml.XmlException: There is an invalid character in the given encoding. Line 1, position
5.
at System.Xml.XmlScanner.GetChars(Byte[] srcBuffer, Int32& srcOffset, Int32 srcLen, Char[]
destBu
ffer, Int32 destOffset, Boolean zeroedOut) at System.Xml.XmlScanner.Read()
at System.Xml.XmlScanner.ScanContent()
at System.Xml.XmlTextReader.ParseRoot()
at System.Xml.XmlTextReader.Read()
at System.Xml.XmlReader.MoveToContent()
at Microsoft.WsusTools.ImportServerStatus.DumpData(String filePath, String dbServerName,
String d
atabaseName)
at Microsoft.WsusTools.WsusRollupTool.Main(String[] args)
and I have no idea why. If I get this thing working one day, I will asap post it here and dance in my office!
From flox - 2/8/06 2:30 AM
From vramanx - 2/7/06 5:40 PM
From RazvanDespa - 2/7/06 2:25 PM
Hi all,
I was looking to install this tool also for several downstream servers, but i get stucked in the configuration of the scheduled jobs.
Can anyone post the exact line that need to be placed in the scheduled task, or in a script file?
Thanks, Razvan Despa
From flox - 2/7/06 7:47 AM
From G3kkie - 12/16/05 7:14 AM
From vramanx - 11/16/05 7:55 PM
jchuyang -- this is the older version of the tool. the link posted on the top of the page should point to the latest version. or you can download the latest from
http://www.microsoft.com/windowsserversystem/updateservices/downloads/default.mspx
From jchuyang - 11/14/05 3:02 PM
I have the basic WSUS Rollup functionality working. My only problem is with the page display. Say for example, you have 800 machines. Page 1 will show machines 1-50. When you click on page 2, it will show machines 1-60. If you click on page 3, it will show machines 1-60 again. If you click on page 4, it again shows machines 1-60. Is there something I'm missing, that would fix this behavior? I can live with the fact that it only shows 50 machines per page, but not showing the same machines on each page.
Any suggestions would be appreciated.
Thanks.
From vramanx - 11/4/05 6:06 PM
vfast -- below is the script to cleanup a stale computer. just substitute the correct database and computer name
use <WsusRollupDatabase>
begin tran
delete ComputerSummary from ComputerSummary
inner join Computer on Computer.ComputerID = ComputerSummary.ComputerID
where Computer.FullDomainName='<stale-computer-name>'
delete from Computer where FullDomainName='<stale-computer-name>'
commit tran
From vramanx - 10/24/05 3:03 PM
vfast -- if you are proficient with SQL, cleaning up stale entries from the rollup database is very straitforward. you need to delete rows from Computer and ComputerSummary tables for all the stale computers.
From vfast - 10/23/05 10:18 PM
Thanks for this great tool. However I have a question:
I have several hundred machines showing in the Rollup reports but they are no longer in WSUS database. Is there a way in which to clean these old machines from the Rollup database?
Thanks
vfast(at)iinet(dot)com(dot)au
From MarcelMerk - 10/21/05 3:06 AM
I am getting 404 when I open the http:/localhost/WSusrollupViewer.
I am using remote SQL server 2000 SP3. Upload of data is okay from replica server into database.
From MarcelMerk - 10/20/05 10:44 AM
I am getting 404 when I open the http:/localhost/WSusrollupViewer.
I am using remote SQL server 2000 SP3. Upload of data is okay from replica server into database.
From atclif - 10/12/05 4:22 AM
From atclif - 10/12/05 4:16 AM
From vramanx - 10/10/05 11:49 AM
atclif -- can you run the below command and send me the full exception?
there is a directory called FailedFiles inside the <tool-install-directory>\RollupData. that will contail all the xml files that failed processing.
from the tool install directory run the below command and send me the full exception.
WsusRollupImport.exe <failed-xml-file> "db-server" "db-name"
also send the xml file with which the tool is failing.
From atclif - 10/7/05 9:03 AM
I've installed and configured the tool, and seems to upload the files OK, but when it tries to import the some of the files it fails with the below:
Application popup: WsusRollupImportMonitor.exe - Common Language Runtime Debugging Services : Application has generated an exception that could not be handled.
Process id=0xe98 (3736), Thread id=0x588 (1416).
Any ideas?
From atclif - 10/7/05 8:58 AM
I've installed and configured the tool, and seems to upload the files OK, but when it tries to import the some of the files it fails with the below:
Application popup: WsusRollupImportMonitor.exe - Common Language Runtime Debugging Services : Application has generated an exception that could not be handled.
Process id=0xe98 (3736), Thread id=0x588 (1416).
Any ideas?
From vramanx - 10/6/05 11:59 AM
we have a new version of the tool available for download. i have updated the links at the top of the page. this has fixes for better paging behavior and SQL datetime data import issue when running on non-US locales
From vramanx - 10/4/05 10:18 AM
d9thc -- you can change the task created on the WSUS server for uploading data to pass https://%computername%/WsusAdmin instead of http://%computername%/WsusAdmin
%computername% will pass the netbios name of your computer. if netbios names will not work for you, then you can pass the FQDN here.
please wait for the task to run and upload data and the task on central rollup server to import the data. then you will be able to access the WSUS servers with the new url.
From d9thc - 10/3/05 12:28 PM
From d9thc - 10/3/05 12:03 PM
From vramanx - 9/29/05 4:19 PM
Shad -- there are no issues with running WMSDE and MSDE on the same box.
you can find instructions for installing MSDE in the WSUS deployment guide
From Shad - 9/29/05 12:04 PM
I would really like to rollout The WSUS Rollup Tool Sample as part of a test project I am wokring on but, I can't find any information on installing MSDE and WMSDE on the same Windows Server 2003 machine. My WSUS installations are all using WMSDE. Are there any problems with running WMSDE for WSUS and MSDE for the Rollup Tool?
Shad
shadmalloy<please_don't_spam>@hotmail.com
From vramanx - 9/21/05 1:35 AM
we have a fix for the date time parsing issue. i am also working on fixing the export batch file for date format issues. we will upload the new bits once the fixes are tested.
From StefanH - 9/20/05 6:36 AM
This is true. This is a possible solution. But you have to change this value on both; WSUS Server and Rollup Server. Attention: It's a user value. You have to change this for the user that you use in your scheduled job.
I have onother problem: On some servers the date value is "Tue 2005/09/19" not "2005/09/19.
In this case the cab file is not created . How can I fix this?
From SEEdER - 9/19/05 10:38 AM
You've just to change the date format to yyyy-MM-dd. You can change this in Control Panel -> Regional and Language Settings -> Tab. Regional Options -> Customize -> Tab. Date.
I think you've just to change the date format on the WSUS - Server.
From jimb09990 - 9/16/05 9:37 AM
I get the same problem as StefanH. Any ideas?
Regards
James
From jimb09990 - 9/16/05 9:12 AM
I get the same problem as StefanH. Any ideas?
Regards
James
From jimb09990 - 9/16/05 8:08 AM
I get the same problem as StefanH. Any ideas?
Regards
James
From StefanH - 9/16/05 5:01 AM
The "Rollupserver" is in Germany locale: German (Germany) 0407
The "WSUS Server" is in Britain locale: English (United Kingdom) 0809
From vramanx - 9/15/05 12:55 PM
From StefanH - 9/15/05 2:45 AM
Hello,
tool works perfect on the Downstraeamserver, but the WsusRollupImportMonitor.exe failed with following exception:
Exception: System.Data.SqlClient.SqlException: The conversion of a char data type to a a datetime data type resulted in a out-of-range datetime value. The statement has been terminated.
On both servers I run the "echo %date%" command. The result is on both: 15/09/2005
After this I find the XML file in ..\WsusRollupSample\RollupData\FailedFiles
I have sended the XML File to vramanx@hotmail.com
I hope this will help to find a solution.From vramanx - 9/13/05 2:13 PM
ah the date formats. i tried to eliminate as many characters as possible in date and time in the batch file. looks like i missed the comma.
we tested the paging behavior for much more computers. is it possible for you send the export xml files cabbed for me to test at vramanx@hotmail.com?
From pmaquoi - 9/13/05 6:44 AM
ok i found the reason
the decimal separator was the , and not the .
now everything is functionnal
But there are some bugs
For example on the "Computers needing updates report" i've got 800 computers, but i'm able to browse till page 40 ???
I know that no more than 50 computers are only retrieved at a time, but it lack some control before adding a new display page etc...
It's a sample, yes i know but for a report, not being able to access the 780th computer without browsing 15 pages (1-50,51-100,etc...) makes the sample inoperable.
From pmaquoi - 9/12/05 2:00 AM
i forgot something in my previous answer
the result of the %date% is the same on the master server but on the master server, the cab creation processus is well done
From pmaquoi - 9/12/05 1:22 AM
ok the date is in French version
i've got "Lun. 12/09/2005" on all my replica server
is it the language the trouble ?
Thanks for all
From vramanx - 9/9/05 8:52 AM
pmaquoi the export tool does work on a replica server.
for the cabbing problem, can you send me the output of echo %date% from a cmd window?
the paging behavior you described is by design. as i mentioned before, we only retrieve 50 records at a time. all we know is we have more records or not.
From pmaquoi - 9/9/05 1:08 AM
ok i 'll explain more the two bugs and a third on a downstream server
if you click on a computer name in the "Computers needing update" choice
you see a list with 50 computers on the first page, that's correct but...
you just see 2 pages on the first lines of the report window (1 2)
iy you click on the second page (click on 2) then you see the second report page buit this time it shows you the 51-100 computers and ...1 2 3 pages on the top. you click on the 3rd pages and then it shows the 100-150 with ...1 2 3 4 so there is a fourth page ? and so on ....
It vould be great to know how many pages you have in the report list. Because if you want to go to the 10th page, it isn't showed before being on the nineth etc... is it more clear now (Sorry for my english)
now the second bug has vanished this morning so forget it. but i found a new one on a downstream server.
The cabarc.exe has been copied in the system32 directory but the cabfile isn't created. Like another message before this one from another tester, i receive this error
"FCI ADDFILE() Failed: Code 1 Failure opening file to be stored in cabinet"
could you help ?
Anoter question ... does it work on a replica server also (i(ve got one master, two downstream and 4 replica)
And a final note, this module is great for a better view of WUS status.
From vramanx - 9/8/05 5:44 PM
pmaquoi the account with which you are running the upload task should have write access to the central share. if not the upload will fail. can you check if this is the issue?
the paging behavior is by design. we retrieve only the required records from the rollup database. the page should show 50 records at a time.
i dont understand the problem "Another bug : If you click on a computer, the second tab doesn't display anything". can you send me a screenshot?
From pmaquoi - 9/8/05 8:40 AM
Ok, the trouble was with the instance of SQL / MSDE
I've restarted the installation and now it's better but ....
the cab file is created but is not upload to the directory. iv'e controlled the syntax of the scheduled task and it looks fine
if i upload it manually, the import cmd works well and the display of the site is ok
some other bug...
If you sort a big list of computers (800) you just see 2 pages of 30 computers if you click on the "2" then the second page show a "1.2.3". If you click on 3 then 1.2.3.4
Another bug : If you click on a computer, the second tab doesn't display anything
From pmaquoi - 9/8/05 8:31 AM
Ok, the trouble was with the instance of SQL / MSDE
I've restarted the installation and now it's better but ....
the cab file is created but is not upload to the directory. iv'e controlled the syntax of the scheduled task and it looks fine
if i upload it manually, the import cmd works well and the display of the site is ok
some other bug...
If you sort a big list of computers (800) you just see 2 pages of 30 computers if you click on the "2" then the second page show a "1.2.3". If you click on 3 then 1.2.3.4
Another bug : If you click on a computer, the second tab doesn't display anything
From pmaquoi - 9/8/05 8:31 AM
Ok, the trouble was with the instance of SQL / MSDE
I've restarted the installation and now it's better but ....
the cab file is created but is not upload to the directory. iv'e controlled the syntax of the scheduled task and it looks fine
if i upload it manually, the import cmd works well and the display of the site is ok
some other bug...
If you sort a big list of computers (800) you just see 2 pages of 30 computers if you click on the "2" then the second page show a "1.2.3". If you click on 3 then 1.2.3.4
Another bug : If you click on a computer, the second tab doesn't display anything
From pmaquoi - 9/8/05 8:27 AM
Ok, the trouble was with the instance of SQL / MSDE
I've restarted the installation and now it's better but ....
the cab file is created but is not upload to the directory. iv'e controlled the syntax of the scheduled task and it looks fine
if i upload it manually, the import cmd works well and the display of the site is ok
some other bug...
If you sort a big list of computers (800) you just see 2 pages of 30 computers if you click on the "2" then the second page show a "1.2.3". If you click on 3 then 1.2.3.4
Another bug : If you click on a computer, the second tab doesn't display anything
From pmaquoi - 9/8/05 7:59 AM
Ok, the trouble was with the instance of SQL / MSDE
I've restarted the installation and now it's better but ....
the cab file is created but is not upload to the directory. iv'e controlled the syntax of the scheduled task and it looks fine
if i upload it manually, the import cmd works well and the display of the site is ok
some other bug...
If you sort a big list of computers (800) you just see 2 pages of 30 computers if you click on the "2" then the second page show a "1.2.3". If you click on 3 then 1.2.3.4
Another bug : If you click on a computer, the second tab doesn't display anything
From vramanx - 9/7/05 1:37 PM
ADAMEKPA sorry i pressed submit too early.
can u post the log file created by the export script?
From vramanx - 9/7/05 1:33 PM
ADAMEKPA can u check if the data is getting exported successfully? on the WSUS server from which you are exporting the data goto the directory where you copied the client tools.
From ADAMEKPA - 9/7/05 5:55 AM
The Sctipt does not work. On an export server i alway get this:
FCIAddFile() failed: code 1 [Failure opening file to be stored in cabinet]
I think there is a problem with the cab creation proicess.
By the way, what does this here do:
set __FileDate=%date%
set __FileDate=%__FileDate: =_%
set __FileDate=%__FileDate:/=_%
From ADAMEKPA - 9/7/05 5:45 AM
The Sctipt does not work. On an export server i alway get this:
FCIAddFile() failed: code 1 [Failure opening file to be stored in cabinet]
I think there is a problem with the cab creation proicess.
By the way, what does this here do:
set __FileDate=%date%
set __FileDate=%__FileDate: =_%
set __FileDate=%__FileDate:/=_%
From ADAMEKPA - 9/7/05 5:44 AM
The Sctipt does not work. On an export server i alway get this:
FCIAddFile() failed: code 1 [Failure opening file to be stored in cabinet]
I think there is a problem with the cab creation proicess.
By the way, what does this here do:
set __FileDate=%date%
set __FileDate=%__FileDate: =_%
set __FileDate=%__FileDate:/=_%
From vramanx - 9/6/05 3:11 PM
From vramanx - 9/6/05 3:11 PM
pmaquoi did you install a SQL/MSDE instance before running the tool setup? if you have an instance, are you running as a user who can create a database?
From mbakunas - 9/6/05 8:30 AM
From pmaquoi - 9/5/05 7:53 AM
For me
"Failed to create the sql database"
From vramanx - 9/1/05 5:19 PM
From vramanx - 9/1/05 5:15 PM
From vramanx - 9/1/05 5:02 PM
From mbakunas - 9/1/05 4:17 PM
Last Modified 10/22/05 5:48 PM