TMG2010: Server Configuration does not match the stored configuration

Issue: Not Synced Server Configuration does not match with stored configuration

image4

Cause: FF TMG 2010 Array certificates expired.

Solutions: The following steps will fix the issue. Please note that I am explaining the situation where my TMG 2010 enterprise Array is deployed in workgroup.

Step1: Run ISA BPA on TMG 2010 Array Member

image1

Step2: Verify certificate expiry date

1. From the Start menu, click Run. Type MMC, and then click OK.

2. In MMC, click File, and then click Add/Remove Snap-in.

3. Click Add to open the Add Standalone Snap-in dialog box.

4. From the list of snap-ins, select Certificates, and then click Add.

5. Select the service account and click Next.

6. Click Next.

7. Select ISASTGCTRL and click Finish.

8. Browse to ADAM_ISASTGCTRL\Personal > Certificates.

9. Open the certificate to see if it is expired.

Step3: Create a Request.inf file. Open notepad and copy the following and paste into notepad. modify CN and domain details as per your own requirement. rename the file as request.inf. An example of the inf file is:

[Version]

Signature=”$Windows NT$

[NewRequest]

Subject = “CN=myTMG.mydomain.com”

EncipherOnly = FALSE

Exportable = TRUE  

KeyLength = 1024

KeySpec = 1 ; Key Exchange

KeyUsage = 0xA0 ; Digital Signature, Key Encipherment

MachineKeySet = True

ProviderName = “Microsoft RSA SChannel Cryptographic Provider”

ProviderType = 12

RequestType = CMC

; Omit entire section if CA is an enterprise CA

[EnhancedKeyUsageExtension]

OID=1.3.6.1.5.5.7.3.1 ; Server Authentication

[RequestAttributes]

CertificateTemplate = WebServer

Step4: request Certificate to the Root/Subordinate CA

Open a elevated command prompt. At the command prompt, type the following command, and then press ENTER:

certreq -new –f request.inf certnew.req

Important! This command uses the information in the Request.inf file to create a request in the format that is specified by the RequestType value in the .inf file. When the request is created, the public and private key pair is automatically generated and then put in a request object in the enrollment requests store on the local computer.

Step5:Submit the request and obtain certificate

Open a elevated command prompt. At the command prompt, type the following command, and then press ENTER:

certreq -submit certnew.req certnew.cer

Important! certnew.req is generated in the previous command. certnew.cer is the certificate you are looking for.

An alternative way of submitting certificate to CA

  1. Open Certificate Authority
  2. Right Click on CA Server>All Task>Submit a New request
  3. Point to the location of certnew.req file
  4. Save Certificate As certnew.CER file into the preferred location

Step6:Convert certificate into .pfx format

Import the certificate certnew.cer into a server or an admin workstation

1. On the head node, click Start, click Run, and then type mmc to start the Microsoft Management Console.

2. On the File menu, click Add/Remove Snap-in. The Add or Remove Snap-ins dialog box appears.

3. In Available snap-ins, click Certificates, and then click Add.

4. Select Computer account, and then click Next.

5. Select Local computer, and then click Finish.

6. If you have no more snap-ins to add to the console, click OK.

7. In the Microsoft Management Console, in the console tree, expand Certificates, and then expand Personal.

8. In the details pane, click the certificate you want to manage.

9. On the Action menu, point to All Tasks, and then click Import. The Certificate Export Wizard appears. Click Next.

10. Browse to location of certnew.cer file

11. Import Certificate

To export a certificate in PFX format using the Certificates snap-in

1. On the head node, click Start, click Run, and then type mmc to start the Microsoft Management Console.

2. On the File menu, click Add/Remove Snap-in. The Add or Remove Snap-ins dialog box appears.

3. In Available snap-ins, click Certificates, and then click Add.

4. Select Computer account, and then click Next.

5. Select Local computer, and then click Finish.

6. If you have no more snap-ins to add to the console, click OK.

7. In the Microsoft Management Console, in the console tree, expand Certificates, and then expand Personal.

