Software Update to allow all users to connect USB devices for which signed drivers are available [HFXCC3105]
Published Date : 15 Feb 2005��
Last Updated : 13 Feb 2020��
Content Ref: DWN356182��
Operating System
Community Connect 3 SR3, Community Connect 3 SR4, RM Smart-Tools 3 SR3, RM Smart-Tools 3 SR4
Part No
(none)
Summary
Community Connect� 3 Software Update to allow users to connect USB devices for which signed drivers are available, without being prompted for administrator rights.
Description
**Please note this only applies to Community Connect 3 and RM Smart-Tools 3 networks**
Before installing any Software Update, please refer to TEC90813 and DWN59018 in the 'Other Useful Articles' section below. These articles detail RM's recommendations regarding Software Update installation and support.
Any references to Community Connect 3 in this document apply equally to RM Smart-Tools 3.
Platforms
Community Connect 3 with Service Release 3 (SR3) or above.
Symptoms
When connecting USB devices such as pen drives or USB mice to Community Connect 3 workstations, users who are not administrators are prevented from installing the device. When users plug in the USB device the 'Found New Hardware' wizard appears but the install fails due to user restrictions. The operating system reports that administrator-level rights are required because the device uses unsigned drivers. Even when the device requires standard, signed Microsoft� drivers, a standard user may be presented with the Installing New Hardware wizard which cannot be completed without administrator rights. There is information about what are signed drivers in the More Information section below.
The user is unable to use the USB device until an administrator-level user (eg systemadmin) has logged on to the workstation to install the device.
Investigation may reveal that the workstation has no signed driver files, ie files that were previously signed are now unsigned.
Cause
The problem behaviour can be caused by file corruption in the catroot2 Windows� system folder. Please see the More Information section below for further details.
Requirements
You should consider installing HFXCC3105 if you have the problem described above.
The Software Update can only be installed on to networks with Community Connect 3 SR3 or above.
Important: During the installation of HFXCC3105, the Update Package List procedure and allocation of a workstation package must be done manually. Please ensure that you fully complete all steps in the 'How to install the Update' section of this article.
Download Instructions
Click the HFXCC3105.exe file link to download the update.
Choose to Save the file, browse to the temporary location you wish to save it to (eg D:\temp) and click Save.
When it has been downloaded, follow the installation instructions below to install the update.
Download
Filename
File Size
Download
HFXCC3105.exe
311 kb
Installation Instructions
How to install the Software Update
Note: If you previously started to install the update but cancelled the operation, follow the installation instructions in the 'Installing after cancelling a previous install' section below.
1.Download HFXCC3105.
2.Log on to your first Community Connect 3 domain controller as Administrator (not SystemAdmin) and copy the update to a temporary location (eg D:\temp).
3.Run the update by double-clicking the self-extracting executable file (HFXCC3105.exe).The update will extract files automatically and run the RM Installation Assistant to install the update.
4.When prompted, click Continue.
5.The installation will proceed automatically.When prompted that the RM Installation Assistant has finished, click Finish.
6.Repeat steps 2-5 for all your other Community Connect 3 domain controllers.
7.When all Community Connect 3 domain controllers have had the update applied, open the RM Management Console at a domain controller or a workstation.
8.In the RM Management Console, expand Workstations, right-click on Main Site and choose to Update Package List. Click Yes to confirm this action.
Note: If you have a multi-site network, run this update on every server at all sites and then update the package list once per site only.
9.In the RM Management Console, allocate the system package 'USB Fix' to affected workstations as required.
10.Restart your affected Community Connect 3 workstations at your convenience for the updated package to be applied.
Note: It is recommended that USB devices are removed from workstations when allocating the USB Fix package and re-connected once the package has been installed.
Installing after cancelling a previous installation
1.Browse to D:\RMNetwork\RMManage\RM Hotfixes\HFXCC3105_extracted and double-click the file RM Installation Assistant.exe. (If this folder or its contents does not exist, re-run the HFXCC3105.exe file downloaded from the RM Support Web site).
2.The RM Installation Assistant will initialise, click Continue to proceed with the installation.
3.The installation should proceed automatically; click Finish when prompted.
4.Follow the procedures in 'How to install the Software Update' from step 5 above.
Important - Interaction with RM Service Releases
HFXCC3105 can be installed on networks running CC3 SR3 or above.
This hotfix is included in a RM Service Release 6 for Community Connect 3.
HFXCC3105 is not included in CC3 SR4 or CC3 XPSP2. It will not need to be reapplied after installing CC3 SR4 or CC3 XPSP2.
Important: The hotfix may need to be reapplied if the cause of the issue re-occurs. Please refer to the More Information section below.
More Information
What will this Software Update change?
HFXCC3105 delivers a new workstation package, USB Fix, which may be allocated to affected Community Connect 3 workstations. The USB Fix package, when installed, makes the following changes:
1.Deletes the contents of c:\windows\system32\catroot2.
2.Re-registers the following system files: Softpub.dll; Wintrust.dll; Initpki.dll; Dssenh.dll; Rsaenh.dll; Gpkcsp.dll; Sccbase.dll; Slbcsp.dll; Mssip32.dll; Cryptdlg.dll.
More information on the issue addressed by this update
The problem behaviour can be caused by file corruption in the catroot2 Windows system folder. For example, TEC243705 details one cause of the issue being .cat files. The driver signing mechanism ceases to function correctly. Running Sigverif.exe at a problem workstation verifies that driver files are no longer signed correctly. Microsoft� knowledge base article KB813442 discusses driver signing issues in Microsoft� Windows� XP.
If the problem re-occurs after the update has been installed, the USB fix package should be reallocated to affected workstations using the RM Management console. If a reallocate fails to fix the issue, the package should be deallocated and then allocated, this forces an uninstall and then a fresh install.
More information on Signed Drivers
The Driver Signing feature is included in Microsoft� Windows� to help promote driver quality. This feature can notify a user whether or not a driver that the user wants to install has passed the Microsoft� certification process.
If this article has not helped provide a solution then it is also possible to
log a call...
Document Keywords:�hfx105, hotfix 105, universal serial bus, usb mouse, usb mice, pendrive, pen drive, register dll, regsvr, regsvr32, install new hardware, 356182