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

VMware vCenter XVP Manager and Converter

    VMware vCenter XVP Manager and Converter provides basic virtualization management capabilities for non-vSphere hypervisor platforms towards enabling centralized visibility and control across heterogeneous virtual infrastructures. It also simplifies and enables easy migrations of virtual machines from non-vSphere virtualization platforms to VMware vSphere.

    Features

    • Management of the following Microsoft Hyper-V platforms:
      • Microsoft Hyper-V Server 2008
      • Microsoft Windows Server 2008 (64-bit) with Hyper-V role enabled
      • Microsoft Hyper-V Server 2008 R2
      • Microsoft Windows Server 2008 R2 with Hyper-V role enabled
    • Familiar vCenter Server graphical user interface for navigating through and managing non-vSphere inventory
    • Ease of virtual machine migrations from non-vSphere hosts to vSphere inventory
    • Compatible with VMware vCenter Server 4.0 & 4.1
    • Scalable up to management of 50 non-vSphere hosts

For more detailed information refer to the vCenter XVP Manager and Converter Technology Preview Release Notes and Installation Guide (included in zip file download).

VIDEO’s

Installation

Host Operations

Convert HyperV VMs to vSphere

Guest VM Operations inside HyperV

Download: HERE

VMware View 4.6 New Features

VMware released VMWare View 4.6

Updated Features:
Security servers can now accommodate PCoIP connections – Security servers now include a PCoIP Secure Gateway component. The PCoIP Secure Gateway connection offers the following advantages:

  • The only remote desktop traffic that can enter the corporate data center is traffic on behalf of a strongly authenticated user.
  • Users can access only the desktop resources that they are authorized to access.
  • No VPN is required, as long as PCoIP is not blocked by any networking component.
  • Security servers with PCoIP support run on Windows Server 2008 R2 and take full advantage of the 64-bit architecture.

Enhanced USB device compatibility – View 4.6 supports USB redirection for syncing and managing iPhones and iPads with View desktops. This release also includes improvements for using USB scanners, and adds to the list of USB printers that you can use with thin clients. For more information, see the list of View Client resolved issues.

Keyboard mapping improvements – Many keyboard-related issues have been fixed. For more information, see the list of View Client resolved issues.

New timeout setting for SSO users – With the single-sign-on (SSO) feature, after users authenticate to View Connection Server, they are automatically logged in to their View desktop operating systems. This new timeout setting allows administrators to limit the number of minutes that the SSO feature is valid for.
For example, if an administrator sets the time limit to 10 minutes, then 10 minutes after the user authenticates to View Connection Server, the automatic login ability expires. If the user then walks away from the desktop and it becomes inactive, when the user returns, the user is prompted for login credentials. For more information, see the VMware View Administration documentation.

VMware View 4.6 includes more than 160 bug fixes – For descriptions of selected resolved issues, see Resolved Issues.

Support for Microsoft Windows 7 SP1 operating systems (Not Experimental of RC wrong on the VMware site)

VDI Documentation
VMware View 4.6 Release Notes
VMware View Architecture Planning
VMware View Administration
VMware View Installation
VMware View Upgrades
VMware View Integration
View4_Marketecture_05

Exchange 2010 Opening multiple shared calendars & additional mailboxes

Current Status: Issue with mitigation

Exchange 2010 SP1 together with the resolutions mentioned later in this section, allows you to open as many as 16 shared calendars or additional mailboxes simultaneously independent on whether the mailboxes are located on Exchange 2003, 2007, or 2010. If you have more than 16 calendars or additional mailboxes opened, you may randomly see error message similar to the one shown in Figure 4.


Figure 4:
Error message when opening more than 16 calendars

With Exchange Server 2010 RTM deployed into an Exchange 2003 or Exchange 2007 organization, it was a common issue that when an Exchange 2003 or Exchange 2007 user tried to open more than two additional Exchange 2010 mailboxes or shared calendars using Outlook 2003, she would receive one of the following error messages:

  • The set of folders could not be opened
  • The information store could not be opened
  • Unable to display the folder. The information store could not be opened

When an Exchange 2007 user tried to send an e-mail using Outlook 2003, she would sometimes also receive the following error message:

  • Task ‘Microsoft Exchange Server – Sending’ reported error (0x800C8100): ‘Unknown Error 0x800c8100’

