Author Archives: Bastiaan van Leeuwen

Disabling access to VMware Tools

Posted on by

VMware KB:  http://kb.vmware.com/kb/1006354

Purpose

This articles provides steps to disable VMware Tools access for other users.

Resolution

Disabling access to VMware Tools in the system tray by setting ShowTray to 0  in the registry under HKEY_CURRENT_USER\Software\VMware, Inc.\VMware , does not prevent other users from accessing the VMware Tools from the Control Panel.
 
To ensure users cannot access VMware Tools from the system tray or control panel:  
  1. Go to C:\Program files\VMware\VMware Tools .
  2. Right-click VMControlPanel.cpl properties and choose Security.
  3. Click Advanced and deselect Allow inheritable permissions.
  4. Click Deny for Read and Execute and Read for the users
  5. Log in as an Administrator.
  6. Right-click on the VMware Tools system tray icon.
  7. Choose Disable.
  8. In the registry editor, delete the VMware Tools key under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run .

vSphere Client does not open on any Windows operating systems with the error: parsing the server “” “clients.xml” file

Posted on by

Symptoms

  • When trying to launch the vSphere Client you receive errors similar to:

    Error parsing the server “<servername>” “clients.xml” file.

    The type initializer for VirtualInfrastructure.Utils.HttpWebRequestProxy’ threw an exception.

Resolution

You cannot use vSphere Clients prior to the Update 1 release, to access the vCenter Server or ESX hosts because of a Microsoft update that targets the .NET Framework (980773), released on June 9th 2010.  
 
