VMware vCenter Protect - Downloads
Aktuelle Versionen
Um VMware vCenter Protect optimal nutzen zu können, sollten Sie immer die aktuelle Version einsetzen. Bitte beachten Sie auch, dass ältere Versionen vom Hersteller VMware (ehemals SHAVLIK) nach dem Erreichen des EOF ( End of Life ) nicht mehr weiter supportet und mit aktualisierten XML Daten versorgt werden.
Beachten Sie hierzu unseren Beitrag Technische Unterstützung für Shavlik Produkte in der ProSoft KnowledgeBase
Wichtige HINWEISE:
- 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 Hinwesie 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.
DEMOLIZENZ:
Nachdem Sie VMware vCenter Protect geladen haben, müssen Sie für die kostenlose Trial Edition auf der Webseite des Herstellers VMWARE (ehemals SHAVLIK) noch einen Demokey anfordern.
Nach der Registrierung erhalten Sie von VMware eine eMail mit dem gültigen Key.
Der Demokey schaltet den gesamten Funktionsumfang frei und ist limitiert auf 50 Rechner und 45 Tage Laufzeit ab Erhalten des Demokeys!
Dokumentationen
Benutzerhandbücher im PDF Format, Onlinehilfen im CHM Format, Anleitungen, Schritt-für-Schritt Anweisungen, Releasenotes und sonstige Informationen ...
Ziparchiv aller verfügbaren Dokumentationen zum Produkt VMware vCenter Protect Essentials 8.0
VMWARE VCENTER PROTECT ESSENTIALS 8.0 - DOKUMENTATION
(11/23/11
-- 17.0 Megabyte)
VMware vCenter Protect Essentials 8.0 Releasenotes ( Fixes, neue Features, u.s.w. )
VMWARE VCENTER PROTECT ESSENTIALS 8.0 - RELEASENOTES
(11/23/11
-- 106 Kilobyte)
Systemvoraussetzungen
Für den Einsatz der Software sind folgende Mindestanforderungen notwendig:
Console
- A FAT file system cannot be used on a console machine
- If you install the console on a domain controller that uses LDAP certificate authentication, you may need to configure the server to avoid conflict issues between the SSL certificate and the NetChk Protect program certificate. There is no easy way to configure this on a Windows Server 2003-based domain controller and this combination is not recommended for use as a console.
Processor:
- Minimum: Pentium 4
- Recommended: 2.0 GHz CPU (multi-processor machine if more than 1000 seat license)
Memory:
- Minimum: 1 GB of RAM
- Recommended: 2 GB of RAM (4 GB if more than 1000 seat license)
Video:
- 1024 x 768 screen resolution or higher (1280 x 1024 recommended)
Disk Space:
- 100 MB for application
- 2 GB or more for patch repository
Operating System (one of the following):
Minimum:
- Windows XP Professional, SP3 or later (SP2 or later if using 64-bit version)
- Windows Vista, SP1 or later, Business, Enterprise, or Ultimate Edition
- Windows 7, Professional, Enterprise, or Ultimate Edition
Recommended:
- Windows Server 2003 Family, SP2 or later
- Windows Server 2008 Family, excluding Server Core
- Windows Server 2008 Family R2, excluding Server Core
Note: NetChk Protect supports 32- and 64-bit versions of the listed operating systems for both console and target systems.
Database:
- Use of a SQL Server database (SQL Server 2005, SQL Server 2005 Express Edition, SQL Server 2008, or SQL Server 2008 Express Edition) is required. If you do not have a SQL Server database, the option to install SQL Server 2008 Express Edition will be provided during the prerequisite software installation process.
- Note: SQL Server 2000 is not supported for use as a back-end database.
- Size: 1.5 GB
Prerequisite Software:(Installed automatically)
- MSXML 6.0 SP2 Hotfix (only required on console machines using Windows Vista SP1 or earlier)
- Windows Installer 4.5 or later (when installing SQL Express 2008)
- Use of Microsoft SQL Server 2005, SQL Server 2005 Express Edition, SQL Server 2008, or SQL Server 2008 Express Edition
- SQL Native Client or SQL 2008 Native Client
- Microsoft .NET Framework 3.5, SP1 or later
Configuration Requirements:
- When performing an asset scan of the console machine, Windows Management Instrumentation (WMI) service must be enabled and the protocol allowed to the machine. In Windows Firewall, on Windows XP/Windows 2003 machines the service is called Remote Administration, and on Windows Vista/Windows 7/Windows Server 2008 machines the service is called Windows Management Instrumentation (WMI)/Remote Administration.
Clients (agentless)
Browser:
- Internet Explorer 5.5 or later required to receive patch deployments
Operating Systems (any of the following):
Note: Version 7.5 is the last release that will support Windows NT 4.0.
- Windows 2000 Professional
- Windows 2000 Server
- Windows 2000 Advanced Server
- Windows 2000 Datacenter Server
- Windows 2000 Small Business Server
- Windows XP Professional
- Windows XP Tablet PC Edition
- Windows XP Embedded
- Windows Server 2003, Enterprise Edition
- Windows Server 2003, Standard Edition
- Windows Server 2003, Web Edition
- Windows Server 2003 for Small Business Server
- Windows Server 2003, Datacenter Edition
- Windows Vista, Home Basic Edition
- Windows Vista, Home Premium Edition
- Windows Vista, Business Edition
- Windows Vista, Enterprise Edition
- Windows Vista, Ultimate Edition
- Windows 7, Home Premium Edition
- Windows 7, Professional Edition
- Windows 7, Enterprise Edition
- Windows 7, Ultimate Edition
- Windows Server 2008, Standard
- Windows Server 2008, Enterprise
- Windows Server 2008, Datacenter
- Windows Server 2008, Standard - Core
- Windows Server 2008, Enterprise - Core
- Windows Server 2008, Datacenter - Core
- Windows Server 2008 R2, Standard
- Windows Server 2008 R2, Enterprise
- Windows Server 2008 R2, Datacenter
- Windows Server 2008 R2, Standard - Core
- Windows Server 2008 R2, Enterprise - Core
- Windows Server 2008 R2, Datacenter - Core
Virtual Machines (offline images created by any of the following):
- VMware ESX Server 3.0 or later
- VMware VirtualCenter 2.0 or later
- VMware Server
- VMware Workstation 4.0 or later
- VMware Player
Configuration Requirements:
- Remote Registry service must be running
- Simple File Sharing must be turned off
- Server service must be running
- NetBIOS (tcp139) or Direct Host (tcp445) ports must be accessible
- When deploying patches on Windows Vista or later operating systems, the Windows Update service Startup type must be set to either Manual or Automatic.
- When performing an asset scan, Windows Management Instrumentation (WMI) service must be enabled and the protocol allowed to the machine (TCP port 135). In Windows Firewall, on Windows XP/Windows 2003 machines the service is called Remote Administration, and on Windows Vista/Windows 7/Windows Server 2008 machines the service is called Windows Management Instrumentation (WMI)/Remote Administration.
Products Supported:
- See http://xml.shavlik.com/data/supportedproducts.htm for the current list
Disk Space:
- Free space equal to five times the size of the patches being deployed
Supported Languages (for patch download):
- Arabic, Chinese (Simplified), Chinese (Traditional), Czech, Danish, Dutch, English, Finnish, French, German, Greek, Hebrew, Hungarian, Italian, Japanese, Korean, Norwegian, Polish, Portuguese (Brazil), Portuguese (Portugal), Russian, Spanish, Swedish, Thai, Turkish
Clients Running NetPt Agent
Processor:
- 500 MHz or faster CPU
Memory:
- Minimum: 256 MB RAM
- Recommended: 512 MB RAM or higher
Disk Space:
Note: FAT file systems are not supported on agent machines.
- 30 MB for NetChk Agent client
- 500 MB or more for patch repository
Operating Systems (any of the following):
- Windows 2000 SP4 or later (with Windows Installer 3.1 or the latest version supported by Windows 2000)
- Windows XP SP3 or later
- Windows Vista Family
- Windows 7 Family
- Windows Server 2003 Family
- Windows Server 2008 Family
- Windows Server 2008 Family R2
Prerequisite Software:
- MSXML 3.0 or later
Port Requirements
These are the default port requirements. The port numbers are configurable.
| Inbound Ports (Basic NAT Firewall) | |||||||
| TCP 80 | TCP 135 | TCP 139 OR TCP 445 | TCP 3121 | TCP 4155 | TCP 5120 | TCP 443 | |
| Client System | X (For Asset Scans) | X | X (For listening agents) | X | |||
| Console System | X | ||||||
| Distribution Server | X | X | X | ||||
| Outbound Ports (Highly Restricted Network Environment) | |||||
| TCP 80 | TCP 139 OR TCP 445 | TCP 3121 | TCP 5120 | UDP 9 | |
| Client System | X (For Agents) | X | X (For Agents) | ||
| Console System | X | X | X | X (For WoL & error reporting) | |
| Distribution Server | |||||
