Use the following to create a searchable list of all Programs currently installed. This is useful when trying to identify what Windows considers to be installed.

Note:This will create the Software_%Computername%.txt file in the directory that Command Prompt is currently listed in.

1. OpenCommand Prompt.
2. Typewmic product get /format:list > Software_%Computername%.txt
3. Gather the output .TXT file from the directory displayed in Command Prompt.
   

ISSUE / SYMPTOMS

Patch installation of MSWU-766 (KB2836502) may fail out with an exit code of 2145124329, or if you manually run the patch file it fails with the message, "The update is not applicable to your computer."

If MSWU-716 is uninstalled from a system or doesn't fully install but leaves behind the below listed registry key it can cause MSWU-766 to falsely show as missing.

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Microsoft-Windows-PlatformUpdate-Win7-SRV08R2-Package-TopLevel~31bf3856ad364e35~amd64~~7.1.7601.16492

SOLUTION

MSWU-716 should be installed prior to attempting installation of MSWU-766.

There are two possible solutions in this scenario:

1. Reinstall MSWU-716. Then you should be able to install MSWU-766.

2. Delete the above listed registry key. MSWU-766 would no longer be offered as a missing patch. This may cause MSWU-716 to be offered as a missing patch again, though.

Note: *Backup the registry key before deleting*

Most of the following information can also be found within Protect under Help > Contents > Quick Start Information > How to Manage Your Virtual Machines > Notes About Virtual Machine Templates.

• Only virtual machine templates that are hosted on a VMware server are supported by Shavlik Protect. The templates are added to a machine group using the Hosted Virtual Machines tab. Virtual machine templates that reside on individual workstations are not supported.
• A unique icon is used to identify virtual machine templates. You will see this icon when adding a template to a machine group and when viewing scan results in Scan View and in Machine View. The icon can be seen below:
  
  
• During a scan, a template will be accessed using the VMware server credentials. Any individual credentials supplied for the template are ignored.
• When you initiate a patch or an asset scan of a virtual machine template, Shavlik Protect will scan the template in its current state and will report the results the same way it does for virtual machines and physical machines.
• You should supply online (individual) credentials for any virtual machine template that will be included in a patch deployment process. During the patch deployment process the template is converted to a virtual machine and powered on -- Shavlik Protect will need the supplied credentials in order to access the online virtual machine.
• When deploying patches to a virtual machine template, the following VMware server permissions are required in order to manage snapshots and to perform the deployment: 

  • VirtualMachine.State.CreateSnapshot

  • VirtualMachine.State.RemoveSnapshot

  • VirtualMachine.Provisioning.MarkAsTemplate

  • VirtualMachine.Provisioning.MarkAsVM

• When you initiate a patch deployment to a virtual machine template, Shavlik Protect will do the following: 

1. Convert the virtual machine template to an offline virtual machine.

2. (Optional) Take a snapshot if the patch deployment template is configured to take a pre-deployment snapshot.

3. (Optional) Delete old snapshots if one of the snapshot thresholds defined on the patch deployment template is exceeded.

4. Push the patches to the offline virtual machine.

5. Reconfigure the following on the offline virtual machine:

   • Disable the network adaptor'sConnect at power onoption. This is done so that the machine is isolated from the network when the patch process is run.

   • If Sysprep is scheduled to run, disable it so it will not automatically configure the machine's operating system when the machine is first powered on.

6.   Power on the virtual machine. 

7. Install the patches.

8. Power down the virtual machine.

9. Reset the machine configuration to its original network connection and Sysprep settings.

10. (Optional) Take a snapshot if the patch deployment template is configured to take a post-deployment snapshot.

11. (Optional) Delete old snapshots if one of the snapshot thresholds defined on the patch deployment template is exceeded.

12. Convert the offline virtual machine back to a virtual machine template.

• The patch deployment template you use must not specify the use of a distribution server. The offline virtual machine will be disconnected from the network and unable to download the patches from the distribution server.
• The patch deployment template you use must not specify the use of a Office media path. The offline virtual machine will be disconnected from the network and unable to access the location of the original Office installation media.
• The patch deployment template you use should not specify a pre-deploy reboot (the program will be unable to initiate the reboot because the machine will be offline) and it should always perform a post-deploy reboot (this is a "best practice" when deploying patches). For deployments to virtual machine templates it is recommended you use the Virtual Machine Standard deployment template.
• During a patch deployment, a virtual machine template that may normally be available only to an administrator will become visible to other users. This is because during the patch deployment process the template is temporarily converted to a virtual machine and powered on.
• As with anything that involves components on a network, errors can occur if connections go bad, if servers are shut down, if a template is modified while being accessed by Shavlik Protect, etc. In general, the templates should not be touched at any time during the scanning or patch deployment process.