8. In the details pane, click the certificate you want to manage.

9. On the Action menu, point to All Tasks, and then click Export. The Certificate Export Wizard appears. Click Next.

10. On the Export Private Key page, click Yes, export the private key. Click Next.

11. On the Export File Format page, select Personal Information Exchange – PKCS #12 (.PFX). Click Next.

12. On the Password page, type and confirm the password that is used to encrypt the private key. Click Next.

13. Follow the pages of the wizard to export the certificate in PFX format.

Step7: Import Certificate into TMG Array

Log on to the TMG Server

Open FF TMG 2010 Console

Click on System>Click Server that is one of the array member>Click Import Server Certificate from the task pan>Browse location of the certificate import certnew.PFX format certificate

Click Ok.

Click refresh on the systems

Step8: Repeat the entire steps into all array members

Step9: Refresh Array members and check system

image2

Check TMG related services.

image3

Special thanks to Raihan Al-Beruni

Windows Server 2012 Release Candidate Build 8400 in VMware Workstation Technology Preview 2012

This procedure describes how to install Windows Server 2012 in VMware Workstation. The following versions are used:

  • VMware Workstation Technology Preview 2012 e.x.p Build-646643
  • Windows Server 2012 Release Candidate Datacenter Build 8400

In VMware Workstation Technology Preview 2012 create a new VM with the following settings:

  • New Virtual Machine
  • Custom (advanced)
  • Workstation Tech Preview
  • Select “I will install the operating system later”
  • Select “Microsoft Windows” and select as version “Windows 8 x64”
  • Set the Name and Location
  • Minimal 1 processor, 1 core
  • 2048 MB memory
  • Select “Use network address translation (NAT)”
  • Select “LSI Logic SAS”
  • Create a new virtual disk
  • SCSI
  • 60 GB disk size
  • Leave default disk file
  • Finish
  • After the VM is created, edit virtual Machine settings and browse for the Windows Server 2012 ISO in the the CD/DVD option

image

Edit the VMX file  and add the following line to the end to of the VMX file:

vmGenCounter.enable = FALSE

During the installation choose for the Windows Server 2012 Release Candidate (Server wit GUI)

Special thanks to my colleague Ivo Beerens

Windows Server 8 Beta Active Directory install in Workstation 2012 Tech Preview

Some days ago I was installing Windows Server 8 aka 2012 in Workstation 2012 Tech Preview. I used the default settings where I choise for Windows 8 x64 as version.
image

I have used these VMs with the VMware Tools from the TechPreview.

As soon as I try to install and configure the Active Director Domain Services, the VM needs to reboot. Once it has rebooted, it goes in a blank screen, and there is nothing I can do. Workstation thinks the VM is running, but there is no response via the GUI in the VM, no response to ping traffic to the VM or RDP.

Solution:
Downgrade from Workstation TP2012 hardware to Workstation 8 hardware and to select Windows 2008 R2 as the guest OS Knipogende emoticon
imageimage

image

HP takes the next step and provides ready-made driver packages for MDT and SCCM

HP takes the next step and provides ready-made driver packages for MDT and SCCM for the business models of notebooks, desktops and workstations. The packages can be obtained via SoftPaq Download Manager (SDM) or from the HP support website. It appears they are primarily for the current generation of products.
To get the download manager, navigate to the HP manageability website: www.hp.com/go/easydeploy or directly to www.hp.com/go/sdm

Here are screenshots from the new packages in SoftPaq Download Manager and from the HP support website.


Special Thanks to: Deploymentresearch

VMware Workstation 2012 TechPreview

What’s new for Workstation?

  • Installation and operation of VMware Workstation on Windows 8 and Windows Server 8
  • Installation and operation of Windows 8 consumer preview and Windows Server 8 in a virtual machine
  • Rendering and graphics correctness issues on all platforms and applications
  • Linux 3D desktop experience, particularly when using the Ubuntu 12.04 LTS Beta
  • Linux 3D application graphics correctness and performance
  • Stability in real-world scenarios including suspend/resume and display and device support
  • Nested Virtualization – running ESX and even trying Hyper-V* as a guest OS
  • VNC connection performance and stability

