Performing WUSU 3.0 database maintenance (database re-indexing) via WsusDBMaintenance under Windows Server 2008

System Requirements:

  • Windows Software Update Services 3.0
  • Windows Server 2008, 2008 R2

The Problem:

Microsoft recommend that you perform monthly maintenance on your WSUS database to keep it in good order. The following pages represent the instruction for undertaking this activity

This document simply seeks to clarify the process when using Windows Internal Database (instead of SQL Server) under Windows Server 2008/R2.

The Fix

The following summarises the steps involved in the process.

  1. Install the SQL Server Native Client for your processor on the WSUS server
  2. Install the SQLCmd utility for your processor on the WSUS server
  3. Copy & Paste the T-SQL code from Re-index the WSUS 3.0 Database into a notepad file and save it on c:\ as WsusDBMaintenance.sql (or download here)

If you wish to automate or schedule the task:

  1. Create a .cmd file on your desktop
  2. Enter the following into it
"c:\Program Files\Microsoft SQL Server\90\Tools\Binn\sqlcmd.exe" -I -i"c:\WsusDbMaintenance.sql" -S "np:\\.\pipe\MSSQL$MICROSOFT##SSEE\sql\query"
  1. Note that the version of the SQL Server SQLCmd that you install will need to be reflected in the version number (90 above). 90 = SQL Server 2005, 100 = SQL Server 2008 and so on.
  2. Right click the .cmd file and select “Run as Administrator” to launch it through an elevated command prompt
  3. If you setup a scheduled task for this, remember to set the always run with full permissions option.

If you just want to run it once:

  1. Open an elevated command prompt
  2. Enter the command:
"c:\Program Files\Microsoft SQL Server\90\Tools\Binn\sqlcmd.exe" -I -i"c:\WsusDbMaintenance.sql" -S "np:\\.\pipe\MSSQL$MICROSOFT##SSEE\sql\query"
  1. Note that the version of the SQL Server SQLCmd that you install will need to be reflected in the version number (90 above). 90 = SQL Server 2005, 100 = SQL Server 2008 and so on.

Cannot install the integrated audio AC97′ hardware from a Asus P4S333 or P4S533 under Windows Vista

System Requirements:

  • Windows Vista SP1
  • Windows Server 2008

The Problem:

So, you get fed-up of trying to get PCI sound cards working under Vista and opted for the integrated sound CPU clogging solution?! I don’t blame you.

The P4S333 may be old kit, but it’s a solid motherboard, very much Vista capable with the right upper end P4 and enough RAM, particularly if you flashed the P4S333 with the P4S533’s BIOS to make use of the 533 MHz FSB. The difficulty we have is however in that the C-Media CMI8738 AC97′ chip that the board uses cannot be matched to any of Windows Updates hardware ID’s and Asus, naturally, do not offer a Vista driver.

More Information:

Thankfully, C-Media do provide generic drivers, and there is a January 2009 driver release for the CMI8738 as of writing. The driver does work once you get it out of the RAR file, however:

  1. The driver does not have the necessary hardware ID to install automatically against the customised chip on the P4S333 / P4S533
  2. The driver is not digitally signed

Despite that, I’ve not seen any problems with it, and despite the CPU connotations, it got rid of irritating buzzing that the Creative Labs Sound Blaster Live! 5.1 was causing with the useless Vista driver set.

The Fix

