Entradas

Mostrando entradas de julio, 2010

vMotion migration error when migrating between a host using Intel Xeon Processor 56xx series or 36xx series

vMotion fails between hosts using Intel Xeon 56xx or 36xx series processors to hosts using either Intel Xeon Processor 34xx series or Intel Core i3/i5 processors. RESOLUTION To resolve this issue, install this patch based on the product you are using: ESX 3.5 VMware ESX 3.5, Patch ESX350-201006401-SG: Updates VMkernel, VMware Tools, hostd, VMX, VMnix (1022899) ESXi 3.5 VMware ESXi 3.5, Patch ESXe350-201006401-I-SG: Updates firmware (1020052) For more information on modifying CPU masks, see section Modifying Default Mask for Intel CPUs in VMotion CPU Compatibility - Migrations Prevented Due to CPU Mismatch - How to Override Masks (1993) MORE INFO http://kb.vmware.com/kb/1021023

Virtual machine memory usage alarms in Intel Xeon 3500, 3600, 5500 and 5600 Series

Virtual machine memory usage alarms triggered for virtual machines when guest operating system memory usage is low. Affect VMware ESXi 4.0 and ESX 4.0 When operating a virtual machine on an ESX 4.0 host with Intel systems that support EPT technology or AMD systems that support RVI technology, virtual machine memory usage alarms are triggered regularly even though the guest operating system reports minimal memory utilization. Note : Intel Core i7 (Nehalem) series CPUs include Intel Xeon 3500 and 3600 Series (numbered 35xx and 36xx) and Intel Xeon 5500 and 5600 Series (numbered 55xx and 56xx). The ESX host shows committed memory equal or near equal to that of the assigned memory even when the guest operating system is not in demand of memory. When a virtual machine memory usage alarm is triggered, the guest operating system shows that the memory usage is low. A discrepancy is noted between the performance monitoring tools on the ESX host and performance monitor

Install SQL Server Integration Services SSIS in a different Server

Install SQL Server Integration Services in a Server different to SQL Server Database Server for example in an application server. In Application Server where you install SSIS modify the follow file to connect a Database Server “C:\Program Files\Microsoft SQL Server\90\DTS\Binn\ MsDtsSrvr.ini.xml” Change  the parameter according to you environment: <ServerName>.</ServerName> For example: <ServerName>SERVERSQL01\INSTANCE03</ServerName> Restart SQL Server Integration Services.

Remove VMware tool Tray Icon in Terminal Services and RDS

Imagen
Disable access to VMware tools in Virtual machines is a task important in security and resource management. You can remove it in two way: Between MSCONFIG.EXE, in tab Startup, uncheck: VMwareTray.exe VMwareUser.exe   Modify the following registry keys: DELETE [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run] "VMware Tools"="C:\\Program Files\\VMware\\VMware Tools\\VMwareTray.exe" "VMware User Process"="C:\\Program Files\\VMware\\VMware Tools\\VMwareUser.exe" MODIFY [HKEY_LOCAL_MACHINE\SOFTWARE\VMware, Inc.\VMware Tools] "ShowTray"=dword:00000000 MORE INFO http://kb.vmware.com/kb/1006354

Enable Hot Add CPU and Memory in vSphere

Imagen
In vSphere, there is a new feature, hot add memory and CPU. This is very cool as downtime can be avoided which is, at least in my company, very helpful during daily operations. This feature is not enabled by default. To enable these features, do the following: Make sure the virtual machine hardware is upgraded to version 7, if it is not, then right click the VM and choose 'Upgrade Virtual hardware'. You can find the hardware version by clicking on the 'Summary' tab. Go to edit settings for the VM, then the options tab, under 'Advanced', select 'Memory/CPU hotplug' and in the pane to the right, enable the memory hot add and CPU hot plug features. This change must be made when the VM is powered down. If the VM is running, the options will be greyed out as in the image below. Hot add memory and CPU is not supported by all OS's, Windows 2008 Enterprise 64 bit edition is one of the suppoted OS's, for a complete list, t

Monitoring TCP and UDP Ports Activity - Port Reporter (PortRptr.exe)

Imagen
Port Reporter logs TCP and UDP port activity on a local Windows system. Port Reporter is a small application that runs as a service on Windows 2000, Windows XP, and Windows Server 2003. On Windows XP and Windows Server 2003 this service is able to log which ports are used, which process is using the port, if the process is a service, which modules the process has loaded and which user account is running the process. On Windows 2000 systems, this service is limited to logging which ports are used and when. In both cases the information that the service provides can be helpful for security purposes, troubleshooting scenarios, and profiling systems’ port usage. DOWNLOAD http://www.microsoft.com/downloads/details.aspx?familyid=69BA779B-BAE9-4243-B9D6-63E62B4BCD2E&displaylang=en

PortQryUI – Troubleshoot TCP/IP connectivity issues

Imagen
Portqry.exe is a command-line utility that you can use to help troubleshoot TCP/IP connectivity issues. Portqry.exe runs on Windows 2000-based computers, on Windows XP-based computers, and on Windows Server 2003-based computers. The utility reports the port status of TCP and UDP ports on a computer that you select. However, PortqryUI is GUI interface for portqry command line utility.This utility reports the port status of target TCP and User Datagram Protocol (UDP) ports on a local computer or on a remote computer. Because PortQry is intended as a troubleshooting tool, it is expected that users who use it to troubleshoot a particular problem have sufficient knowledge of their computing environment. PortQry version 2.0 supports the following session layer and application layer protocols: • Lightweight Directory Access Protocol (LDAP) • Remote Procedure Calls (RPC) • Domain Name System (DNS) • NetBIOS Name Service • Simple Network Management Protocol (SNMP) • Int

Volume Shadow Copy Service error

The snapshot creation failed because the VSS writer {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f} on source machine xxx did not respond within the expected time interval. (Internal error code: 0x809933BB) RECOMMENDED ACTION: Ensure that VSS writer is functioning properly and then try the operation again. 4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f is the Shadow Copy Optimization Writer APPLICATION EVENT LOG: Log Name:      Application Source:        VSS Date:          2/15/2010 6:19:11 PM Event ID:      8193 Task Category: None Level:         Error Keywords:      Classic User:          N/A Computer:      ServerName.Domain.com Description: Volume Shadow Copy Service error: Unexpected error calling routine ConvertStringSidToSid.  hr = 0x80070539. RESOLUTION Open regedit and locate 'HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList' Under the ProfileList subkey, delete any subkey th