There were one or more problems downloading components: VMware Tools for Windows 95, 98, Me, and NT: Could not find component on update server. Contact VMware Support or your system administrator. VMware Tools for Windows 2000 or later: Could not find component on update server. Contact VMware Support or your system administrator. Could not find component on update server. Contact VMware Support or your system administrator. Running Windows version 7.0 sp1 and Vmware player 7.1.1 build-2771112. Usually, users may come across this type of problems when the Windows Update agent related services stop working, there’s an issue with the update cache, or some components are corrupted. In these situations, you can reset Windows Update on Windows 10 to fix most problems. The update history shows that one update failed for March 17, a printer driver update, but the history shows 13 failed updates for Feb 17. Not sure what else to try. Windows-server-2012 windows-server-2012-r2 wsus windows-update.

  1. Vmware Workstation Could Not Find Component On Update Server
  2. Could Not Find Component On Update Server

Symptom: Inside of Event Viewer, you see the following Error entry.

On 06/27/14 07:29:39, component SMS_SITE_COMPONENT_MANAGER on computer sccm.mydomain.local reported: Configuration Manager cannot update the already existing object “cn=SMS-MP-LAX-sccm.mydomain.LOCAL” in Active Directory (mydomain.local).

Possible cause: The site server’s machine account may not have full control rights for the “System Management” container in Active Directory
Solution: Give the site server’s machine account full control rights to the “System Management” container, and all child objects in Active Directory.

Could not find component on update server vmware tools

Possible cause: The Active Directory object “cn=SMS-MP-LAX-sccm.mydomain.LOCAL” has been moved to a location outside of the “System Management” container, or has been lost.
Solution: Delete the object from its current location, and let the site create a new object.

Possible cause: The Active Directory schema has not been extended with the correct ConfigMgr Active Directory classes and attributes.
Solution: Turn off Active Directory publishing for each site in the forest, until the schema can be extended. The schema can be extended with the tool “extadsch.exe” from the installation media.

Vmware Workstation Could Not Find Component On Update Server

Solution: Complete the steps below to ensure that the SCCM computer account has the ability to write to Active Directory.

Could Not Find Component On Update Server

  1. Add Permission to the System Management Container
    1. From the following technet article: http://technet.microsoft.com/en-us/library/bb633169.aspx
      After you have created the System Management container in Active Directory Domain Services, you must grant the site server’s computer account the permissions that are required to publish site information to the container.
      1. On your domain controller navigate to Server Manager -> Tools -> Active Directory Users and Computers
      2. Click View and select Advanced Features
      3. Expand your site, System, System Management and select Properties
      4. On the System Management Properties dialog box select the Security Tab
      5. Click Add.. on the Security Tab
      6. Click the Object Types… button, check Computers, and click OK
      7. Type in the computer’s name and click OK
      8. Check Full Control on the Security Permissions for your SCCM machine
      9. Click the Advanced button, select the computer account, and click Edit
      10. Select This object and all descendant objects in the Applies to section and click OK
      11. Restart the SMS_SITE_COMPONENT_MANAGER and service