Download

VMware Workstation 8.0.1 Released

What’s New

Highlights of VMware Workstation 8.0.1 functionality include:

  • Graphics performance and compatibility enhancements.
  • Improvements in creating and using shared virtual machines and remote virtual machines.
  • Ubuntu 11.10 is officially supported as a guest operating system.
  • Disk and memory management issues have been addressed.
  • Many customer-reported issues have been resolved.

VMware Workstation 8.0.1 is a free update for all VMware Workstation 8 users.

Resolved Issues

The following sections list the resolved issues in VMware Workstation 8.0.1.

  • Windows 7 guest installation failed after powering on the virtual machine with the error A required CD/DVD drive device driver is missing. If you have a driver floppy disk,
    CD, DVD, or USB flash drive, please insert it now.
  • VMware Tools failed with the message VMware Tools unrecoverable error.
  • VMware Tools failed to start in Fedora 15 guests.
  • An Ubuntu 11.10 guest crashed with a signal 11 error if you installed or upgraded VMware Tools.
  • On hosts with Nvidia GeForce and Quadro video cards, some of the clouds in the Unigine Heaven Benchmark application were drawn solid black.
  • Easy Install did not properly function on Ubuntu 11.10.
  • If remote virtual machines were open, you could not shut down the Windows hosts.
  • When transitioning from Full Screen mode to Exclusive mode, the Full Screen toolbar sometimes failed to hide.
  • Host memory reservation restrictions on Windows hosts are more relaxed in VMware Workstation 8.0.1 than in previous versions of VMware Workstation.
  • CD/DVD mount Linux.iso failed while installing VMware Tools in Ubuntu 11.10 guests.
  • The AltGr key was not working in an Ubuntu guest in Unity mode when the host and guest keyboards were both set to a layout that contained the AltGr key.

VMware Workstation 8

What’s New

This release of VMware Workstation adds the following new features and support.

Installation Changes and Enhanced Keyboards

The hardware requirements to install this version of Workstation have changed. Workstation now requires a relatively modern 64-bit CPU. See Installation Requirements for details.

The keyboard filter driver is no longer installed by default. When the driver is not installed, the enhanced keyboard functionality is unavailable and you must press Ctrl-Alt-Ins instead of Ctrl-Alt-Del to send a Ctrl-Alt-Del keystroke to the guest. To use the enhanced keyboard functionality, you must perform a custom installation and select the component. If you select the component, you must reboot whenever you install or uninstall Workstation.

Virtual Hardware Improvements

This version of Workstation includes many hardware improvements. To try new hardware features, you must upgrade the hardware version of your virtual machine or create a new virtual machine that uses the latest virtual hardware version.

  • The display technology has been changed to provide a better experience for Unity users and users who have multiple monitors. These changes also allow you to add a projector to your laptop without restarting your virtual machine.
  • Virtual machines can now support up to 64GB of memory. The host system should have more than 64GB of memory to use this feature.
  • An HD Audio device is available for Windows Vista, Windows 7, Windows 2008, and Windows 2008 R2 guests. The HD Audio device is compatible with the RealTek ALC888 7.1 Channel High Definition Audio Codec.
  • USB 3.0 support is available for Linux guests running kernel version 2.6.35 or later (Ubuntu 10.10) through a new virtual xHCI USB controller. To enable this feature, add the following line to the .vmx file: usb_xhci.present = “true”. Do not enable this feature for Windows guests. Because Windows does not currently have a generic xHCI driver, this feature will not work in Windows.
  • Bluetooth devices on the host can now be shared with Windows guests. With the latest hardware version, Bluetooth devices that are paired to the host system radio are available to Windows guests and can be paired from within the guest. You should not pair Bluetooth audio devices, such as headphones, or Bluetooth input devices, such as keyboards and mice, to a guest.
  • You can now enable Virtual VT-X/EPT or AMD-V/RVI in the processor settings interface. With this feature, applications running in a guest can take advantage of these virtualization technologies. You can also run 64-bit guest operating systems inside of vSphere running inside Workstation.
