Session Broker Newbee

I am new to the server world and am at a loss. I am looking to use my 4 virtual servers to run my application for approximately 300 users. I believe Session Broker Services will work based on my research. However, I did not see the service in the
list of features on my server Windows 2008 R2. Do I need the Windows 2008 Enterprise version or am I missing something on my servers?? Also, do you know of any step-by-step instructions from beginning to end?

Hi,
Thank you for posting in Windows Server Forum.
From your description I can say that you can create load balance RDSH farm by using RD Connection broker. Please check below article for detailed information.
Checklist: Create a Load-Balanced RD Session Host Server Farm by Using RD Connection Broker
http://technet.microsoft.com/en-in/library/cc753891.aspx
Hope it helps!
Thanks.
Dharmesh Solanki
TechNet Community Support

Similar Messages

Cannot connect to Session broker server, but can to other servers in Cluster

Hi Everyone,
Hopefully this is the right place to post. Have searched quite a bit through the forums (not all 19000+ pages though), and can't seem to find a similiar issue.
I have also searched the internet and tried all solutions others with a similiar problem have.
This is my problem:
We have two servers running Server 2008 R2, set up as Remote Desktop Servers in a cluster setup.
The session broker is located on the second server (This is an active server which has sessions load balanced to it). There is also a DNS round robin setup
Problem: When sessions are allowed to be load balanced on Server2, then the users cannot connect to the cluster. The round robin seems to still send some sessions to the first server, and these seem to connect fine.
I suspected the issue was with the WMI Respository, and so started. I found a lot of errors, but have been unable to fix them.
I downlaoded the WMIDiag from Microsoft, and here is the report:
48866 15:56:44 (0) ** WMIDiag v2.1 started on 15 April 2015 at 15:48.
48867 15:56:44 (0) **
48868 15:56:44 (0) ** Copyright (c) Microsoft Corporation. All rights reserved - July 2007.
48869 15:56:44 (0) **
48870 15:56:44 (0) ** This script is not supported under any Microsoft standard support program or service.
48871 15:56:44 (0) ** The script is provided AS IS without warranty of any kind. Microsoft further disclaims all
48872 15:56:44 (0) ** implied warranties including, without limitation, any implied warranties of merchantability
48873 15:56:44 (0) ** or of fitness for a particular purpose. The entire risk arising out of the use or performance
48874 15:56:44 (0) ** of the scripts and documentation remains with you. In no event shall Microsoft, its authors,
48875 15:56:44 (0) ** or anyone else involved in the creation, production, or delivery of the script be liable for
48876 15:56:44 (0) ** any damages whatsoever (including, without limitation, damages for loss of business profits,
48877 15:56:44 (0) ** business interruption, loss of business information, or other pecuniary loss) arising out of
48878 15:56:44 (0) ** the use of or inability to use the script or documentation, even if Microsoft has been advised
48879 15:56:44 (0) ** of the possibility of such damages.
48880 15:56:44 (0) **
48881 15:56:44 (0) **
48882 15:56:44 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
48883 15:56:44 (0) ** ----------------------------------------------------- WMI REPORT: BEGIN ----------------------------------------------------------
48884 15:56:44 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
48885 15:56:44 (0) **
48886 15:56:44 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
48887 15:56:44 (0) ** Windows Server 2008 R2 - Service pack 1 - 64-bit (7601) - User 'MIBCO\CONN.LOMBARD' on computer 'SSCRDS02'.
48888 15:56:44 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
48889 15:56:44 (0) ** INFO: Environment: .................................................................................................. 1 ITEM(S)!
48890 15:56:44 (0) ** INFO: => 3 possible incorrect shutdown(s) detected on:
48891 15:56:44 (0) **          - Shutdown on 05 December 2014 22:55:28 (GMT-0).
48892 15:56:44 (0) **          - Shutdown on 12 December 2014 06:43:00 (GMT-0).
48893 15:56:44 (0) **          - Shutdown on 27 February 2015 05:19:26 (GMT-0).
48894 15:56:44 (0) **
48895 15:56:44 (0) ** System drive: ....................................................................................................... C: (Disk #0 Partition #1).
48896 15:56:44 (0) ** Drive type: ......................................................................................................... SCSI (DELL PERC H700 SCSI Disk Device).
48897 15:56:44 (0) ** There are no missing WMI system files: .............................................................................. OK.
48898 15:56:44 (0) ** There are no missing WMI repository files: .......................................................................... OK.
48899 15:56:44 (0) ** WMI repository state: ............................................................................................... CONSISTENT.
48900 15:56:44 (0) ** AFTER running WMIDiag:
48901 15:56:44 (0) ** The WMI repository has a size of: ................................................................................... 26 MB.
48902 15:56:44 (0) ** - Disk free space on 'C:': .......................................................................................... 297281 MB.
48903 15:56:44 (0) **   - INDEX.BTR,                     5513216 bytes,      2015/04/15 03:52:21 PM
48904 15:56:44 (0) **   - MAPPING1.MAP,                  76804 bytes,        2015/04/15 03:50:51 PM
48905 15:56:44 (0) **   - MAPPING2.MAP,                  76804 bytes,        2015/04/15 03:52:21 PM
48906 15:56:44 (0) **   - OBJECTS.DATA,                  22036480 bytes,     2015/04/15 03:52:21 PM
48907 15:56:44 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
48908 15:56:44 (0) ** INFO: Windows Firewall status: ...................................................................................... ENABLED.
48909 15:56:44 (0) ** Windows Firewall Profile: ........................................................................................... DOMAIN.
48910 15:56:44 (0) ** Inbound connections that do not match a rule BLOCKED: ............................................................... ENABLED.
48911 15:56:44 (0) ** => This will prevent any WMI remote connectivity to this computer except
48912 15:56:44 (0) **    if the following three inbound rules are ENABLED and non-BLOCKING:
48913 15:56:44 (0) **    - 'Windows Management Instrumentation (DCOM-In)'
48914 15:56:44 (0) **    - 'Windows Management Instrumentation (WMI-In)'
48915 15:56:44 (0) **    - 'Windows Management Instrumentation (ASync-In)'
48916 15:56:44 (0) **    Verify the reported status for each of these three inbound rules below.
48917 15:56:44 (0) **
48918 15:56:44 (0) ** Windows Firewall 'Windows Management Instrumentation (WMI)' GROUP rule: ............................................. ENABLED.
48919 15:56:44 (0) ** Windows Firewall 'Windows Management Instrumentation (WMI-Out)' rule: ............................................... ENABLED.
48920 15:56:44 (0) ** Windows Firewall 'Windows Management Instrumentation (WMI-In)' rule: ................................................ ENABLED.
48921 15:56:44 (0) ** Windows Firewall 'Windows Management Instrumentation (DCOM-In)' rule: ............................................... ENABLED.
48922 15:56:44 (0) ** Windows Firewall 'Windows Management Instrumentation (ASync-In)' rule: .............................................. ENABLED.
48923 15:56:44 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
48924 15:56:44 (0) ** DCOM Status: ........................................................................................................ OK.
48925 15:56:44 (0) ** WMI registry setup: ................................................................................................. OK.
48926 15:56:44 (0) ** INFO: WMI service has dependents: ................................................................................... 2 SERVICE(S)!
48927 15:56:44 (0) ** - Internet Connection Sharing (ICS) (SHAREDACCESS, StartMode='Disabled')
48928 15:56:44 (0) ** - SMS Agent Host (CCMEXEC, StartMode='Automatic')
48929 15:56:44 (0) ** => If the WMI service is stopped, the listed service(s) will have to be stopped as well.
48930 15:56:44 (0) **    Note: If the service is marked with (*), it means that the service/application uses WMI but
48931 15:56:44 (0) **          there is no hard dependency on WMI. However, if the WMI service is stopped,
48932 15:56:44 (0) **          this can prevent the service/application to work as expected.
48933 15:56:44 (0) **
48934 15:56:44 (0) ** RPCSS service: ...................................................................................................... OK (Already started).
48935 15:56:44 (0) ** WINMGMT service: .................................................................................................... OK (Already started).
48936 15:56:44 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
48937 15:56:44 (0) ** WMI service DCOM setup: ............................................................................................. OK.
48938 15:56:44 (0) ** WMI components DCOM registrations: .................................................................................. OK.
48939 15:56:44 (0) ** WMI ProgID registrations: ........................................................................................... OK.
48940 15:56:44 (0) ** WMI provider DCOM registrations: .................................................................................... OK.
48941 15:56:44 (0) ** WMI provider CIM registrations: ..................................................................................... OK.
48942 15:56:44 (0) ** WMI provider CLSIDs: ................................................................................................ OK.
48943 15:56:44 (0) ** WMI providers EXE/DLL availability: ................................................................................. OK.
48944 15:56:44 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
48945 15:56:44 (0) ** INFO: User Account Control (UAC): ................................................................................... ENABLED.
48946 15:56:44 (0) ** => WMI tasks requiring Administrative privileges on this computer MUST run in an elevated context.
48947 15:56:44 (0) **    i.e. You can start your scripts or WMIC commands from an elevated command
48948 15:56:44 (0) **         prompt by right clicking on the 'Command Prompt' icon in the Start Menu and
48949 15:56:44 (0) **         selecting 'Run as Administrator'.
48950 15:56:44 (0) **    i.e. You can also execute the WMI scripts or WMIC commands as a task
48951 15:56:44 (0) **         in the Task Scheduler within the right security context.
48952 15:56:44 (0) **
48953 15:56:44 (0) ** INFO: Local Account Filtering: ...................................................................................... ENABLED.
48954 15:56:44 (0) ** => WMI tasks remotely accessing WMI information on this computer and requiring Administrative
48955 15:56:44 (0) **    privileges MUST use a DOMAIN account part of the Local Administrators group of this computer
48956 15:56:44 (0) **    to ensure that administrative privileges are granted. If a Local User account is used for remote
48957 15:56:44 (0) **    accesses, it will be reduced to a plain user (filtered token), even if it is part of the Local Administrators group.
48958 15:56:44 (0) **
48959 15:56:44 (0) ** DCOM security for 'Microsoft WBEM UnSecured Apartment' (Launch & Activation Permissions): ........................... MODIFIED.
48960 15:56:44 (1) !! ERROR: Actual trustee 'NT AUTHORITY\SYSTEM' DOES NOT match corresponding expected trustee rights (Actual->Default)
48961 15:56:44 (0) **        - ACTUAL ACE:
48962 15:56:44 (0) **          ACEType: &h0
48963 15:56:44 (0) **                    ACCESS_ALLOWED_ACE_TYPE
48964 15:56:44 (0) **          ACEFlags: &h4
48965 15:56:44 (0) **                    NO_PROPAGATE_INHERIT_ACE
48966 15:56:44 (0) **          ACEMask: &hB
48967 15:56:44 (0) **                    DCOM_RIGHT_EXECUTE
48968 15:56:44 (0) **                    DCOM_RIGHT_LAUNCH_LOCAL
48969 15:56:44 (0) **                    DCOM_RIGHT_ACTIVATE_LOCAL
48970 15:56:44 (0) **        - EXPECTED ACE:
48971 15:56:44 (0) **          ACEType: &h0
48972 15:56:44 (0) **                    ACCESS_ALLOWED_ACE_TYPE
48973 15:56:44 (0) **          ACEFlags: &h0
48974 15:56:44 (0) **          ACEMask: &h1F
48975 15:56:44 (0) **                    DCOM_RIGHT_EXECUTE
48976 15:56:44 (0) **                    DCOM_RIGHT_LAUNCH_LOCAL
48977 15:56:44 (0) **                    DCOM_RIGHT_LAUNCH_REMOTE
48978 15:56:44 (0) **                    DCOM_RIGHT_ACTIVATE_LOCAL
48979 15:56:44 (0) **                    DCOM_RIGHT_ACTIVATE_REMOTE
48980 15:56:44 (0) **
48981 15:56:44 (0) ** => The actual ACE has the right(s) '&h14 DCOM_RIGHT_LAUNCH_REMOTE DCOM_RIGHT_ACTIVATE_REMOTE' removed!
48982 15:56:44 (0) **    This will cause some operations to fail!
48983 15:56:44 (0) **    It is possible to fix this issue by editing the security descriptor and adding the removed right.
48984 15:56:44 (0) **    For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
48985 15:56:44 (0) **
48986 15:56:44 (0) ** DCOM security for 'Microsoft WBEM UnSecured Apartment' (Launch & Activation Permissions): ........................... MODIFIED.
48987 15:56:44 (1) !! ERROR: Actual trustee 'NT AUTHORITY\INTERACTIVE' DOES NOT match corresponding expected trustee rights (Actual->Default)
48988 15:56:44 (0) **        - ACTUAL ACE:
48989 15:56:44 (0) **          ACEType: &h0
48990 15:56:44 (0) **                    ACCESS_ALLOWED_ACE_TYPE
48991 15:56:44 (0) **          ACEFlags: &h4
48992 15:56:44 (0) **                    NO_PROPAGATE_INHERIT_ACE
48993 15:56:44 (0) **          ACEMask: &hB
48994 15:56:44 (0) **                    DCOM_RIGHT_EXECUTE
48995 15:56:44 (0) **                    DCOM_RIGHT_LAUNCH_LOCAL
48996 15:56:44 (0) **                    DCOM_RIGHT_ACTIVATE_LOCAL
48997 15:56:44 (0) **        - EXPECTED ACE:
48998 15:56:44 (0) **          ACEType: &h0
48999 15:56:44 (0) **                    ACCESS_ALLOWED_ACE_TYPE
49000 15:56:44 (0) **          ACEFlags: &h0
49001 15:56:44 (0) **          ACEMask: &h1F
49002 15:56:44 (0) **                    DCOM_RIGHT_EXECUTE
49003 15:56:44 (0) **                    DCOM_RIGHT_LAUNCH_LOCAL
49004 15:56:44 (0) **                    DCOM_RIGHT_LAUNCH_REMOTE
49005 15:56:44 (0) **                    DCOM_RIGHT_ACTIVATE_LOCAL
49006 15:56:44 (0) **                    DCOM_RIGHT_ACTIVATE_REMOTE
49007 15:56:44 (0) **
49008 15:56:44 (0) ** => The actual ACE has the right(s) '&h14 DCOM_RIGHT_LAUNCH_REMOTE DCOM_RIGHT_ACTIVATE_REMOTE' removed!
49009 15:56:44 (0) **    This will cause some operations to fail!
49010 15:56:44 (0) **    It is possible to fix this issue by editing the security descriptor and adding the removed right.
49011 15:56:44 (0) **    For DCOM objects, this can be done with 'DCOMCNFG.EXE'.
49012 15:56:44 (0) **
49013 15:56:44 (0) **
49014 15:56:44 (0) ** DCOM security warning(s) detected: .................................................................................. 0.
49015 15:56:44 (0) ** DCOM security error(s) detected: .................................................................................... 2.
49016 15:56:44 (0) ** WMI security warning(s) detected: ................................................................................... 0.
49017 15:56:44 (0) ** WMI security error(s) detected: ..................................................................................... 0.
49018 15:56:44 (0) **
49019 15:56:44 (1) !! ERROR: Overall DCOM security status: ................................................................................ ERROR!
49020 15:56:44 (0) ** Overall WMI security status: ........................................................................................ OK.
49021 15:56:44 (0) ** - Started at 'Root' --------------------------------------------------------------------------------------------------------------
49022 15:56:44 (0) ** INFO: WMI permanent SUBSCRIPTION(S): ................................................................................ 5.
49023 15:56:44 (0) ** - ROOT/SUBSCRIPTION, NTEventLogEventConsumer.Name="SCM Event Log Consumer".
49024 15:56:44 (0) **   'select * from MSFT_SCMEventLogEvent'
49025 15:56:44 (0) ** - ROOT/CCM/POLICY, CCM_PolicyReplicationConsumer.Id="{9099D177-1AD6-46e6-BBC0-70F460786953}".
49026 15:56:44 (0) **   'SELECT * FROM __NamespaceCreationEvent'
49027 15:56:44 (0) ** - ROOT/CCM/POLICY, CCM_PolicyReplicationConsumer.Id="{9099D177-1AD6-46e6-BBC0-70F460786953}".
49028 15:56:44 (0) **   'SELECT * FROM __ClassOperationEvent WHERE TargetClass ISA "CCM_Policy_EmbeddedObject"'
49029 15:56:44 (0) ** - ROOT/CCM/POLICY, CCM_PolicyReplicationConsumer.Id="{9099D177-1AD6-46e6-BBC0-70F460786953}".
49030 15:56:44 (0) **   'SELECT * FROM __ClassOperationEvent WHERE TargetClass ISA "CCM_Policy_Config"'
49031 15:56:44 (0) ** - ROOT/CCM/POLICY, CCM_PolicyReplicationConsumer.Id="{9099D177-1AD6-46e6-BBC0-70F460786953}".
49032 15:56:44 (0) **   'SELECT * FROM __ClassOperationEvent WHERE TargetClass ISA "CCM_Policy"'
49033 15:56:44 (0) **
49034 15:56:44 (0) ** WMI TIMER instruction(s): ........................................................................................... NONE.
49035 15:56:44 (0) ** INFO: WMI namespace(s) requiring PACKET PRIVACY: .................................................................... 3 NAMESPACE(S)!
49036 15:56:44 (0) ** - ROOT/CIMV2/SECURITY/MICROSOFTTPM.
49037 15:56:44 (0) ** - ROOT/CIMV2/TERMINALSERVICES.
49038 15:56:44 (0) ** - ROOT/SERVICEMODEL.
49039 15:56:44 (0) ** => When remotely connecting, the namespace(s) listed require(s) the WMI client to
49040 15:56:44 (0) **    use an encrypted connection by specifying the PACKET PRIVACY authentication level.
49041 15:56:44 (0) **    (RPC_C_AUTHN_LEVEL_PKT_PRIVACY or PktPrivacy flags)
49042 15:56:44 (0) **    i.e. 'WMIC.EXE /NODE:"SSCRDS02" /AUTHLEVEL:Pktprivacy /NAMESPACE:\\ROOT\SERVICEMODEL Class __SystemSecurity'
49043 15:56:44 (0) **
49044 15:56:44 (0) ** WMI MONIKER CONNECTIONS: ............................................................................................ OK.
49045 15:56:44 (0) ** WMI CONNECTIONS: .................................................................................................... OK.
49046 15:56:44 (1) !! ERROR: WMI GET operation errors reported: ........................................................................... 34 ERROR(S)!
49047 15:56:44 (0) ** - Root/CIMV2, MSFT_NetInvalidDriverDependency, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
49048 15:56:44 (0) **   MOF Registration: ''
49049 15:56:44 (0) ** - Root/CIMV2, Win32_OsBaselineProvider, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
49050 15:56:44 (0) **   MOF Registration: ''
49051 15:56:44 (0) ** - Root/CIMV2, Win32_OsBaseline, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
49052 15:56:44 (0) **   MOF Registration: ''
49053 15:56:44 (0) ** - Root/CIMV2, Win32_DriverVXD, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
49054 15:56:44 (0) **   MOF Registration: ''
49055 15:56:44 (0) ** - Root/CIMV2, Win32_PerfFormattedData_Counters_GenericIKEandAuthIP, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
49056 15:56:44 (0) **   MOF Registration: ''
49057 15:56:44 (0) ** - Root/CIMV2, Win32_PerfRawData_Counters_GenericIKEandAuthIP, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
49058 15:56:44 (0) **   MOF Registration: ''
49059 15:56:44 (0) ** - Root/CIMV2, Win32_PerfFormattedData_Counters_IPsecAuthIPv4, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
49060 15:56:44 (0) **   MOF Registration: ''
49061 15:56:44 (0) ** - Root/CIMV2, Win32_PerfRawData_Counters_IPsecAuthIPv4, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
49062 15:56:44 (0) **   MOF Registration: ''
49063 15:56:44 (0) ** - Root/CIMV2, Win32_PerfFormattedData_Counters_IPsecAuthIPv6, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
49064 15:56:44 (0) **   MOF Registration: ''
49065 15:56:44 (0) ** - Root/CIMV2, Win32_PerfRawData_Counters_IPsecAuthIPv6, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
49066 15:56:44 (0) **   MOF Registration: ''
49067 15:56:44 (0) ** - Root/CIMV2, Win32_PerfFormattedData_Counters_IPsecIKEv4, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
49068 15:56:44 (0) **   MOF Registration: ''
49069 15:56:44 (0) ** - Root/CIMV2, Win32_PerfRawData_Counters_IPsecIKEv4, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
49070 15:56:44 (0) **   MOF Registration: ''
49071 15:56:44 (0) ** - Root/CIMV2, Win32_PerfFormattedData_Counters_IPsecIKEv6, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
49072 15:56:44 (0) **   MOF Registration: ''
49073 15:56:44 (0) ** - Root/CIMV2, Win32_PerfRawData_Counters_IPsecIKEv6, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
49074 15:56:44 (0) **   MOF Registration: ''
49075 15:56:44 (0) ** - Root/CIMV2, Win32_PerfFormattedData_NETDataProviderforOracle_NETDataProviderforOracle, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
49076 15:56:44 (0) **   MOF Registration: ''
49077 15:56:44 (0) ** - Root/CIMV2, Win32_PerfRawData_NETDataProviderforOracle_NETDataProviderforOracle, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
49078 15:56:44 (0) **   MOF Registration: ''
49079 15:56:44 (0) ** - Root/CIMV2, Win32_PerfFormattedData_TermService_TerminalServices, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
49080 15:56:44 (0) **   MOF Registration: ''
49081 15:56:44 (0) ** - Root/CIMV2, Win32_PerfRawData_TermService_TerminalServices, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
49082 15:56:44 (0) **   MOF Registration: ''
49083 15:56:44 (0) ** - Root/WMI, ReserveDisjoinThread, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
49084 15:56:44 (0) **   MOF Registration: ''
49085 15:56:44 (0) ** - Root/WMI, ReserveLateCount, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
49086 15:56:44 (0) **   MOF Registration: ''
49087 15:56:44 (0) ** - Root/WMI, ReserveJoinThread, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
49088 15:56:44 (0) **   MOF Registration: ''
49089 15:56:44 (0) ** - Root/WMI, ReserveDelete, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
49090 15:56:44 (0) **   MOF Registration: ''
49091 15:56:44 (0) ** - Root/WMI, ReserveBandwidth, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
49092 15:56:44 (0) **   MOF Registration: ''
49093 15:56:44 (0) ** - Root/WMI, ReserveCreate, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
49094 15:56:44 (0) **   MOF Registration: ''
49095 15:56:44 (0) ** - Root/WMI, SystemConfig_PhyDisk, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
49096 15:56:44 (0) **   MOF Registration: ''
49097 15:56:44 (0) ** - Root/WMI, SystemConfig_Video, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
49098 15:56:44 (0) **   MOF Registration: ''
49099 15:56:44 (0) ** - Root/WMI, SystemConfig_IDEChannel, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
49100 15:56:44 (0) **   MOF Registration: ''
49101 15:56:44 (0) ** - Root/WMI, SystemConfig_NIC, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
49102 15:56:44 (0) **   MOF Registration: ''
49103 15:56:44 (0) ** - Root/WMI, SystemConfig_Network, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
49104 15:56:44 (0) **   MOF Registration: ''
49105 15:56:44 (0) ** - Root/WMI, SystemConfig_CPU, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
49106 15:56:44 (0) **   MOF Registration: ''
49107 15:56:44 (0) ** - Root/WMI, SystemConfig_LogDisk, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
49108 15:56:44 (0) **   MOF Registration: ''
49109 15:56:44 (0) ** - Root/WMI, SystemConfig_Power, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
49110 15:56:44 (0) **   MOF Registration: ''
49111 15:56:44 (0) ** - root/ccm/LocationServices, ClientInfo, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
49112 15:56:44 (0) **   MOF Registration: ''
49113 15:56:44 (0) ** - root/ccm/LocationServices, ClientInfo, 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
49114 15:56:44 (0) **   MOF Registration: ''
49115 15:56:44 (0) ** => When a WMI performance class is missing (i.e. 'Win32_PerfRawData_TermService_TerminalServices'), it is generally due to
49116 15:56:44 (0) **    a lack of buffer refresh of the WMI class provider exposing the WMI performance counters.
49117 15:56:44 (0) **    You can refresh the WMI class provider buffer with the following command:
49118 15:56:44 (0) **
49119 15:56:44 (0) **    i.e. 'WINMGMT.EXE /SYNCPERF'
49120 15:56:44 (0) **
49121 15:56:44 (0) ** WMI MOF representations: ............................................................................................ OK.
49122 15:56:44 (0) ** WMI QUALIFIER access operations: .................................................................................... OK.
49123 15:56:44 (0) ** WMI ENUMERATION operations: ......................................................................................... OK.
49124 15:56:44 (0) ** WMI EXECQUERY operations: ........................................................................................... OK.
49125 15:56:44 (2) !! WARNING: WMI GET VALUE operation errors reported: ................................................................... 5 WARNING(S)!
49126 15:56:44 (0) ** - Root, Instance: __EventConsumerProviderCacheControl=@, Property: ClearAfter='00000000000030.000000:000' (Expected default='00000000000500.000000:000').
49127 15:56:44 (0) ** - Root, Instance: __EventProviderCacheControl=@, Property: ClearAfter='00000000000030.000000:000' (Expected default='00000000000500.000000:000').
49128 15:56:44 (0) ** - Root, Instance: __EventSinkCacheControl=@, Property: ClearAfter='00000000000015.000000:000' (Expected default='00000000000230.000000:000').
49129 15:56:44 (0) ** - Root, Instance: __ObjectProviderCacheControl=@, Property: ClearAfter='00000000000030.000000:000' (Expected default='00000000000500.000000:000').
49130 15:56:44 (0) ** - Root, Instance: __PropertyProviderCacheControl=@, Property: ClearAfter='00000000000030.000000:000' (Expected default='00000000000500.000000:000').
49131 15:56:44 (0) **
49132 15:56:44 (0) ** WMI WRITE operations: ............................................................................................... NOT TESTED.
49133 15:56:44 (0) ** WMI PUT operations: ................................................................................................. NOT TESTED.
49134 15:56:44 (0) ** WMI DELETE operations: .............................................................................................. NOT TESTED.
49135 15:56:44 (0) ** WMI static instances retrieved: ..................................................................................... 6304.
49136 15:56:44 (0) ** WMI dynamic instances retrieved: .................................................................................... 0.
49137 15:56:44 (0) ** WMI instance request cancellations (to limit performance impact): ................................................... 3.
49138 15:56:44 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
49139 15:56:44 (0) ** # of Event Log events BEFORE WMIDiag execution since the last 20 day(s):
49140 15:56:44 (0) **   DCOM: ............................................................................................................. 0.
49141 15:56:44 (0) **   WINMGMT: .......................................................................................................... 0.
49142 15:56:44 (0) **   WMIADAPTER: ....................................................................................................... 0.
49143 15:56:44 (0) **
49144 15:56:44 (0) ** # of additional Event Log events AFTER WMIDiag execution:
49145 15:56:44 (0) **   DCOM: ............................................................................................................. 0.
49146 15:56:44 (0) **   WINMGMT: .......................................................................................................... 0.
49147 15:56:44 (0) **   WMIADAPTER: ....................................................................................................... 0.
49148 15:56:44 (0) **
49149 15:56:44 (0) ** 34 error(s) 0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found
49150 15:56:44 (0) ** => This error is typically a WMI error. This WMI error is due to:
49151 15:56:44 (0) **    - a missing WMI class definition or object.
49152 15:56:44 (0) **      (See any GET, ENUMERATION, EXECQUERY and GET VALUE operation failures).
49153 15:56:44 (0) **      You can correct the missing class definitions by:
49154 15:56:44 (0) **      - Manually recompiling the MOF file(s) with the 'MOFCOMP <FileName.MOF>' command.
49155 15:56:44 (0) **      Note: You can build a list of classes in relation with their WMI provider and MOF file with WMIDiag.
49156 15:56:44 (0) **            (This list can be built on a similar and working WMI Windows installation)
49157 15:56:44 (0) **            The following command line must be used:
49158 15:56:44 (0) **            i.e. 'WMIDiag CorrelateClassAndProvider'
49159 15:56:44 (0) **      Note: When a WMI performance class is missing, you can manually resynchronize performance counters
49160 15:56:44 (0) **            with WMI by starting the ADAP process.
49161 15:56:44 (0) **    - a WMI repository corruption.
49162 15:56:44 (0) **      In such a case, you must rerun WMIDiag with 'WriteInRepository' parameter
49163 15:56:44 (0) **      to validate the WMI repository operations.
49164 15:56:44 (0) **    Note: ENSURE you are an administrator with FULL access to WMI EVERY namespaces of the computer before
49165 15:56:44 (0) **          executing the WriteInRepository command. To write temporary data from the Root namespace, use:
49166 15:56:44 (0) **          i.e. 'WMIDiag WriteInRepository=Root'
49167 15:56:44 (0) **    - If the WriteInRepository command fails, while being an Administrator with ALL accesses to ALL namespaces
49168 15:56:44 (0) **      the WMI repository must be reconstructed.
49169 15:56:44 (0) **    Note: The WMI repository reconstruction requires to locate all MOF files needed to rebuild the repository,
49170 15:56:44 (0) **          otherwise some applications may fail after the reconstruction.
49171 15:56:44 (0) **          This can be achieved with the following command:
49172 15:56:44 (0) **          i.e. 'WMIDiag ShowMOFErrors'
49173 15:56:44 (0) **    Note: The repository reconstruction must be a LAST RESORT solution and ONLY after executing
49174 15:56:44 (0) **          ALL fixes previously mentioned.
49175 15:56:44 (2) !! WARNING: Static information stored by external applications in the repository will be LOST! (i.e. SMS Inventory)
49176 15:56:44 (0) **
49177 15:56:44 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
49178 15:56:44 (0) ** Unexpected, wrong or missing registry key values: ................................................................... 1 KEY(S)!
49179 15:56:44 (0) ** INFO: Unexpected registry key value:
49180 15:56:44 (0) **   - Current: HKLM\SOFTWARE\Microsoft\WBEM\CIMOM\Logging (REG_SZ) -> 0
49181 15:56:44 (0) **   - Expected: HKLM\SOFTWARE\Microsoft\WBEM\CIMOM\Logging (REG_SZ) -> 1
49182 15:56:44 (0) **     From the command line, the registry configuration can be corrected with the following command:
49183 15:56:44 (0) **     i.e. 'REG.EXE Add "HKLM\SOFTWARE\Microsoft\WBEM\CIMOM" /v "Logging" /t "REG_SZ" /d "1" /f'
49184 15:56:44 (0) **
49185 15:56:44 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
49186 15:56:44 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
49187 15:56:44 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
49188 15:56:44 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
49189 15:56:44 (0) **
49190 15:56:44 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
49191 15:56:44 (0) ** ------------------------------------------------------ WMI REPORT: END -----------------------------------------------------------
49192 15:56:44 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
49193 15:56:44 (0) **
49194 15:56:44 (0) ** ERROR: WMIDiag detected issues that could prevent WMI to work properly!. Check 'C:\USERS\CONN.LOMBARD\APPDATA\LOCAL\TEMP\WMIDIAG-V2.1_2K8R2.SRV.SP1.64_SSCRDS02_2015.04.15_15.48.25.LOG' for details.
49195 15:56:44 (0) **
49196 15:56:44 (0) ** WMIDiag v2.1 ended on 15 April 2015 at 15:56 (W:110 E:41 S:1).
This seems to be the biggest problem:
48960 15:56:44 (1) !! ERROR: Actual trustee 'NT AUTHORITY\SYSTEM' DOES NOT match corresponding expected trustee rights (Actual->Default)
This seems to be the second biggest error (and there are a few of them):
0x80041002 - (WBEM_E_NOT_FOUND) Object cannot be found.
I have tried:
winmgmt /resyncperf
winmgmt /verifyrepository
winmgmt /salvagerepository
winmgmt /resetrepository
I have also tried registering the mof files with
MOFCOMP <FileName.mof>
Lastly, I even disabled the WMI service, renamed the Repository folder, and had it rebuild the repository.
I got stuck on re registering the 'NT AUTHORITY\SYSTEM' (I think it is in the Components section in Administrative tools), as I could not find clear instructions on exactly how to go about it.
Chkdsk found no errors
Sfc /scannow found no errors
winmgmt /verifyrepository finds no errors.
I'm hoping someone here might be able to steer me in the right direction to get this resolved, as I do not want to rebuild a server that hosts a connection broker and has over 100 user profiles on it, as well as some very annoying and finniky LOB apps installed,
which will have to manually be reinstalled for each profile.

Hi,
Here is a blog regarding how to fix WMI issue might be useful to you:
Fixing WMI issues Using Batch Script
http://social.technet.microsoft.com/wiki/contents/articles/6887.fixing-wmi-issues-using-batch-script.aspx
In addition, you mentioned Remote Desktop Servers are in a cluster setup, would you tell us how did you create the cluster?
As far as I know, with RD Connection Broker, we don’t need to create a cluster but just add multiple RD session hosts into one collection, then RD connection Broker would redirect sessions automatically.
Best Regards,
Amy
Please remember to mark the replies as answers if they help and un-mark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

Session broker and custom conversion manager

I'm having some problem using session broker and a custom conversion manager. I just moved from using single session to using a session broker in the sessions.xml. I'm using a custom conversion manager as shown in this tech. tips URL
http://www.oracle.com/technology/products/ias/toplink/technical/tips/customconversion/index.html
Here's my conversion manager set up code -
public class JpmiConversionManagerSetup extends SessionEventAdapter
* During the pre-login event the new MyConversionManager must be installed
* @see oracle.toplink.sessions.SessionEventAdapter#preLogin
* @param event
public void preLogin(SessionEvent event) {
ConversionManager cm= new JpmiConversionManager();
ConversionManager.setDefaultManager(cm);
event.getSession().getLogin().getPlatform().setConversionManager(cm);
My session broker manages 2 sessions. In sessions.xml for one session I have the <event-listener-class> entry where I need some conversion, another session I don't have any such entry as I don't need any conversion.
Now when I try to run a named query using session broker the conversion part blows up, throws a ConversionException. Any idea? Do I need to configure the session broker instead of session in the preLogin or anything like that?

I think sessions editor is not available in 10.1.3dp4 yet. So I have to write the sessions.xml by hand. But the parser throwing me an error saying that <session-broker> is not allowed in sessions.xml.
SessionLoaderExceptions:
org.xml.sax.SAXParseException: <Line 41, Column 18>: XML-24534: (Error) Element 'session-broker' not expected.
     at oracle.xml.parser.v2.XMLError.flushErrorHandler(XMLError.java:415)
     at oracle.xml.parser.v2.XMLError.flushErrors1(XMLError.java:284)
     at oracle.xml.parser.v2.NonValidatingParser.parseDocument(NonValidatingParser.java:302)
     at oracle.xml.parser.v2.XMLParser.parse(XMLParser.java:199)
     at oracle.xml.jaxp.JXDocumentBuilder.parse(JXDocumentBuilder.java:155)
     at oracle.xml.jaxp.JXDocumentBuilder.parse(JXDocumentBuilder.java:111)
     at oracle.toplink.platform.xml.xdk.XDKParser.parse(XDKParser.java:160)
     at oracle.toplink.platform.xml.xdk.XDKParser.parse(XDKParser.java:190)
     at oracle.toplink.tools.sessionconfiguration.XMLSessionConfigLoader.loadDocument(XMLSessionConfigLoader.java:191)
     at oracle.toplink.tools.sessionconfiguration.XMLSessionConfigLoader.loadDocument(XMLSessionConfigLoader.java:151)
     at oracle.toplink.tools.sessionconfiguration.XMLSessionConfigLoader.load(XMLSessionConfigLoader.java:88)
     at oracle.toplink.tools.sessionmanagement.SessionManager.getSession(SessionManager.java:364)
     at oracle.toplink.tools.sessionmanagement.SessionManager.getSession(SessionManager.java:331)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
Any idea how to or where to write sessions broker in sessions.xml for 10.1.3dp4???

RD Session Broker + NLB doesn't work for external users (internal users on network/WAN are OK)

Hi all,
I have run into an issue as the title of this question suggests.
So the senario is, I have (all Virtual):
2x 2008 R2 Remote Desktop Servers
1x 2008 R2 with Session Broker install
I haven't configured any RD settings on the session broker server (i.e. RD virtual desktop, RD Gateway, etc) It's purely setup as the RD Connection Broker
Each of the RD servers I have configured 2 NIC's. The 1st NIC is configured with NLB (NLB only setup for traffic on port 3389 all other traffic isn't handled by NLB). The other NIC is configured to be used only for session reconnection. I'm hoping this is
the right configuration as it's how I have interpreted these guides:
http://technet.microsoft.com/en-us/library/cc772418%28WS.10%29.aspx
http://technet.microsoft.com/en-us/library/cc771300%28WS.10%29.aspx
Please correct me if I have setup the servers incorrectly and what should be differently.
I have setup the NLBs Cluster IP. A rule has been set on the router to make it available externally
This worked fine with an old single RD Server (same IP as NLB Cluster IP, currently offline so no conflict) before the RD Farm was implemented. So I know the port forwarding is OK.
So NLB and Connection Broker Load-Balancing work well for users inside the network. It spreads sessions evenly and there is no problem with DNS resolving the farm name etc. Sessions that are disconnected are reconnected to the same server, etc.
Accessing the TS Farm from the external address isn't so successful
Connectivity is random. Rarely it works, sometimes it gets to "initiating remote connection..." and then disconnects. It doesn't work more times than it does.
So what do I need to do to get this working? Is there another component or something else that I need to configure to get it all working?
I look forward you your help
Thanks,
Trent

Hi Trent,
If both the RD session broker and the NLB are working fine in
the internal network, I suspect that there is something wrong with the external connection. I’d like to confirm the following questions to narrow down this issue:
1.
Can you PING and telnet this RDS farm name when encountering the “disconnect” issue? For example: telnet farmname
3389.
2.
Can you individually connect to the RDS server when failing to connect it via farm name?
3.
Did you configure any certificate on the RDS server or RD gateway server?
4.
Do you get any event log when this issue happens on the server and client side? If yes, please let me know it word-by-word including the event ID.
Thanks.

Terminalserver Session Broker not reconnecting to existing session

Hi!
Following scenario:
Terminalserver-Farm
2x RemoteDesktopServer (Windows Server 2008R2)
1x TS Session Broker (Windows Server 2008)
A user connects to TS-Farm -> occasionally it happens that he is redirected to (for example) TS2, even if he has an active session on TS1. There is no error message displayed on the client. Subsequently he has 2 sessions, allthough the setting on the Session
Broker is set to "allow only 1 session per user". Interestingly this happens to 2 users only - both are the only ones working on Windows 8 clients (other users are on Win7).
Any ideas how to track down the problem? I don't see the correlation with Windows 8 clients at all.
Best Regards,
Stefan

Hi!
Affected are ThinClients with RDP 5.2 - it's still working on one of the 2008R2, not on the 2nd.
I used network monitor to see traffic from an XP-Thin Client to both Terminalservers. I can see (but not understand): "T125:Disconnect Provider Ultimatum, rn-user-requested" in line 27 at the non-working Terminalserver
Client -> TS 2008R2 with working RDP:
3 11:57:33 08.01.2014 5.3233299 10.5.4.173 10.5.0.106 TCP TCP:Flags=......S., SrcPort=1633, DstPort=MS WBT Server(3389), PayloadLen=0, Seq=2968904019, Ack=0, Win=65535 ( ) = 65535 {TCP:2, IPv4:1}
4 11:57:33 08.01.2014 5.3238252 10.5.0.106 10.5.4.173 TCP TCP:Flags=...A..S., SrcPort=MS WBT Server(3389), DstPort=1633, PayloadLen=0, Seq=2063055863, Ack=2968904020, Win=8192 ( Scale factor not supported ) = 8192 {TCP:2, IPv4:1}
5 11:57:33 08.01.2014 5.3242143 10.5.4.173 10.5.0.106 TCP TCP:Flags=...A...., SrcPort=1633, DstPort=MS WBT Server(3389), PayloadLen=0, Seq=2968904020, Ack=2063055864, Win=65535 (scale factor 0x0) = 65535 {TCP:2, IPv4:1}
6 11:57:33 08.01.2014 5.3255958 10.5.4.173 10.5.0.106 X224 X224:Connection Request {ISOTS:3, TCP:2, IPv4:1}
7 11:57:33 08.01.2014 5.3273352 10.5.0.106 10.5.4.173 TCP TCP:Flags=...A...., SrcPort=MS WBT Server(3389), DstPort=1633, PayloadLen=0, Seq=2063055864, Ack=2968904031, Win=64240 (scale factor 0x0) = 64240 {TCP:2, IPv4:1}
8 11:57:33 08.01.2014 5.3274171 10.5.0.106 10.5.4.173 X224 X224:Connection Confirm {ISOTS:3, TCP:2, IPv4:1}
9 11:57:33 08.01.2014 5.3293456 10.5.4.173 10.5.0.106 T125 T125:MCSConnect Initial {T125:4, ISOTS:3, TCP:2, IPv4:1}
10 11:57:33 08.01.2014 5.3298119 10.5.0.106 10.5.4.173 T125 T125:MCSConnect Response {T125:4, ISOTS:3, TCP:2, IPv4:1}
11 11:57:33 08.01.2014 5.3315607 10.5.4.173 10.5.0.106 TCP TCP:Flags=...A...., SrcPort=1633, DstPort=MS WBT Server(3389), PayloadLen=0, Seq=2968904443, Ack=2063057917, Win=65535 (scale factor 0x0) = 65535 {TCP:2, IPv4:1}
12 11:57:33 08.01.2014 5.3322727 10.5.4.173 10.5.0.106 T125 T125:Erect Domain Request, SubHeight = 0, SubInterval = 0 {T125:4, ISOTS:3, TCP:2, IPv4:1}
13 11:57:33 08.01.2014 5.3324046 10.5.4.173 10.5.0.106 T125 T125:Attach User Request {T125:4, ISOTS:3, TCP:2, IPv4:1}
14 11:57:33 08.01.2014 5.3324212 10.5.0.106 10.5.4.173 TCP TCP:Flags=...A...., SrcPort=MS WBT Server(3389), DstPort=1633, PayloadLen=0, Seq=2063057917, Ack=2968904463, Win=63808 (scale factor 0x0) = 63808 {TCP:2, IPv4:1}
15 11:57:33 08.01.2014 5.3324293 10.5.0.106 10.5.4.173 T125 T125:Attach User Confirm, Result = rt-successful, Indicator = 0x3ef {T125:4, ISOTS:3, TCP:2, IPv4:1}
16 11:57:33 08.01.2014 5.3330774 10.5.4.173 10.5.0.106 T125 T125:Channel Join Request, UserID = 0x3ef,ChannelId = 0x3ef {T125:4, ISOTS:3, TCP:2, IPv4:1}
17 11:57:33 08.01.2014 5.3331055 10.5.0.106 10.5.4.173 T125 T125:Channel Join Confirm, ChannelId = 1007, Result = rt-successful {T125:4, ISOTS:3, TCP:2, IPv4:1}
18 11:57:33 08.01.2014 5.3340565 10.5.4.173 10.5.0.106 T125 T125:Channel Join Request, UserID = 0x3ef,ChannelId = 0x3eb {T125:4, ISOTS:3, TCP:2, IPv4:1}
19 11:57:33 08.01.2014 5.3340826 10.5.0.106 10.5.4.173 T125 T125:Channel Join Confirm, ChannelId = 1003, Result = rt-successful {T125:4, ISOTS:3, TCP:2, IPv4:1}
20 11:57:33 08.01.2014 5.3345604 10.5.4.173 10.5.0.106 T125 T125:Channel Join Request, UserID = 0x3ef,ChannelId = 0x3ec {T125:4, ISOTS:3, TCP:2, IPv4:1}
21 11:57:33 08.01.2014 5.3345856 10.5.0.106 10.5.4.173 T125 T125:Channel Join Confirm, ChannelId = 1004, Result = rt-successful {T125:4, ISOTS:3, TCP:2, IPv4:1}
22 11:57:33 08.01.2014 5.3356991 10.5.4.173 10.5.0.106 T125 T125:Channel Join Request, UserID = 0x3ef,ChannelId = 0x3ed {T125:4, ISOTS:3, TCP:2, IPv4:1}
23 11:57:33 08.01.2014 5.3357256 10.5.0.106 10.5.4.173 T125 T125:Channel Join Confirm, ChannelId = 1005, Result = rt-successful {T125:4, ISOTS:3, TCP:2, IPv4:1}
24 11:57:33 08.01.2014 5.3362559 10.5.4.173 10.5.0.106 T125 T125:Channel Join Request, UserID = 0x3ef,ChannelId = 0x3ee {T125:4, ISOTS:3, TCP:2, IPv4:1}
25 11:57:33 08.01.2014 5.3362827 10.5.0.106 10.5.4.173 T125 T125:Channel Join Confirm, ChannelId = 1006, Result = rt-successful {T125:4, ISOTS:3, TCP:2, IPv4:1}
26 11:57:33 08.01.2014 5.3450865 10.5.4.173 10.5.0.106 RDPBCGR RDPBCGR: {RDPBCGR:5, T125:4, ISOTS:3, TCP:2, IPv4:1}
27 11:57:33 08.01.2014 5.3456510 10.5.4.173 10.5.0.106 RDPBCGR RDPBCGR:TsClientSecurityExchangePDU Encrypted {RDPBCGR:5, T125:4, ISOTS:3, TCP:2, IPv4:1}
28 11:57:33 08.01.2014 5.3456706 10.5.0.106 10.5.4.173 TCP TCP:Flags=...A...., SrcPort=MS WBT Server(3389), DstPort=1633, PayloadLen=0, Seq=2063058003, Ack=2968904946, Win=63325 (scale factor 0x0) = 63325 {TCP:2, IPv4:1}
29 11:57:33 08.01.2014 5.3460200 10.5.0.106 10.5.4.173 RDPELE RDPELE:Encrypted {RDPBCGR:5, T125:4, ISOTS:3, TCP:2, IPv4:1}
30 11:57:33 08.01.2014 5.3900913 10.5.0.106 10.5.4.173 RDPBCGR RDPBCGR:SlowPathPacket Encrypted {RDPBCGR:5, T125:4, ISOTS:3, TCP:2, IPv4:1}
31 11:57:33 08.01.2014 5.3909177 10.5.4.173 10.5.0.106 TCP TCP:Flags=...A...., SrcPort=1633, DstPort=MS WBT Server(3389), PayloadLen=0, Seq=2968904946, Ack=2063058498, Win=64954 (scale factor 0x0) = 64954 {TCP:2, IPv4:1}
32 11:57:33 08.01.2014 5.4047118 10.5.4.173 10.5.0.106 RDPBCGR RDPBCGR:SlowPathPacket Encrypted {RDPBCGR:5, T125:4, ISOTS:3, TCP:2, IPv4:1}
33 11:57:33 08.01.2014 5.4047805 10.5.0.106 10.5.4.173 RDPBCGR RDPBCGR:SlowPathPacket Encrypted {RDPBCGR:5, T125:4, ISOTS:3, TCP:2, IPv4:1}
34 11:57:33 08.01.2014 5.4047946 10.5.0.106 10.5.4.173 RDPBCGR RDPBCGR:SlowPathPacket Encrypted {RDPBCGR:5, T125:4, ISOTS:3, TCP:2, IPv4:1}
Client -> TS 2008R2 with non-working RDP:
3 11:21:03 08.01.2014 4.7063150 10.5.4.173 10.5.0.144 TCP TCP:Flags=......S., SrcPort=1526, DstPort=MS WBT Server(3389), PayloadLen=0, Seq=459527613, Ack=0, Win=65535 ( ) = 65535 {TCP:2, IPv4:1}
4 11:21:03 08.01.2014 4.7067575 10.5.0.144 10.5.4.173 TCP TCP:Flags=...A..S., SrcPort=MS WBT Server(3389), DstPort=1526, PayloadLen=0, Seq=2589137033, Ack=459527614, Win=8192 ( Scale factor not supported ) = 8192 {TCP:2, IPv4:1}
5 11:21:03 08.01.2014 4.7071555 10.5.4.173 10.5.0.144 TCP TCP:Flags=...A...., SrcPort=1526, DstPort=MS WBT Server(3389), PayloadLen=0, Seq=459527614, Ack=2589137034, Win=65535 (scale factor 0x0) = 65535 {TCP:2, IPv4:1}
6 11:21:03 08.01.2014 4.7101168 10.5.4.173 10.5.0.144 X224 X224:Connection Request {ISOTS:3, TCP:2, IPv4:1}
7 11:21:03 08.01.2014 4.7101591 10.5.0.144 10.5.4.173 X224 X224:Connection Confirm {ISOTS:3, TCP:2, IPv4:1}
8 11:21:03 08.01.2014 4.7110721 10.5.4.173 10.5.0.144 T125 T125:MCSConnect Initial {T125:4, ISOTS:3, TCP:2, IPv4:1}
9 11:21:03 08.01.2014 4.7114117 10.5.0.144 10.5.4.173 T125 T125:MCSConnect Response {T125:4, ISOTS:3, TCP:2, IPv4:1}
10 11:21:03 08.01.2014 4.7130978 10.5.4.173 10.5.0.144 TCP TCP:Flags=...A...., SrcPort=1526, DstPort=MS WBT Server(3389), PayloadLen=0, Seq=459528060, Ack=2589139965, Win=65535 (scale factor 0x0) = 65535 {TCP:2, IPv4:1}
11 11:21:03 08.01.2014 4.7131136 10.5.0.144 10.5.4.173 TCP TCP:[Continuation to #9]Flags=...AP..., SrcPort=MS WBT Server(3389), DstPort=1526, PayloadLen=2286, Seq=2589139965 - 2589142251, Ack=459528060, Win=63828 (scale factor 0x0) = 63828 {TCP:2, IPv4:1}
12 11:21:03 08.01.2014 4.7137283 10.5.4.173 10.5.0.144 TCP TCP:Flags=...A...., SrcPort=1526, DstPort=MS WBT Server(3389), PayloadLen=0, Seq=459528060, Ack=2589141425, Win=65535 (scale factor 0x0) = 65535 {TCP:2, IPv4:1}
13 11:21:03 08.01.2014 4.7142557 10.5.4.173 10.5.0.144 T125 T125:Erect Domain Request, SubHeight = 0, SubInterval = 0 {T125:4, ISOTS:3, TCP:2, IPv4:1}
14 11:21:03 08.01.2014 4.7143931 10.5.4.173 10.5.0.144 T125 T125:Attach User Request {T125:4, ISOTS:3, TCP:2, IPv4:1}
15 11:21:03 08.01.2014 4.7144101 10.5.0.144 10.5.4.173 TCP TCP:Flags=...A...., SrcPort=MS WBT Server(3389), DstPort=1526, PayloadLen=0, Seq=2589142251, Ack=459528080, Win=63808 (scale factor 0x0) = 63808 {TCP:2, IPv4:1}
16 11:21:03 08.01.2014 4.7144276 10.5.0.144 10.5.4.173 T125 T125:Attach User Confirm, Result = rt-successful, Indicator = 0x3ef {T125:4, ISOTS:3, TCP:2, IPv4:1}
17 11:21:03 08.01.2014 4.7152352 10.5.4.173 10.5.0.144 T125 T125:Channel Join Request, UserID = 0x3ef,ChannelId = 0x3ef {T125:4, ISOTS:3, TCP:2, IPv4:1}
18 11:21:03 08.01.2014 4.7152672 10.5.0.144 10.5.4.173 T125 T125:Channel Join Confirm, ChannelId = 1007, Result = rt-successful {T125:4, ISOTS:3, TCP:2, IPv4:1}
19 11:21:03 08.01.2014 4.7162762 10.5.4.173 10.5.0.144 T125 T125:Channel Join Request, UserID = 0x3ef,ChannelId = 0x3eb {T125:4, ISOTS:3, TCP:2, IPv4:1}
20 11:21:03 08.01.2014 4.7163087 10.5.0.144 10.5.4.173 T125 T125:Channel Join Confirm, ChannelId = 1003, Result = rt-successful {T125:4, ISOTS:3, TCP:2, IPv4:1}
21 11:21:03 08.01.2014 4.7172413 10.5.4.173 10.5.0.144 T125 T125:Channel Join Request, UserID = 0x3ef,ChannelId = 0x3ec {T125:4, ISOTS:3, TCP:2, IPv4:1}
22 11:21:03 08.01.2014 4.7172699 10.5.0.144 10.5.4.173 T125 T125:Channel Join Confirm, ChannelId = 1004, Result = rt-successful {T125:4, ISOTS:3, TCP:2, IPv4:1}
23 11:21:03 08.01.2014 4.7183019 10.5.4.173 10.5.0.144 T125 T125:Channel Join Request, UserID = 0x3ef,ChannelId = 0x3ed {T125:4, ISOTS:3, TCP:2, IPv4:1}
24 11:21:03 08.01.2014 4.7183348 10.5.0.144 10.5.4.173 T125 T125:Channel Join Confirm, ChannelId = 1005, Result = rt-successful {T125:4, ISOTS:3, TCP:2, IPv4:1}
25 11:21:03 08.01.2014 4.7193451 10.5.4.173 10.5.0.144 T125 T125:Channel Join Request, UserID = 0x3ef,ChannelId = 0x3ee {T125:4, ISOTS:3, TCP:2, IPv4:1}
26 11:21:03 08.01.2014 4.7193736 10.5.0.144 10.5.4.173 T125 T125:Channel Join Confirm, ChannelId = 1006, Result = rt-successful {T125:4, ISOTS:3, TCP:2, IPv4:1}
27 11:21:03 08.01.2014 4.7234596 10.5.4.173 10.5.0.144 T125 T125:Disconnect Provider Ultimatum, rn-user-requested {T125:4, ISOTS:3, TCP:2, IPv4:1}
28 11:21:03 08.01.2014 4.7237173 10.5.4.173 10.5.0.144 TCP TCP:Flags=...A...F, SrcPort=1526, DstPort=MS WBT Server(3389), PayloadLen=0, Seq=459528149, Ack=2589142337, Win=64623 (scale factor 0x0) = 64623 {TCP:2, IPv4:1}
29 11:21:03 08.01.2014 4.7237356 10.5.0.144 10.5.4.173 TCP TCP:Flags=...A...., SrcPort=MS WBT Server(3389), DstPort=1526, PayloadLen=0, Seq=2589142337, Ack=459528150, Win=63739 (scale factor 0x0) = 63739 {TCP:2, IPv4:1}
30 11:21:03 08.01.2014 4.7237527 10.5.0.144 10.5.4.173 TCP TCP:Flags=...A.R.., SrcPort=MS WBT Server(3389), DstPort=1526, PayloadLen=0, Seq=2589142337, Ack=459528150, Win=0 (scale factor 0x0) = 0 {TCP:2, IPv4:1}

How to test individual servers using session broker

Hi,
We have 6 terminal servers and have recently switched from NLB to Session broker using RR DNS. This method balances our users much better, but has introduced a new issue. After we make a change to the terminal servers (such as applying a patch) We like to
log onto to each one with a user account and ensure everything is working as expected. But now we've found with session broker when we try to log directly onto a server we are redirected to the farm and put on the same server over and over again. We know about
using mstsc /admin to log onto as admin, but this is not the functionality we want to test (are admin accounts can't do things the user account can such as access the internet, and there is a concern that if we are using an admin account it may mask an issue
that the less privileged user accounts might have.
Thanks,

" Doesn't applying a patch to a server change the state and thus introduce risk?" Yes it does, which is why we are testing the server, but we prefer to test the server in the actual state the users will be using the server, plus there is the concern
if a server wasn't added back it it would cause a problem.
"If you are concerned about temporarily changing the load-balancing participation of each server then I recommend you go with "bulk" testing--keep logging on users until you hit all of your RDSH servers." The problem with this approach is that we would be
allowing users to log onto to servers before testing was completed (we do these changes off hours). And since right now we only have one user account to test with what is happening we log onto the first server test it, log off, but then we are repeatably load
balanced onto that server.
"Another idea would be to write a custom plugin for the RD Connection Broker that would change the load balancing logic. For example, when enabled, it would look at an xml file to determine if the user was listed and if yes direct them to a certain
server, otherwise use default load balancing logic."
We might have to look into this idea.
Thanks for your suggestions.
Rich

IsolatedClientSession (10.1.3) vs. custom session broker

Hi, Doug.
You may still remember the design of the custom session broker originated from you in our project.
Basically, we dynamically partition the classes during the session initiation time such that all the read-only classes (reference data) are put to a shared server session and all the non-read-only classes (transactional data) to a database session. A custom client session broker is constructed based on two sessions, the shared server session and a private database session whose life only spans a single transaction. The main idea here is that, the transactional data is volatile, and should not been cached in the shared session cache.
Now, with TopLink_10.1.3 available, I noticed that there is a new type of session called isolated client session, and that a class can be configured to be isolated. In my understanding, this solves the exactly same problem as the custom session broker.
I did some investigation to see whether it is possible for replace the custom session broker by the isolated client session. However, I got a run time exception:
Isolated Data is not currently supported within a Client Session Broker.
My questions is:
Is the isolated data to be supported by the client session broker soon?
Or you have other suggestions?
Thanks.
Zhonghua

Thanks for your response.
Yes, you are right, and it is not entirely necessary for us to use SessionBroker any more. I already did some experiments in this regard.
But, there are two downsides here:
(1) The existing code and configuration are tied to the SessionBroker, and lots of changes would be required.
(2) SessionBroker does provide us some flexibility in case we do need to use multiple databases in the future.
Therefore, if TopLink will support isolated classes in the client SessionBroker soon, it would be better for us to just wait for a future release.

2012 R2 Terminalserver Shadow a Session from Session Broker

Hi,
I installed 3 RD Session Hosts Windwos 2012 R2 and one Session Broker also Windows 2012 R2.
Now, when a user is logged in to a session on the RD Host, and i would to shadow it from the Session Broker Server Manager, or send a message, I bekame a error: the Session ar not connected!
How i resolve this issue?
Thx, Edin

Hi,
Before going further, can you elaborate with us which Windows updates you have installed? Besides, can we boot the servers into Safe Mode? If the servers can boot into Safe Mode, we can try to uninstall the updates to see
if it helps.
Best regards,
Frank Shen

RDS Session Broker

Hi,
actually I have an issue in an Broker scenario on Windows 2008 R2.
Scenario: Windows 2008 R2 RDS
2 Session Hosts for RemoteApps and Desktop (No VD)
NLB configured for the a farm on 10.1.1.100 on both Session Hosts
Farmname = RDSFarm.xxxx.xxx
No WebAccess (IIS is installed on the Session Broker Server)
DNS Entry in place = 10.1.1.100 (nslookup works)
I moved the Session Broker from an an Domain Controller to an Member Server based on Windows 2008 R2.
I also renewed the farm certificate RDSFarm.xxx.xxx and configure it on all RDS Hosts to use this certificate.
Now the problem:
I cannot connect to my RDSFarm.xxx.xxx: Error (using Windows 7):
"The connection cannot be completed because the remote computer that was reached is not the one you specified. This could be caused by an outdated entry in the DNS cache. Try using the IP address of the computer instead of the name."
What I've checked (and double checked):
- RDS Session Hosts are in the local Group of the new Session Broker Host -> check
- Farm certificate in all required Settings on Broker and Session Hosts
- DNS Entries (Also tried with round robin and without)
- Farm Membership
- FlushDNS
- Trying to use IP - then there is a certificate warning that the computername 10.1.1.100 does not match the certificate named RDSFarm.xxx.xxx (Tis is what I expected) - and i got a connection.
I get no more error messages except that my RDP Client cannot connect. How can I find more connection information or how to troubleshoot this ? Do I miss something during the migration from a DC to a member server ? Can anyone gave me a hint ? :-)
Greetings
Tobias

Hi,
Thanks for the update and I am glad to hear that the issue has been resolved.
Cheers.
Jeremy Wu
TechNet Community Support

How to use Session Broker ? (Where to add Session Broker Code)

Hi all,
My requirement is, I have to use two different database session in one Top Link.
I know it can be done using Session Broker, but where actually I need to add that code ? I am using JDeveloper 10.1.2.0.0(Build 1811) as i need to implement this in a BPEL process. Is it possible use Session Broker with this version , if so how to do that ?
Thanks in advance,
Anant.

Hello Anant,
Not sure what code you are refering to. Using a SessionBroker is similar to how you would use a regular session, and can be configured using sessions.xml or through java code. If you are using java code, you would do this where ever you first acquire the sessionbroker and login.
Please refer to the docs on what it is and how it is used:
http://download-west.oracle.com/docs/cd/B25221_04/web.1013/b13593/sesun007.htm#CACGDDHE
The docs are for TopLink 10.1.3, and though I think TopLink 10.1.2 (9.0.4.5) is what ships with Jdev 10.1.2, they should still apply.
Best Regards,
Chris

Core/examples/sessions/Broker example not working

Guys
I am trying the example with Oracle database instead of the HSQL database. I replaced the driver & url strings and put the classes12.jar in the classpath
But I continue to get the following error. Can someone please tell me what I am missing.
D:\toplink\examples\core\examples\sessions\broker>D:\JDev9i\jdk\bin\java.exe -classpath ""D:\JDev9i\jdk\lib\tools.jar";"d:\to
plink\ant\lib\jaxp.jar";"d:\toplink\ant\lib\jakarta-ant-1.4.1-optional.jar";"d:\toplink\ant\lib\crimson.jar";"d:\toplink\ant\
lib\ant.jar";.;d:\toplink\core\lib\toplink.jar;D:\JDev9i\jdbc\lib\classes12.jar;d:\toplink\core\lib\toplink.
jar;D:\JDev9i\jdbc\lib\classes12.jar" -Dant.home=d:\toplink\ant -Dtl.home=d:\toplink -Dwls61.home= -Dwls70.home= -Dwas.home=
-Doracle.home=D:\JDev9i\OC4J903 -Dexamples.home=d:\toplink\examples -Dtoplink.dir=d:\toplink\core\lib -Dtoplink.library=topli
nk.jar,xerces.jar -Dtoplink.weblogic.path=d:\toplink\wls_cmp\lib\tl_wlsx.jar -Dtoplink.was.path=d:\toplink\was_cmp\lib\tl_wa
sx.jar -Dhsql.path=d:\toplink\HSQL\lib\hsqldb.jar -DDEBUG=on org.apache.tools.ant.Main runExample -DtestClass=examples.sessions.broker.Demo
Buildfile: build.xml
init:
verify.build.done:
runExample:
[java] 2003.05.19 03:54:35.625--DatabaseSession(11)--Thread[main,5,main]--Connection(12)--TopLink, version:TopLink - 9.0
.3 (Build 423)
[java] 2003.05.19 03:54:35.685--DatabaseSession(11)--Thread[main,5,main]--Connection(12)--connecting(DatabaseLogin(
[java] platform => OraclePlatform
[java] user name => "asdfbf"
[java] datasource URL => "jdbc:oracle:thin:@localhost:fims"
[java] ))
[java] 2003.05.19 03:54:35.705--DatabaseSession(11)--Thread[main,5,main]--EXCEPTION [TOPLINK-4003] (TopLink - 9.0.3 (Bui
ld 423)): oracle.toplink.exceptions.DatabaseException
[java] EXCEPTION DESCRIPTION: Configuration error. Class [oracle.jdbc.driver.OracleDriver] not found.LOCAL EXCEPTION ST
ACK:

One more thing to add:
I am not able to get any of the examples to work with Oracle database. Again the only thing I suppose I need to change are the folloowing lines in the EmployeeProject.java
     login.usePlatform(new oracle.toplink.internal.databaseaccess.OraclePlatform());
     login.setDriverClassName("oracle.jdbc.driver.OracleDriver");
     login.setConnectionString("jdbc:oracle:thin:@localhost:1522:fims");
     login.setUserName("kumarv");
     login.setEncryptedPassword("7AD96CD575D1A7FCAA504BA7E4FC");
Also one line change in the sessions.xml file to use the OraclePlatform instead of the HSQLPlatform.
Has any one got these to work with Oracle, Any help is really appreciated.
classes12.jar is in the classpath so I don;t understand why I get the execption that:
[java] EXCEPTION DESCRIPTION: Configuration error. Class [oracle.jdbc.driver.OracleDriver] not found.
[java] oracle.toplink.exceptions.DatabaseException oracle.toplink.exceptions.DatabaseException.configurationErrorCla
ssNotFound(java.lang.String)
Thanks

2008 R2 Session Broker allowing multiple sessions

I have the options set to restrict a user to a single session in RDS however I am having problems with two things. i initially thought it was because I had a startup script setup in GPO however I removed that and the issue is still happening.
1. If a user disconnects they do not always get reconnected to their disconnected session.
2. A user with an active session can go on a different device and connect and get a new session on a different session host.
Configuration:
3 Session hosts
RDS Session Broker (Is the session broker for 2 different RDS farms)
GPO to restrict users to a single session in place for session hosts

Hi,
Can you able to connect each RDSH server with its unique IP address?
You can check under RDSH configuration on RDSH server that IP redirection for selecting dedicated IP address for individual server is used. For a connection to redirect for RDSH server it must be the unique IP address for destination RDSH server.
For this issue there is hotfix (KB 977541) available for Server 2008 (you can refer for workaround part), might it works for your case. Refer below article for more information on
IP redirection.
About IP Address and Token Redirection
http://technet.microsoft.com/en-us/library/cc732852.aspx
Hope it helps!
Thanks.

Rdesktop version and 2k8 Session Broker

Has anyone had success utilizing Sun Ray with Server 2k8 TS Session Broker load balancing. If not, what is everyone using to load balance TS connections?
Thanks!

When can we expect the new release? Is this support documented anywhere and do you know if there may be a beta program available?
Thanks!

NLB need if RDS Session Broker present ???

Hi,
- For RDS, i already installed RDS session broker. Is NLB still need ??
- What's the different between NLB and RDS session broker ?? Since they do the same thing.
Thanks

Hi,
Thank you for your posting in Windows Server Forum.
As per my research, if you are using RD Connection Broker then you don’t need NLB. RD Connection broker will act as redirector to redirect different RDSH server. When it receives a session-connection request, an initial load-balancing mechanism (Network Load
Balancing [NLB], Round Robin DNS [RRDNS] or a hardware load balancer) will send the request to the redirector (one of the RD Session Host servers in a farm).
Please go through beneath article for clear understanding of RDCB server.
Understand the RD Connection Broker
http://technet.microsoft.com/en-us/magazine/hh413262.aspx
Remote Desktop Connection Broker
http://technet.microsoft.com/en-us/library/cc771419.aspx
Remote Desktop Server farms explained (Part 1)
http://www.virtualizationadmin.com/articles-tutorials/vdi-articles/general/remote-desktop-server-farms-explained-part1.html
Hope it helps!
Thanks,
Dharmesh

RD Session broker issue; Cannot connect to one of the host servers through RDC

Hello,
I am testing a RD session broker role.
So I have 4 VMs: lest call them VM1, VM2 VM3 and VM4
VM1 is the DC and all other 3 VMs are under VM1.
VM2 is the Session broker server.
VM3 and VM4 are the host servers which are in a farm called Farm1.
Now I have done everything pretty much right. VM2, VM3 and VM4 all are listed in the Session broker computer local group (which is on VM2 since it is the session broker server)
Then I also have VM3 and VM4 setup in regards to their Remote desktop session host configuration.
RD Connection broker is VM2 and Farm name is Farm1.
everything sounds good right?
Okay.. So then I also have added those "New host (A or AAAA)" for VM3 and VM4 in the DNS on VM1 (which is DC).
Both VM3 and VM4 are set to 100 in "Relative weight of this server in the farm".
Now I am trying to do MSTSC from VM2 to farm1.domain.net. First user goes to VM3 just fine. But when I try to do MSTSC again with the second user, it tells me this:
The remote computer hat you are trying to connect is redirecting you to the remote computer.
Remote Desktop Connection cannot verify that the two remote computers belong to the same farm.
This can occur if there is another computer on your network with the same name as the computer your are trying to connect to.
I have read 10 pages of google search about this and still have no clue what to do. I have tried flushing DNS cache on VM1. Time and date is exactly the same on all 4 VMs.
I also read the following thread but could not understand the answer that he has given there.
http://social.technet.microsoft.com/Forums/windowsserver/en-US/40be1eda-f752-4b64-bb47-dbe2156218f9/remoteapp-cannot-verify-computers-belong-to-the-same-server-farm?forum=winserverTS
Please help me on this.
Thanks,

Okay, so I found the issue and was able to solve the problem.
Here is how to do this and I wonder why most of the online guides to do this whole thing don't talk about it!
Go to Start --> Administrative tools --> Remote desktop services --> RemoteApp Manager
Now a new window will open and in the window there's a box which says "Overview".
The first option will say " RD Session Host Server Setting; Clients will be redirected to: computer.domain.com"
That's where you need to make a change. If you'd open that, it will tell you that "If the RD session Host Server is in a farm, enter the DNS name of the farm".
So now make that "Server name" look like this: farm.domain.com or whatever your farm's DNS name is.
Do this on all the host servers and yeah then you might need to refresh the DNS settings on the DC.
It should start working then :)

Session Broker Newbee

Similar Messages

Maybe you are looking for