Microsoft Assessment and Planning Toolkit 5.5

The Microsoft Assessment and Planning Toolkit (MAP) is an agentless, automated, multi-product planning and assessment tool for quicker and easier desktop and server migrations. MAP provides detailed readiness assessment reports and executive proposals with extensive hardware and software information, and actionable recommendations to help organizations accelerate their IT infrastructure planning process, and gather more detail on assets that reside within their current environment. MAP also provides server utilization data for Hyper-V server virtualization planning; identifying server placements, and performing virtualization candidate assessments, including ROI analysis for server consolidation with Hyper-V.

MAP helps make the following IT planning projects faster and easier:

  • Migration to Windows 7, Windows Server 2008 R2, and Microsoft Office 2010
  • Migration to Windows 7 compatible versions of Internet Explorer
  • Migration to cloud-based services
  • Server virtualization with Hyper-V
  • SQL Server consolidation and migration to SQL Server 2008 R2
  • Assessment of current software usage and client access history for simplified software asset management
  • PC security assessment and migration to Microsoft Forefront Client Security

You can use MAP to inventory the following technologies:

  • Windows 7
  • Windows Vista
  • Windows XP Professional
  • Office 2010 and previous versions
  • Windows Server 2008 or Windows Server 2008 R2
  • Windows Server 2003 or Windows Server 2003 R2
  • Windows 2000 Professional or Windows 2000 Server
  • VMware ESX
  • VMware ESXi
  • VMware Server
  • Linux variants
  • LAMP application stack discovery
  • SQL Server 2008
  • SQL Server 2008 R2
  • MySQL
  • Oracle
  • Sybase

Download MAP 5.5 HERE

Clipboard Copy and Paste option is disabled in vSphere Client 4.1

I upgraded my home test server to ESXi 4.1 and I the Clipboard Functie is disabled by default and that is so annying

Solution:

Starting with vSphere 4.1, the Copy and Paste options are, by default, disabled for security reasons.

To be able to copy and paste between the guest operating system and the remote console, you must enable the Copy and Paste options using the vSphere Client. Alternatively, you can use RDP (Remote Desktop Protocol) to connect to the Windows virtual machines.

To enable this option for a specific virtual machine:

  1. Log into a vCenter Server system using the vSphere Client and power off the virtual machine.
  2. Select the virtual machine and click the Summary tab.
  3. Click Edit Settings.
  4. Navigate to Options > Advanced > General and click Configuration Parameters.
  5. Click Add Row and type the following values in the Name and Value columns:

    • isolation.tools.copy.disable – false
    • isolation.tools.paste.disable – false
      Note: These options override any settings made in the VMware Tools control panel of the guest operating system.

  6. Click OK to close the Configuration Parameters dialog, and click OK again to close the Virtual Machine Properties dialog.
  7. Power on the virtual machine.

Note: If you vMotion a virtual machine to a host where the isolation.tools.*="FALSE" is already set, the copy and paste options are automatically activated for that virtual machine.

To enable this option for all the virtual machines in the ESX/ESXi host:

  1. Log in to the ESX/ESXi host as a root user and open the /etc/vmware/config file using a text editor.
  2. Add these entries to the file:
    isolation.tools.copy.disable="FALSE"
    isolation.tools.paste.disable="FALSE"
  3. Save and close the file. The Copy and Paste options are only enabled when the virtual machines restart or resume the next time.

For more information, see the Limiting Exposure of Sensitive Data Copied to the Clipboard section of the  ESX Configuration Guide.

http://kb.vmware.com/kb/1026437

VMware vSphere 4.1 Released

WHAT’S NEW:

Installation and Deployment