Purpose

This article provides steps to perform a manual uninstall and reinstallation of the Shavlik (ST) Remote Scheduler service on a single machine.

Resolution

1. On the target machine:
   1. Open a command prompt as an administrator. 
   2. Run this command:
      
      CD C:\Windows\ProPatches\scheduler
   3. Run this command:
      
      stschedex.exe /remove
      

2.  Open Windows Explorer and delete the C:\Windows\ProPatches folder and its contents.  

3.  Open Windows Registry Editor and verify that the following registry keys have been deleted:

• 8.x for 32 bit: HKEY_LOCAL_MACHINE\SOFTWARE\Shavlik\Scheduler
• 8.x for 64 bit: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Shavlik\Scheduler
• 9.x key for 32bit: HKEY_LOCAL_MACHINE\SOFTWARE\LANDesk\Shavlik Protect\Scheduler
• 9.x key for 64bit: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\LANDesk\Shavlik Protect\Scheduler

Further steps to ensure successfull reinstallation of the scheduler service:


1. On the Protect console:  
   
   • In VMware vCenter Protect 8.x: 
     • Go to Manage> Credentials. 
     • Add credentials that you want to use as default or edit existing credentials to ensure that the password is up-to-date. 
     • Ensure to set the proper credentials as the default credentials. 
     • Go to Tools> Options> Scheduling and ensure that the VMware Scheduler is selected.
   • In Shavlik Protect 9.x:
     • Go to Manage> Credentials. 
     • Add credentials that you want to use as default or edit existing credentials to ensure that the password is up-to-date. 
     • Ensure to set the proper credentials as the default credentials.
     • Go to Tools > Options > Scheduling and ensure the Shavlik Scheduler is selected.

Alternatively, to uninstall the Scheduler from a target machine on the Protect console:

1. Click Manage> Scheduled Tasks. 
2. Right-click the target machine name in the list on the left, and click Scheduler Service> Uninstall.

Installation of the scheduler service:

During next deployment to the target system, the scheduler is automatically reinstalled. If you prefer to force the install of the scheduler service prior to the next deployment you can do so in the Protect console by going to Manage > Scheduled Tasks, then right click on a target system name in the list on the left and choose Scheduler Service > Install.



If this issue exists on multiple systems:

If you are experiencing this problem on multiple systems and would like a way to resolve the issue for all machines affected, please refer to this document on how to set up a custom action to delete the scheduler service from target systems:

http://community.shavlik.com/docs/DOC-23009

Products

Shavlik Protect 9.x

vCenter Protect 8.x

Symptoms

Installing Patch for Visual Basic 6 (MS12-046/Q2688865)fails. This is often seen to include the returned exit code: -2147023728.

Cause

This appears to be a problem with the patch itself (rather than with our product). The issue has been presented to the vendor for correction, though no corrections have been made available to date.

Work Around

If a supported version of an Office product is installed (BOTH version and SP), MS12-046 should be indicated as missing for both the Office product and the operating system.
In this case, installing (e.g. deploying) the Office patch will succeed, and future scans will show the patch as installed for both the Office product and for the operating system.
If both patches are deployed, the operating system patch installation will fail, but the Office product patch installation will still succeed, and future scans will show the patch as installed for both the Office product and for the operating system (the affected DLL gets updated).

If an Office product is installed, but the patch is not indicated as missing for that Office product, then the Office product is likely an older, unsupported version. After upgrading the Office product (i.e. to a supported version or service pack level), you should be able to proceed as outlined above.

If no Office product is installed, a third-party product installed the affected DLL, and the third-party should supply the necessary patch.

Installing the operating system patch manually (e.g. as a logged in user) will usually succeed, but may not patch the affect program.  See Frequently Asked Questions "I have applied the required Microsoft security updates, but I still have an affected version of the Visual Basic for Applications runtime (VBE6.dll) on my system. How do I update this DLL?" in http://technet.microsoft.com/en-us/security/bulletin/ms12-046

If this does not correct your issue please consider checking with our community of users at
http://community.shavlik.com

If you would prefer you may also submit a ticket for Technical Support at
http://support.shavlik.com/