New User Interface

The Workstation user interface has been updated to include new menus, toolbars, and an improved preferences screen.

  • The favorites sidebar has been replaced with a virtual machine library. Instead of identifying every virtual machine created in Workstation as a favorite, the library is a comprehensive list of all of the virtual machines that Workstation users create, open, or access.
  • A new folder summary page helps you to better manage a group of related virtual machines. Live thumbnails make it easy to see what is happening in running virtual machines.
  • The full screen toolbar has been updated so that you can do more without having to leave full screen mode. Quick switch mode is no longer needed.
What Happened to Teams?

Although at first it might appear that the teams feature has been removed, you can add team attributes to any virtual machine in this version of Workstation.

  • The team structure has been converted to a simple folder of virtual machines.
  • A new advanced settings dialog box has been added for network adapters to let you throttle the bandwidth of incoming and outgoing transmissions and simulate packet loss.
  • You can perform power operations on several virtual machines at the same time by selecting virtual machines on the folder tab and pressing the power button on the toolbar. If all of the virtual machines in a folder are in the same power state, you can select the folder to perform a power operation on all of the virtual machines in the folder.
  • You use a global Workstation preference to configure the delay between powering on virtual machines.
  • To implement LAN segments, you can use traditional VMnets or put all of the virtual machines that you want to communicate on the same custom VMnet.
Shared Virtual Machines and AutoStart

You can share virtual machines with remote users in this version of Workstation. A shared virtual machine can be accessed remotely by other instances of Workstation. Workstation moves virtual machines to the shared virtual machines folder, where the VMware Host Agent service manages them. The VMware Host Agent service is used by other VMware products, including VMware Server and vSphere, and provides additional capabilities required by professional users. An extensive permissions interface lets you control the users who can access and use shared virtual machines.

You can use the new AutoStart feature to configure shared virtual machines to start with the host system. You can also configure AutoStart for shared virtual machines on remote hosts running Workstation and ESX 4.x and later.

Remote Connections

In this version of Workstation, you are no longer constrained to working only with virtual machines that your computer has enough power to run. You can use the new Connect to Server feature to connect to remote hosts running Workstation, ESX 4.x and later, and VMware vCenter Server. After connecting to a remote host, all of the virtual machines that you have permission to access are displayed in the virtual machine library.

Upload to ESX/ESXi and vCenter Server

VMware OVF Tool is now integrated with Workstation so that you can upload a virtual machine from Workstation to a remote server running ESX, ESXi, or vCenter Server. After connecting to a remote server, you drag the virtual machine from the local My Computer section of the virtual machine library to the remote server. A wizard walks you through the process.

Documentation Changes

This version of Workstation includes several important documentation changes.

(NEW) Getting Started with VMware Workstation
Describes how to install and upgrade Workstation, create a typical virtual machine, and perform common virtual machine operations.

Using VMware Workstation
(previously VMware Workstation User’s Guide)
Describes how to create typical, custom, and shared virtual machines, add virtual devices, configure network connections, connect to remote servers and use remote virtual machines, upload virtual machines to remote servers, and perform all virtual machine operations.

Getting Started with VMware Player
(previously VMware Player Getting Started Guide)
Now contains complete information on installing and using Player.

Online help
Has been redesigned to provide context-sensitive help and information on performing common tasks. For complete information on using Workstation and Player, see the guides.

(NEW) Installing and Configuring VMware Tools
Contains comprehensive information on installing, upgrading, and configuring VMware Tools.

Top of Page

Installation Requirements

When you install Workstation, the installer performs checks to make sure the host system has a processor that meets the following requirements. You cannot install Workstation if the host system does not meet these requirements.

  • 64-bit x86 CPU
  • LAHF/SAHF support in long mode

You can use CPU-Z or a similar utility to determine if the host system CPU is 64-bit capable. CPU-Z shows EM64T (Intel) or AMD64 (AMD) if the processor is 64-bit capable.