Perform one of these two options to correct the issue:
  1. Download and install vSphere Client 4.0 Update 1 (build 208111) or Update 2 (build 258672) using method a or b below, depending on your environment.
  1. To download and install the vSphere Client for ESX, ESXi (paid version), and vCenter Server:
    1. Go the downloads site.

      Note      : The vSphere Client .exe is part of the ESX, ESXi, or vCenter Server download binaries.
    2. Click Download next to your ESX, ESXi, or vCenter Server edition.
    3. Log in with your VMware Account credentials.
    4. Click Yes to agree to the EULA.
    5. Click the .exe link next to vSphere Client and Host Update Utility.

      Note: You do not need to download the entire vSphere suite, only the vSphere Client.

    6. Follow the on-screen instructions to install the updated vSphere Client.
  2. To download and install the vSphere Client Update 1 for ESXi (free version):
    2. Click Download.
    3. Log in with your account credentials, or register for free.
    4. Click Download next to vSphere Client and Host Update Utility.
    5. Follow the on-screen instructions to install the updated vSphere Client.

 

  • Remove the MS update from your Windows operating system. The vSphere Client works after the update is removed.
    • Note: This affects Windows XP, Windows 2003, Windows 2008, Windows Vista, and Windows 7.
     
    If the build number for your vSphere Client is 208111 or higher, then you have vSphere Client Update 1 or later, and should not be affected by this issue.
     
    You can determine the version of vSphere Client by reviewing the build number located in the first line of a viclient.log file, located in %USERPROFILE%\Local Settings\Application Data\VMware\vpx on the system running the vSphere Client if the OS is Windows XP or 2003 and %USERPROFILE%\AppData\Local\VMware\vpx in 64 bit Windows 7 or 2008. Build 208111 or higher indicates you are using vSphere Client 4.0 Update 1 or later.
     
    For example:
     
    2010-05-19 03:08:58.508  Log for vSphere Client Launcher, pid=4756, version=4.0.0, build=build-208111, option=release
    VMware KB 1022611

    Adding a EXP810 to an existing DS4700

    Posted on by

    More information: ftp://ftp.software.ibm.com/systems/support/system_x_pdf/59y7287.pdf

    Connecting storage expansion enclosures at the end (bottom) of a drive loop 

    To add a 16-drive expansion enclosure, for example, an EXP810 or EXP420 to the DS4000 subsystem configuration, you basically follow the same procedure as in adding the 14-drive enclosure to a DS4000 subsystem configuration; however, the port connections on the 16-drive enclosure are different, as illustrated in Figure 4and the three steps that follow it.

    1. Insert the small form-factor pluggables (SFPs) or gigabit interface converters (GBICs) into only those ports that you intend to use. Do not leave GBICs or SFPs inserted into port connectors without connecting them to other ports using cables.
    2. Extend one of the drive loops (that is, drive loop A) in a DS4000 storage subsystem redundant drive loop pair by connecting the OUT port of the last storage expansion enclosure to the IN port of the storage expansion enclosure as shown in Figure 1Note: The port name on an EXP810 is not labeled IN. See Figure 4 for details.

    Attention: Carefully reconfigure only one drive loop at a time, making sure that the drive loop that you modify is correctly connected and in Optimal state before you attempt to reconfigure another drive loop. Take this precaution to prevent the arrays from being inadvertently failed by the DS4000 storage subsystem controllers, which happens when two or more drives in the arrays cannot be reached through either drive loop in the redundant drive loop pair.
    3. Power on the added storage expansion enclosure unit.
    4. Wait a few seconds; verify that the port bypass LEDs of all of the ports in drive loop A, now extended to the storage expansion enclosure, are not lit. Using the DS Storage Manager Client Subsystem Management window, verify that the storage expansion enclosure is added and displayed in the Logical/Physical view of the window.Correct any errors before you proceed to step 5. For port bypass, complete the following steps:

    1. Make sure that the SFPs and GBICs or fiber cables are in good condition.
    2. Remove and reinsert SFPs, GBICs, and fiber cables.
    3. Make sure the drive expansion enclosure speed switch is set to the same speed as the existing drive expansion enclosures and the DS4000 storage subsystem speed setting.
    4. Make sure that the ESM is functioning correctly by removing and swapping it with the other ESM in the same drive expansion enclosure. For enclosure ID conflict, set the drive expansion enclosure ID switch to values that are unique from the current settings in the existing drive expansion enclosures and storage server.

     

    Call IBM support for assistance, if the problem remains.
    5. In the other drive loop (drive loop B) in a DS4000 storage subsystem redundant drive loop pair, remove the connection from the storage subsystem drive loop port to the OUT port of the last storage expansion enclosure and connect it to the OUT port of the drive enclosure as shown in Figure 2.Note: The port name on an EXP810 is not labeled OUT. See Figure 4 for details.
    6. Wait a few seconds; verify that the port bypass LEDs of the two ports in the connection between the storage subsystem drive loop port and the OUT port of the drive enclosure are not lit. Using the DS Storage Manager Client Subsystem Management window, verify that the drive enclosure does not indicate the Drive enclosure lost redundancy path error. See step 4 for possible corrective actions, as needed.Note: The existing storage expansion enclosures are shown with “Drive enclosure lost redundancy” path errors until you establish the Fibre Channel cabling connection that is described in step 7.
    7. In drive loop B, cable the drive enclosure IN port to the OUT port of the last enclosure in the already functioning storage expansion enclosure drive loop, as shown in Figure 3.
    8. Wait a few seconds; verify that the port bypass LEDs of all of the ports in drive loop B to which you have added a connection are not lit. Using the DS Storage Manager Client Subsystem Management window, verify that all of the drive enclosures in the DS4000 redundant drive loop pair to which the enclosure was added do not report the “Drive enclosure lost redundancy” path error.

     

    Figure 1: Cabling a single drive enclosure to the end of a functioning drive loop (step 1 of 3)

    Figure 2: Cabling a single drive enclosure to the end of a functioning drive loop (step 2 of 3)

     

    Figure 3: Cabling a single drive enclosure to the end of a functioning drive loop (step 3 of 3)

     

    Figure 4: Cabling an EXP810 to the end of a functioning drive loop

    Connect Powervault 220s to a server

    Posted on by

    Cabling Your System for Joined-Bus, Split-Bus, or Cluster Mode

    How you cable your storage system to your host system(s) depends on the bus configuration you choose: joined-bus, split-bus, or cluster.

    • A joined-bus configuration is one in which two SCSI buses are joined to form one contiguous bus.
    • A split-bus configuration enables you to connect your storage system to either one server with a multichannel RAID controller, or to two servers. However, if one server fails, information controlled by that server is inaccessible.
    • A cluster configuration offers multiple paths to the system, which provides high data availability.

    Joined-Bus Configuration

     

    Split-Bus Configuration (One Server)

    Cluster Configuration or Split-Bus Configuration (Two Servers)

    SCSI ID Assignments

    Configuration Cables
    Used    		 SCSI IDs Used
    15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
    Joined-bus 1                 H S            
    Split-bus—primary EMM 1                 H S            
    Split-bus—secondary EMM 1                 H S            
    Cluster 2 S               H H            
    NOTE: The unshaded SCSI IDs are available for hard-drive use as indicated for each configuration. The reserved SCSI IDs are used as follows:
    H = used by the host system initiator.
    S = used by the storage system SES.

    SCSI ID Numbers and Associated Hard Drives 

     

    Split-Bus Module Modes

    Mode LED Icon Position of Bus Configuration Switch Function
    Joined-bus mode  

     

    		 Top LVD termination on the split-bus module is disabled, electrically joining the two SCSI buses to form one contiguous bus. In this mode, neither the split-bus nor the cluster LED indicators on the front of the system are illuminated.
    Split-bus mode  

     

    		 Center LVD termination on the split-bus module is enabled and the two buses are electrically isolated, resulting in two seven-drive SCSI buses. The split-bus LED indicator on the front of the system is illuminated while the system is in split-bus mode.
    Cluster mode  

     

    		 Bottom LVD termination is disabled and the buses are electrically joined. The cluster LED on the front of the system is illuminated while the system is in cluster mode.
    More information:

    CPUID – VMotion CPU Compatibility

    Posted on by

    We have problems doing a vmotion (ESX 4) from virtual machines from a Dell R710 to a Dell PowerEdge 2950. It gives a SSE4.2 error before we can vmotion it.

    A quick solution is to set CPU Masks. To do this, do the following:

    1. Shut down the server
    2. Edit settings
    3. Go to Options
    4. Choose CPUID Mask
    5. Select the Expose Options
    6. Click Advanced
    7. Set the following options:
      Feature Level Row Mask
      SSE4.2 1 ecx —- —- 0–0 —- —- —- —- —-
      80000001 edx —- 0— —- —- —- —- —- —-
    8. Press OK twice

    Now you can do a vmotion.

    How to backup a MsSQL database to a Share

    Posted on by

     Use a MsSQL query to backup a database to a network share:

    EXEC master.dbo.sp_configure 'show advanced options', 1