Patches applicable to Office 2007 & 2010 do not require the installation media. This is reflected by the abscense of an Office 2007 or 2010 option within the Deployment Template- Office tab.

This is a current list of distributable programs as of: 06/26/2013

Related Document:Distributing software with vCenter Protect Essentials using a patch group

To test if a connection is succcessful through a specific port, use the Telnet command.

Open Command Prompt and enter: telnet {MachineName} {Port}

For Example:

telnet {machinename} 5120

If the command prompt returns a blank screen the connection was successful on the indicated port.

If an error occurs verify the MachineName as well as port. If Machine name is correct, the port may be blocked.

If a message indicating telnet is not a recognized command, it may be necessary to enable it on the operating sytem.

http://social.technet.microsoft.com/wiki/contents/articles/910.how-to-enable-telnet-client-in-windows-7.aspx

A common Test for Protect would be:

Console to Target:

telnet {machinename} 5120

Target to Console:

telnet {machinename} 3121

Related:

Shavlik Protect Inbound and Outbound Port Requirements Explanations

http://community.shavlik.com/docs/DOC-22939

1. If you have not yet installed it, download and install SQL Server Management Studio.

• If using SQL 2005 you will need the 2005 Version here:
  • http://www.microsoft.com/en-us/download/details.aspx?id=8961
• If using SQL 2008 you’ll need the 2008 Version here:
  • http://www.microsoft.com/en-us/download/details.aspx?id=7593
• If using SQL 2012 you will need the 2012 Version here:
  • http://www.microsoft.com/en-us/download/details.aspx?id=29062

2. Detach the ShavlikScans Database as shown here:
      
3. Go to theC:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data(or similar) directory and copy the ShavlikScans.mdf and ShavlikScans.ldf files.
4. Move these files to the machine you’ve now installed Protect on.
5. Reattach the database on the new machine. To do this, Right Click on ‘Databases’, then choose Attach.
6. Run the Shavlik Database Setup Tool (this can be found at Start Menu > All Programs > Shavlik Technologies > Database setup tool), and choose to use the existing database you copied over.

Error loading patch definitions: the given key was not present in the dictionary.

This error occurs when Protect tries to import bad custom patch data. The error may occur when clicking Help > Refresh Files, or Patch View.

Solution:

Navigate to directory containing custom patch data.

Protect 9.x

Windows Vista and Newer: C:\ProgramData\LANDesk\Shavlik Protect\Console

Windows XP: C:\Documents and Settings\All Users\Application Data\LANDesk\Shavlik Protect\Console

Protect 8.x

Windows Vista and Newer: C:\ProgramData\Shavlik Technologies\NetChk

Windows XP: C:\Documents and Settings\All Users\Application Data\Shavlik Technologies\NetChk

Identify the custom patch file by its .XML extension, right click the file, choose rename, add .OLD at the end.

This will effectively remove the file from being processed by Protect, and allow verifying that the abscense of that file fixes the problem.

Purpose

This article provides information about the port requirements for Shavlik Protect.

Resolution

Impact/Risks

Some functions in Protect do not work correctly if these port requirements are not met. 

Additional Information

There is a port requirements table within Protect under Help> Contents> System Requirements. 

Products

Shavlik Protect 9.x

vCenter Protect 8.x

Symptoms

Left navigation panel in Protect is missing/hidden.

Cause

The left navigation panel in Protect can be collapsed on demand.

Resolution

Click the thin bar that borders the right side of the navigation panel to expand/unhide it.

SCENARIO

The following applies in a scenario where you may have one of the following setups:

-One Protect console connected to the internet, and other Protect consoles within an offline (disconnected) network.

-The internet connected console may be a rollup console with the other consoles sending results back to it.

This document is meant to provide an overview of requirements necessary for this configuration and the specific options that need to be set for this to work.

REQUIREMENTS

You will need to be able to set up a distribution server (share) that can be accessible in both the internet connected and disconnected networks, and it must meet any connection/port requirements. See the following linked documentation for more information on configuring a distribution server and any requirements:

*Note* For the configurations mentioned below it would be easiest to make your existing 'Patch download directory' as the share for the distribution server. This way the patch downloads from your internet facing console will automatically be downloaded to the share and patch files don't need to be synced.

Configuring a Distribution Server:

http://www.shavlik.com/onlinehelp/Protect90HTMLHelp/HFN.htm

Navigate to: Contents > Common Tasks > Configuring Program Operations > Using Distribution Servers > Configuring Distribution Servers