If you plan to install a 64-bit guest operating system in a virtual machine, the host system must have one of the following processors. Workstation will not allow you to install a 64-bit guest operating system if the host system does not have one of these processors.

  • AMD CPU that has segment-limit support in long mode.
  • Intel CPU that has VT-x support. VT-x support must be enabled in the host system BIOS. The BIOS settings that must be enabled for VT-x support vary depending on the system vendor. See VMware KB article 1003944 for information on how to determine if VT-x support is enabled.

Top of Page

Known Issues

The known issues are grouped as follows:

Remote Connection and Remote Virtual Machine Issues
  • When Workstation is installed on a Linux host, VMware Workstation Server writes the core file to /usr/bin instead of to /var/core or /var/log/vmware.
  • You cannot use Workstation to create a remote virtual machine on an ESX or ESXi 4.1 host if the virtual machine name contains non-ASCII characters.
  • When you upload a virtual machine to a remote server (VM > Manage > Upload), Workstation modifies the MAC address and PCI slot number of the virtual Ethernet device in the newly created remote virtual machine. Network errors can occur in the remote virtual machine if the network settings in the guest operating system require the original network hardware configuration.
    Workaround: Change the network settings in the guest operating system in the remote virtual machine to match the new network hardware configuration.
  • VMware Workstation Server occasionally crashes on a 32-bit Red Hat Enterprise Linux 6.x host.
Role and Permission Issues
  • On a Windows host, if you edit a permission, assign the Administrator role, and then immediately click Remove to delete the permission, the original permission still exists when you reopen the Permissions dialog box.
Shared Virtual Machine Issues
  • On Windows hosts, if a shared virtual machine has a floppy drive that is configured to connect at power on, and a remote user powers on the virtual machine, a dialog box appears on the host system asking whether to connect the device every time the virtual machine powers on. If you click Yes to close the dialog box on the host system after the virtual machine is completely up and running on the host system, Workstation crashes on the host system.
  • On a 32 or 64-bit Windows 7, 64-bit Windows 2008 R2, or 32-bit Windows XP Professional SP3 host, if you uninstall Workstation, preserve the configuration, and then reinstall Workstation to a different path, the Shared VMs item is unavailable in the virtual machine library.
  • On a Windows host, if you create a virtual machine with a name that contains non-ASCII characters in the New Virtual Machine wizard, you cannot share the virtual machine with the Move the virtual machine option if the destination path is other than the system operating system location. The sharing process stops with the error message Failed to move VM to destination path.
    Workaround: If you want to share the virtual machine, you must use only ASCII characters in the virtual machine name when you create the virtual machine in the New Virtual Machine wizard.
Display and Input Issues
  • On an Ubuntu 11.04 host, the virtual machine icon does not appear on the system tray when you set the Show tray icon setting (Edit > Preferences > Workspace) to Always or When a virtual machine is powered on.
    Workaround: Whitelist vmware-tray as an application that can show system tray icons in Ubuntu 11.04. Alternatively, enable Notification Area (Systray) for all applications, for example:
    gsettings set com.canonical.Unity.Panel systray-whitelist "['all']"
    After you run the command, log out and log back in. The command can take several minutes to take effect.
  • On a Fedora 15 host, powering on a virtual machine that has DirectX 9 accelerated graphics enabled might fail with the error "Unable to change virtual machine power state: Cannot find a valid peer process to connect to."
    Workaround: Deselect the Accelerate 3D graphics setting (VM > Settings > Hardware > Display) to disable DirectX 9 accelerated graphics in the virtual machine.
  • When you enter Unity mode in an Ubuntu 11.04 guest, application menus do not appear for applications that were opened before entering Unity mode. Application menus do appear for applications that are opened from the Unity launch menu after entering Unity mode.
    Workaround: Disable the APPMENU (Global menu) in the Ubuntu 11.04 guest. See the Ubuntu documentation for more information.
  • After you upload a Windows XP virtual machine from the local host to a remote server, you cannot autofit the guest in full screen mode. This problem occurs because VRAM is reduced to 4 MB when the virtual machine is uploaded to the remote server.
