Tag Archives: Software

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

    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

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

    Posted on by

    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.

    ESX 3.5 Logfile Retrieval

    Posted on by

    vLogView is a Windows® based application which manages VMware® ESX Server log files.

    The product is designed to be installed on an administrators PC, and provides the ability to store, view and search ESX Server log files from multiple ESX Servers, without requiring individual login, navigation and manual file transfer.

    http://xtravirt.com/xd10132

    Migrate Symantec Anti Virus to Symantec Endpoint Protection

    Posted on by

    Document ID: 2007071909500548

    What should I think about in advance before I begin migrating my Symantec AntiVirus environment to Symantec Endpoint Protection?
    Consider several factors before you begin your migration:

    • Do you have the resources to create a test migration environment?
      If you create such an environment is highly beneficial before you begin migration so that you can test exactly how clients and servers are grouped, which settings are migrated, and the overall migration success rate.
    • Can you perform a complete migration to Symantec Endpoint Protection?
      If your network contains operating systems (such as Netware) that are not supported with Symantec Endpoint Protection, then Symantec System Center must manage a subset of the clients and servers.
    • Do you want to create a new client groupings or use the existing groupings from Symantec System Center?
    • How do you plan on migrating Symantec Endpoint Protection to your clients? Do you plan to use third party tools or the Migration and Deployment Wizard?
    • After you determine the method that you want to use to migrate your clients, you can determine whether to use certain Symantec Endpoint Protection features.
    • Are there client settings that you must disable or reconfigure to ensure successful migration?
    • Some client settings such as scheduled scans must be disabled before you begin migration.

    Before you begin migration, you must read the migration chapters in the Installation Guide for Symantec Endpoint Protection and Symantec Network Access Control.

    What are the general steps to migrating Symantec AntiVirus to Symantec Endpoint Protection?
    You must complete the following steps to migrate Symantec AntiVirus to Symantec Endpoint Protection in the order listed:

    1. Uninstall the Reporting Sever if you have it installed.
    2. Use Symantec System Center to configure settings for the management server and clients that prepare them for migration.
      These settings changes are: disable scheduled scans, modify Quarantine purge options, delete histories, disable LiveUpdate, disable roaming, unlock server groups, and disable Tamper Protection. Install the Symantec Endpoint Protection Manager.
    3. Migrate your legacy clients and servers.
    4. Uninstall Symantec System Center
    5. Migrate the legacy client or server that was used to protect the computer running Symantec System Center.

    Create user account in Symantec System Center 10.x

    Posted on by

    To create a user account for a server group

    1. Start Symantec System Center.
    2. Right-click the appropriate server group.
    3. Click Account Management.
    4. In the Configure Server Group Accounts dialog box, click Add.
    5. In the Account Setup dialog box, do the following:
      • Type the user name.
      • In the New password box, type the password.
      • In Confirm password box, type the password again.
      • Under Account Type, check the role that you want to assign to the user: Read-only, Administrator, Central Quarantine, or Gateway Security.
    6. Click OK.
    7. Click Finished.
      The changes are then sent to the secondary management servers in the server group.

    source

    Install windows 2003 Server on a Dell Latitude E6500

    Posted on by

    When you try to install windows 2003 server onto a dell laptop, it will crash during the dos setup.

    This is because the Hard disk mode has the wrong type. Change the hard disk mode in the bios of the system to ATA and try again.

    When booting press F12
    Select BIOS
    Change Hard disk mode to ATA
    Reboot, and install Windows 2003 Server

    INGRES installation corrupt

    Posted on by

    When rebooting a server with problems, it could lead to a corrupt ingress installation.

    This leads to all kind of problems. When starting the Ingres Visual Manager you get an error: “II_INSTALLATION must be set before the configuration utility is run”.

    To fix this problem you need to restore the symbols.tbl file located in the ingres\files directory. If you want to restore them manually, you need to know the original settings. You can get them back with the utility: ingsetenv.exe

    If you restore the file, make sure ingres is down and run after the restore the following command: ingsetenv II_GCNI2_PORT “”

    If you do not know the exact settings, you can try to take a look at the install.log. The settings of the ingres environment are also mentioned their.