Port Requirements:

http://community.shavlik.com/docs/DOC-2161

Synchronizing Distribution Servers:

http://www.shavlik.com/onlinehelp/Protect90HTMLHelp/HFN.htm

Navigate to: Contents > Common Tasks > Configuring Program Operations > Using Distribution Servers > Synchronizing Servers

Document on Manually Synchronizing Distribution Servers:

http://community.shavlik.com/docs/DOC-23034

CONFIGURATION

This section assumes that you have already set up a distribution server meeting all requirements outlined in above documents. Below are the special requirements or information you may need to set up special configurations. The graphic below is intended to provide a basic illustration of possible configurations covered here.

Using Distribution Server to Host Datafiles & Patch Files for disconnected consoles

This configuration is meant to be used if you have at least one offline console system that can reach the distribution server share. This allows the offline

console(s) to update patch & threat defintions, binaries, and patch files easily without being connected to the internet.

*Note* The distribution server will need to be set up under Tools > Operations > Distribution Servers for all consoles.

Once you have your distribution server set up in all consoles, change the following settings for the Protect console systems within the offline network:

1. Go into Tools > Operations.

2. Click the 'Downloads' tab.

3. Change the 'Definition download source' to "Specific Distribution Server" and set it to use your distribution server.

4. Change the 'Patch and Service Pack download source' to use a "Specific Distribution Server" and point to your distribution server.

(Optional) You can set the 'Schedule automatic downloads' settings.

Important: This configuration requires that you are downloading the latest engines, definitions, and patch files on your internet connected console, and that you are synchronizing those downloads to the distribution server from the internet connected console. Definitions are downloaded by running Help > Refresh Files, and patch files are downloaded manually - either using View > Patches or by downloading from a scan result.

If the latest definitions and patches do not exist on the distribution sever share, your offline consoles will not display the latest patches and most likely fail to install many outdated patches.

If using data rollup

You can still use the data rollup function, however, you will need to either:

A) Open port 3121 and have a connection available to the master console system, or;

B) Set up port forwarding to port 3121 from one network to the other. We do not assist in setting this up so you will need to contact your network admin.

This will allow you to run reports on your master console to see the current status of all machines in your environment. Note that the master console for data rollup has no control over the other Protect consoles - it is only able to run reports based on results available from any other console that is set to run data rollup to the master console.

More information about setting up the data rollup function can be found here:

http://www.shavlik.com/onlinehelp/Protect90HTMLHelp/HFN.htm

Navigate to: Contents > Common Tasks > Configuring Program Operations > Data Rollup Operations

If there is a problem with threat scan detection we may need full tracing from the threat (antivirus) scan. Follow the steps below to obtain these additional logs.

1. Go to the client (agent) system where you are seeing the issue.

2. Open Services.msc, and stop the following services:

     For version 9.x:

          Shavlik Protect Agent

          Shavlik Protect Agent Dispatcher

          Shavlik Protect Threat Engine

     For version 8.x:

          VMware vCenter Protect Agent

          VMware vCenter Protect Agent Dispatcher

          VMware vCenter Protect Threat Engine

3. Open task manager, Processes, and end the STAgentUI.exe process. (Displayed as Agent UI in Windows 8/Server 2012 process manager.) All other agent processes should have ended when the services were stopped.         

4. Delete or move ALL the files that currently exist in the following directory:

     v.9.x on Windows 7,8,2008,Vista,2012: C:\ProgramData\LANDesk\Shavlik Protect\Logs

     v.9.x on Windows XP or 2003: C:\Documents and Settings\All Users\Application Data\LANDesk\Shavlik Protect\Logs

     v.8.x on Windows 7,8,2008,Vista,2012: C:\ProgramData\Shavlik Technologies\Logs

     v.8.x on Windows XP or 2003: C:\Documents and Settings\All Users\Application Data\Shavlik Technologies\Logs

5. Go into the following directory:

     v.9.x on 64bit: C:\Program Files (x86)\LANDesk\Shavlik Protect Agent

     v.9.x on 32bit: C:\Program Files\LANDesk\Shavlik Protect Agent

     v.8.x on 64bit: C:\Program Files (x86)\VMware\vCenter Protect Agent

     v.8.x on 32bit: C:\Program Files\VMware\vCenter Protect Agent

6. Locate the STThreat.exe.config, and open the file in a text editor.