Storage

  • Boot from SAN. vSphere 4.1 enables ESXi boot from SAN (BFN). iSCSI, FCoE, and Fibre Channel boot are supported. Refer to the Hardware Compatibility Guide for the latest list of NICs and Converged Adapters that are supported with iSCSI boot. See the iSCSI SAN Configuration Guide and the Fibre Channel SAN Configuration Guide.
  • Hardware Acceleration with vStorage APIs for Array Integration (VAAI). ESX can offload specific storage operations to compliant storage hardware. With storage hardware assistance, ESX performs these operations faster and consumes less CPU, memory, and storage fabric bandwidth. See the ESX Configuration Guide and the ESXi Configuration Guide.
  • 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 VMDK and datastore statistics are included. All statistics are available through the vSphere SDK. See the vSphere Datacenter Administration Guide.
  • 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 a datastore, regardless of which host they are running on. Using Storage I/O Control, vSphere administrators can ensure that the most important virtual machines get adequate I/O resources even in times of congestion. See the vSphere Resource Management Guide.
  • iSCSI Hardware Offloads. vSphere 4.1 enables 10Gb iSCSI hardware offloads (Broadcom 57711) and 1Gb iSCSI hardware offloads (Broadcom 5709). See the ESX Configuration Guide, the ESXi Configuration Guide, and the iSCSI SAN Configuration Guide.
  • NFS Performance Enhancements. Networking performance for NFS has been optimized to improve throughput and reduce CPU usage. See the ESX Configuration Guide and the ESXi Configuration Guide.

Network

Availability

  • Windows Failover Clustering with VMware HA. Clustered Virtual Machines that utilize Windows Failover Clustering/Microsoft Cluster Service are now fully supported in conjunction with VMware HA. See Setup for Failover Clustering and Microsoft Cluster Service.
  • VMware HA Scalability Improvements. VMware HA has the same limits for virtual machines per host, hosts per cluster, and virtual machines per cluster as vSphere. See Configuration Maximums for VMware vSphere 4.1 for details about the limitations for this release.
  • VMware HA Healthcheck and Operational Status. The VMware HA dashboard in the vSphere Client provides a new detailed window called Cluster Operational Status. This window displays more information about the current VMware HA operational status, including the specific status and errors for each host in the VMware HA cluster. See the vSphere Availability Guide.
  • VMware Fault Tolerance (FT) Enhancements. vSphere 4.1 introduces an FT-specific versioning-control mechanism that allows the Primary and Secondary VMs to run on FT-compatible hosts at different but compatible patch levels. vSphere 4.1 differentiates between events that are logged for a Primary VM and 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-enabled virtual machines are deployed in a cluster, allowing for cluster maintenance operations without turning off FT. See the vSphere Availability Guide.
  • DRS Interoperability for VMware HA and Fault Tolerance (FT). FT-enabled virtual machines can take advantage of DRS functionality for load balancing and initial placement. In addition, VMware HA and DRS are tightly integrated, which allows VMware HA to restart virtual machines in more situations. See the vSphere Availability Guide.
  • Enhanced Network Logging Performance. Fault Tolerance (FT) network logging performance allows improved throughput and reduced CPU usage. In addition, you can use vmxnet3 vNICs in FT-enabled virtual machines. See the vSphere Availability Guide.
  • Concurrent VMware Data Recovery Sessions. vSphere 4.1 provides the ability to concurrently manage multiple VMware Data Recovery appliances. See the VMware Data Recovery Administration Guide.
  • vStorage APIs for Data Protection (VADP) Enhancements. VADP now offers VSS quiescing support for Windows Server 2008 and Windows Server 2008 R2 servers. This enables application-consistent backup and restore operations for Windows Server 2008 and Windows Server 2008 R2 applications.

