2012 RDS + VDI users unable to connect

environment:  2 2012 Hosts, connection broker + rdweb (same vm), no gateway, all 2012 OS.  Standard deployment on the 2 hosts.
I have a 2012 RDS installation of personal VDI.  Users connect to the RDweb server and launch their assigned VDI from there.  Users are experiencing random connection issues when connecting to their VDI via the RDWeb portal.  Here are some
events in the logs:
Event 8964 Remote Desktop Virtualization Host failed to process the orchestration request because virtual desktop [VM7REMSBUCJ] is busy processing cleanup from previous logoff event.
Event 8467 Remote Desktop Virtualization Host failed to get redirection authentication information from the virtual machine [VM7REMSBUCJ] .
The events above correspond with a remote users attempting to login in the morning to a VDI with a state of shutdown.

This isn't the best forum for 2012 Server or RDS.  This is specific to Virtual Server 2005.
Try reposting in Server 2012, or an RDS/VDI forum like one of these:
https://social.technet.microsoft.com/Forums/windowsserver/en-us/home?category=windowsserver

Similar Messages

  • Users unable to connect to RDP farm. (2 session servers 1 broker)

    Issue: Users are unable to connect to the farm when they use tsfarm.mydomain.com to access our servers. On the connection broker server I get lots of: This connection request has timed out. User could not log on to the end point within the
    alloted time. Remote Desktop Connection Broker will stop monitoring this connection request.
    On one of the session servers I get the following:
    Session state for user DOMAIN\Firstname.Lastname changed to: Session Reconnected.
    Target Name = SESSION2.domain.com
    Farm Name = tsfarm.mydomain.com
    Session ID = 8
    It looks like they're getting connected, but this doesn't work either.
    Server Environment
    All servers are Windows 2008 R2 Datacenter SP1
    Connection Broker: CONNECT1
    Session Servers: SESSION1, SESSION2
    External DNS has the following records:
    tsfarm.mydomain.com points to external (NAT) IP for SESSION1
    tsfarm.mydomain.com points to external (NAT) IP for SESSION2
    User Environment
    Almost all my users use Windows 7 running version 6.1 client with protocol version 7.1

    Hi,
    Correct.
    In the Remote Desktop Client, Advanced tab, Connect from anywhere, Settings, they would select Use these RD Gateway server settings, enter
    rdgateway.yourdomain.com (or whatever FQDN you want to use for your RDG).  Then on the General tab they would enter tsfarm.yourdomain.com in the Computer box.
    On the public Internet you would create a DNS A record for rdgateway.yourdomain.com that points to the public ip address for the RDG.  On your firewall you would forward TCP port 443 to the RDG server.
    On your internal network you would create 2 DNS A records for tsfarm.yourdomain.com that point to your RDSH servers.  Based on what you have written I believe you have already created these DNS records for your farm name.
    As a side note you may consider installing RD Web Access on the same server as your RD Gateway server.  That way if you want (it is not required) you could have your users log on to RD Web Access and launch a RemoteApp or a full desktop connection to
    your RDSH farm.
    You will need a certificate (or certificates) from a trusted public authority such as GoDaddy, GeoTrust, Thawte, VeriSign, etc.  One option is to get a wildcard (*.yourdomain.com) which you may use for all RDS purposes (Broker, RDG, RDWeb,
    RDSH, Digital signing).  A second option would be to get multiple single-name certificates.  For example, one certificate with subject rdgateway.yourdomain.com and a second certificate with subject of tsfarm.yourdomain.com.
    For planning purposes keep in mind that if you have RD Gateway and RD Web on the same server they will use the same certificate.  So if you were to use a single-name certificate for RD Gateway of rdgateway.yourdomain.com then your users would need to
    access RDWeb using rdgateway.yourdomain.com.  If you choose a wildcard you have maximum flexibility to use different names for each purpose since it is all the same certificate.
    -TP

  • SSRS 2012 with SharePoint 2010: Unable to connect to the remote server

    We had originally installed SSRS 2012 with SP 2010 and I did not like how the installation was configured, so we uninstalled everything and removed the SSRS server from the SharePoint farm and uninstalled all the SQL bits (SSRS was deployed to web tier in
    sharepoint mode).
    I've since added a new application server to host the SSRS SharePoint Mode and Installed the reporting services add-in on the WFE.   For reference, I have 1 WFE and 2 App Servers.  the WFE has the Reporting Service Add-in and both App Servers have
    the SharePoint mode of SSRS installed as described here: https://msdn.microsoft.com/en-us/library/hh479774(v=sql.110).aspx
    I've also installed the Service Application and all seems to work well up until I make an attempt to create a report or data source on the WFE.
    It looks like somewhere, the WFE is still looking to connect to the original SSRS machine we installed.  I've gone through registry, config files and the SharePoint config database to see if I can see where the reference value is.  Still can't
    find it anywhere.  None of the Reporting commandlets are helping.
    Technically what is occurring;
    Add Reporting service content types and create a New Reporting Data Source through UI
    ULS Logs go after the url: /_layouts/ReportServer/NewSharedDataSource.rsds
    Exception occurs after some time because it times out trying to connect to wrong host.  Exception below:
    Exception encountered for SOAP method GetSystemProperties: System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond <WRONG HOST IP>:80
    at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
    at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Int32 timeout, Exception& exception) -
    -- End of inner exception stack trace ---
    at Microsoft.SqlServer.ReportingServices2010.RSConnection2010.SetConnectionProtocol()
    at Microsoft.SqlServer.ReportingServices2010.RSConnection2010.SoapMethodWrapper`1.ExecuteMethod(Boolean setConnectionProtocol)
    No powershell commands or any of the settings in the service application allow me to set this.  Any help would be appreciated.
    20 Bay Windows Home Server (Not Vail!)
    http://piroozjavan.blogspot.com/

    Issue an iisreset on the WFE, and validate that SSRS Service is running on the App servers.
    Trevor Seward
    Follow or contact me at...
    &nbsp&nbsp
    This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

  • OD users unable to connect to a server via afp

    We have a Mac OS 10.9.2 with Server 3.1.2.  We are able to access the server for file sharing via smb with OD accounts just fine.  But we are unable to connect to the server using afp with any OD account, only local system accounts.  I have tried turning off SMB for all of the file shares, but this did not help resolve the issue.
    The log shows a login attempt immediately followed by a logout.
    Aug  7 13:40:33 server.company.com AppleFileServer[736] <Info>: IP 192.168.101.2 - - "Login -----" -5023 0 0
    Aug  7 13:40:33 server.company.com AppleFileServer[736] <Info>: IP 192.168.101.2 - - "Logout -----" -5023 0 0
    I did edit out the user and the server name.
    Any help would be greatly appreciated.
    Thank you.

    Many Open Directory problems can be resolved by taking the following steps. Test after each one, and back up all data before making any changes.
    1. The OD master must have a static IP address on the local network, not a dynamic address.
    2. You must have a working DNS service, and the server's hostname must match its fully-qualified domain name. To confirm, select the server by name in the sidebar of the Server application window, then select the Overview tab. Click the Edit button on the Host Name line. On the Accessing your Server sheet, Domain Name should be selected. Change the Host Name, if necessary. The server must have at least a three-level name (e.g. "server.yourdomain.com"), and the name must not be in the ".local" top-level domain, which is reserved for Bonjour.
    3. The primary DNS server used by the server must be 127.0.0.1 (that is, itself) unless you're using another server for internal DNS. The only DNS server set on the clients should be the internal one, which they should get from DHCP if applicable.
    4. Follow these instructions to rebuild the Kerberos configuration on the master.
    5. If you use authenticated binding, check the validity of the master's certificate. The common name must match the hostname and domain name. Deselecting and then reselecting the certificate in Server.app has been reported to have an effect in some cases.
    6. Unbind and then rebind the clients in the Users & Groups preference pane. Use the fully-qualified domain name of the master.
    7. Reboot the master and the clients.
    8. Don't log in to the server with a network user's account.
    9. As a last resort, export all OD users. In the Open Directory pane of Server, delete the OD server. Then recreate it and import the users. Ensure that the UID's are in the 1001+ range.

  • User unable to connect to new access point AIR-CAP3502P-S-K9

    Hi Guys,
              In my branch there are 8 access points[ AIR-CAP3502I-S-K9 ] connected to Wireless controller which is been working fine since the beginning.. I had to add two more access points to this branch and after the failure, i realised this Access point [ AIR-CAP3502P-S-K9 ] is latest and it needs the minimum image 7.3.101.. So i did a upgrade on WLC 5508 and all 10 access points have joined successfully...
    Issue am facing is when NEW users come under AP 9 and AP 10 get associated successfully, but the old users(Projetc Manager) who been in the branch for very long and able to get associated with other AP's [1 to 8] gets associated successfully with all old AP's but not with the new AP's..
    Could please some one advise, why this strange behaviour... I googled for answer but am not getting any right solution...

    Issue am facing is when NEW users come under AP 9 and AP 10 get associated successfully, but the old users(Projetc Manager) who been in the branch for very long and able to get associated with other AP's [1 to 8] gets associated successfully with all old AP's but not with the new AP's..
    Do you have AP Groups configured? 
    The old wireless clients, are their drivers up to date?

  • User unable to connect wireless network with errors APF-1-USER_ADD_FAILED

    there are many events logs related to user add failed today, can anyone please help to explain what is this error message about?
    Thanks.
    Sep 29 10:02:28.091 apf_ms.c:4776 APF-1-USER_ADD_FAILED: Unable to create username ASIA-PACIFIC\Surya_Dharamdass for mobile00:24:2b:a0:e2:49
    Sep 29 10:02:28.083 apf_ms.c:4776 APF-1-USER_ADD_FAILED: Unable to create username ASIA-PACIFIC\Hour_Sou_Cheng for mobile18:3d:a2:3b:6e:8c
    Sep 29 10:02:27.970 apf_ms.c:4776 APF-1-USER_ADD_FAILED: Unable to create username ASIA-PACIFIC\Sherene_Chan for mobile00:23:4d:1a:56:ac
    Sep 29 10:02:27.895 apf_ms.c:4776 APF-1-USER_ADD_FAILED: Unable to create username ASIA-PACIFIC\Kai_Choo_Wong for mobile18:3d:a2:25:e5:2c
    Sep 29 10:02:27.786 apf_ms.c:4776 APF-1-USER_ADD_FAILED: Unable to create username ASIA-PACIFIC\Madhura_Marippan for mobilef0:7b:cb:73:3d:4d

    This error indicates that the controller was unable to create a username entry internally for this mobile device, it could be a number of things that are causing this. \
    Is this a new issue or has this been happening for sometime?
    Is this a new network or has it been in production for some time?
    Is this happening to every client?
    What type of security on the SSID in question?

  • Users unable to connect to application for few minutes

    Dear All,
    Sometimes new users are not able to connect to ERP production application for few minutes. Moreover connected users are running fine.
    No errorr were found at Concurrent Manager and Oracle Database. Two Node Application (Web & Forms at one Node) & (Concurrent & Database at other Node)
    Errors are generated at the error_log.1362009600 log file as follows
    [Thu Feb 28 15:30:45 2013] [error] [client 200.0.1.237] mod_security: Access denied with code 400. Pattern match "!^([-_@|#!=A-Za-z0-9/ :.$]){0,255}([-_@|#!=A-Za-z0-9/ :.$]){0,255}$" at ARGS_NAMES. [hostname "%"] [uri "/oprocmgr-service"] [unique_id US-FfcgAAeIAogBcCOA]
    Errors are generated at the error_log.1362009600 log file as follows
    appnode_prst - "" [28/Feb/2013:15:30:54 -0530] "GET /pls/PROD/fnd_icx_launch.launch?resp_app=ONT&resp_key=FPL+MKG+PRODUCT+OM+USER+WEST&secgrp_key=STANDARD&start_func=JAINEORD_FUN&other_params= HTTP/1.0" 302 0 1
    appnode_prst - "" [28/Feb/2013:15:30:59 -0530] "GET /pls/PROD/fnd_icx_launch.runforms?ICX_TICKET=&resp_app=ONT&resp_key=FPL%20MKG%20PRODUCT%20OM%20USER%20WEST&secgrp_key=STANDARD&start_func=JAINEORD_FUN&other_params= HTTP/1.0" 302 0 1
    appnode_prst - "" [28/Feb/2013:15:31:40 -0530] "GET /pls/PROD/fnd_icx_launch.launch?resp_app=PO&resp_key=FPL+MKG+PRODUCT+PR+USER&secgrp_key=STANDARD&start_func=MOVE+ORDERS+CUSTOM&other_params= HTTP/1.0" 302 0 0
    appnode_prst - "" [28/Feb/2013:15:31:48 -0530] "GET /pls/PROD/fnd_icx_launch.runforms?ICX_TICKET=&resp_app=PO&resp_key=FPL%20MKG%20PRODUCT%20PR%20USER&secgrp_key=STANDARD&start_func=MOVE%20ORDERS%20CUSTOM&other_params= HTTP/1.0" 302 0 0
    appnode_prst - "" [28/Feb/2013:15:31:53 -0530] "GET /pls/PROD/fnd_icx_launch.launch?resp_app=GMI&resp_key=FPL+MKG+14+INCH+FG+YARD+USER&secgrp_key=STANDARD&start_func=FPL_MM_NOTES_PIPE&other_params= HTTP/1.0" 302 0 0
    appnode_prst - "" [28/Feb/2013:15:31:57 -0530] "GET /pls/PROD/fnd_icx_launch.runforms?ICX_TICKET=&resp_app=GMI&resp_key=FPL%20MKG%2014%20INCH%20FG%20YARD%20USER&secgrp_key=STANDARD&start_func=FPL_MM_NOTES_PIPE&other_params= HTTP/1.0" 302 0 0
    Your Suggestions are Welcome
    Regards
    Surinder Singh
    Edited by: Surinder Singh on Feb 28, 2013 3:59 PM

    Sometimes new users are not able to connect to ERP production application for few minutes. Moreover connected users are running fine. What is the error they get?
    No errorr were found at Concurrent Manager and Oracle Database. Two Node Application (Web & Forms at one Node) & (Concurrent & Database at other Node)
    Errors are generated at the error_log.1362009600 log file as follows
    [Thu Feb 28 15:30:45 2013] [error] [client 200.0.1.237] mod_security: Access denied with code 400. Pattern match "!^([-_@|#!=A-Za-z0-9/ :.$]){0,255}([-_@|#!=A-Za-z0-9/ :.$]){0,255}$" at ARGS_NAMES. [hostname "%"] [uri "/oprocmgr-service"] [unique_id US-FfcgAAeIAogBcCOA]
    Errors are generated at the error_log.1362009600 log file as follows
    appnode_prst - "" [28/Feb/2013:15:30:54 -0530] "GET /pls/PROD/fnd_icx_launch.launch?resp_app=ONT&resp_key=FPL+MKG+PRODUCT+OM+USER+WEST&secgrp_key=STANDARD&start_func=JAINEORD_FUN&other_params= HTTP/1.0" 302 0 1
    appnode_prst - "" [28/Feb/2013:15:30:59 -0530] "GET /pls/PROD/fnd_icx_launch.runforms?ICX_TICKET=&resp_app=ONT&resp_key=FPL%20MKG%20PRODUCT%20OM%20USER%20WEST&secgrp_key=STANDARD&start_func=JAINEORD_FUN&other_params= HTTP/1.0" 302 0 1
    appnode_prst - "" [28/Feb/2013:15:31:40 -0530] "GET /pls/PROD/fnd_icx_launch.launch?resp_app=PO&resp_key=FPL+MKG+PRODUCT+PR+USER&secgrp_key=STANDARD&start_func=MOVE+ORDERS+CUSTOM&other_params= HTTP/1.0" 302 0 0
    appnode_prst - "" [28/Feb/2013:15:31:48 -0530] "GET /pls/PROD/fnd_icx_launch.runforms?ICX_TICKET=&resp_app=PO&resp_key=FPL%20MKG%20PRODUCT%20PR%20USER&secgrp_key=STANDARD&start_func=MOVE%20ORDERS%20CUSTOM&other_params= HTTP/1.0" 302 0 0
    appnode_prst - "" [28/Feb/2013:15:31:53 -0530] "GET /pls/PROD/fnd_icx_launch.launch?resp_app=GMI&resp_key=FPL+MKG+14+INCH+FG+YARD+USER&secgrp_key=STANDARD&start_func=FPL_MM_NOTES_PIPE&other_params= HTTP/1.0" 302 0 0
    appnode_prst - "" [28/Feb/2013:15:31:57 -0530] "GET /pls/PROD/fnd_icx_launch.runforms?ICX_TICKET=&resp_app=GMI&resp_key=FPL%20MKG%2014%20INCH%20FG%20YARD%20USER&secgrp_key=STANDARD&start_func=FPL_MM_NOTES_PIPE&other_params= HTTP/1.0" 302 0 0
    Your Suggestions are Welcome What about access_log file?
    Can you reproduce the issue after running AutoConfig?
    If you are on 11i, please make sure you have (Patch 9535311: TXK AUTOCONFIG AND TEMPLATES ROLLUP PATCH U) applied.
    Thanks,
    Hussein

  • Windows 2012 RDS CALs - OLP NL downgrade to Windows 2003 TS CALs

    Hi,
    Hope someone can shed some light on this inquiry
    I plans to purchase the following:
     2x Windows 2014 SQL STD 2 Core License OLP NL
     30 Windows 2012 RDS CALs (User or Device) OLP NL
               Breakdown example
                Site A = 10 
                Site B = 5
                Site C = 15
    Existing servers are Windows 2003 R2 STD running Terminal Services
    Tried setting up a Windows 2003 R2 TS Server and install TS Roles & Licensing Manager
    Questions.
     1. When I tried to add Windows 2003 TS CALs - OLP NL, the activation screen requires to enter the Authorization & License numbers.
     Can I use the Authorization and License number of the newly purchased Windows 2012 RDS CALs on the Windows 2003 TS Server?
     2. Should I get a separate Authorization & License number per site? (In the example above 3x Authorization & License numbers). Or can we use a single Authorization & License number for all sites? Each site is independent from each
    other.
     3. As I understand, SQL 2014 can be downgraded to any prior previous version at the same editions. (as far as SQL 2000, provided he has the installer), If client has an existing SQL 2003 STD activated already, does he need to change the license key?
    Thanks,
    Paul

    Hi Paul,
    Thank you for posting in Windows Server forum.
    Yes, you can use newly purchased server 2012 RDS CAL on server 2003 terminal server. 
    RDS and TS CAL Interoperability Matrix
    For detail regarding the licensee issue I suggest you to contact MS Volume Licensing.
    As per my research, I think you don’t have to change the old license key if client already have the key. And in regards to SQL server you can have a look over beneath article.
    SQL Server 2014 
    Hope it helps!
    Thanks.
    Dharmesh Solanki

  • Unable to Connect to: sysadmin@ my_Database

    Hello all,
    I am new to Oracle and for the past several days I have been trying to login to an Oracle apps database (11.5.10) through Discover desktop. I get the following error when trying to login as an application user
    Unable to Connect to: sysadmin@<my_Database>
    Failed to connect to database - Unable to connect to Oracle Applications database: invalid username/password.
    I successfully installed Discoverer Administrator and Desktop clients (9.0.4). I also was able to login to Discoverer Administrator and successfully created an EUL with the "grant access to public" and "New EUL is for use by Oracle Applications users ONLY" options selected. I added a simple business area and granted the appropriate Security and Privileges to SYSADMIN.
    I have looked all over and havent found anything that has helped.
    Thank in advance
    Maro

    Hi Russ
    Actually, in Discoverer 10.1.2 this setting is only required for Desktop and only if Apps is running in secure mode, HTTPS, which is quite common. For the web versions, Plus and Viewer, this setting is picked up from the OPMN.XML file which is located here:
    On UNIX: <ORACLE_HOME>/opmn/conf/opmn.xml
    On Windows: <ORACLE_HOME>\opmn\conf\opmn.xml
    By default, in OPMN.XML there should be a setting called FND_SECURE which should point to the folder referred to by Magesh:
    "C:\oracle\BIToolsHome_1\discoverer\secure"
    In fact the line should look like this:
    <variable id="FND_SECURE" value="C:\oracle\BIToolsHome_1\discoverer\secure"/>
    where the $ORACLE_HOME for where the Discoverer server is installed being embedded like this: C:\oracle\BIToolsHome_1
    However, we still have to make sure that the secure files, those ending in DBC, are in fact located here. As Mugesh points out these can be found on the E-Business Suite server here:
    $FND_TOP/secure
    Discoverer will first attempt to find a secure DBC file with the filename <database name>.dbc. If not found, Discoverer will then attempt to use a file with the filename <host name>_<SID>.dbc.
    By the way, if there is nothing defined for FND_SECURE, Discoverer will attempt to use the value specified by FND_TOP, which is the setting used by previous versions of Discoverer. In those installs, the DBS files would be located in the $ORACLE_HOME\Discoverer folder itself, not in a separate folder called secure.
    By the way, the service name in tnsnames.ora and dbc file name should be same <service name>.dbc
    You might find this link to be of use:
    http://download-east.oracle.com/docs/cd/B14099_19/bi.1012/b13918/con_files.htm
    Best wishes
    Michael

  • Unable to Connect to Face Time Server

    I see this issue has been discussed at great length, but mostly in 2012.
    I am unable to connect with the Face Time server on my iPad.  The generation of my iPad is current.  I am connected ti WiFi.  My time zone is correct on the iPad.  Unable to connect.
    It appears as though there have been "server issues" with Face Time over recent months.  Are those issues continuing as of the present?  If not, what do I have to do in order to connect to the Face Time server?

    Hello there, PDMike.
    The following Knowledge Base article has some great information to help with troubleshooting Facetime connectivity and Wi-Fi connectivity issues:
    iOS: Troubleshooting FaceTime
    http://support.apple.com/kb/ts3367
    It seems you've covered the "Troubleshooting Facetime" portion, but feel free to review the instruction there. Additionally the "Wi-Fi Network Issues" has more great information to review:
    Wi-Fi network issues
    If you encounter issues using a Wi-Fi network, use standard Wi-Fi network troubleshooting to resolve interference and other issues.
    If you are using router, firewall, or security software that restricts Internet access, verify that the ports documented in Using FaceTime behind a Firewall are open.
    FaceTime requires a broadband connection. Performance may vary according to network throughput and usage.
    Thanks for reaching out to Apple Support Communities.
    Cheers,
    Pedro D.

  • [Forum FAQ] "Unable to connect to the server by using Windows PowerShell Remoting" error while installing RDS roles on Server 2012 R2

    When you try to install RDS role on server 2012 R2 using standard deployment, this issue may occur (Figure 1).
    “Unable to connect to the server by using Windows PowerShell remoting”.
    Figure 1: Unable to connect to the server by using Windows PowerShell remoting
    First of all, we need to verify the configurations as it suggested:
    1. The server must be available by using Windows PowerShell remotely.
    2. The server must be joined to a domain.
    3. The server must be running at least Windows Server 2012 R2.
    4. The currently logged on user must be a member of the local Administrators group on the server.
    5. Remote Desktop Services connections must be enabled by using Group Policy.
    In addition, we need to check if the “Windows Remote Management “service is running and related firewall exceptions have been created for WinRM listener.
    To enabling PowerShell remoting, we can run this PowerShell command as administrator (Figure 2).
    Enable-PSRemoting -Force
    Figure 2: Enable PowerShell Remoting
    However, if issue persists, we need to check whether it has enough memory to work.
    By default, remote shell allots only 150 MB of memory. If we have IIS or SharePoint App pool, 150 MB of memory is not sufficient to perform the remoting task. Therefore, we need to increase
    the memory via the PowerShell command below:
    Set-Item WSMan:\localhost\Shell\MaxMemoryPerShellMB 1000
    Then, you need to restart the server and the issue should be resolved.
    You can get more information regarding Remote Troubleshooting by below link:
    about_Remote_Troubleshooting
    If you need further assistance, welcome to post your questions in the
    RDS forum.
    Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

    i found another possible reason, this solution worked for me:
    http://oyvindnilsen.com/solution-for-powershell-remoting-error-it-cannot-determine-the-content-type-of-the-http-response-from-the-destination-computer/
    I tried to set up powershell remoting on a server and kept getting this error:
    Enter-PSSession : Connecting to remote server failed with the following error message : The WinRM client cann
    ot process the request. It cannot determine the content type of the HTTP response from the destination comput
    er. The content type is absent or invalid. For more information, see the about_Remote_Troubleshooting Help to
    pic.
    After a bit of troubleshooting I discovered that the problem was that the authentication packets was to big (over 16k), this will cause WinRM to reject the request. The reason for authentication packets getting too big can be because the user is member of very
    many security groups or in my case because of the SidHistory attribute.
    The solution was to increase the MaxFieldLength and MaxRequestBytes keys in the registry under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\HTTP\Parameters
    If the keys does not exists you can create them, be sure to use the DWORD type.
    I sat MaxFieldLength to DEC value 40000 and MaxRequestBytes to DEC value 32768 and rebooted the server. Problem solved.

  • Remote Desktop Connection Client 9.3.9600 unable to connect to Server 2012 RDS via Gateway

    Hi,
    I have a Windows Sever 2012 R2 RDS environment with two Gateways servers configured in high availability mode (RD Web Access, RD Gateway, RD Connection Broker roles installed) and four Windows Server 2012 R2 RDS Session Hosts. The servers are all running
    the most recent public server updates. With this configuration I when connecting externally using a Windows 7 computer with the older Remote Desktop Connection client (6.1.7601) I am able to connect without any problems however when I try connecting with a
    newer client from a computer running Windows 8.1 and the 9.3.9600 client I am unable to connect. 
    At the moment a NAT rule is configured to pass 80/443 traffic to only one of the RDS gateway servers, I've removed our load balancer from the configuration for the moment to reduce the complexity. 
    No error is generated by the client when it tries to connect it just stops trying to connect after a while.
    On the Gateways servers event logs for 
    Things I have looked into so far.
    - I've double and triple checked the RDS configuration and checked it against one of my other clients configurations that is working and they are identical. 
    - Connecting from an older client version works fine.
    I'm not sure what else can be checked does anyone have any ideas?

    Hi,
    1. What entries are you seeing in the RD Gateway's log?  Event Viewer\ Applications and Services Logs\ Microsoft\ Windows\ TerminalServices-Gateway
    2. How come you are not forwarding UDP port 3391 in addition to TCP port 443?  It should work without UDP, but you will not have UDP support which is one of the benefits of RDP 8.0/8.1.
    3. Are there any non-default group policy settings being applied to the servers and/or client PCs?  To be clear, I'm asking if any changes have been made to the default local and domain security policies, group policy objects, new GPOs that may have
    been added, etc., that are applicable to the servers and or client PCs.
    -TP

  • Database Error (maybe) while working on User-Role or Assiging a Cloud (Unable to connect to the VMM database because of a general database failure)

    Hi,
    Suddenly I got this error in SCVMM 2012-R2 Roll-up 1:
    When working with User-Roles (create/update) or assigning a Cloud :
    "VMM encountered a critical exception and created an exception report....
    search user forums for well-known failure root causes for self-help" (how sweet)... (if it's "well known", why not coding the exception handling correctly?)
    The relevant part of the report might be this:
    "SCVMM Version=3.2.7620.0
    SCVMM flavor=C-buddy-RTL-AMD64
    Default Assembly Version=3.2.7620.0
    Executable Name=vmmservice.exe
    Executable Version=3.2.7510.0
    Base Exception Target Site=140717670746840
    Base Exception Assembly name=System.Data.dll
    Base Exception Method Name=System.Data.SqlClient.SqlConnection.OnError
    Exception Message=Unable to connect to the VMM database because of a general database failure.
    Ensure that the SQL Server is running and configured correctly, then try the operation again."
    (side question: what does this mean: "Ensure that the SQL Server is ... configured correctly"?
    I can say that :
    SQL is configured by the book, that all services are running (did a reboot of VMM server too) and that all other VMM functions work OK. I don't believe that SQL is only used for user-roles...
    Acting as Domain admin and VMM admin.
    All updates are installed.
    Please find the report @the and and a screen shot attached.
    Thanks for any help.
    Report.txt:
    ------------------- Error Report -------------------
    Error report created 03.04.2014 15:07:56
    CLR is not terminating
    --------------- Bucketing Parameters ---------------
    EventType=VMM20
    P1(appName)=vmmservice.exe
    P2(appVersion)=3.2.7620.0
    P3(assemblyName)=Utils.dll
    P4(assemblyVer)=3.2.7620.0
    P5(methodName)=Microsoft.VirtualManager.DB.SqlRetryCommand.ExecuteNonQuery
    P6(exceptionType)=Microsoft.VirtualManager.DB.CarmineSqlException
    P7(callstackHash)=4c11
    SCVMM Version=3.2.7620.0
    SCVMM flavor=C-buddy-RTL-AMD64
    Default Assembly Version=3.2.7620.0
    Executable Name=vmmservice.exe
    Executable Version=3.2.7510.0
    Base Exception Target Site=140717670746840
    Base Exception Assembly name=System.Data.dll
    Base Exception Method Name=System.Data.SqlClient.SqlConnection.OnError
    Exception Message=Unable to connect to the VMM database because of a general database failure.
    Ensure that the SQL Server is running and configured correctly, then try the operation again.
    EIP=0x00007ffb74c75a88
    Build bit-size=64
    ------------ exceptionObject.ToString() ------------
    Microsoft.VirtualManager.DB.CarmineSqlException: Unable to connect to the VMM database because of a general database failure.
    Ensure that the SQL Server is running and configured correctly, then try the operation again. ---> System.Data.SqlClient.SqlException: Procedure or function prc_RBS_UserRoleSharedObjectRelation_Insert has too many arguments specified.
       at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
       at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
       at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)
       at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
       at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async, Int32 timeout, Task& task, Boolean asyncWrite, SqlDataReader ds)
       at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, TaskCompletionSource`1 completion, Int32 timeout, Task& task, Boolean asyncWrite)
       at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(TaskCompletionSource`1 completion, String methodName, Boolean sendToPipe, Int32 timeout, Boolean asyncWrite)
       at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
       at Microsoft.VirtualManager.DB.SqlRetryCommand.ExecuteNonQuery()
       --- End of inner exception stack trace ---
       at Microsoft.VirtualManager.DB.SqlRetryCommand.ExecuteNonQuery()
       at Microsoft.VirtualManager.DB.DelegatedAdmin.UserRoleDBHelper.<>c__DisplayClass15.<AddObjectSharingData>b__14()
       at Microsoft.VirtualManager.Engine.DbAccessHelper.<>c__DisplayClass4.<HandleInsertErrors>b__3()
       at Microsoft.VirtualManager.Engine.DbAccessHelper.HandleInsertErrors[_RetTy](DbAccessDelegate`1 func, ErrorInfo duplicateErrorInfo)
       at Microsoft.VirtualManager.DB.DelegatedAdmin.UserRoleDBHelper.AddObjectSharingData(SqlContext ctx, ITaskContext taskCtx, Guid objectId, CarmineObjectType objectType, AccessControlData accessData)
       at Microsoft.VirtualManager.DB.DelegatedAdmin.ResourceSharingHelper.AddSharingData(SqlContext ctx, ITaskContext taskContext, LockableObject resource, AccessControlData data)
       at Microsoft.VirtualManager.DB.DelegatedAdmin.ResourceSharingHelper.AddResourceSharing(SqlContext ctx, ITaskContext taskCtx, LockableObject resource, List`1 destinationRoles, UserOrGroup destinationUser)
       at Microsoft.VirtualManager.Engine.AuthorizationManager.GrantResourceTask.RunSharingSubTask()
       at Microsoft.VirtualManager.Engine.AuthorizationManager.ResourceSharingTaskBase.RunSubtask()
       at Microsoft.VirtualManager.Engine.TaskRepository.SubtaskBase.Run()
       at Microsoft.VirtualManager.Engine.AuthorizationManager.UserRoleTaskHelper.RunNewAndSetUserRoleSubtasks(ITaskContext taskContext, List`1 queuedSubtasks, UserRoleData userRoleData)
       at Microsoft.VirtualManager.Engine.AuthorizationManager.SetUserRoleSubtask.RunSubtask()
       at Microsoft.VirtualManager.Engine.TaskRepository.SubtaskBase.Run()
       at Microsoft.VirtualManager.Engine.TaskRepository.Task`1.SubtaskRun(Object state)
    *** Carmine error was: DatabaseFailure (2605); SQLServer; 8144
    [s#5cf2] ExecuteNonQuery()
    [s#5c38] Task`1.SubtaskRun(this: (Task`1#b), TaskID: (guid) 0e1c3e3d-76de-4d8b-bfc2-cbcc400fadf4)
    Full call stack from when the exception was thrown:   at System.Environment.GetStackTrace(Exception e, Boolean needFileInfo)
       at System.Environment.get_StackTrace()
       at Microsoft.VirtualManager.DB.CarmineSqlException..ctor(SqlException sqlException)
       at Microsoft.VirtualManager.DB.SqlRetryCommand.ExecuteNonQuery()
       at Microsoft.VirtualManager.DB.DelegatedAdmin.UserRoleDBHelper.<>c__DisplayClass15.<AddObjectSharingData>b__14()
       at Microsoft.VirtualManager.Engine.DbAccessHelper.<>c__DisplayClass4.<HandleInsertErrors>b__3()
       at Microsoft.VirtualManager.Engine.DbAccessHelper.HandleInsertErrors[_RetTy](DbAccessDelegate`1 func, ErrorInfo duplicateErrorInfo)
       at Microsoft.VirtualManager.DB.DelegatedAdmin.UserRoleDBHelper.AddObjectSharingData(SqlContext ctx, ITaskContext taskCtx, Guid objectId, CarmineObjectType objectType, AccessControlData accessData)
       at Microsoft.VirtualManager.DB.DelegatedAdmin.ResourceSharingHelper.AddSharingData(SqlContext ctx, ITaskContext taskContext, LockableObject resource, AccessControlData data)
       at Microsoft.VirtualManager.DB.DelegatedAdmin.ResourceSharingHelper.AddResourceSharing(SqlContext ctx, ITaskContext taskCtx, LockableObject resource, List`1 destinationRoles, UserOrGroup destinationUser)
       at Microsoft.VirtualManager.Engine.AuthorizationManager.GrantResourceTask.RunSharingSubTask()
       at Microsoft.VirtualManager.Engine.AuthorizationManager.ResourceSharingTaskBase.RunSubtask()
       at Microsoft.VirtualManager.Engine.TaskRepository.SubtaskBase.Run()
       at Microsoft.VirtualManager.Engine.AuthorizationManager.UserRoleTaskHelper.RunNewAndSetUserRoleSubtasks(ITaskContext taskContext, List`1 queuedSubtasks, UserRoleData userRoleData)
       at Microsoft.VirtualManager.Engine.AuthorizationManager.SetUserRoleSubtask.RunSubtask()
       at Microsoft.VirtualManager.Engine.TaskRepository.SubtaskBase.Run()
       at Microsoft.VirtualManager.Engine.TaskRepository.Task`1.SubtaskRun(Object state)
       at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
       at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
       at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
       at System.Threading.ThreadPoolWorkQueue.Dispatch()
    --- SqlException details -----------------
    System.Data.SqlClient.SqlException (0x80131904): Procedure or function prc_RBS_UserRoleSharedObjectRelation_Insert has too many arguments specified.
       at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
       at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
       at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)
       at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
       at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async, Int32 timeout, Task& task, Boolean asyncWrite, SqlDataReader ds)
       at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, TaskCompletionSource`1 completion, Int32 timeout, Task& task, Boolean asyncWrite)
       at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(TaskCompletionSource`1 completion, String methodName, Boolean sendToPipe, Int32 timeout, Boolean asyncWrite)
       at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
       at Microsoft.VirtualManager.DB.SqlRetryCommand.ExecuteNonQuery()
    ClientConnectionId:b85c83f3-e87d-4ec4-af12-41b4dd6ad8cb
     Error = 8144
    Index #0
    Source: .Net SqlClient Data Provider
    Number: 8144
    State: 2
    Class: 16
    Server: localhost\SCVMM
    Message: Procedure or function prc_RBS_UserRoleSharedObjectRelation_Insert has too many arguments specified.
    Procedure: prc_RBS_UserRoleSharedObjectRelation_Insert
    Line: 0
    --- Caller StackTrace -----------------
    FileName:; Method:ExecuteNonQuery(); lineNo:0; ilOffset:178.
    FileName:; Method:<AddObjectSharingData>b__14(); lineNo:0; ilOffset:12.
    FileName:; Method:<HandleInsertErrors>b__3(); lineNo:0; ilOffset:11.
    FileName:; Method:HandleInsertErrors(); lineNo:0; ilOffset:6.
    FileName:; Method:AddObjectSharingData(); lineNo:0; ilOffset:312.
    FileName:; Method:AddSharingData(); lineNo:0; ilOffset:23.
    FileName:; Method:AddResourceSharing(); lineNo:0; ilOffset:464.
    FileName:; Method:RunSharingSubTask(); lineNo:0; ilOffset:49.
    FileName:; Method:RunSubtask(); lineNo:0; ilOffset:23.
    FileName:; Method:Run(); lineNo:0; ilOffset:354.
    FileName:; Method:RunNewAndSetUserRoleSubtasks(); lineNo:0; ilOffset:166.
    FileName:; Method:RunSubtask(); lineNo:0; ilOffset:140.
    FileName:; Method:Run(); lineNo:0; ilOffset:354.
    FileName:; Method:SubtaskRun(); lineNo:0; ilOffset:221.
    FileName:; Method:RunInternal(); lineNo:0; ilOffset:112.
    FileName:; Method:Run(); lineNo:0; ilOffset:4.
    FileName:; Method:System.Threading.IThreadPoolWorkItem.ExecuteWorkItem(); lineNo:0; ilOffset:0.
    FileName:; Method:Dispatch(); lineNo:0; ilOffset:162.
    -------- exception.InnerException.ToString() -------
    System.Data.SqlClient.SqlException (0x80131904): Procedure or function prc_RBS_UserRoleSharedObjectRelation_Insert has too many arguments specified.
       at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
       at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
       at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)
       at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
       at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async, Int32 timeout, Task& task, Boolean asyncWrite, SqlDataReader ds)
       at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, TaskCompletionSource`1 completion, Int32 timeout, Task& task, Boolean asyncWrite)
       at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(TaskCompletionSource`1 completion, String methodName, Boolean sendToPipe, Int32 timeout, Boolean asyncWrite)
       at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
       at Microsoft.VirtualManager.DB.SqlRetryCommand.ExecuteNonQuery()
    ClientConnectionId:b85c83f3-e87d-4ec4-af12-41b4dd6ad8cb
    --------------- exception.StackTrace ---------------
    at Microsoft.VirtualManager.DB.SqlRetryCommand.ExecuteNonQuery()
       at Microsoft.VirtualManager.DB.DelegatedAdmin.UserRoleDBHelper.<>c__DisplayClass15.<AddObjectSharingData>b__14()
       at Microsoft.VirtualManager.Engine.DbAccessHelper.<>c__DisplayClass4.<HandleInsertErrors>b__3()
       at Microsoft.VirtualManager.Engine.DbAccessHelper.HandleInsertErrors[_RetTy](DbAccessDelegate`1 func, ErrorInfo duplicateErrorInfo)
       at Microsoft.VirtualManager.DB.DelegatedAdmin.UserRoleDBHelper.AddObjectSharingData(SqlContext ctx, ITaskContext taskCtx, Guid objectId, CarmineObjectType objectType, AccessControlData accessData)
       at Microsoft.VirtualManager.DB.DelegatedAdmin.ResourceSharingHelper.AddSharingData(SqlContext ctx, ITaskContext taskContext, LockableObject resource, AccessControlData data)
       at Microsoft.VirtualManager.DB.DelegatedAdmin.ResourceSharingHelper.AddResourceSharing(SqlContext ctx, ITaskContext taskCtx, LockableObject resource, List`1 destinationRoles, UserOrGroup destinationUser)
       at Microsoft.VirtualManager.Engine.AuthorizationManager.GrantResourceTask.RunSharingSubTask()
       at Microsoft.VirtualManager.Engine.AuthorizationManager.ResourceSharingTaskBase.RunSubtask()
       at Microsoft.VirtualManager.Engine.TaskRepository.SubtaskBase.Run()
       at Microsoft.VirtualManager.Engine.AuthorizationManager.UserRoleTaskHelper.RunNewAndSetUserRoleSubtasks(ITaskContext taskContext, List`1 queuedSubtasks, UserRoleData userRoleData)
       at Microsoft.VirtualManager.Engine.AuthorizationManager.SetUserRoleSubtask.RunSubtask()
       at Microsoft.VirtualManager.Engine.TaskRepository.SubtaskBase.Run()
       at Microsoft.VirtualManager.Engine.TaskRepository.Task`1.SubtaskRun(Object state)
    ------------- StackTrace from handler --------------
    This is the call stack from where the exception was caught, not where it was thrown.
    at Microsoft.VirtualManager.Utils.Diagnostics.WatsonReport.WriteReportTextFile(TextWriter reportFile)
       at Microsoft.VirtualManager.Utils.Diagnostics.WatsonReport.Send()
       at Microsoft.VirtualManager.Utils.Diagnostics.WatsonExceptionReport.Send()
       at Microsoft.VirtualManager.Utils.Diagnostics.WatsonCenter.ReportException(Exception e, WERReportOptions options, String& localReportPath)
       at Microsoft.VirtualManager.Engine.TaskRepository.Task`1.SubtaskRun(Object state)
       at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
       at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
       at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
       at System.Threading.ThreadPoolWorkQueue.Dispatch()
    -------------------- Assemblies --------------------
    mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
        Location=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\mscorlib.dll
        Module=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\mscorlib.dll
        Version=4.0.30319.34011
        BuildType=retail
        Product=Microsoft® .NET Framework
    VMMService, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
        Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\vmmservice.exe
        Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\vmmservice.exe
        Version=3.2.7510.0
        BuildType=retail
        Product=System Center Virtual Machine Manager 2012 R2
    System.ServiceProcess, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
        Location=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.ServiceProcess\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.ServiceProcess.dll
        Module=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.ServiceProcess\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.ServiceProcess.dll
        Version=4.0.30319.33440
        BuildType=retail
        Product=Microsoft® .NET Framework
    System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
        Location=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System\v4.0_4.0.0.0__b77a5c561934e089\System.dll
        Module=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System\v4.0_4.0.0.0__b77a5c561934e089\System.dll
        Version=4.0.30319.34003
        BuildType=retail
        Product=Microsoft® .NET Framework
    TraceWrapper, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
        Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\TraceWrapper.dll
        Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\TraceWrapper.dll
        Version=3.2.7510.0
        BuildType=retail
        Product=System Center Virtual Machine Manager 2012 R2
    Utils, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
        Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Utils.dll
        Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Utils.dll
        Version=3.2.7620.0
        BuildType=retail
        Product=System Center Virtual Machine Manager 2012 R2
    NativeMethods, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
        Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\NativeMethods.dll
        Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\NativeMethods.dll
        Version=3.2.7510.0
        BuildType=retail
        Product=System Center Virtual Machine Manager 2012 R2
    Engine.Common, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
        Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.Common.dll
        Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.Common.dll
        Version=3.2.7620.0
        BuildType=retail
        Product=System Center Virtual Machine Manager 2012 R2
    Engine.IndigoAccessLayer, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
        Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.IndigoAccessLayer.dll
        Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.IndigoAccessLayer.dll
        Version=3.2.7620.0
        BuildType=retail
        Product=System Center Virtual Machine Manager 2012 R2
    System.Core, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
        Location=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Core\v4.0_4.0.0.0__b77a5c561934e089\System.Core.dll
        Module=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Core\v4.0_4.0.0.0__b77a5c561934e089\System.Core.dll
        Version=4.0.30319.33440
        BuildType=retail
        Product=Microsoft® .NET Framework
    Skuhelper, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
        Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Skuhelper.dll
        Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Skuhelper.dll
        Version=3.2.7510.0
        BuildType=retail
        Product=System Center Virtual Machine Manager 2012 R2
    Errors, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
        Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Errors.dll
        Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Errors.dll
        Version=3.2.7510.0
        BuildType=retail
        Product=System Center Virtual Machine Manager 2012 R2
    Remoting, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
        Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Remoting.dll
        Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Remoting.dll
        Version=3.2.7620.0
        BuildType=retail
        Product=System Center Virtual Machine Manager 2012 R2
    System.Runtime.Serialization, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
        Location=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Runtime.Serialization\v4.0_4.0.0.0__b77a5c561934e089\System.Runtime.Serialization.dll
        Module=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Runtime.Serialization\v4.0_4.0.0.0__b77a5c561934e089\System.Runtime.Serialization.dll
        Version=4.0.30319.33440
        BuildType=retail
        Product=Microsoft® .NET Framework
    System.Data, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
        Location=C:\Windows\Microsoft.Net\assembly\GAC_64\System.Data\v4.0_4.0.0.0__b77a5c561934e089\System.Data.dll
        Module=C:\Windows\Microsoft.Net\assembly\GAC_64\System.Data\v4.0_4.0.0.0__b77a5c561934e089\System.Data.dll
        Version=4.0.30319.33440
        Product=Microsoft® .NET Framework
    System.Configuration, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
        Location=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Configuration\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.Configuration.dll
        Module=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Configuration\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.Configuration.dll
        Version=4.0.30319.33440
        BuildType=retail
        Product=Microsoft® .NET Framework
    System.DirectoryServices.AccountManagement, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
        Location=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.DirectoryServices.AccountManagement\v4.0_4.0.0.0__b77a5c561934e089\System.DirectoryServices.AccountManagement.dll
        Module=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.DirectoryServices.AccountManagement\v4.0_4.0.0.0__b77a5c561934e089\System.DirectoryServices.AccountManagement.dll
        Version=4.0.30319.33440
        BuildType=retail
        Product=Microsoft® .NET Framework
    System.ServiceModel, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
        Location=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.ServiceModel\v4.0_4.0.0.0__b77a5c561934e089\System.ServiceModel.dll
        Module=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.ServiceModel\v4.0_4.0.0.0__b77a5c561934e089\System.ServiceModel.dll
        Version=4.0.30319.33440
        BuildType=retail
        Product=Microsoft® .NET Framework
    Engine.Adhc.Operations, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
        Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.Adhc.Operations.dll
        Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.Adhc.Operations.dll
        Version=3.2.7620.0
        BuildType=retail
        Product=System Center Virtual Machine Manager 2012 R2
    Engine.TaskRepository, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
        Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.TaskRepository.dll
        Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.TaskRepository.dll
        Version=3.2.7510.0
        BuildType=retail
        Product=System Center Virtual Machine Manager 2012 R2
    ImgLibEngine, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
        Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\ImgLibEngine.dll
        Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\ImgLibEngine.dll
        Version=3.2.7620.0
        BuildType=retail
        Product=System Center Virtual Machine Manager 2012 R2
    VmmHelperHost, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
        Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\VmmHelperHost.dll
        Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\VmmHelperHost.dll
        Version=3.2.7510.0
        BuildType=retail
        Product=System Center Virtual Machine Manager 2012 R2
    VirtualizationInterfaces, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
        Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\VirtualizationInterfaces.dll
        Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\VirtualizationInterfaces.dll
        Version=3.2.7510.0
        BuildType=retail
        Product=System Center Virtual Machine Manager 2012 R2
    NetworkServiceInterfaces, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
        Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\NetworkServiceInterfaces.dll
        Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\NetworkServiceInterfaces.dll
        Version=3.2.7510.0
        BuildType=retail
        Product=System Center Virtual Machine Manager 2012 R2
    ClusterUtil, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
        Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\ClusterUtil.dll
        Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\ClusterUtil.dll
        Version=3.2.7510.0
        BuildType=retail
        Product=System Center Virtual Machine Manager 2012 R2
    VMWareImplementation, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
        Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\VMWareImplementation.dll
        Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\VMWareImplementation.dll
        Version=3.2.7620.0
        BuildType=retail
        Product=System Center Virtual Machine Manager 2012 R2
    Engine.AuthorizationManager, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
        Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.AuthorizationManager.dll
        Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.AuthorizationManager.dll
        Version=3.2.7620.0
        BuildType=retail
        Product=System Center Virtual Machine Manager 2012 R2
    Engine.AuthorizationManagerTasks, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
        Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.AuthorizationManagerTasks.dll
        Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.AuthorizationManagerTasks.dll
        Version=3.2.7620.0
        BuildType=retail
        Product=System Center Virtual Machine Manager 2012 R2
    Engine.Backup, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
        Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.Backup.dll
        Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.Backup.dll
        Version=3.2.7620.0
        BuildType=retail
        Product=System Center Virtual Machine Manager 2012 R2
    Engine.BitBos, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
        Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.BitBos.dll
        Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.BitBos.dll
        Version=3.2.7510.0
        BuildType=retail
        Product=System Center Virtual Machine Manager 2012 R2
    System.Management.Automation, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
        Location=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Management.Automation\v4.0_3.0.0.0__31bf3856ad364e35\System.Management.Automation.dll
        Module=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Management.Automation\v4.0_3.0.0.0__31bf3856ad364e35\System.Management.Automation.dll
        Version=6.3.9600.16394
        BuildType=retail
        Product=Microsoft (R) Windows (R) Operating System
    WsManWrappers, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
        Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\WsManWrappers.dll
        Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\WsManWrappers.dll
        Version=3.2.7510.0
        BuildType=retail
        Product=System Center Virtual Machine Manager 2012 R2
    SqmWrapper, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
        Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\SqmWrapper.dll
        Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\SqmWrapper.dll
        Version=3.2.7510.0
        BuildType=retail
        Product=System Center Virtual Machine Manager 2012 R2
    Engine.Deployment, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
        Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.Deployment.dll
        Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.Deployment.dll
        Version=3.2.7620.0
        BuildType=retail
        Product=System Center Virtual Machine Manager 2012 R2
    Engine.Placement.ResourceModel, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
        Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.Placement.ResourceModel.dll
        Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.Placement.ResourceModel.dll
        Version=3.2.7510.0
        BuildType=retail
        Product=System Center Virtual Machine Manager 2012 R2
    Engine.ImgLibOperation, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
        Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.ImgLibOperation.dll
        Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.ImgLibOperation.dll
        Version=3.2.7620.0
        BuildType=retail
        Product=System Center Virtual Machine Manager 2012 R2
    System.Xml, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
        Location=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Xml\v4.0_4.0.0.0__b77a5c561934e089\System.Xml.dll
        Module=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Xml\v4.0_4.0.0.0__b77a5c561934e089\System.Xml.dll
        Version=4.0.30319.33440
        BuildType=retail
        Product=Microsoft® .NET Framework
    Engine.CustomProperties, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
        Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.CustomProperties.dll
        Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.CustomProperties.dll
        Version=3.2.7510.0
        BuildType=retail
        Product=System Center Virtual Machine Manager 2012 R2
    Engine.VmOperations, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
        Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.VmOperations.dll
        Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.VmOperations.dll
        Version=3.2.7620.0
        BuildType=retail
        Product=System Center Virtual Machine Manager 2012 R2
    Engine.MomDal, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
        Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.MomDal.dll
        Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.MomDal.dll
        Version=3.2.7510.0
        BuildType=retail
        Product=System Center Virtual Machine Manager 2012 R2
    System.Web.Services, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
        Location=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Web.Services\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.Web.Services.dll
        Module=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Web.Services\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.Web.Services.dll
        Version=4.0.30319.33440
        BuildType=retail
        Product=Microsoft® .NET Framework
    Engine.PxeServer, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
        Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.PxeServer.dll
        Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.PxeServer.dll
        Version=3.2.7510.0
        BuildType=retail
        Product=System Center Virtual Machine Manager 2012 R2
    Engine.Placement, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
        Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.Placement.dll
        Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.Placement.dll
        Version=3.2.7510.0
        BuildType=retail
        Product=System Center Virtual Machine Manager 2012 R2
    Engine.P2VCommon, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
        Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.P2VCommon.dll
        Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.P2VCommon.dll
        Version=3.2.7510.0
        BuildType=retail
        Product=System Center Virtual Machine Manager 2012 R2
    PatchExtractor, Version=0.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
        Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\PatchExtractor.dll
        Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\PatchExtractor.dll
    Engine.ConfigurationProviders, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
        Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.ConfigurationProviders.dll
        Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.ConfigurationProviders.dll
        Version=3.2.7510.0
        BuildType=retail
        Product=System Center Virtual Machine Manager 2012 R2
    GatewayInterfaces, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
        Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\GatewayInterfaces.dll
        Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\GatewayInterfaces.dll
        Version=3.2.7510.0
        BuildType=retail
        Product=System Center Virtual Machine Manager 2012 R2
    Microsoft.Management.Infrastructure, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
        Location=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\Microsoft.Management.Infrastructure\v4.0_1.0.0.0__31bf3856ad364e35\Microsoft.Management.Infrastructure.dll
        Module=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\Microsoft.Management.Infrastructure\v4.0_1.0.0.0__31bf3856ad364e35\Microsoft.Management.Infrastructure.dll
        Version=6.3.9600.16384
        BuildType=retail
        Product=Microsoft (R) Windows (R) Operating System
    Microsoft.CapacityManager.Modeling.Store.ModelLibrary, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
        Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Microsoft.CapacityManager.Modeling.Store.ModelLibrary.dll
        Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Microsoft.CapacityManager.Modeling.Store.ModelLibrary.dll
        Version=3.2.7510.0
        BuildType=retail
        Product=System Center Virtual Machine Manager 2012 R2
    Engine.CustomPropertyTasks, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
        Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.CustomPropertyTasks.dll
        Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.CustomPropertyTasks.dll
        Version=3.2.7510.0
        BuildType=retail
        Product=System Center Virtual Machine Manager 2012 R2
    Engine.UMOperation, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
        Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.UMOperation.dll
        Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.UMOperation.dll
        Version=3.2.7510.0
        BuildType=retail
        Product=System Center Virtual Machine Manager 2012 R2
    Engine.Scheduler, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
        Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.Scheduler.dll
        Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.Scheduler.dll
        Version=3.2.7510.0
        BuildType=retail
        Product=System Center Virtual Machine Manager 2012 R2
    Engine.Tasks, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
        Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.Tasks.dll
        Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.Tasks.dll
        Version=3.2.7510.0
        BuildType=retail
        Product=System Center Virtual Machine Manager 2012 R2
    Engine.ServiceOperations, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
        Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.ServiceOperations.dll
        Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.ServiceOperations.dll
        Version=3.2.7510.0
        BuildType=retail
        Product=System Center Virtual Machine Manager 2012 R2
    GoalState, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
        Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\GoalState.dll
        Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\GoalState.dll
        Version=3.2.7510.0
        BuildType=retail
        Product=System Center Virtual Machine Manager 2012 R2
    Engine.CloudService, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
        Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.CloudService.dll
        Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.CloudService.dll
        Version=3.2.7510.0
        BuildType=retail
        Product=System Center Virtual Machine Manager 2012 R2
    WSManAutomation, Version=3.2.7510.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
        Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\WSManAutomation.dll
        Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\WSManAutomation.dll
    wmiWrappers, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
        Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\WMIWrappers.dll
        Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\WMIWrappers.dll
        Version=3.2.7510.0
        BuildType=retail
        Product=System Center Virtual Machine Manager 2012 R2
    System.Transactions, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
        Location=C:\Windows\Microsoft.Net\assembly\GAC_64\System.Transactions\v4.0_4.0.0.0__b77a5c561934e089\System.Transactions.dll
        Module=C:\Windows\Microsoft.Net\assembly\GAC_64\System.Transactions\v4.0_4.0.0.0__b77a5c561934e089\System.Transactions.dll
        Version=4.0.30319.33440
        Product=Microsoft® .NET Framework
    System.EnterpriseServices, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
        Location=C:\Windows\Microsoft.Net\assembly\GAC_64\System.EnterpriseServices\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.EnterpriseServices.dll
        Module=C:\Windows\Microsoft.Net\assembly\GAC_64\System.EnterpriseServices\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.EnterpriseServices.dll
        Module=C:\Windows\Microsoft.Net\assembly\GAC_64\System.EnterpriseServices\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.EnterpriseServices.Wrapper.dll
        Version=4.0.30319.33440
        BuildType=retail
        Product=Microsoft® .NET Framework
    SMDiagnostics, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
        Location=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\SMDiagnostics\v4.0_4.0.0.0__b77a5c561934e089\SMDiagnostics.dll
        Module=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\SMDiagnostics\v4.0_4.0.0.0__b77a5c561934e089\SMDiagnostics.dll
        Version=4.0.30319.33440
        BuildType=retail
        Product=Microsoft® .NET Framework
    DB.DelegatedAdmin, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
        Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\DB.DelegatedAdmin.dll
        Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\DB.DelegatedAdmin.dll
        Version=3.2.7620.0
        BuildType=retail
        Product=System Center Virtual Machine Manager 2012 R2
    DB.TieredPerfCounters, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
        Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\DB.TieredPerfCounters.dll
        Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\DB.TieredPerfCounters.dll
        Version=3.2.7510.0
        BuildType=retail
        Product=System Center Virtual Machine Manager 2012 R2
    Engine.PhysicalMachine, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
        Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.PhysicalMachine.dll
        Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.PhysicalMachine.dll
        Version=3.2.7515.0
        BuildType=retail
        Product=System Center Virtual Machine Manager 2012 R2
    Engine.UpdateManagement, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
        Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.UpdateManagement.dll
        Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.UpdateManagement.dll
        Version=3.2.7510.0
        BuildType=retail
        Product=System Center Virtual Machine Manager 2012 R2
    Engine.RunAs, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
        Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.RunAs.dll
        Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.RunAs.dll
        Version=3.2.7510.0
        BuildType=retail
        Product=System Center Virtual Machine Manager 2012 R2
    System.Numerics, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
        Location=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Numerics\v4.0_4.0.0.0__b77a5c561934e089\System.Numerics.dll
        Module=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Numerics\v4.0_4.0.0.0__b77a5c561934e089\System.Numerics.dll
        Version=4.0.30319.33440
        BuildType=retail
        Product=Microsoft® .NET Framework
    Engine.DB.Scheduler, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
        Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.DB.Scheduler.dll
        Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.DB.Scheduler.dll
        Version=3.2.7510.0
        BuildType=retail
        Product=System Center Virtual Machine Manager 2012 R2
    System.ServiceModel.Internals, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
        Location=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.ServiceModel.Internals\v4.0_4.0.0.0__31bf3856ad364e35\System.ServiceModel.Internals.dll
        Module=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.ServiceModel.Internals\v4.0_4.0.0.0__31bf3856ad364e35\System.ServiceModel.Internals.dll
        Version=4.0.30319.33440
        BuildType=retail
        Product=Microsoft® .NET Framework
    System.DirectoryServices, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
        Location=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.DirectoryServices\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.DirectoryServices.dll
        Module=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.DirectoryServices\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.DirectoryServices.dll
        Version=4.0.30319.33440
        BuildType=retail
        Product=Microsoft® .NET Framework
    System.Management, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
        Location=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Management\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.Management.dll
        Module=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Management\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.Management.dll
        Version=4.0.30319.33440
        BuildType=retail
        Product=Microsoft® .NET Framework
    System.IdentityModel, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
        Location=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.IdentityModel\v4.0_4.0.0.0__b77a5c561934e089\System.IdentityModel.dll
        Module=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.IdentityModel\v4.0_4.0.0.0__b77a5c561934e089\System.IdentityModel.dll
        Version=4.0.30319.33440
        BuildType=retail
        Product=Microsoft® .NET Framework
    --------- Extra Data for Watson Report -------------
    Error Reporting Enabled=True
    *** Extra Data ***
    Process ID = 1500 (0x05dc)
    Managed Thread ID = 25
    Native Thread ID = 1260 (0x04ec)
    Thomas.

    I (quite honestly) am one of those folks that generally do not read the KB articles associated with a patch or UR or SP - as you don't expect details like have been put into this particular one.
    But as Kristian pointed out - within that KB article is the SQL script that modifies / updates this SQL Stored Procedure.
    http://blogs.technet.com/b/scvmm/archive/2014/01/29/how-to-update-scvmm-2012-r2-to-update-rollup-1.aspx
    Needless to say, the feedback was given to MSFT that folks would overlook that this SQL script needed to be run.  So we are just trying to help out.
    Brian Ehlert
    http://ITProctology.blogspot.com
    Learn. Apply. Repeat.
    Disclaimer: Attempting change is of your own free will.

  • Outlook is unable to connect to the proxy server.(Error Code 10) when users opened Outlook 2010

    Hi All
    Exchange Server - 2013 CU2 (Windows 2012 Standard)
    AD Server - 2003 R2 SP2
    exchange-svr01.domain.com - internal name
    mail.company.net - external name
    When users opened Outlook 2010, they will encountered
    "There is a problem with the proxy server's security certificate. The name on the security certificate is invalid or does not match the name of the target site exchange-svr01.domain.com.
    Outlook is unable to connect to the proxy server.(Error Code 10)"
    I also used the Microsoft Remote Connectivity Analyzer to test RPC/HTTP connectivity.
    The RPC/HTTP test completed successfully.
        Validating the certificate name.
         Certificate name validation failed.
         Host name company.net doesn't match any name found on the server certificate CN=AMAZONA-U59HG9G.
    Testing SSL mutual authentication with the RPC proxy server.
         The test passed with some warnings encountered.
    The certificate common name company.net doesn't match the mutual authentication string provided mail.company.net; however, a match was found in the subject alternative name extension.
     please help.

    Hi PS CL
    [PS] C:\Windows\system32>Get-OutlookAnywhere
    RunspaceId                         : c457e8aa-a0f3-4a0f-aa02-9eff24d02821
    ServerName                         : exchange-svr01
    SSLOffloading                      : True
    ExternalHostname                   : mail.company.net
    InternalHostname                   : exchange-svr01.domain.com
    ExternalClientAuthenticationMethod : Negotiate
    InternalClientAuthenticationMethod : Ntlm
    IISAuthenticationMethods           : {Basic, Ntlm, Negotiate}
    XropUrl                            :
    ExternalClientsRequireSsl          : True
    InternalClientsRequireSsl          : True
    MetabasePath                       : IIS://exchange-svr01.domain.COM/W3SVC/1/ROOT/Rpc
    Path                               : C:\Program Files\Microsoft\Exchange Server\V15\FrontEnd\HttpProxy\rpc
    ExtendedProtectionTokenChecking    : None
    ExtendedProtectionFlags            : {}
    ExtendedProtectionSPNList          : {}
    AdminDisplayVersion                : Version 15.0 (Build 712.22)
    Server                             : exchange-svr01
    AdminDisplayName                   :
    ExchangeVersion                    : 0.20 (15.0.0.0)
    Name                               : Rpc (Default Web Site)
    DistinguishedName                  : CN=Rpc (Default Web
                                         Site),CN=HTTP,CN=Protocols,CN=exchange-svr01,CN=Servers,CN=Exchange
    Administrative
                                         Group (FYDIBOHF23SPDLT),CN=Administrative
    Groups,CN=domain,CN=Microsoft
                                         Exchange,CN=Services,CN=Configuration,DC=domain,DC=COM
    Identity                           : exchange-svr01\Rpc (Default Web Site)
    Guid                               : 33c3cb74-e490-487d-844c-4072334089a1
    ObjectCategory                     : domain.COM/Configuration/Schema/ms-Exch-Rpc-Http-Virtual-Directory
    ObjectClass                        : {top, msExchVirtualDirectory, msExchRpcHttpVirtualDirectory}
    WhenChanged                        : 8/17/2013 10:14:55 AM
    WhenCreated                        : 6/25/2013 1:47:50 PM
    WhenChangedUTC                     : 8/17/2013 2:14:55 AM
    WhenCreatedUTC                     : 6/25/2013 5:47:50 AM
    OrganizationId                     :
    OriginatingServer                  : ADserver.domain.COM
    IsValid                            : True
    ObjectState                        : Changed

  • DPM 2012 R2 unable to connect to Database after failed Update Rollup 4 Installation

    We have a DPM 2012 R2 Server with SQL Server 2012 installed locally.
    We tried to install Rollup 4 for DPM 2012 R2 (KB3009516) using Windows Update
    and it failed with error code 0x80070643. Now when we open the DPM Console
    it is totally empty (no Protection Groups, Servers, Disks, just like a fresh install).
    In the eventlog we get a lot of Errors and warnings:
    Event 941 (MSDPM)
    Unable to connect to the DPM database.  Make sure that SQL Server is running and that it is configured correctly.
    Cannot open database "DPMDB" requested by the login. The login failed.
    Event 4209 (MSDPM)
    The description for Event ID 4209 from source MSDPM cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
    If the event originated on another computer, the display information had to be saved with the event.
    The following information was included with the event:
    DPM Writer encountered an internal error.  Please restart the DPM Writer service, and then try the backup operation again. For additional troubleshooting information, review the application event log and the DPM Troubleshooting Guide.
    Event 107 (Report Server Windows Service (MSSQLSERVER)
    Report Server Windows Service (MSSQLSERVER) cannot connect to the report server database.
    Event 274 (SQLISService110)
    Microsoft SSIS Service:
    Registry setting specifying configuration file does not exist.
    Attempting to load default config file.
    Then there are some Errors/warnings from SQLSERVERAGENT about failed scheduled Jobs.
    I think the failed Installation changed some database Settings, so that now the DPM Console
    cant access the database anymore.
    I would be happy if someone can help me getting this Server working again!

    Our biggest problem is, that the DPM is not working any more. So there is no chance to backup the SQL Server via DPM.
    I think the main problem is that DPM have no access to the database. Every time I start the DPM Application, I get an error "verify that the DPM service is running on this computer". In the eventlog are many errors that the msdpm service was unable
    to connect to DPM Database. Another "information" is that the user 'nt authority\system' failed to open the database of dpm.
    We've tried to reinstall the DPM but its still the same problem. I suppose that is a corrupt database.
    Tomorrow I try to restore the database and hope it will be the solution of our problem.

Maybe you are looking for

  • Where can I download HP Recovery Manager for my TouchSmart 610--1150x​t running WIndows 7 x64?

    Many users would prefer a clean install of Windows with the option to install only those applications that they personally find useful.  Currently, if performing a clean install of Windows -- even if creating recovery disks and maintaining the HP rec

  • How do I convert a Pages document to pdf on the iPad?

    Does anyone know if there is an app that allows you to do this? I have to create a document in pages, create a pdf of the document, then email it to several addresses. Seems like there ought to be a way to accomplish this on the iPad, and not go to m

  • Can i place controls from the properties dialog of an express vi on the front panel?

    I'm using the spectral measurements express vi in my vi and I'd like to put the "window" and "number of averages" controls from the properties dialog on the front panel. However, there are not outputs on the express vi icon for these parameters. Can

  • APs not registering with WLC

    Hi guys, i'll try to explain our trouble as best as i can: Im trying to do some basic scenario here. Picture this: One L3 Switch connecting a 4402 Controller, 3 Administrative Vlans for APs (63, 93 and 127) and 3 Vlans for clients (one for each Admin

  • DNG problems in Windows XP Explorer

    I have been shooting with the Olympus EP1 and since LR does not recognize the files yet I decided to try the new version of the DNG Converter. It (the DNG converter) recognized the EP1 RAW files fine, converted them and I was then able to import into