Folder and Team Conversion Issues
  • When you select a newly created folder in the Workstation library, the toolbar power option button is dimmed and you cannot perform batch power operations on the virtual machines in the folder.
    Workaround: If you select a virtual machine in the folder, move the selection off the virtual machine (for example, click anywhere on the folder tab), and then select the folder in the library again, the toolbar power option button becomes available.
Device Issues
  • On Windows hosts, Player crashes if you click Connect or Disconnect in the Removable Devices menu before the console appears.
  • An Ubuntu 11.04 host might crash when you try to connect a USB device to a running virtual machine from the status bar icon’s context menu. This problem typically occurs after Workstation is freshly installed, the host is rebooted, and the first time the device is connected to the virtual machine.
Physical Machine Virtualization Issues
  • When simple file sharing or UAC is enabled on the physical machine, the Virtualize a Physical Machine wizard returns an "incorrect user credentials" error instead of an error message that indicates simple file sharing or UAC must be disabled before virtualizing the physical machine. See the online help or Using VMware Workstation for information on preparing a physical machine for virtualization.
  • You cannot use the Virtualize a Physical Machine wizard if the Workstation installation path contains non-ASCII characters.

Upgrade ESXi 4.0 to ESXi 4.1

1. You need vSphere CLI – Download Here

For Windows or Linux and install on your workstation.

2. Download the Upgrade Package for 4.0 to 4.1

3. Power off your VM’s and put the host into maintenance mode

4. From the vSphere CLI prompt

vihostupdate.pl –server hostname or IP -i –b d:\downloads\upgrade-from-ESXi4.0-to-4.1.0-0.0.260247-release.zip -B ESXi410-GA

Preventing Automatic Service Pack 1 Update to Windows 7 and Windows Server 2008 R2

Microsoft began to distribute Windows 7 and Windows Server 2008 R2 Service Pack 1 (SP1) as a high-priority update through Automatic Updates. However, as with most large corporate environments, IT organizations may want to delay the introduction of a new Service Pack until they have tested compatibility with internal applications and sites.

Microsoft created a tool called “Windows Service Pack Blocker Tool Kit” to stop it from updating your servers and workstations without your permission. Unlike the Blocker Toolkit for IE9, this tool does have an expiration date – the 22nd of February 2012. The tool and can be configured either by running the registry file on the client machines or through Group Policy in domain joined environments.

Download

Download details: www.microsoft.com/downloads/en/details.aspx?FamilyID=D7C9A07A-5267-4BD6-87D0-E2A72099EDB7

The tool can be used with:

  • Windows 7 Service Pack 1
  • Windows Server 2008 R2 Service Pack 1

Toolkit Components

The tool contains three components. All of them function primarily to set or clear a specific registry key that is used to detect and block download of Service Packs from Windows Update. You need to only use one of the components, the one that best serves your organization’s computer management infrastructure.

The components are:

  • A Microsoft-signed executable
  • A script
  • An ADM template

Registry key

The executable creates a registry key on the computer on which it is runs that blocks or unblocks (depending on the command-line option used) the delivery of a Service Pack to that computer through Windows Update. The key used is HKLM\Software\Policies\Microsoft\Windows\WindowsUpdate.

Key value name: DoNotAllowSP

  • When the key value name is not defined, distribution is not blocked.
  • When the key value name is set to 0, distribution is not blocked.
  • When the key value name is set to 1, distribution is blocked.

Blocker Script

The script does the same thing as the executable, but allows you to specify the remote machine name on which to block or unblock delivery of Service Packs.

When the ‘/B’ command line option is used, the key value name ‘DoNotAllowSP‘ is created and its value set to 1. This value blocks delivery of a Service Pack to the computer through Automatic Update or Windows Update.

When the ‘/U’ command line option is used, the previously created registry value that temporarily blocked the delivery of a Service Pack to the computer through Automatic Update or Windows Update is removed. If the value does not exist on the computer on which it is run, no action is taken.