RECONFIGURE
EXEC master.dbo.sp_configure 'xp_cmdshell', 1
RECONFIGURE

exec master.dbo.xp_cmdshell 'net use Z: \\sharename password /user:user'
BACKUP DATABASE Staging TO DISK='Z:\database.bak'
EXEC master.dbo.xp_cmdshell 'net use /delete Z:'

EXEC master.dbo.sp_configure 'xp_cmdshell', 0
RECONFIGURE
EXEC master.dbo.sp_configure 'show advanced options', 0
RECONFIGURE

    Sync Google Calendar & Outlook 2010

    Posted on by

    Google Calendar Sync is an official tool from Google for syncing Outlook with Google calendar. At the moment it is only compatible with Outlook 2003 & 2007 versions, Outlook 2010 is not yet supported but you can still use it with Outlook 2010 (Beta & RTM) by tweaking Outlook executable file. In this post we will guide you through step-by-step procedure of tweaking Outlook 2010 executable file to finally make Outlook 2010 work with Google Calendar Sync.

    Read more: http://www.addictivetips.com/microsoft-office/sync-google-calendar-outlook-2010-quick-fix

    Cannot issue a new session ticket because the maximum number of tickets have been issued

    Posted on by

    This issue occurs when the Console tab is being viewed on 10 or more virtual machines in under 30 seconds.

    This issue occurs when the number of session tickets exceeds the the amount of default concurrent connections that vpxd allows.    To workaround this issue, increase the Session Ticket maximum value to 1024.   To increase the Session Ticket maximum value:  

    1. Open the vCenter Server’s vpxd.cfg file in text editor.Notes:
      • In Windows Server 2003, the vpxd.cfg is located on the vCenter Server in C:\Documents and Settings\All Users\Application Data\VMware\VMware VirtualCenter\. In Windows Server 2008, it is located in C:\ProgramData\VMware\VMware VirtualCenter\.
      • For more information about editing files, see Editing files on an ESX host using vi or nano (1020302).
    2. In between the vpxd tags, insert:     <sessionTicket>
              <max>1024</max>
           </sessionTicket>
    3. Restart the VMware VirtualCenter Server service. For more information, see Stopping, starting, or restarting vCenter services (1003895).

    VMware KB: 1020496