VMware View Manager 4.0.1 Release Notes
View Manager Version 4.0.1 18 February 2010 Build: 233023 (View Manager), 210930 (View Composer)
Last Updated: 18 February 2010
These release notes cover the following topics:
•What's New in View Manager 4.0.1
•Before You Begin
•Known Issues
•Resolved Issues
What's New in View Manager 4.0.1
VMware View 4.0.1 is a maintenance release that resolves some known issues in the previous releases. For details, see the Resolved Issues section.
This release includes the following new features.
Localization of VMware View
The View Client and online help for View Client are now available in Japanese, French, German, and simplified Chinese. The View Manager Administration Guide, View Manager Release Notes, Getting Started with VMware View document, View Upgrade Guide, and View Architecture Planning Guide are also available in these languages.
VirtualCenter 2.5 Update 6 and ESX 3.5 Update 5 Support
View Manager 4.0.1 includes support for VirtualCenter 2.5 Update 6 and ESX 3.5 Update 5.
Enhancements to the PCoIP Display Protocol
PCoIP now supports the following features:
•Virtual Printing, which allows end users to use local or network printers from a View desktop without requiring that additional print drivers be installed in the View desktop.
•Single sign-on support for third party providers such as Sentillion and Imprivata.
•View Client supports international keyboards when using PCoIP.
For PCoIP-related bug fixes, see the View Client Resolved Issues section.
more details please refer to...
http://www.vmware.com/support/view40/doc/releasenotes_viewmanager401.html
2010年2月23日 星期二
2010年2月22日 星期一
VMware View 4.0 Client Support PCoIP in Linux OS
VMware View Client 4.0 Support PCoIP in Linux OS
目前VMware官方尚未公佈VMware View 4.0 View Client在Linux有支援PCoIP,這是本人提供的"非正式"資訊給各位參考!相信很快的就可以看到官方支援的資訊了!^^
目前VMware官方尚未公佈VMware View 4.0 View Client在Linux有支援PCoIP,這是本人提供的"非正式"資訊給各位參考!相信很快的就可以看到官方支援的資訊了!^^
2010年2月19日 星期五
VMware Partner Exchange 2010(Las Vegas) 課程
VMware Partner Exchange 2010(Las Vegas)課程
我把參與活動的課程相關內容都發表在我的Facebook上，當然您必須有Facebook帳號並加入我.
我把參與活動的課程相關內容都發表在我的Facebook上，當然您必須有Facebook帳號並加入我.
2010年2月18日 星期四
VMware "VMware Partner Exchange 2010" 邀請函
非常榮幸也非常興奮有這樣的機會受邀參加"VMware Partner Exchange 2010",據說還是全台灣唯一的一個,當然非常感謝公司支持給我這樣的機會!後續會提供更多活動相關的資訊給台灣的各位VMware同好!
vSphere Client從vSphere 4.0版就會因為windows語言區域問題造成顯示或登出錯誤
vSphere Client從vSphere 4.0版就會因為windows語言區域問題造成顯示或登出錯誤，VMware新的Update 1特別在官網上提供了解決的方式,提供給各位參考。
PS:我只能說沒有微軟哪有更多讓我們成長的機會!^^
vSphere Client Locale Forcing Mode
With vSphere 4.0 Update 1, you can configure the vSphere Client to provide the interface text in English even when the machine on which it is running is non-English. This configuration can be done for the duration of a single session by supplying a command-line switch. This configuration applies to the interface text and will not affect other locale-related settings such as date/time or numeric formatting.
The following vSphere Client command will cause the individual session to appear in English:
vpxClient -locale en_US
修改方式:請直接修改vSphere Client捷徑,請參考下面圖例。
圖例:
PS:我只能說沒有微軟哪有更多讓我們成長的機會!^^
vSphere Client Locale Forcing Mode
With vSphere 4.0 Update 1, you can configure the vSphere Client to provide the interface text in English even when the machine on which it is running is non-English. This configuration can be done for the duration of a single session by supplying a command-line switch. This configuration applies to the interface text and will not affect other locale-related settings such as date/time or numeric formatting.
The following vSphere Client command will cause the individual session to appear in English:
vpxClient -locale en_US
修改方式:請直接修改vSphere Client捷徑,請參考下面圖例。
圖例:
如何更改Virtual Machine的MAC Address
如何更改Virtual Machine的MAC Address:
此畫面為範例VM MAC Address為00:50:56:a0:35:e6 將修改為00:50:56:ac:52:3f。
#請注意!目前VMware vSphere已無法由GUI介面修改Virtual Machine的MAC，必須手動修改設定檔(*.vmx)。
此畫面為範例VM MAC Address為00:50:56:a0:35:e6 將修改為00:50:56:ac:52:3f。
#請注意!目前VMware vSphere已無法由GUI介面修改Virtual Machine的MAC，必須手動修改設定檔(*.vmx)。
請經由Datastore Browser找到該Virtual Machine目錄，將設定擋下載到自己的電腦存檔。
再經由文件編輯軟體開啟，直接修改存檔，注意MAC Address 00:50:56:XX:XX:XX 前三組預設是不能修改的是VMware預設的!
再經由Datastore Browser將設定擋上傳並複寫到該Virtual Machine。
請將該Virtual Machine點選案右鍵執行 Remove from Inventory，並重新加入”add to inventory”讓設定重新載入。
再確認一次，設定已經完成修改!
What's New in vSphere 4.1
What's New in vSphere 4.1
With this release, the VMware virtual datacenter operating system continues to transform x86 IT infrastructure into the most efficient, shared, on-demand utility, with built-in availability, scalability, and security services for all applications and simple, proactive automated management. The new and enhanced features in vSphere 4.1 are listed below.
•Installation and Deployment
•Storage
•Network
•Availability
•Management
•Platform Enhancements
•Partner Ecosystem
Installation and Deployment
•Automated Deployment of ESXi Images using PXE Boot — With VMware Auto Deploy, you can rapidly deploy and configure large numbers of ESXi hosts using the PXE boot infrastructure. The Auto Deploy virtual appliance provides all the components necessary to automate deployment of ESXi to servers configured to PXE boot. See the Administration Automation Documentation page.
•Scripted Install for ESXi — Scripted installation of ESXi to local and remote disks allows rapid deployment of ESXi to many machines. You can start the scripted installation with a CD-ROM drive or over the network using PXE booting. You cannot use scripted installation to install ESXi to a USB device.
Storage
•Storage I/O Control — This feature provides quality-of-service capabilities for storage I/O, in the form of I/O shares and limits that are enforced across all virtual machines accessing each datastore, regardless of which host they are running on.
•Storage Performance Statistics — vSphere 4.1 offers enhanced visibility into storage throughput and latency of hosts and virtual machines, and aids in troubleshooting storage performance issues. NFS statistics are now available in vCenter Server performance charts, as well as esxtop. New statistics for virtual machine for VMDK and datastore provide virtual machine insight. All statistics are available through the vSphere SDK.
Network
•Network I/O Traffic Management — Traffic-management controls allow flexible partitioning of physical NIC bandwidth between different traffic types, including virtual machine, vMotion, FT, and IP storage traffic.
•IPv6 Enhancements — IPv6 in ESX supports Internet Protocol Security (IPsec) and Internet Key Exchange (IKEv2).
Availability
•VMware HA Healthcheck Status — HA provides an ongoing healthcheck facility to ensure that the required cluster configuration is met at all times. Deviations from the required configuration result in an event or alarm on the cluster within the vCenter Server inventory.
•VMware HA Operational Status — The HA dashboard in the vSphere Client provides a new detailed window called Cluster Operational Status, which displays more information about the current HA operational status, including the specific status and errors for each host in the HA cluster.
•Fault Tolerance (FT) Enhancements — FT virtual machines are now fully interoperable with DRS when EVC is enabled in the cluster, allowing DRS to place FT Primary VMs and load balance FT Primary and Secondary VMs. An FT-specific versioning-control mechanism ensures that hosts are fully compatible with running FT Primary and Secondary VMs, which eliminates the need to rely on ESX build number consistency. vSphere 4.1 differentiates between events that are logged for a Primary VM from those that are logged for its Secondary VM, and reports why a host might not support FT. In addition, you can disable VMware HA when FT virtual machines are deployed in a cluster.
•Concurrent VMware Data Recovery Sessions — vSphere 4.1 provides the ability to concurrently manage multiple VMware Data Recovery appliances.
Management
•Access Virtual Machine Serial Ports Over the Network— You can redirect virtual machine serial ports over a standard network link in vSphere 4.1. This enables solutions such as third-party virtual serial port concentrators for virtual machine serial console management or monitoring.
•vCenter Converter Hyper-V Import — vCenter Converter allows users to point to a Hyper-V machine. Converter displays the virtual machines running on the Hyper-V system, and users can select a powered-off virtual machine to import to a VMware destination.
•Enhancements to Host Profiles — Host Profiles provides flexibility by allowing you to roll out administrator password changes in vSphere 4.1. Enhancements also include improved Cisco Nexus 1000V support and PCI device ordering configuration.
•Unattended Authentication in vSphere Management Assistant (vMA) — vMA 4.1 offers improved authentication capability, including integration with Active Directory and command-line interface commands to configure the connection.
•Updated Deployment Environment in vSphere Management Assistant (vMA) — The updated deployment environment in vMA 4.1 is fully compatible with vMA 4.0. A significant change is the transition from RHEL to CentOS.
•vCenter Orchestrator Workflows — vCenter Orchestrator offers new workflows to automate vCenter Server management tasks, including managing snapshots, locating orphaned VMDK files, converting multiple disks from thick to thin provisioning, and bulk operations such as detaching removable media from all virtual machines in vCenter Server.
•Improved Support for Handling Recalled Patches in vCenter Update Manager — Update Manager 4.1 immediately sends critical notifications about recalled ESX and related patches. In addition, Update Manager prevents you from installing a recalled patch that you might have already downloaded. This feature also helps you identify hosts where recalled patches might already be installed.
Platform Enhancements
•DRS Virtual Machine Host Affinity Rules — DRS provides the ability to set constraints that restrict placement of a virtual machine to a subset of hosts in a cluster. This feature is useful for enforcing host-based ISV licensing models, as well as keeping sets of virtual machines on different racks or blade systems for availability reasons.
•Memory Compression — Compressed memory is a new level of the memory hierarchy, between RAM and disk. Slower than memory, but much faster than disk, this feature improves the performance of virtual machines when memory is under contention, because less virtual memory is swapped to disk as a result.
•vMotion Enhancements — In vSphere 4.1, vMotion enhancements significantly reduce the overall time for host evacuations, with support for more simultaneous virtual machine migrations and faster individual virtual machine migrations. The result is a performance improvement of up to 8x for an individual virtual machine migration, and support for four to eight simultaneous vMotion migrations per host, depending on the vMotion network adapter (1GbE or 10GbE respectively).
•8GB Fibre Channel Support — vSphere 4.1 supports 8GB Fibre Channel storage arrays. You can deploy ESX and ESXi with 8GB end-to-end Fibre Channel SANs.
•ESXi Active Directory Integration — Integration with Microsoft Active Directory allows seamless user authentication on ESXi. You can maintain users and groups in Active Directory for centralized user management and you can assign privileges to users or groups on ESXi hosts. Active Directory integration on ESX is also supported using the same interface. In vSphere 4.1, integration with Active Directory allows you to roll out permission rules to hosts using Host Profiles.
•Configuring USB Device Passthrough from an ESX/ESXi Host to a Virtual Machine — Virtual machines can be configured to use USB devices that are connected to the ESX host on which the virtual machine is running. However, you cannot use vMotion to migrate a virtual machine that has a connected USB device. The device must be disconnected from the virtual machine before it can be migrated. You can connect up to 20 USB devices to a virtual machine.
•Improvements in Enhanced vMotion Compatibility — vSphere 4.1 includes an AMD Opteron Generation 3 without 3DNow!™ EVC mode that prepares clusters for vMotion compatibility with future AMD processors. EVC also provides numerous usability improvements, including the display of EVC modes for virtual machines, more timely error detection, better error messages, and reduced need to restart virtual machines.
Partner Ecosystem
•Enablement of Intel Xeon Processor 7500 Series, Intel Xeon Processor 5600 Series, and Intel Xeon Processor 3600 Series — vSphere 4.1 supports the Intel Xeon Processor 7500 Series, Intel Xeon Processor 5600 Series, and Intel Xeon Processor 3600 Series. Support includes Enhanced vMotion Compatibility (EVC) capabilities. For more information on previous processor families supported by Enhanced vMotion, see Enhanced vMotion Compatibility (EVC) processor support (KB 1003212).
•Enablement of AMD Opteron Processor 4000 Series and AMD Opteron Processor 6000 Series — vSphere 4.1 supports the AMD Opteron Processor 4000 Series and AMD Opteron Processor 6000 Series. Support includes Enhanced vMotion Compatibility (EVC) capabilities. For more information on previous processor families supported by Enhanced vMotion, see Enhanced vMotion Compatibility (EVC) processor support (KB 1003212).
•vCenter Update Manager Support for Provisioning, Patching, and Upgrading EMC's ESX PowerPath Module — vCenter Update Manager can provision, patch, and upgrade third-party modules that you can install on ESX, such as EMC's PowerPath multipathing software. Using the capability of Update Manager to set policies using the Baseline construct and the comprehensive Compliance Dashboard, you can simplify provisioning, patching, and upgrade of the PowerPath module at scale.
•User-configurable Number of Virtual CPUs per Virtual Socket — You can configure virtual machines to have multiple virtual CPUs reside in a single virtual socket, with each virtual CPU appearing to the guest operating system as a single core. Previously, virtual machines were restricted to having only one virtual CPU per virtual socket.
With this release, the VMware virtual datacenter operating system continues to transform x86 IT infrastructure into the most efficient, shared, on-demand utility, with built-in availability, scalability, and security services for all applications and simple, proactive automated management. The new and enhanced features in vSphere 4.1 are listed below.
•Installation and Deployment
•Storage
•Network
•Availability
•Management
•Platform Enhancements
•Partner Ecosystem
Installation and Deployment
•Automated Deployment of ESXi Images using PXE Boot — With VMware Auto Deploy, you can rapidly deploy and configure large numbers of ESXi hosts using the PXE boot infrastructure. The Auto Deploy virtual appliance provides all the components necessary to automate deployment of ESXi to servers configured to PXE boot. See the Administration Automation Documentation page.
•Scripted Install for ESXi — Scripted installation of ESXi to local and remote disks allows rapid deployment of ESXi to many machines. You can start the scripted installation with a CD-ROM drive or over the network using PXE booting. You cannot use scripted installation to install ESXi to a USB device.
Storage
•Storage I/O Control — This feature provides quality-of-service capabilities for storage I/O, in the form of I/O shares and limits that are enforced across all virtual machines accessing each datastore, regardless of which host they are running on.
•Storage Performance Statistics — vSphere 4.1 offers enhanced visibility into storage throughput and latency of hosts and virtual machines, and aids in troubleshooting storage performance issues. NFS statistics are now available in vCenter Server performance charts, as well as esxtop. New statistics for virtual machine for VMDK and datastore provide virtual machine insight. All statistics are available through the vSphere SDK.
Network
•Network I/O Traffic Management — Traffic-management controls allow flexible partitioning of physical NIC bandwidth between different traffic types, including virtual machine, vMotion, FT, and IP storage traffic.
•IPv6 Enhancements — IPv6 in ESX supports Internet Protocol Security (IPsec) and Internet Key Exchange (IKEv2).
Availability
•VMware HA Healthcheck Status — HA provides an ongoing healthcheck facility to ensure that the required cluster configuration is met at all times. Deviations from the required configuration result in an event or alarm on the cluster within the vCenter Server inventory.
•VMware HA Operational Status — The HA dashboard in the vSphere Client provides a new detailed window called Cluster Operational Status, which displays more information about the current HA operational status, including the specific status and errors for each host in the HA cluster.
•Fault Tolerance (FT) Enhancements — FT virtual machines are now fully interoperable with DRS when EVC is enabled in the cluster, allowing DRS to place FT Primary VMs and load balance FT Primary and Secondary VMs. An FT-specific versioning-control mechanism ensures that hosts are fully compatible with running FT Primary and Secondary VMs, which eliminates the need to rely on ESX build number consistency. vSphere 4.1 differentiates between events that are logged for a Primary VM from those that are logged for its Secondary VM, and reports why a host might not support FT. In addition, you can disable VMware HA when FT virtual machines are deployed in a cluster.
•Concurrent VMware Data Recovery Sessions — vSphere 4.1 provides the ability to concurrently manage multiple VMware Data Recovery appliances.
Management
•Access Virtual Machine Serial Ports Over the Network— You can redirect virtual machine serial ports over a standard network link in vSphere 4.1. This enables solutions such as third-party virtual serial port concentrators for virtual machine serial console management or monitoring.
•vCenter Converter Hyper-V Import — vCenter Converter allows users to point to a Hyper-V machine. Converter displays the virtual machines running on the Hyper-V system, and users can select a powered-off virtual machine to import to a VMware destination.
•Enhancements to Host Profiles — Host Profiles provides flexibility by allowing you to roll out administrator password changes in vSphere 4.1. Enhancements also include improved Cisco Nexus 1000V support and PCI device ordering configuration.
•Unattended Authentication in vSphere Management Assistant (vMA) — vMA 4.1 offers improved authentication capability, including integration with Active Directory and command-line interface commands to configure the connection.
•Updated Deployment Environment in vSphere Management Assistant (vMA) — The updated deployment environment in vMA 4.1 is fully compatible with vMA 4.0. A significant change is the transition from RHEL to CentOS.
•vCenter Orchestrator Workflows — vCenter Orchestrator offers new workflows to automate vCenter Server management tasks, including managing snapshots, locating orphaned VMDK files, converting multiple disks from thick to thin provisioning, and bulk operations such as detaching removable media from all virtual machines in vCenter Server.
•Improved Support for Handling Recalled Patches in vCenter Update Manager — Update Manager 4.1 immediately sends critical notifications about recalled ESX and related patches. In addition, Update Manager prevents you from installing a recalled patch that you might have already downloaded. This feature also helps you identify hosts where recalled patches might already be installed.
Platform Enhancements
•DRS Virtual Machine Host Affinity Rules — DRS provides the ability to set constraints that restrict placement of a virtual machine to a subset of hosts in a cluster. This feature is useful for enforcing host-based ISV licensing models, as well as keeping sets of virtual machines on different racks or blade systems for availability reasons.
•Memory Compression — Compressed memory is a new level of the memory hierarchy, between RAM and disk. Slower than memory, but much faster than disk, this feature improves the performance of virtual machines when memory is under contention, because less virtual memory is swapped to disk as a result.
•vMotion Enhancements — In vSphere 4.1, vMotion enhancements significantly reduce the overall time for host evacuations, with support for more simultaneous virtual machine migrations and faster individual virtual machine migrations. The result is a performance improvement of up to 8x for an individual virtual machine migration, and support for four to eight simultaneous vMotion migrations per host, depending on the vMotion network adapter (1GbE or 10GbE respectively).
•8GB Fibre Channel Support — vSphere 4.1 supports 8GB Fibre Channel storage arrays. You can deploy ESX and ESXi with 8GB end-to-end Fibre Channel SANs.
•ESXi Active Directory Integration — Integration with Microsoft Active Directory allows seamless user authentication on ESXi. You can maintain users and groups in Active Directory for centralized user management and you can assign privileges to users or groups on ESXi hosts. Active Directory integration on ESX is also supported using the same interface. In vSphere 4.1, integration with Active Directory allows you to roll out permission rules to hosts using Host Profiles.
•Configuring USB Device Passthrough from an ESX/ESXi Host to a Virtual Machine — Virtual machines can be configured to use USB devices that are connected to the ESX host on which the virtual machine is running. However, you cannot use vMotion to migrate a virtual machine that has a connected USB device. The device must be disconnected from the virtual machine before it can be migrated. You can connect up to 20 USB devices to a virtual machine.
•Improvements in Enhanced vMotion Compatibility — vSphere 4.1 includes an AMD Opteron Generation 3 without 3DNow!™ EVC mode that prepares clusters for vMotion compatibility with future AMD processors. EVC also provides numerous usability improvements, including the display of EVC modes for virtual machines, more timely error detection, better error messages, and reduced need to restart virtual machines.
Partner Ecosystem
•Enablement of Intel Xeon Processor 7500 Series, Intel Xeon Processor 5600 Series, and Intel Xeon Processor 3600 Series — vSphere 4.1 supports the Intel Xeon Processor 7500 Series, Intel Xeon Processor 5600 Series, and Intel Xeon Processor 3600 Series. Support includes Enhanced vMotion Compatibility (EVC) capabilities. For more information on previous processor families supported by Enhanced vMotion, see Enhanced vMotion Compatibility (EVC) processor support (KB 1003212).
•Enablement of AMD Opteron Processor 4000 Series and AMD Opteron Processor 6000 Series — vSphere 4.1 supports the AMD Opteron Processor 4000 Series and AMD Opteron Processor 6000 Series. Support includes Enhanced vMotion Compatibility (EVC) capabilities. For more information on previous processor families supported by Enhanced vMotion, see Enhanced vMotion Compatibility (EVC) processor support (KB 1003212).
•vCenter Update Manager Support for Provisioning, Patching, and Upgrading EMC's ESX PowerPath Module — vCenter Update Manager can provision, patch, and upgrade third-party modules that you can install on ESX, such as EMC's PowerPath multipathing software. Using the capability of Update Manager to set policies using the Baseline construct and the comprehensive Compliance Dashboard, you can simplify provisioning, patching, and upgrade of the PowerPath module at scale.
•User-configurable Number of Virtual CPUs per Virtual Socket — You can configure virtual machines to have multiple virtual CPUs reside in a single virtual socket, with each virtual CPU appearing to the guest operating system as a single core. Previously, virtual machines were restricted to having only one virtual CPU per virtual socket.
訂閱：
文章 (Atom)