Note: The executable and script have been tested only as a command-line tool and not in conjunction with other systems management tools or remote execution mechanisms.

Group Policy Administrative Template (.ADM file)

The ADM template allows administrators to import group policy settings to block or unblock delivery of Service Packs into their Group Policy environment. Administrators can then use Group Policy to centrally execute the action across systems in their environment.

Add the .ADM file to the Group Policy by going to Computer Configuration > Administrative Templates. Right click and select Add/Remote Templates. Browse to the location of the .ADM file and click Ok.

Windows 7 and Windows Server 2008 R2 SP1 Blocker: Group Policy Settings

Users running Windows 7 and Windows Server 2008 R2 will see the policy setting under Computer Configuration > Administrative Templates > Classic Administrative Templates (ADM) > Windows Components > Windows Update.

Block Windows 7 and Windows Server 2008 R2 SP1 automatic updates

Please note that this toolkit will not prevent the installation of the service pack from CD/DVD, or from the stand-alone download package. This simply prevents Windows 7 and Windows Server 2008 R2 Service Pack 1 (SP1) from being delivered over Windows Update.

VMware Workstation 7.1.4

    What’s New

    Support for Windows 7 SP1

    Security Fixes

    • Workstation 7.1.4 addresses a local privilege escalation in the vmrun utility

      VMware vmrun is a utility that is used to perform various tasks on virtual machines. The vmrun utility runs on any platform with VIX libraries installed. It is installed in Workstation by default. In non-standard filesystem configurations, an attacker with the ability to place files into a predefined library path could take execution control of vmrun. This issue is present only in the version of vmrun that runs on Linux

      The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the name CVE-2011-1126 to this issue.

        Other Resolved Issues

        • In Workstation 7.1, the default main memory VA cache size (mainMem.vaCacheSize) for 32-bit Windows guests was reduced to accommodate 3D emulation memory requirements. However, the reduced value resulted in performance loss. For 7.1.4, the default main memory VA cache size has been be increased to 1000 MB and performance is improved.

        • Because Workstation failed to identify more than 10 USB host controllers in newer Windows guests, some USB devices did not appear in the Removable Devices menu. Now Workstation shows all USB devices in the Removable Devices menu as long as they are connected to the first identified 16 USB controllers.

        • When using the Capture Movie option, the captured video stopped playing around the 1GB mark if the video file exceeded 1GB. Now you can capture and play video files that are greater than 1GB. 

        • On Windows host systems that have more than 4GB of memory, Workstation sometimes crashed during cryptographic operations, for example, when performing disk encryption.

        • VMware Tools upgrade could be started by a non-administrator user from the VMware Tools Control Panel in a Windows guest. In this release, only administrator users can start VMware Tools upgrade from the VMware Tools Control Panel. To prevent non-administrator users from starting VMware Tools upgrade from a guest by using other applications, set isolation.tools.autoinstall.disable to TRUE in the virtual machine configuration (.vmx) file.

        • When a virtual machine running on a Windows host was used to access an Omron Industrial CP1L Programmable Logic Controller, Workstation generated an unrecoverable error.

        • When using NAT virtual networking on Windows hosts, the traceroute command did not work when used within virtual machines.

        • Workstation crashed with an access violation when a user tried to open the sidebar after closing all tabs in Quick Switch mode. 

        • The VMware Tools HGFS provider DLL caused a deadlock when making calls to the WNetAddConnection2 function from an application such as eEye Rentina in a Windows guest operating system.

        • There was no option to disable guest time sync when a host resumes. Now you can set time.synchronize.resume.host to FALSE in the virtual machine configuration (.vmx) file to disable guest time sync when a host resumes. See VMware Knowledge Base Article 1189 for other time sync options.

        • Setting a hidden attribute on a file in a shared folder from a Windows guest on a Linux host failed with an error. This problem caused applications such as SVN checkout to fail when checking out to shared folders on Linux hosts from Windows guests

        Translate »