Sometimes you need to query the WSUS database using T-SQL statements.
The WSUS database can be installed using the Windows Internal Database (shipping with WSUS 3.0) or a standard SQL database.
When a Windows Internal Database is used, you can use SQL Management Studio Express to connect to. Use the following string to connect to this database: \\.\pipe\MSSQL$MICROSOFT##SSEE\sql\query
For more info, see http://blogs.technet.com/b/gborger/archive/2009/02/27/exploring-the-wsus-windows-internal-database.aspx.
Continue reading SQL queries on WSUS database
Check out Microsoft article http://support.microsoft.com/kb/968872 for a quick way to open the necessary ports for SQL Server on Windows Server 2008.
The batch file below (from link above) does the trick:
netsh advfirewall firewall add rule name="Open Port 80" dir=in action=allow protocol=TCP localport=80
@echo ========= SQL Server Ports ===================
@echo Enabling SQLServer default instance port 1433
netsh advfirewall firewall add rule name="SQL Server" dir=in action=allow protocol=TCP localport=1433
@echo Enabling Dedicated Admin Connection port 1434
netsh advfirewall firewall add rule name="SQL Admin Connection" dir=in action=allow protocol=TCP localport=1434
@echo Enabling Conventional SQL Server Service Broker port 4022
netsh advfirewall firewall add rule name="SQL Service Broker" dir=in action=allow protocol=TCP localport=4022
@echo Enabling Transact SQL/RPC port 135
netsh advfirewall firewall add rule name="SQL Debugger/RPC" dir=in action=allow protocol=TCP localport=135
@echo ========= Analysis Services Ports ==============
@echo Enabling SSAS Default Instance port 2383
netsh advfirewall firewall add rule name="Analysis Services" dir=in action=allow protocol=TCP localport=2383
@echo Enabling SQL Server Browser Service port 2382
netsh advfirewall firewall add rule name="SQL Browser" dir=in action=allow protocol=TCP localport=2382
@echo ========= Misc Applications ==============
@echo Enabling HTTP port 80
netsh advfirewall firewall add rule name="HTTP" dir=in action=allow protocol=TCP localport=80
@echo Enabling SSL port 443
netsh advfirewall firewall add rule name="SSL" dir=in action=allow protocol=TCP localport=443
@echo Enabling port for SQL Server Browser Service's 'Browse' Button
netsh advfirewall firewall add rule name="SQL Browser" dir=in action=allow protocol=UDP localport=1434
@echo Allowing multicast broadcast response on UDP (Browser Service Enumerations OK)
netsh firewall set multicastbroadcastresponse ENABLE
Check out http://www.symantec.com/business/support/index?page=content&id=TECH23760 if you installed the 60-days trial and you’d like to know how to enter your serial number(s). (Backup Exec 12 or higher)
The McAfee Global Solutions Lab, http://www.mcafeegsl.com/, already exists for a long time, and since some time v2.0 is available.
You need to create an account (which is free) to proceed. Once this is done you can select your desired environment (see screenshot below for current environments).
If you want to have a look at the McAfee range of products, or want to do some tests, etc, you have a virtual machine with McAfee ePolicy Orchestrator 4.5. or 4.6, … available in minutes.
You created a custom policy, but how do you assign it to a system ?
It’s not that difficult, here is how:
- Select the system (via the System Tree, or standard Dashboard)
- Actions > Agent
- Set Policy & Inheritance
- Assign Policy for 1 system
- Product: [select the product]
- Category: [select category]
- Policy: [Select the policy you want to assign]
- Inheritance: Break inheritance
If you want more information on managing policies and task in ePO 4.5, check out McAfee article “How to manage policies and tasks for selected computers in ePO 4.5”, https://kc.mcafee.com/corporate/index?page=content&id=KB65979.
This article also contains a link to a video tutorial: (Adobe Flash Player required)
KB65979 – How to manage policies and tasks for selected computers in ePO 4.5
I encountered this recurring issue on a Citrix server. The event ID you’ll find in the application log:
Event ID 5051: A thread in process … took longer than 90000 ms to complete a request. The process will be terminated …
All details about cause and possible workarounds can be found in McAfee KB52441: https://kc.mcafee.com/corporate/index?page=content&id=KB52441. I used workaround 5, disable oppurtunistic locking in Windows, and this solved the issue on the server.