Die Homepage wurde heute aktualisiert.

VMware vCenter Protect

Ab sofort kann die neue Version 8.0 Build 3787 geladen werden.
Diese Version benötigt keine neue Lizenznummer.

VMware vCenter Protect – Programme & Dokumentation

Demokey anfordern unter => http://www.shavlik.com/pDownloadForm4.aspx?resellerid=14EEEDE5-975D-47C7-8E05-5DEE1A176CB3&productid=74
Nach der Registrierung wird von VMware eine eMail mit einem Demokey gültig für 50 Rechner und 45 Tage ab Erhalten (!) des Demokeys verschickt.

Bitte beachten:

  • Erstellen Sie vor der Installation der Version 7.x ein Backup Ihrer SQL Datenbank
  • Erstellen Sie einen Backup- und Wartungsplan für Ihre SQL Datenbank.
    Beachten Sie hierzu die Hinweise des Herstellers unter Shavlik Database Maintenance
  • Ein Update auf die aktuelle Version 7.x wird vom Hersteller VMWARE nur von Version 7.x oder 6.x unterstützt.
  • Um eine vorhandene Version 5.x zu aktualisieren, müssen Sie eine Neuinstallation durchführen.
  • SQL 2000 wird nicht mehr unterstützt.

Änderungen:

Bug Fixes

  • Enhanced ITScripts engine to provide more user-friendly error messages.
  • Resolved an issue where scheduled value in Tracker and deployment status was showing date and time the job was scheduled on, and not the date and time the job would execute.
  • Resolved an issue in the STAgent.exe where a race condition could cause a crash.
  • Resolved an issue in the IAVA reporter where Patch Status Detail would crash if viewed by specific product and service pack combinations.
  • Resolved an issue in the Help file where a link for ITScripts would redirect to custom patch instead.
  • Resolved an issue where refreshing a license after viewing a power status scan result could result in a crash.
  • Resolved an issue where Browse Active Directory feature in Machine Groups did not list child OUs.
  • Updated Help file to correct steps for creating a manual install script for agent installation.
  • Resolved an issue where upgrade from 7.x to 8.x results in agents running threat protection needing to be re-installed.
  • Resolved an issue where STAgentUpdater could crash when creating SSL registration.
  • Resolved an issue where the service could crash when retrieving system credentials due to size of credential store.
  • Resolved a regression where the patch pane in Machine View defaulted to expanded instead of collapsed.
  • Resolved an issue in Custom Patch where a string registry value always returned missing.
  • Resolved an issue where database upgrade fails with uniqueness constraint violation. This only affects 7.x upgrade to 8.0.
  • Resolved an issue where agents would be unable to deploy a custom patch

Willy Nachtigall


Support Engineer at ProSoft Software Vertriebs GmbH

 Leave a Reply

(erforderlich)

(erforderlich)

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong> <pre lang="" line="" escaped="" highlight="">

   
© 2011 ProSoft Knowledgebase Suffusion theme by Sayontan Sinha
Sharing Buttons by Linksku