Management

  • vCLI Enhancements. vCLI adds options for SCSI, VAAI, network, and virtual machine control, including the ability to terminate an unresponsive virtual machine. In addition, vSphere 4.1 provides controls that allow you to log vCLI activity. See the vSphere Command-Line Interface Installation and Scripting Guide and the vSphere Command-Line Interface Reference.
  • Lockdown Mode Enhancements. VMware ESXi 4.1 lockdown mode allows the administrator to tightly restrict access to the ESXi Direct Console User Interface (DCUI) and Tech Support Mode (TSM). When lockdown mode is enabled, DCUI access is restricted to the root user, while access to Tech Support Mode is completely disabled for all users. With lockdown mode enabled, access to the host for management or monitoring using CIM is possible only through vCenter Server. Direct access to the host using the vSphere Client is not permitted. See the ESXi Configuration Guide.
  • 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. See the vSphere Virtual Machine Administration Guide.
  • 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. See the vCenter Converter Installation and Administration Guide.
  • Enhancements to Host Profiles. You can use Host Profiles to roll out administrator password changes in vSphere 4.1. Enhancements also include improved Cisco Nexus 1000V support and PCI device ordering configuration. See the ESX Configuration Guide and the ESXi Configuration Guide.
  • Unattended Authentication in vSphere Management Assistant (vMA). vMA 4.1 offers improved authentication capability, including integration with Active Directory and commands to configure the connection. See VMware vSphere Management Assistant.
  • 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. See VMware vSphere Management Assistant.
  • vCenter Orchestrator 64-bit Support. vCenter Orchestrator 4.1 provides a client and server for 64-bit installations, with an optional 32-bit client. The performance of the Orchestrator server on 64-bit installations is greatly enhanced, as compared to running the server on a 32-bit machine. See the vCenter Orchestrator Installation and Configuration Guide.
  • 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. See the vCenter Update Manager Installation and Administration Guide.
  • License Reporting Manager. The License Reporting Manager provides a centralized interface for all license keys for vSphere 4.1 products in a virtual IT infrastructure and their respective usage. You can view and generate reports on license keys and usage for different time periods with the License Reporting Manager. A historical record of the utilization per license key is maintained in the vCenter Server database. See the vSphere Datacenter Administration Guide.
  • Power Management Improvements. ESX 4.1 takes advantage of deep sleep states to further reduce power consumption during idle periods. The vSphere Client has a simple user interface that allows you to choose one of four host power management policies. In addition, you can view the history of host power consumption and power cap information on the vSphere Client Performance tab on newer platforms with integrated power meters. See the vSphere Datacenter Administration Guide.