7. Find the line that says;

     <threatServiceStartup preventAPIfIncompatiblesExist="false" debugFiles="false" tslog="false"/>

     Change it to the following:

     <threatServiceStartup preventAPIfIncompatiblesExist="true" debugFiles="true" tslog="true"/>

8. Save the file.

9. Start all the agent services back up (see step two).

10. Start the agent. You can do this by opening the agent UI from the start menu (paths below) or by going into the program files directory and running the STAgentUI.exe.

     v.9.x: Start > All Programs > Shavlik Protect > Shavlik Protect Agent

     v.8.x: Start > All Programs > VMware vCenter Protect > VMware vCenter Protect Agent

11. Run a full threat scan or recreate the issue.

12. Once the scan is complete or you have reproduced, zip and send ALL the files that now exist in the directory mentioned in step four.

     Note: Some of the additional logging created may be in XML format.

Here are some basic instructions on how to gather console, client (target) side logs, and agent logs for Protect 8.x and 9.x.  These should work for most console and agent type issues.

Protect 9.X console logging:

1. Please open the Protect GUI and then go to Tools > Options > Logging and change logging to “All” for both user interface and services.

a. If you are unable to set logging via the GUI see this doc: http://community.shavlik.com/docs/DOC-22938

2. Close the Protect GUI.

3. Stop the Shavlik Protect Console Service.

4. Delete all the logs from

a.  Windows 7, 8, 2008, 2012 & Vista: C:\ProgramData\LANDesk\Shavlik Protect\Logs

b.  Earlier OS’s:  C:\Documents and Settings\All Users\Application Data\LANDesk\Shavlik Protect\Logs

5.  Start the console service and open the Protect GUI.

6. Attempt to reproduce the issue. Please document steps to reproduce.

a. Collect the logs from the Logs folder mentioned earlier in step 4 (please zip if possible)

b. [Deployment issues only] On the target system please zip and send a copy of the entire C:\Windows\Propatches folder and its contents (you can leave out the Patches sub-folder).

7. Zip and send all the logs.

Protect 9.x agent logging:

1. Open the agent policy assigned to the machine we are gathering logs from.

2. Change the logging level to ‘All’ and Save and update Agents.  Choose to update agents if prompted.

3. Go to the target machine, close the agent GUI and stop the services:

     o The services start with Shavlik or ST.

4. Delete all the logs from:

     o Vista & Later: C:\ProgramData\LANDesk\Shavlik Protect\Logs

     o Earlier OS’s:  C:\Documents and Settings\All Users\Application Data\ LANDesk\Shavlik Protect\Logs

5. Start services.

6. Attempt to reproduce the issue. Please note the steps to reproduce.

7. Take applicable screenshots.

8. Zip and send all the logs and screenshots. (from the previous specified folders above)

Deployment Logs (All current supported versions)

(For agentless deployment)

It may be best to enable target side verbose logging before obtaining these logs. See the following document on how to do so:
http://community.shavlik.com/docs/DOC-23048

1. On the machine you are deploying to navigate to C:\Windows\ProPatches
2. Locate the CL5.log, dplyevts.log, and Safereboot.log and copy to a new folder on the desktop.
3. Navigate to C:\Windows\ProPatches\Scheduler.
4. Locate the Scheduler.log and add it to the folder created in step 2 so all logs are together.
5. Zip and send all the logs.

Protect 8.X console logging:

1. Please open the Protect GUI and then go to Tools > Options > Logging and change logging to “All” for both user interface and services.

     a. If you are unable to enable logging via the GUI see doc: http://community.shavlik.com/docs/DOC-22938

2. Close the Protect GUI.

3.  Stop all of the services:

     a.  For Protect 8.X, the service name starts with VMware vCenter Protect.

4. Delete all the logs from:

     a.  Vista & Later: C:\ProgramData\Shavlik Technologies\Logs

     b.  Earlier OS’s:    C:\Documents and Settings\All Users\Application Data\Shavlik Technologies\Logs

5. Start services and open the Protect GUI.

6. Attempt to reproduce the issue.  (please note how to reproduce)

7.  Take applicable screenshots.

8.  Zip and send all the logs and screenshots. (from the previous specified folders above)

Protect 8.X agent logging:

1. Open your agent policy assigned to the machine we are gather logs from.

2. Change the logging level to ‘All’ and Save and update Agents.

3. Go to the target machine, close the agent GUI and stop the services:

     o For Protect 8.X, the service name starts with VMware vCenter Protect.

