Disabling access to VMware Tools

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

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):
    1. Click Download.
    2. Log in with your account credentials, or register for free.
    3. Click Download next to vSphere Client and Host Update Utility.
    4. 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

    How to backup a MsSQL database to a Share

     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

    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

    PowerCLI: Windows Disk Alignment on VMware

    Searching for disk alignments off the windows 2003 servers on VMware ESX i found a CLI script which can automate the search. The original site: http://ict-freak.nl/2009/12/15/powercli-check-partition-alignment-windows-vms-only/

    Script:

    $myCol = @()
    $vms = get-vm | where {$_.PowerState -eq "PoweredOn" -and `
    $_.Guest.OSFullName -match "Microsoft Windows*" } | Sort Name 
    
    foreach($vm in $vms){
    $wmi = get-wmiobject -class "Win32_DiskPartition" `
    -namespace "root\CIMV2" -ComputerName $vm            
    
        foreach ($objItem in $wmi){
            $Details = "" | Select-Object VMName, Partition, Status
                if ($objItem.StartingOffset -eq "65536"){
                    $Details.VMName = $objItem.SystemName
                       $Details.Partition = $objItem.Name
                    $Details.Status = "Partition aligned"
                }
                else{
                    $Details.VMName = $objItem.SystemName
                       $Details.Partition = $objItem.Name
                    $Details.Status = "Partition NOT aligned"
                }
        $myCol += $Details
        }
    }
    $myCol | Export-Csv -NoTypeInformation "C:\PartitionAlignment.csv"
    #$myCol | Export-Clixml "C:\PartitionAlignment.xml"

    TS Licensing Step-by-Step Guide

    How should I prepare to use TS Licensing?
    To use TS Licensing to manage TS CALs, you will need to do the following on a server running Windows Server 2008:

    1. Install the TS Licensing role service.
    2. Open TS Licensing Manager and connect to the Terminal Services license server.
    3. Activate the license server.
    4. Install required TS CALs on the license server.

    For a detailed instruction, browse to: http://technet.microsoft.com/en-gb/library/cc754034(WS.10).aspx

    Keep in mind that a terminal server running Windows Server 2008 cannot communicate with a license server running Windows Server 2003. However, it is possible for a terminal server running Windows Server 2003 to communicate with a license server running Windows Server 2008.

    Windows Disk timeout is not set at default

    source: http://technet.microsoft.com/en-us/library/aa997069(EXCHG.80).aspx

    Disk timeout is not set at default

    This topic is intended to address a specific issue called out by the Exchange Server Analyzer Tool. You should apply it only to systems that have had the Exchange Server Analyzer Tool run against them and are experiencing that specific issue. The Exchange Server Analyzer Tool, available as a free download, remotely collects configuration data from each server in the topology and automatically analyzes the data. The resulting report details important configuration issues, potential problems, and nondefault product settings. By following these recommendations, you can achieve better performance, scalability, reliability, and uptime. For more information about the tool or to download the latest versions, see “Microsoft Exchange Analyzers” at http://go.microsoft.com/fwlink/?linkid=34707.

    The Microsoft® Exchange Server Analyzer Tool reads the following registry entry to determine whether the disk time-out value has been changed from the default value:

    HKEY_LOCAL_MACHINESystemCurrentControlSetServicesDiskTimeOutValue

    If the Exchange Server Analyzer finds the TimeOutValue present and configured with any value other than 10, and the server is non-clustered, a non-default configuration message is displayed. If the Exchange Server Analyzer finds the TimeOutValue present and configured with any value other than 20, and the server is clustered, a non-default configuration message is displayed.

    Disk time-out is a registry setting that defines the time that Microsoft Windows® will wait for a hard disk to respond to a command. On a non-clustered system, this key is not present and a default value of 10 seconds is used for all disks. On a Windows cluster, this key is present and uses a default value of 20 seconds. If the time-out time is more than the value in this registry setting, Windows will show an error and will stop disk access. Sometimes, this may be set to a greater value if you are running multipath disk-access software. Multipath software lets you connect multiple physical paths (such as fiber) to a single disk drive for redundancy. Multipath software manages the multiple physical connections so that Windows handles only a single handle to the disk.

    Installing host bus adapters (HBA) or other storage controllers can cause this key to be created and configured. When you install or reinstall these drivers, the TimeOutValue registry value is overwritten with the value that is required by those drivers. You may have to contact the hardware vendor to determine the correct TimeOutValue registry value for your configuration.

    To revert to the default configuration

    1. Open a registry editor, such as Regedit.exe or Regedt32.exe.
    2. Navigate to:

      HKLMSystemCurrentControlSetServicesDiskTimeOutValue

    3. In the right pane, delete the TimeOutValue entry. Alternatively, double-click the TimeOutValue entry and set it to one of the following values:
      • On a non-clustered server, set the value to 10.
      • On a clustered server, set the value to 20.
      • If your hardware manufacturer recommends a different value for either a clustered or non-clustered system, use the value from your hardware manufacturer instead.
    4. Close the registry editor, and then restart the computer for the change to take effect.

    Many Acrobat 7.0.x acr*.tmp files created in the WindowsTemp folder

    On a system there are many acr*.tmp files in the windostemp folder. After searching for this problem we found that this has to do with the windows indexing service and acrobat 7.

    Windows Indexing Service indexes contents and properties of files on local and remote computers, improving search performance. Windows Indexing Service calls the PDF iFilter to extract text from PDF files. This process causes Acrobat to generate a significant number of temporary files depending on the content of the PDF files. When you disable the Windows Indexing Service or the PDF iFilter, the creation of these temporary files is stopped.

    Because we can not disable the index service we upgraded acrobat to a newer version.

    For other solutions see the following article:

    http://kb2.adobe.com/cps/330/330414.html

    Solution 1:Upgrade to Acrobat 8.0 (Professional or Standard) or Adobe Reader 8.0.

    — To purchase an upgrade from Adobe, visit the Adobe Store at http://store.adobe.com/store/ , click Acrobat Family and choose Acrobat Standard or Acrobat Professional.

    — To locate an authorized reseller, visit the Adobe website at www.adobe.com/store/customerregistration/other_places.jhtml .

    — To download the free Adobe Reader 8.0, visit the Adobe website at www.adobe.com/products/acrobat/readstep2.html .

    Solution 2: Rename or delete the PDF iFilter indexing plug-in.

    For Adobe Reader 7.0.x:

    1. From the Start menu, select Search and then select All Files Or Folders.

    2. In the All Or Part Of The File Name field, type AcroRdIF.dll.

    3. After the search result(s) appears, right-click the AcroRdIF.dll file and select Rename.

    4. Rename AcroRdIF.dll to AcroRdIF.old.

    For Acrobat Standard,and Pro 7.0.x and Acrobat 3D:

    1. From the Start menu, select Search and then select All Files Or Folders.

    2. In the All Or Part Of The File Name field, type AcroIF.dll.

    3. After the search result(s) appears, right-click the AcroIF.dll file and select Rename.

    4. Rename AcroIF.dll to AcroIF.old.

    Solution 3: Stop the Windows Indexing Service.

    On Windows XP:

    1. From the Start menu, select Search, and the select Change Preferences.

    2. Select Without Indexing Service.

    3. Select “No, do not enable Indexing Service.”

    On Windows 2000:

    1. From the Start menu, select Search > For Files Or Folders.

    2. Select Indexing Service.

    3. Select “No, do not enable Indexing Service.”

    Note: Disabling the Indexing Service may make searching for files or folders on your machine somewhat slower.

    Delete files & Directories older then n days

    To delete files and directories older then a specified days, use the following vbs script:

    '
    'delete folders specified in a number of days, also specified in the script.
    '
    On error resume next
    
    Dim Directory
    Dim Noofdays
    Dim FSO
    Dim FSO2
    Dim LogFile
    Dim Folderlist
    Dim folders
    
    Directory ="D:\Logs\directory"
    Noofdays=cint(31)
    LogFile="D:\logs\result.txt"
    
    Set FSO = CreateObject("Scripting.FileSystemObject")
    Set FSO2 = CreateObject("Scripting.FileSystemObject")
    Set oFSO = CreateObject("Scripting.FilesyStemObject")
    '
    If oFSO.FileExists(Logfile) Then
    Const ForAppending = 8
    Set ofile = oFSO.OpenTextFile(LogFile, ForAppending, True)
    Else
    Set oFile = oFSO.CreateTextFile(logfile, true)
    End If
    ofile.writeline "Delete Folders older than 31 days Started   --> " & now()
    
    Set Folderlist = FSO.GetFolder(Directory)
    
    Set folders = Folderlist.SubFolders
    For Each d In Folders
    '          msgbox d.name
    '          msgbox d.size
    '          msgbox d.dateCreated
    '          msgbox d.dateLastModified
    '          msgbox d.dateLastAccessed
    tempdirectory = Directory & d.name
    
    If  datediff("d",d.dateCreated,now()) > Noofdays Then
    FSO2.DeleteFolder(tempdirectory )
    ofile.writeline "Deleting Folder...." & tempdirectory
    
    if err.number <>0 then
    ofile.writeline cstr(now()) & "    " & Err.description
    err.clear
    end if
    End If
    Next
    ofile.writeline "Delete Folders older than 31 days Completed --> " &now()
    ofile.writeline "--------------------------------------------"
    ofile.close