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

        Group Policy Preferences Data Sources Failed with error 0x80070057

        clip_image002
        Group Policy Data Sources is voltooid.

        Aanvullende gegevens:

        Het voorkeursitem computer ‘Nordined’ in het groepsbeleidsobject ‘De naam van de policy {54A928D5-EAA8-421B-9F12-066B350B6671}’ is niet toegepast, omdat het is mislukt met foutcode ‘0x80070057 De parameter is onjuist.’%%100790273

        Oplossing:

        clip_image004

        clip_image006

        Edit Datasources.xml
        <?xml version="1.0" encoding="utf-8"?>

        <DataSources clsid="{380F820F-F21B-41ac-A3CC-24D4F80F067B}"><DataSource clsid="{5C209626-D820-4d69-8D50-1FACD6214488}" name="WARD" image="2" changed="2011-03-02 09:04:35" uid="{2E9E5014-DEA3-4B65-AD9A-B8A6C602E576}" userContext="1" removePolicy="0"><Properties action="U" userDSN="0" dsn="WARD" driver="SQL Server" description="Ward" username="" cpassword=""><Attributes><Attribute name="SERVER" value="SQLSERVERNAME"/><Attribute name="TRUSTED_CONNECTION" value="Yes"/><Attribute name="DATABASE" value="DATABASENAAM"/></Attributes></Properties></DataSource>

        </DataSources>

        Delete username="" and cpassword=""
        <?xml version="1.0" encoding="utf-8"?>

        <DataSources clsid="{380F820F-F21B-41ac-A3CC-24D4F80F067B}"><DataSource clsid="{5C209626-D820-4d69-8D50-1FACD6214488}" name="WARD" image="2" changed="2011-03-02 09:04:35" uid="{2E9E5014-DEA3-4B65-AD9A-B8A6C602E576}" userContext="1" removePolicy="0"><Properties action="U" userDSN="0" dsn="WARD" driver="SQL Server" description="Ward" ><Attributes><Attribute name="SERVER" value="SQLSERVERNAME"/><Attribute name="TRUSTED_CONNECTION" value="Yes"/><Attribute name="DATABASE" value="DATABASENAAM"/></Attributes></Properties></DataSource>

        Now the policy is deployed succesvol Open-mouthed smile

        Rollup 3 for Exchange Server 2010 Service Pack 1

        exchange 2010

         

        Microsoft releasd Update Rollup 3 for Exchange Server 2010 SP1 that  resolves the following issues that are described in the following Microsoft Knowledge Base (KB) articles:

        2506998 A call is disconnected when transferring the call from the main auto attendant to an auto attendant that has a different language configured in an Exchange Server 2010 environmen

        2497682 The store.exe process crashes when you try to unmount an active copy of a mailbox database that is hosted by a mailbox server in an Exchange Server 2010 SP1 environmen

        2497669 A meeting request cannot be opened after you disable the "Display sender’s name on messages" option in the EMC on an Exchange Server 2010 server

        2494798 Certain email messages cannot be downloaded when you log on to an Exchange Server 2010 mailbox by using an IMAP4 client applicatio’n

        2494389 Unnecessary events are logged in the Application log when you run the "Test-EcpConnectivity" cmdlet in an Exchange Server 2010 environment

        2489822 "The Mailbox you are trying to access isn’t currently available" error when you use OWA Premium to try to delete an item that is in a shared mailbox

        2489713 Exchange Server 2010 SP1 supports the remote archive feature after an update changes Outlook cookies name

        2489602 The "Get-FederationInformation" cmdlet cannot query federation information from an external Exchange organization in an Exchange Server 2010 environment

        2487852 "You do not have sufficient permissions. This operation can only be performed by a manager of the group." error message when you try to change the "ManagedBy" attribute in an Exchange Server 2010 SP1 environment

        2487501 The body of an email message is empty when you try to use an IMAP client application to read it in an Exchange Server 2010 environment

        2484862 You cannot read an email message by using an IMAP client in an Exchange Server 2010 environment’

        2482471 A content search fails in an IMAP client application that connects to an Exchange Server 2010 mailbox

        2482103 It takes a long time to expand a distribution list by using EWS in an Exchange Server 2010 environment

        2482100 You cannot create or update an inbox rule that specifies the "NoResponseNecessary" value by using EWS in an Exchange Server 2010 environment

        2481283 Various issues occur after you use Outlook to sign and then forward an email message in an Exchange Server 2010 environment

        2479875 The Microsoft Exchange Mailbox Replication Service service crashes when you run the "New-MailboxImportRequest" cmdlet to import a .pst file into a mailbox in an Exchange Server 2010 environment

        2479227 Forwarding rule does not function and the EdgeTransport.exe process crashes on an Exchange Server 2010 server

        2476973 Event ID 2168 is logged when you try to back up Exchange data from a DAG in an Exchange Server 2010 SP1 environment

        2469341 Various issues occur after you forward a signed email message by using Outlook in online mode in an Exchange Server 2010 environment

        2468514 OWA 2010 removes Calendar links that you add into multiple calendar groups by using Outlook 2010 calendar

        2467565 You cannot install an update rollup for Exchange Server 2010 with a deployed GPO that defines a PowerShell execution policy for the server to be updated

        2464564 You cannot change your password if the user name that you type in OWA is in UPN format when you enable Exchange Server 2010 SP1 Password Reset Tool

        2463858 A request to join a distribution group does not contain the distribution group name in an Exchange Server 2010 SP1 environment

        2463798 Users may experience a decrease in performance in Outlook or in OWA when you use IMAP4 to access the calendar folder in an Exchange Server 2010 SP1 environment

        2458543 A memory leak occurs in the Exchange RPC Client Access service on Exchange Server 2010 servers

        2458522 Entries disappear from a junk email blocked list or a junk email safe list after you install Exchange Server 2010 SP1

        2457868 "HTTP Error 400 Bad Request" error message when you use OWA in Exchange Server 2010 SP1 to receive instant messages by using Internet Explorer 9

        2457688 Error message when you try to add an external email address to the safe sender list in OWA in an Exchange Server 2010 SP1 environment

        2457304 You receive a synchronization failed email message when you synchronize your mobile device by using ActiveSync on an Exchange Server 2010 mailbox

        2451101 7BIT is not in quotation marks when you use the "FETCH (BODYSTRUCTURE)" command to request for a specific message in an Exchange Server 2010 environment

        2447629 vent ID 4999 is logged when the Exchange Mail Submission Service crashes intermittently on an Exchange Server 2010 Mailbox server

        2445121 memory leak occurs in the Microsoft.Exchange.Monitoring.exe process when you run the "Test-OwaConnectivity" cmdlet or the "Test-ActiveSyncConnectivity" cmdlet in the EMS on an Exchange Server 2010 server

        2443688 Event ID 10003 and Event ID 4999 are logged when the EdgeTransport.exe process on an Exchange Server 2010 server crashes

        2432494 You cannot view the mailbox database copies that are hosted on certain Mailbox servers by using the Exchange Management Console after you install Exchange Server 2010 SP1

        2426952 You cannot remove a mailbox database copy from a database on an Exchange Server 2010 server

        2424801 The Microsoft Exchange Service Host service on an Exchange Server 2010 server crashes

        2423754 The recipient response status is incorrect after you add another user to an occurrence of a meeting request in an Exchange Server 2010 environment

        2417084 A public folder disappears from the Public Folder Favorites list of an Exchange Server 2010 mailbox

        2410571 A RBAC role assignee can unexpectedly change permissions of mailboxes that are outside the role assignment scope in an Exchange Server 2010 environment

        2398431 Using Pipelining in SMTP to check email addresses does not work correctly when you disable tarpitting functionality on a Receive connector in an Exchange Server 2010 environment

        2277649 You receive misleading information when you run the "New-TestCasConnectivityUser.ps1" script on an Exchange Server 2010 server

        2009942 Folders take a long time to update when an Exchange Server 2010 user uses Outlook 2003 in online mode

        You can download the update HERE

        Rollup 3 for Exchange Server 2007 Service Pack 3

        Exchange-server-2007_logoStacked

        Update Rollup 3 for Exchange Server 2007 SP3 resolves the issues that are described in the following Microsoft Knowledge Base articles:

        2498066 “Insufficient system resources exist to complete the requested service" error message when you try to extend database files in an Exchange Server 2007 environment

        2497679 A meeting request may not open correctly after you disable the "Display sender’s name on messages" option in the EMC of Exchange Server 2007 SP2 or SP3

        2493529 Event ID 1160 is logged and the Microsoft Exchange Information Store service randomly stops responding on an Exchange Server 2007 server

        2492384 A meeting response status from an external attendee may be incorrect if you send the meeting request from an Exchange Server 2007 environment

        2490788 A calendar synchronization times out when you use ActiveSync to synchronize with an Exchange Server 2007 mailbox on a mobile device

        2489898 An item is removed unexpectedly from a public folder in an Exchange Server 2007 environment

        2480197 The "Require SSL" setting is unexpectedly unselected on the RPC virtual directory on an Exchange Server 2007 server

        2479939 The "ScheduleOnlyDuringWorkHours" property of a resource mailbox may not function as expected in an Exchange Server 2007 environment

        2477139 DTMF inputs are not accepted by a UM auto attendant while the greeting message is playing in an Exchange Server 2007 environment

        2470759 The "Test-Replicationhealth" cmdlet fails on a stretched cluster in an Exchange Server 2007 SP3 CCR environment

        2461537 The Microsoft.Exchange.Search.ExSearch.exe process consumes 100% CPU after you apply Update Rollup 1 or Update Rollup 2 for Exchange Server 2007 SP3 on the passive node of a SCC

        2457838 "554 5.6.0" NDR message when you send an email message to an Exchange Server 2007 mailbox from a Macintosh computer

        2450078 The sent time in an email message body is incorrect when you reply or forward the email message by using an EWS application in an Exchange Server 2007 environment

        2448291 "Object has been corrupted and it is in an inconsistent state" warning message when you view a transport rule on an Exchange Server 2007 SP3 server

        2445129 (http://support.microsoft.com/kb/2445129/ ) The W3WP.exe process may crash when a WebDAV client connects to an Exchange Server 2007 server

        2418993 The Edgetransport.exe process crashes when you close a Telnet session before you receive an SMTP banner in an Exchange Server 2007 environment

        2410330 The EdgeTransport.exe process crashes if the pipeline tracing feature is enabled together with a redirect transport rule in an Exchange Server 2007 environment

        2408435 "Computer account for ‘SMTPSVC/’ not found in Active Directory." error message in an Exchange Server 2007 environment

        2394853 The returned URL is incorrect when you use the WebDAV "X-MS-ENUMATTS" method to enumerate an attachment in an Exchange Server 2007 environment

        2294143 Duplicate read receipts are sent when using a POP3 client or an IMAP4 client in an Exchange Server 2007 environment

        2267661 Some body parts of a message are displayed as attachments when an Exchange Server 2007 user sends the message by using a third-party mail client

        2032592 VSS backup fails on a passive node of an Exchange Server 2007 CCR cluster and Event ID 2034 is logged

        982714 The values of total items that are returned by running the "Export-ActiveSyncLog" cmdlet on an Exchange Server 2007 server are incorrect

        979338 Fax communication sessions are dropped by an Exchange Server 2007 Unified Messaging server

        955480 A meeting request is stamped as Busy instead of Tentative when it is sent from an external user to an Exchange Server 2007 user

        Download the Update HERE

        Autodiscover failed on Outlook 2007 client with error 0x800c8203 after installing KB2412171

        After installing KB2412171 on client computers I found another bug in this update.
        Normally Outlook configure your Outlook profile on your primarily smtp address. But after this update this is changed to the user principal name. If you have not added user principal name to a mail user you will see dat autodiscovery wil fail.

        Solution Uninstalling KB2412171

        %windir%\System32\msiexec.exe /package <Office 2007 product code> /uninstall <patch code for the MSP from KB2412171> /Q /L*V %temp%\Remove_KB2412171.log Product codes (or “GUIDs”) for Office 2007 and Outlook 2007 are as follows: Standard: {90120000-0012-0000-0000-0000000FF1CE} Professional: {90120000-0014-0000-0000-0000000FF1CE} Professional Plus:{90120000-0011-0000-0000-0000000FF1CE} Enterprise:{90120000-0030-0000-0000-0000000FF1CE} Outlook 2007 Standalone: {90120000-001A-0000-0000-0000000FF1CE} Patch codes for the MSP files related to KB2412171 are as follows: {7961E819-93A5-40A8-8469-4BE2FBBFACEF}  (for the original patch) {752A0B7C-BD24-4362-AC86-AB63FEE6F46F} (for the re-release patch)

        For my did this the trick
        %windir%\System32\msiexec.exe /package {90120000-0030-0000-0000-0000000FF1CE} /uninstall {752A0B7C-BD24-4362-AC86-AB63FEE6F46F} /Q /L*V c:\Remove_KB2412171.log

        Exchange 2010 Public Folder Database requirement

        Current Status: Issue with mitigation

        Unlike Outlook 2007 and 2010, Outlook 2003 clients rely on public folders. If a public folder database doesn’t exist, Outlook 2003 users will be blocked from connecting to their Exchange 2010 mailbox and receive the error message shown in Figure 8.


        Figure 8:
        Error message when an Outlook 2003 user connects to an Exchange 2010 mailbox

        There are several reasons why a public folder database is required for Outlook 2003 client. First, Outlook 2003 in cached mode uses the “OFFLINE ADDRESS BOOK” system folder to download the offline address book (OAB) and the “SCHEDULE+ FREE BUSY” to retrieve and update free/busy information.


        Figure 9:
        Offline Address Book and Schedule+ Free Busy system folders

        Second, if you’re installing Exchange 2010 into an existing Exchange organization running Exchange 2007, it’s important you add the Exchange 2010 public folder database to the replica list of the “SCHEDULE+ FREE BUSY” folder. If this step isn’t completed, users who use Outlook 2003 cannot publish their free/busy data in Exchange Server 2010. Instead hash marks appear in the free/busy data for these users. More information as well as the steps that can be used to remediate this issue can be found in the following KB article:

        Special Thanks to Henrik Walther

        Concern: Is having Outlook 2003 clients going to prevent me from deploying Exchange 2010

        OVERALL STATUS: No, having Oulook 2003 clients is not a deployment blocker. However, you need to understand the following sections and make configuration changes as applicable.

        Back since November 9th, 2009 where Exchange Server 2010 released to manufacturing (RTM), there have been a growing concern around whether enterprises are prevented from upgrading or migrating their current Exchange 2003 or Exchange 2007 based messaging infrastructure to Exchange 2010, if Outlook 2003 clients is used within the organization.

        But in  this article includes are a few additional concerns about Exchange 2010 and Outlook 2003

        Exchange 2010 lack support for UDP Notifications

        Exchange 2010 Exchange Server name appears as Instance – <GUID>

        Exchange 2010 & Outlook 2003 Offline Address Book (OAB)

        Exchange 2010 RPC over HTTP Connectivity

        Exchange 2010 Opening multiple shared calendars & additional mailboxes

        Exchange 2010 RPC Encryption Requirement

        Exchange 2010 Public Folder Database requirement

        exchange 2010

        Special Thanks to Henrik Walther

        Exchange 2010 lack support for UDP Notifications

        Current Status: Issue with mitigation


        Important
        With Exchange 2010 SP1 RU3 UDP notifications is being re-added to to Exchange 2010 (read more here). This means that the below symptoms will be resolved, once Exchange 2010 SP1 RU3 becomes available in March 2011.

        With Exchange Server 2010, there is no longer support for User Datagram Protocol (UDP) notifications. When opening a mailbox using Outlook 2003, Outlook 2003 tries to register itself to receive new message notifications. By default Outlook 2003 tried to register for UDP notifications but since this notification method isn’t supported with Exchange 2010, Outlook 2003 will instead revert to polling the Exchange server for changes in the mailbox. Despite the fact that Outlook 2003 initiates the polling behavior, the Exchange server will dictate the polling frequency. By default Outlook 2003 polls the Exchange server every 60 seconds.

        Since Exchange 2010 doesn’t support UDP based notifications, Outlook 2003 won’t be able to register itself using this method, which means changes made to any of the folders in the mailbox won’t be reflected before Outlook 2003 polls the Exchange server for changes. The result of this is that notifications about new messages etc. will be reflected in the Outlook 2003 client with delays of up to 60 seconds.
        More specifically, you will see the following symptoms:

        • Outgoing e-mail messages stay in the Outbox for up to 1 minute
        • New e-mail messages do not arrive in the Inbox for up to 1 minute
        • Items that are deleted from folders do not disappear from the folder for up to 1 minute
        • Items that are moved from one folder to another folder take up to 1 minute to disappear from the original folder

        Two methods exist to remediate the polling issue described above:

        Method 1: Change the Polling Frequency

        The issue can be remediated by installing Exchange 2010 Service Pack 1 which includes support for a new registry key that can be used to lower the polling frequency to 5 seconds.


        Figure 3:
        Lowering the polling frequency value


        Note
        The registry key doesn’t reinstate UDP in Exchange 2010; it only lowers the polling frequency.

        Method 2: Enable Cached Mode in Outlook 2003 Clients

        The cached mode synchronization process uses a different architecture to update folders versus Outlook 2003 clients in online mode. So another option is to enable cached mode for all Outlook 2003 clients within the organization.

        The following KB article describes the symptoms and remediation in detail:

        Update: Rollup 3 for Exchange 2010 SP1 is gereleased

        Special Thanks to Henrik Walther