Platform Enhancements

  • Performance and Scalability Improvements. vSphere 4.1 includes numerous enhancements that increase performance and scalability.
    • vCenter Server 4.1 can support three times more virtual machines and hosts per system, as well as more concurrent instances of the vSphere Client and a larger number of virtual machines per cluster than vCenter Server 4.0. The scalability limits of Linked Mode, vMotion, and vNetwork Distributed Switch have also increased.
    • New optimizations have been implemented for AMD-V and Intel VT-x architectures, while memory utilization efficiency has been improved still further using Memory Compression. Storage enhancements have led to significant performance improvements in NFS environments. VDI operations, virtual machine provisioning and power operations, and vMotion have enhanced performance as well.

    See Configuration Maximums for VMware vSphere 4.1.

  • Reduced Overhead Memory. vSphere 4.1 reduces the amount of overhead memory required, especially when running large virtual machines on systems with CPUs that provide hardware MMU support (AMD RVI or Intel EPT).
  • 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. See the vSphere Resource Management Guide.
  • Memory Compression. Compressed memory is a new level of the memory hierarchy, between RAM and disk. Slower than memory, but much faster than disk, compressed memory improves the performance of virtual machines when memory is under contention, because less virtual memory is swapped to disk. See the vSphere Resource Management Guide.
  • 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). See the vSphere Datacenter Administration Guide.
  • ESX/ESXi Active Directory Integration. Integration with Microsoft Active Directory allows seamless user authentication for ESX/ESXi. You can maintain users and groups in Active Directory for centralized user management and you can assign privileges to users or groups on ESX/ESXi hosts. In vSphere 4.1, integration with Active Directory allows you to roll out permission rules to hosts by using Host Profiles. See the ESX Configuration Guide and the ESXi Configuration Guide.
  • Configuring USB Device Passthrough from an ESX/ESXi Host to a Virtual Machine. You can configure a virtual machine to use USB devices that are connected to an ESX/ESXi host where the virtual machine is running. The connection is maintained even if you migrate the virtual machine using vMotion. See the vSphere Virtual Machine Administration Guide.
  • Improvements in Enhanced vMotion Compatibility. vSphere 4.1 includes an AMD Opteron Gen. 3 (no 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 the reduced need to restart virtual machines. See the vSphere Datacenter Administration Guide.

Partner Ecosystem

  • 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. See the vCenter Update Manager Installation and Administration Guide.
  • 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. See the vSphere Virtual Machine Administration Guide.
  • Expanded List of Supported Processors. The list of supported processors has been expanded for ESX 4.1. To determine which processors are compatible with this release, use the Hardware Compatibility Guide. Among the supported processors is the Intel Xeon 7500 Series processor, code-named Nehalem-EX (up to 8 sockets).

You can download VMware vSphere 4.1 HERE

Microsoft Assessment & Planning Toolkit

The Microsoft Assessment and Planning (MAP) Toolkit is an agentless toolkit that finds computers on a network and performs a detailed inventory of the computers using Windows Management Instrumentation (WMI) and the Remote Registry Service. The data and analysis provided by this toolkit can significantly simplify the planning process for migrating to Windows® 7, Windows Vista®, Microsoft Office 2007, Windows Server® 2008 R2, Windows Server 2008, Hyper-V, Microsoft Application Virtualization, Microsoft SQL Server 2008, and Forefront® Client Security and Network Access Protection. Assessments for Windows Server 2008 R2, Windows Server 2008, Windows 7, and Windows Vista include device driver availability as well as recommendations for hardware upgrades.

You can use MAP to inventory the following platforms:

  • Windows 7
  • Windows Vista
  • Windows XP® Professional
  • Windows Server 2008 or Windows Server 2008 R2
  • Windows Server 2003 or Windows Server 2003 R2
  • Windows 2000 Professional or Windows 2000 Server
  • VMware ESX
  • VMware ESXi
  • VMware Server

Reporting
– Identification of currently installed Windows client operating systems, their hardware, and recommendations for migration to Windows 7 and Windows Vista. The tool also reports if desktops have anti-virus and anti-malware programs installed and if the Windows Firewall is turned on.
– Identification of currently installed Windows Server operating systems, their hardware, and recommendations for migration to Windows Server 2008 R2 and Windows Server 2008.
– Identification of currently installed Microsoft Office software and recommendations for migration to Microsoft Office 2007.
– Detailed assessment and reporting of server utilization gathered using the Performance Metrics Wizard.
– Recommendations for server consolidation and virtual machine placement using Hyper-V
– Assessment of client machines, servers, and the technology environment for the implementation of Microsoft Application Virtualization (APP-V)
– Identification of machines where Microsoft SQL Server components are installed.
– Identification of virtual machines, their hosts, and details about each.
– Identification of Windows Server Roles

Hardware Requirements:
– Windows 2003 x86/x64 or Windows 2008 x86/x64
– 1,5 GB (2 GB 2008)

Software Requirements:
– NET Framework 3.5 SP1
– Windows Installer 4.5
– Microsoft Office Word 2007 or Word 2003 SP2
– MIcrosoft Office Excel 2007 or Excel 2003 SP2
– SQL Server 2008 Express Edition, SQL Server 2008, or SQL Server 2005

image image
image image

Download Microsoft Assessment and Planning (MAP) Toolkit HIER

vSphere Client op Windows 7 32 & 64bits

 image

VMWare heeft vorige week Update 1 voor vSphere vrijgegeven.
Met deze update wordt de vSphere client volledig ondersteund op Windows 7 & Windows 2008 R2.

Download de client (Je moet wel een account hebben om in te loggen)

VCP410 Examen gehaald

Vanmiddag heb ik het VCP410 examen gehaald en mag me zelf nu gelukkig prijzen dat ik mijn VCP titel behaald heb.

Wat ik gedaan heb om het te halen staat allemaal hier onder:

Cursus
VMware vSphere: Install, Configure, Manage

PDF’s
VMware Certified Professional on vSphere 4 Blueprint
VMware Education Services
VMware vSphere 4.0 Documentatie
vSphere Configuration Maximum
vSphere 4 reference card
vSphere 4 notes
Virtualisedreality vSphere 4 Cue Cards
VMware port numbers drawing

Practice Exams:
Simon Long vSphere 4 Practice Exams
VMware Mock test examen

DVD Cursus
Train Signal VMware vSphere training

Boeken
Mastering VMware vSphere 4 (Scott Lowe)

Iomega StorCenter ix2-200 NFS Share aan maken voor vSphere

1. Ga naar Device door middel van http://ip adres of via IoMega StorCenter Software

2. Tabblad Settings
image  
3. Network Services
 image

4. NFS
image 
5. Enable NFS Services & Apply

6. Tabblad Shared Storage

7. Klik op Add

image image
8. Apply & daarna OK
9. Overzicht Shares. Je kunt nu de share vmware toevoegen aan je ESX of ESXi Server
image

Server 2008 R2 bevriest in VMware ESX & ESXi

Server 2008 R2 bevriest in VMware ESX & ESXi

Er is een probleem met Windows Server 2008 R2 die draait op VMWare ESX 3.5 & 4.
De oorzaak is de video driver zijn die geïnstalleerd wordt met de VMware Tools.

Oplossing

Bij het installeren van VMware Tools, selecteer Custom Install voor VMware Tools en schakel de SVGA driver uit.
Als alternatief, verwijder de SVGA driver van de Device Manager na het installeren van VMware Tools.
http://kb.vmware.com/kb/1011709

Update
Er is een nieuwe video driver in de laatste vmware tools. Na de VMWare Tools upgrade upgrade de SVGA driver naar de WDDM die te vinden onder C:\Program Files\Common Files\VMware\Drivers\wddm_video. Vink niet de SVGA videokaart driver uit anders moet de WDDM niet mee gekopieerd.

Nvidia Gaming Systeem met Nvidia Chipset = werkend ESX Whitebox

Enige tijd geleden was ik ik opzoek naar ESX whitebox waar ik ESX op kon draaien.

Mijn huidige server met daarop Windows 2008 met VMware Server kreeg ik met vSphere 4 een paars scherm en een berg foutmeldingen.

Na zoeken bleek dit moederbord niet ondersteund te worden. Bale 🙁

Op zoek naar wat anders…

Vandaag was ik weer opzoek naar een ESX whitebox aangezien ik niet verwachte dat mijn gaming systeem niet vSphere compatibel is aangezien het moederbord uitgerust is met een Nvidia chipset en ik tevens naar een HP ML110 aan het kijken was .

Vandaag maar eens mijn USB vSphere ESXi USB Stick in mij gaming systeem gestopt.

Eens even kijken wat het doet, want je weet het maar nooit…

En wat blijkt alles werkt 😀

De twee nvidia nics + nvraid (raid 5) opstelling wordt zonder problemen herkend Cooolll!!!!

Specs:

Intel Q6600
Asus P5NT WS (Nvidia Chipset)
4 GB Geheugen (Nu duimen dat 8GB werkt) (8GB onder windows blue screen 🙁 )
3 x 250GB 7200RPM (Raid 5)
DVD Brander
8800GTS als videokaart beetje overkill maar wel Cool 😀

Het wordt nu even geheugen bestellen en hopen dat alles draaid.

Me is happy 😀

Hoe een bootable vSphere ESXI 4 USB stick maken

vmware image

ESX 4i vereist minimaal 2048 MB aan geheugen.

Je hebt 2 tooltjes nodig om een vSphere ESXI 4.0 USB stick te maken.
Je kunt het ook met WinImage doen zie de handleidingen HIER & HIER

Maar op een of andere  manier krijg ik onder Windows 7 & Windows 7 een error met geen melding dus moet het maar op een andere manier. Zie de afbeelding hieronder.
image

Oplossing (WERKT NIET OP WINDOWS 7 COMPUTER)

1. 7-Zip(Free), DD (Gratis)

2. Download the ESXi ISO (VMware-VMvisor-Installer-4.0.0-164009.x86_64.iso)

3. Open de ISO met 7-Zip

4. Open “image.tgz” met 7-Zip

5. Ga naar  “\image.tgz.temptar\usr\lib\vmware\installer\VMware-VMvisor-big-164009-x86_64.dd.bz2\”

image

6. Extract “VMware-VMvisor-big-164009-x86_64.dd” & kopieer deze naar de map D:\DD

7. Pak dd-0.5.zip uit naar d:\dd\

8. Run –> CMD

9. Ga naar D:\DD

10 Typ het volgende dd –list enter

Je krijgt nu een lijst te zien met alle harddisk apparaten die in je computer zit
dd1

11. Zoek hier je USB stick op. Het is iets in de trend van \\?\Device\HarddiskVolume6

12. Type dan het volgende dd bs=1M if=VMware-VMvisor-big-164009-x86_64.dd of=\\?\Device\HarddiskVolume6 vervang het laatste stukje door je USB Stick…

13. Je hebt nu als het goed is een USB stick met daarop vSphere ESXi 4.0

dd2 

Veel plezier met je VMWare vSphere USB Stick 😀