Very simply, you need to manually install the driver.

  1. Download the latest CMI8738 driver from C-Media (http://www.cmedia.com.tw/). As of writing the driver version was 8.17.33 and it worked a treat
  2. Deflate the RAR into the file system
  3. Open the Control Panel
  4. Open the Device Manager
  5. Find the uninstalled multimedia device in the Other Devices section, right click, Update Driver Software
  6. Click Browse my computer for driver software
  7. Click let me pick from a list of device drivers on my computer
  8. Hit the have disk button
  9. Browse to the path that you inflated the RAR file to, for example if you inflated the RAR file to c:\temp\ you want to browse to the following location:
    c:\temp\PCI-8738-090109-8.17.33(Vista3264-RC-01)\SoftwareDriver\driverNote that if the driver version you are using is newer, then the version in the file name will clearly be different. Ultimately however you are looking to point to the SoftwareDriver\driver folder (there are several INF’s and some CAT files in here)
  10. In the manufacturer list from the available select:
    C-Media
  11. From the Model list select:
    C-Media PCI Audio Device
  12. Click Next
  13. Windows will notify you that the driver has not been digitally signed. You’re going to have to tough this one out I’m afraid and install it.
  14. At that point the audio should just start working.

How to install Windows Media Player 11 with Media Sharing on Windows Server 2003 / R2

System Requirements:

  • Windows Server 2003 SP2
  • Windows Server 2003 R2 SP2

The Problem:

Windows Server 2003 ships with Windows Media Player version 10.0, and this version is maintained and services through Service Packs for Windows Server 2003.

The version of Media Player that ships with 2003 does not include Media Sharing support for distributing central Media Library databases to network clients. Unfortunately, with Microsoft’s decision to not to release Windows Media Player 11 for Server 2003 and not to include media library sharing in their 2008 platform, a minority of users (myself included) who use Server 2003 as a home server platform are forced to find other ways of centrally distributing media or to use an XP license, hardware (VM) and additional electricity to service WMP11 clients.

Prerequisites:

This article specifically discusses and assumes the following:

  • Windows Server 2003 / 2003 R2 SP2
  • Windows Media Player 11 – 11.0.5721.5145 (wmp11-windowsxp-x86-enu.exe published 1/15/2007)

Please Note: If the Windows Media Player 11 build is updated in the Microsoft Download Centre then the Service Pack 2 component of this article may no longer apply.

More Information:

Microsoft have made a conscious decision not to include Windows Media Player 11 in 2003, presumably as an added incentive to upgrade to Server 2008. However even Server 2008 fails to integrate the Media Library sharing components of WMP11 as Microsoft view the feature as not being of intrinsic use in corporate situations.

While Microsoft aren’t wrong here, and they (now) offer the Windows Home Server platform with this support, it isn’t something that I personally wish to look towards using having built a Server solution at home rom NT 4.0 onwards. As I have a domain environment at home and having a server infrastructure I have no desire to add a Windows XP system “server” into the mix just to support media sharing or to purchase Home Server.

As usual I have to wonder what goes through the heads of Microsoft development from time to time. For the sake of the 792 KB of entirely optional DLL files that are required to implement this – DLL’s that are being serviced anyway in the XP/XP64 (which is 2003 Server) and in Vista. You would have thought that adding it as an optional module wouldn’t be an unreasonable thought, however I digress.

The XP/Server 2003 code base is identical and as such the binary versions of WMP11 for Windows XP will run on Server 2003, unofficially.

This article outlines how to install Windows Media Player 11 and the system services necessary for Media Sharing using my nearly fully automated installation process.

Installing Windows Media Player 11 with SSDP & UPnP

This guide outlines how to install WMP11 on Server 2003. The process of getting Windows Media Player 11 onto Server 2003 is fairly simple, and I did start to investigate how to get the services working myself. While searching on Google for a fix for an error message I stumbled upon someone else’s fix for the services. So, not wanting to reinvent the wheel I abandoned my research and have used their process in my automation tool for installing the services for media sharing.

Credit for the process discovery for the system services goes to steven2004 of neowin.net.

If you need the User Mode Driver Framework for mobile device connectivity (e.g. Android), download version 1.0.2 (with thanks to kevin551 from Neowin for the variable tip) if you do not, use version 1.0.1. If you want to replace the default version of UMDF with the newer 1.9 release, see this page.

Please Note:

  1. This is not supported by Microsoft Corporation, Microsoft will not (and should not) be expected to support this
  2. After installing this on a server, Windows/Microsoft Update will no longer track updates for Windows Media Components, you will be responsible for doing this yourself
  3. Do not roll this out in a production environment, it’s one thing to do it on a box at home, quite another to do it in an enterprise environment; so for the sake of arguments, just don’t.

Download: Automatic Installer 1.0.1 (354 KB)
Download: Automatic Installer 1.0.2 (354 KB)

 

  1. Download my automatic installer
  2. Extract the installer files into a directory on your computer
  3. Download wmp11-windowsxp-x86-enu.exe into the SAME directory that you extracted my automated installer
  4. Run INSTALL.cmd
  5. The installer will stop with the following message on the screen:
  6. Open c:\wmp11\1\update\
  7. Right click update.exe
  8. Click properties
  9. Open the Compatibility Tab
  10. Check the box next to “Run this program in compatibility mode for:” and select Windows XP from the drop menu
  11. Click OK
  12. Repeat from step 7 for the version of update.exe found in C:\wmp11\2\update\
  13. Return to the INSTALL.cmd window and press any key to continue with the installation process
  14. Select the UPnP service when prompted by the wizard and click next. If prompted for a file path select c:\wmp11
  15. Finish the Wizard
  16. Restart your Server
  17. You will now be able to start and configure the SSDP and UPnP Services

Note: This process does not patch the WMP11 installation. You will no longer received Windows Media Player updates from Windows/Microsoft Update and will need to apply these patches manually.

If you do not have Windows Media Player 11 on your start menu at this point then you either:

  1. Failed to copy the wmp11-windowsxp-x86-enu.exe to the correct location
  2. You failed to set the update.exe files to Windows XP compatibility mode

Note: It has been suggested in some areas that you can edit the update.inf to change the require Operating System version information. If you do this, the CheckSum verification will fail at the beginning of the installation and WMP11 will not be installed. All Windows XP QFE files are digitally signed and therefore will fail to install if the hash check fails.

Updates

11/02/2013 – Added information on installing UMDF and version 1.0.2 of the install script.

Asus MyCinema P7131 Hybrid – Using the FM Radio tuner on Windows Vista Home Premium / Ultimate Media Centre

System Requirements:

  • Windows Vista Home Premium / Ultimate

The Problem:

The Asus MyCinema P7131 Hybrid tuner is a relatively inexpensive way of getting a good TV picture in your PC so as to allow you to make use of the full range of features available to you through Media Centre 6.0 / 6.1 under Windows Vista. The MyCinema P7131 Hybrid is also very useful as it comes with a LP mounting bracket for use in Low Profile, small form factor cases.

The card is equipped with a DVB-T tuner, FM Radio tuner, Analogue tuner, IR port and Composite/S-Video in connector, making it quite versatile out of the box when used in conjunction with the supplied Cyberlink MyCinema 5.0 software, however this is simply a duplication of functionality for MEdia Centre enabled systems and doesn’t do it quite as eloquently as the Microsoft solution. The problem is however that out of the box the Vista Media Centre is only able to detect the DVB-T tuner in the card. If you attempt to access the Radio feature you will receive the message

No Services Found

Asus Hybrid in MCE 6 - No Radio

You will be offered no other choice of services or configuration for the FM radio and the TV tuner service will only detect the DVB-T tuner irrespective of driver version used.

More Information:

If you install MyCinema, you can get access to the FM Radio, DVB-T and Analogue tuners through the interface and configuration, so it isn’t out of place to assume that the issue lies with the main driver. This isn’t actually the case. If you have the latest BDA driver for the Philips SAA3131 tuner in the device (version 1.3.3.5 at the time of writing) then your drive does expose the FM tuner to the system. The problem is that it doesn’t configure it to an extent that when Media Centre initialises a scan of the system bus for tuners, it is aware that there device is capable of supporting more than one interface (DVB-T, Analogue, Cable, S-Video/Composite and FM).

This issue is fairly trivial when you look into the problem in so far as Asus provide a “MCE Plug-in” on their CD which acts as an abstraction layer between the two, and will resultantly allow a rudimentary level of switching – more on that in a moment. The bigger problem is in that Media Centre itself is not able to handle more than one device type on a single bus. What does that mean?

Well, take my Hauppauge Nova-T-500. It provides two DVB-T tuner chips with each chip being identified on its own bus. This allows you to use both tuners simultaneously even though they are the same card. The Asus P3171 hybrid however uses software switching in the driver to specify which of the input sources to use against the cards one and only bus. This means that only one of the interfaces (DVB-T, Analogue, Cable, FM, S-Video/Composite) can be used at a time (fair enough) however Media Centre does not natively support the switching mechanism and therefore is only aware of the default interface type, you guessed it, the DVB-T tuner.

Personally, I am willing to for go the Analogue TV tuner as it will be switched off in a couple of years anyway, and I don’t have a cable service here so the use of that Tuner doesn’t interest me and I can live without the S-Video/Composite as my TV exposes three interfaces for those directly and I have other PC’s with capture cards in them – but having installed three of these Low Profile MyCinema P7131 Hybrid cards, it was bugging me that I couldn’t get the FM radio to work and complete the “fully featured” claim on my new Media Centre. Having already convinced the powers that be to free up space by getting rid of the separates hi-fi system, I was feeling duty bound to do this before someone asked for a radio station.

The Fix

This fix is not highly technical for the simple reason that having struggled to get it working, and in the possession of some better key-word concepts it turns out that there are others who have done this with other software switched ‘hybrid’ tuners and who were doing it as far back as XP MCE 2005.

So as it turns out that I am simply rediscovering here I shall not go into too much detail. If you already have Vista installed, you can start this process from step 5.

  1. Install your Asus Hybrid tuner
  2. Install Vista Ultimate / Home Premium
  3. Install Vista SP1 if needed
  4. Install Media Centre 6.1 (aka the Windows Media Center TV Pack 2008) if you have it
  5. Install the latest Tuner Drivers for the P7131 Hybrid.
    You can simply use the add-remove hardware wizard to do this, unless you want to use the Asus Splendid technology filtering in which case use the setup.exe for the driver program.
  6. On your Asus CD (Not the MyCinema one, the green one) open the root folder in Windows Explorer and go into the MCE Plug-in folder. Here you will find two executable files. One setup.exe (the 32-bit version) and another with the 64-bit version. Run the version that you require to match your operating system architecture and install it.
    Yes, you have to install it. I know Vista has its own MPEG decoders, but you have to install it. It is this MPEG encoder that provides the filter which allows you to select which of the hardware sources you will be using – Digital, Analogue/FM or Cable.Note: If you try and install this from the CD’s autorun, you will get stuck on a permanent error about Asus DVD 6 being installed. You can ignore this message as I have not seen any adverse effects of not having Asus DVD installed, however you must run the setup.exe from Windows Explorer.
  7. Restart
  8. Start Media Centre and go through setup as you would wish to normally
  9. When prompted to setup the TV Signal, chose to setup the tuner manually
  10. Select the default instance of the DVB-T tuner and go through setup
  11. Once complete, check to ensure that you have a working DVB-T configuration
  12. Exit Media Centre
  13. Open Regedit
  14. Navigate to :
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Media Center
  15. Export the entire key Media Center and everything below it to a reg file. Call it:
    Digital.reg
  16. Open Media Centre
  17. Go to the tasks area and select setting, then TV and finally to Set Up TV Signal
  18. Repeat the tuner process but this time select the Analogue tuner and go through setup normally against that
  19. Once complete, check that the FM Radio and Analogue TV do work (do not worry if you do not have a picture)
  20. Exit Media Centre
  21. Open Regedit
  22. Navigate to :
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Media Center
  23. Export the entire key Media Center and everything below it to a reg file. Call it:
    Analogue.reg
  24. Create a copy of Digital.reg and name it Hybrid.reg
  25. Open Hybrid.reg and Analogue.reg side by side. What you will do in the fairly complicated instructions that follow is copy the configured tuner settings for the analogue tuner and merge them into the same settings file with the digital tuner configuration data. This is fairly complicated, so be sure to take it slowly.
  26. Search the Hybrid.reg for:
    UserSettings\TuneRequest\Tuning Space\Default Locator
  27. Scroll back to the left and look at the first GUID in this key’s path e.g.
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Media Center\Service\Video\Tuners\{71985F48-1CA1-11D3-9CC8-00C04F7971E0}
    Note that this is tuner specific, if you are using a different model tuner this may be different
  28. If you look down to the NEXT key path, the first path GUID will be different e.g.
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Media Center\Service\Video\Tuners\{A799A800-A46D-11D0-A18C-00A02401DCD4}
  29. Search Analogue.reg for this ‘new’ GUID (the second one – A799A800… in my example)
  30. Copy all lines of data associated with the second GUID Path i.e. if the key path still contains A799A800… copy it and its data
  31. Pate the data OVER the same data in Hybrid.reg so that you have full data sets for BOTH GUID’s present in the same reg file.
  32. Save Hybrid.reg and close it and Analogue.reg
  33. Import Hybrid.reg into the Windows Registry
  34. Open Media Centre
  35. Go through the tuner setup process for the DVB-T tuner again
  36. Close Media Centre
  37. In regedit navigate to (create the key if necessary):
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Media Center\Settings\Radio
  38. If it doesn’t already exist inside this key create a new REG_SZ (String) called:
    _radioHardwareExists
    that is “underscore”radioHardwareExists
  39. Set the value of _radioHardwareExists to:
    True
  40. Open Media Centre. You will now have access to the Radio Tuner and be able to watch DVB-T (though not at the same time of course)

If anything goes terribly wrong during this process and/or you want to start again. in Regedit delete the entire key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Media Center

Then simply import the Digital.reg file that you backed up at the beginning of the process. If you backup the .reg settings files, should you ever come to format your system again you will be able to simply re-import them into Media Centre (you may need to adjust the GUID values).