These issues were resolved with Update Rollup 2 for Exchange 2007 Service Pack 2 and a hotfix that were released for Exchange 2003 SP2. More information about the issues and how they are resolved can be found in the following KB articles:

    Although the above mentioned issues were resolved, some customers, partners, and individuals in the Exchange communities reported they still experienced issues when trying to open approximately multiple shared calendars and/or additional mailboxes using Outlook 2003.

    For most organizations, the issue can be remediated by installing Exchange 2010 SP1 as this service pack includes a fix that makes it possible for an Exchange 2003, 2007, or 2010 user to open as many as approximately 16 shared calendars or additional mailboxes using Outlook 2003.


    Figure 5:
    By default approximately 16 Calendars can be opened using Outlook 2003

    If you have users that needs to open more than 16 shared calendars or additional mailboxes using Outlook 2003, you can adjust the RPC related throttling policy settings using the Set-ThrottlingPolicy cmdlet. Specifically, you need to increase the value for “RCAMaxConcurrency” which by default is set to “20”. The RCAMaxConcurrency parameter indicates how many concurrent connections an RPC Client Access user can have against a server running Exchange 2010 at one time.


    Figure 6:
    Default setting for the RCAMaxConcurrency throttling policy value

    For instance, to increase the value of the “RCAMaxConcurrency” setting in the default throttling policy from 20 to 2147483647, open the Exchange Management Shell and run the following command to first create a variable for the policy:

    $a = Get-ThrottlingPolicy | where-object {$_.IsDefault -eq $true}

    Then pipe the variable to the Set-ThrottlingPolicy commandlet:

    $a | Set-ThrottlingPolicy -RCAMaxConcurrency 2147483647


    Figure 7:
    Increasing the value for the RCAMaxConcurrency throttling policy setting

    In order to apply the changes, restart the “Microsoft Exchange Throttling” service on each CAS server in the organization.

    You can read more about Exchange 2010 SP1 throttling policies in the Exchange 2010 documentation on Microsoft TechNet.

    If you still have issues opening shared calendars or additional mailboxes, you may want to increase the value of the RCAMaxConcurrency throttling policy setting to 100 or even higher. Read more in Error message when Outlook 2003 clients try to open multiple shared calendars in Exchange Server 2010: "The connection to the Microsoft Exchange server in unavailable. Outlook must be online or connected to complete this action".

    If you see event 4696 with a description similar to the following logged in the application log on the Mailbox servers in the organization:

    "Mapi session "00cc8dde-64d7-4353-8050-00fc2057aae3: /O=xxxx/OU=xxxx/cn=Recipients/cn=ward" exceeded the maximum of 32 objects of type "session"."

    You need to increase the maximum allowed sessions per user and/or maximum allowed service sessions per user limit from "32" to "64" or even higher. See more information at: Exchange 2010 SP1 Store Limits.

    but when I tried to add the “szMaxAllowedSessionsPerUser” and/or “szMaxAllowedServiceSessionsPerUser”, I still saw 9646 in the app log.

    Guess why? yes the registry keys are actually listed with wrong names in that article. Instead of:

    • szMaxAllowedSessionsPerUser
    • szMaxAllowedServiceSessionsPerUser

    You need to use:

    • Maximum Allowed Sessions Per User
    • Maximum Allowed Service Sessions Per User

    And then everything worked as expected…

    Hopefully the TechNet page is updated soon.

    Special Thanks to Henrik Walther

    Deploy office 2010 and a previous office version together on one PC with MDT 2010

    Deploy office 2010 and  a previous office version together on one PC with MDT 2010. Then you need to do the following things

    Needed.
    – Office 2010 ISO
    – Office 2010 Administrative Template files (ADM, ADMX/ADML) and Office Customization Tool

    1. Make sure you have a working Office 2007 deployment. Check this How to deploy Office 2007 with MDT

    2. Extract the Office 2010 ISO to the application folder on de MDT Server

    2. Extract AdminTemplates_32.exe or AdminTemplates_64.exe to a folder.

    3. Copy the Admin folder that you can find in the extracted folder to the Office 2010 folder that you created at step 1.

    4. Run setup.exe /admin

    5. Check the Screenshots for the settings
    imageimage
    imageimage

    6. Save the file in Updates folder that you find in Office folder. I named the file setup.MSP

    7. Create a new application without source files.

    imageimage
    imageimage
    image

    Command Line is:
    setup.exe /adminfile “\\mdtservername\deploymentshare$\Applications\Microsoft Office 2010 x86\Updates\setup.msp”

    Exchange 2010 RPC Encryption Requirement

    Current Status: Non-issue

    Exchange 2010 SP1
    With Exchange 2010 RTM, the RPC encryption requirement was an issue with mitigation. However, in Exchange Server 2010 Service Pack 1, the RPC encryption requirement has been disabled by default. This means that any new Exchange 2010 SP1 Client Access Servers (CAS) deployed in the organization won’t require encryption and Outlook 2003 clients will connect without the need to enable the RPC encryption feature in the Outlook profile.

    Important
    Having the RPC encryption requirement on an Exchange 2010 CAS server disabled doesn’t lower the security between Outlook 2007/2010 and any Exchange 2010 CAS server. RPC communication for these Outlook versions will remain encrypted as long as the client has the RPC encryption feature enabled. It’s only the requirement itself that is disabled on the Exchange 2010 CAS server.

    Exchange 2010 CAS servers deployed prior to Service Pack 1, or upgraded to Service Pack 1, will retain the existing RPC encryption requirement setting.

    Exchange 2010 RTM
    When upgrading or migrating an organization that fully or partly uses Outlook 2003 to Exchange 2010, we hear there are out of the box problems, when trying to connect an Outlook 2003 client to an Exchange 2010 RTM mailbox? We heard this is because an Exchange 2010 RTM Client Access Server by default requires an Outlook client to support RPC encrypted traffic in order to be able to connect.

    While it’s true the default configuration of an Outlook 2003 client doesn’t have support for RPC encryption, this requirement is fully supported with Outlook 2003.

    There are two methods that can be used in order to have Outlook 2003 clients connect to an Exchange 2010 RTM mailbox:

    Method 1: Enable the RPC encryption support in Outlook 2003

    If “Encrypt data between Microsoft Office Outlook and Microsoft Exchange Server” is enabled under the “Security” tab in the Outlook 2003 profile (see figure 1), the client will be able to connect to an Exchange 2010 RTM mailbox.


    Figure 1:
    RPC Encryption enabled in Outlook 2003

    If you are working with or for a small organization, it may be acceptable the end user enables this feature manually, but if you have thousands of users in the organization, you would want to enable it using a group policy (GPO). The steps necessary to implement a GPO to enable this setting are included in this KB article.


    Important

    The “EnableRPCEncryption” registry key mentioned in the KB article was originally introduced via a hotfix for Outlook 2003 SP2. This means that clients that either runs Outlook 2003 SP2 or an older version of Outlook 2003 doesn’t respect this registry key. In addition, Outlook 2003 clients not running SP3 are not supported by Microsoft.

    Method 2: Disable the RPC Encryption requirement on the Client Access Servers

    Instead of enabling support for RPC encryption in the Outlook 2003 profiles, you also have the option of disabling the requirement for RPC encryption on all Exchange 2010 RTM Client Access Servers in the organization.

    This can be accomplished using the Set-RpcClientAccess cmdlet:

    Set-RpcClientAccess –Server Exchange_server_name –EncryptionRequired $False


    Figure 2:
    RPC Encryption requirement disabled on Exchange 2010 CAS servers

    As mentioned earlier Exchange 2010 SP1 servers that hasn’t been upgraded from Exchange 2010 RTM has the RPC encryption requirement disabled by default.

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

    The core Exchange 2010 TechNet documentation also describes the configuration that can be used to remediate the issue:

    Important
    Unmanaged client machines cannot be controlled using GPOs or login scripts. If you have unmanaged machines connecting to Exchange 2010 using Outlook 2003, one solution would be to send those users a script or a registry file which they can run manually on their machine to enable the RPC encryption setting.

    Special Thanks to Henrik Walther

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

    Current Status: Issue – no issue

    A few customers, partners, and individual folks in the Exchange community have reported that a few of the Exchange 2010 users running Outlook 2003 randomly have issues connecting to their mailbox. After examining the mail profile in Outlook 2003, you can see the Exchange server name appears as Instance-<GUID> where <GUID> is a randomly generated GUID (or number). Re-resolving (‘Check Name’) the appropriate server name in the Outlook mail profile resolves the issue.


    Figure 11: Instance-GUID issue in Outlook 2003

    Note
    Seeing Instance-<GUID> in conversation between an Outlook 2003 client and an Exchange 2010 server is normal (when Instance-<GUID> appears inside Outlook in the folders list view on left hand side); It does NOT mean you are hitting this particular issue. You experience this issue if the Outlook mail profile gets updated to refer to the Exchange server as Instance-GUID.

    The problem behavior can be triggered by networking issues, patch applications, server reboots, etc. It requires Outlook 2003 to lose connectivity to Exchange and have a delegate mailbox logon attempted on a connection before the primary mailbox logon is attempted on that connection. This can affect users who are accessing shared mailboxes or folders of other users from their Outlook 2003 while connecting to Exchange 2010.

    Currently there is no proper resolution available for this issue. However, to remediate this issue temporarily, simply re-resolve the Exchange server name in the Outlook mail profile. If possible, you may also remove the shared mailboxes or shared folders (like calendars) from the profile, preventing this issue from occurring in the future or create a new mail profile in Outlook.

    Microsoft is working to investigate this issue for a fix. You can contact Microsoft Support to report this issue and request further assistance. Currently no KB article exists for this issue.

    Update:

    Microsoft has confirmed this to be a bug and the bug was assigned to the Outlook team within Microsoft. It has been fixed and a hotfix can be downloaded here: http://support.microsoft.com/kb/2510153

     

    Special Thanks to Henrik Walther & Jaap Wesselius

    Unable to connect from the View Client on Windows 7 to the View Connection Server after installing the patch kb2482017 or kb2467023

    This issue occurs when you have installed one of these Microsoft patches, 2482017 or 2467023.

    If you have already installed these patches, you can install VMware View Client (build 353760) or uninstall the Microsoft patches.

    If you have not installed these patches, delay the installation of the Microsoft patches until you have installed VMware View Client (build 353760).

    VMware View Client build 353760 has been tested on:

    • Windows 7 Enterprise 32 bit +  Internet Explorer 8
    • Windows 7 Enterprise 64 bit +  Internet Explorer 8
    • Windows 7 Home 32 bit +  Internet Explorer 8 

    The View Client patch can be downloaded from here. Enter your credentials, accept the EULA and download the appropriate file:

    • If you are using Windows 7 32-bit, use VMware-viewclient-4.5.0-353760.exe.
    • If you are using Windows 7 64-bit, use VMware-viewclient-x86_64-4.5.0-353760.exe.

    To apply this patch

    1. Click Start > Settings > Control Panel > Add or Remove Programs.
    2. Choose the previously installed VMware View Client and click Remove.
    3. Navigate to where you downloaded VMware-viewclient-xxx-4.5.0-353760.exe and run the executable file.
    4. Follow the installation installation wizard to complete installation.
    5. Reboot the computer.

    Very Important: VMware View Clients with build number 353760 or later are not affected by this issue.

    SCVMM RDS Connection Broker plugin released

    SCVMM RDV plug-in enables dynamic placement of VDI VMs for both personal and pooled VMs. The key benefit of using this plug-in is that it reduces the number of Hyper-V servers required since VMs are placed on demand rather than statically placed.  Dynamic placement is achieved by integrating SCVMM 2008 R2 with the RDS Connection Broker in Windows Server 2008 R2.

    Dynamic Placement for Personal VM is available in Windows Server 2008 R2. Pooled VM requires Windows Server 2008 R2 SP1.

    Figure below shows the integration:

    The bits and content are available at: http://go.microsoft.com/fwlink/?LinkID=195952

    For those of you that don’t understand how this works Ill write a little process workflow so you understand.

    1. The VDI client tries to connect to the last VM it was using via the Connection Broker.

    2. The Broker, knowing where it was in the cluster, in communication with SCVMM, tries to wake the VM from a save state

    3. Problem is that the server its trying to start the VM on is already at capacity and it cant start there

    4. SCVMM gets involved as part of this and moves the VM to another node in the cluster based on its dynamic placement algorithm, via a SAN move

    5. The Connection Broker is then told which host the VM is now on and running

    6. The user connects to the VM

    Nice huh Winking smile

    Microsoft Desktop Virtualization is going to be a real competitor against VMware View

    Translate »