4. Delete all the logs from:

     o Vista & Later: C:\ProgramData\Shavlik Technologies\Logs

     o Earlier OS’s:    C:\Documents and Settings\All Users\Application Data\Shavlik Technologies\Logs

5. Start services.

6. Attempt to reproduce the issue.  Please note the steps to reproduce.

7. Take applicable screenshots.

8. Zip and send all the logs and screenshots. (from the previous specified folders above

Additional Logging for Threat Protection/Antivirus Issues:

There is additional logging that can be obtained for Threat Protection/Antivirus related issues, such as detection of false positives. See the following document for the steps to obtain this addtional logging:

http://community.shavlik.com/docs/DOC-23066

Issue:

     When attempting to manually install an agent on a machine, you receive the error "File System must be NTFS."

Resolution:

     1. Ensure your Operating System is using an NTFS file system. This can confirmed by running msinfo32.exe from the run dialog box within          Components>Storage>Drives

     2. Within the agent machines registry, removed any folders and/or keys related to the Protect Agent from

         hkey_local_machine\software\classes\installer\products\

         Note: It is highly recommended that a registry backup be created prior to altering.

     3. Once the registry entries have been removed, you may run the agent installer again.

Symptoms

Synchronizing Distribution Server shows error in event history: Distribution Server with id 1 cannot be found.
Note:The ID value may vary.

Cause

The Synchronization action is no longer associated with a Distribution Server. This typically occurs when a Distribution Server has been added, sync jobs scheduled, and then the Distribution Server removed.

Resolution

Delete the scheduled sync jobs and readd them assigned to a Distribution Server.

ISSUE / SYMPTOMS

The Protect console crashes upon attempting to open the application.

The GUI will display one of the following errors:

"At least one of your credentials can no longer be decrypted. Please edit or delete every credential with a 'User Name' of 'None' in the Credential Manager."

"Protect can no longer decrypt credentials for this user. This typically happens when someone does a hard password reset on a Windows Account."

"The console service can no longer decrypt shared credentials. All users who have shared credentials with the console service must go to the Credential Manager and re-share them to restore functionality."

The ST.Protect.managed.log will show the following error:

System.Security.Cryptography.CryptographicException: Key not valid for use in specified state.

RESOLUTION

In some instances these issues can be resolved by deleting invalid and/or duplicate credentials from the Manage > Credentials section of Protect. However, if there is no way to access the Protect console and get into the credential manager, the workaround is to use the attached SQL query.

The attached SQL query will delete ALL credentials stored in the Protect database for ALL users.

Basic Steps to use the attached SQL query:

1. Ensure Protect is closed.

2. Open SQL Server Management Studio

3. Connect to the database that contains the Protect database you want to delete the credentials from.

4. Backup the database.

5. Open DeleteCredentials.sql into a query window.

6. Read disclaimer at the top.

7. Execute the script

8. *Note: 2 tables TMPUserCredential and TMPUserCredentialUsage are created and

  need to be renamed or deleted to run the script again

  - These tables can be deleted at some point in the future when

   you have entered new credentials and do not want the old ones back

9. Close SQL Server Management Studio, and try opening Protect now.

APPLIES TO

vCenter Protect 8.x

Shavlik Protect 9.x

Test Connection fails

The affected client report one of the following errors when a Test Connection is run:

• Registry reports: The network path was not found(53)
• Perfmon reports: Unable to connect to specified machine or machine is offline (-2147481648)

This can happen if the Remote Registry is not running, not responding, or if the IPC pipe is blocked by a policy or registry change.

To troubleshoot this issue:

1. Click Start > Control Panel > Administrative Tools > Services.
2. Find the "Remote Registry" service. Ensure the Startup Type is set to Automatic and the Status is set to Started. Start the service or change the startup type to match these values.
3. If the connection still fails, restart the "Remote Registry" service and try again.
4. Check the Active Directory or domains for a policy blocking access to the Remote Registry service.
5. Open the Registry Editor (regedit.exe ) and check the key:HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurePipeServers\winreg
   • If the key is missing, restore it by exporting a known good key from another server running the same operating system and service pack level. Restart the server.
6. If the connection still fails, reboot any Active Directory domain controllers.

Purpose

This article provides steps to obtain and publish Apple Application Support (AAS) when using SCUPdates content.  

Resolution

Obtaining the AAS MSI package

Products

Shavlik SCUPdates

VMware vCenter Protect Update Catalog