Zdroje informací pro profesionály v oboru IT >
Domovská stránka fór
>
Terminal Services
>
Unable to join Terminal Servers to Session Broker Farm
Unable to join Terminal Servers to Session Broker Farm
- Hey I'm hoping someone can give me an answer here. I'm setting up a TS Farm of two servers. I've got my Session Broker all set up on another server and everything looks to be running fine on that server.
I've added the Terminal Servers to the Local Group on the Session Broker, and set up everything as it should be there.
When I'm on the Terminal Servers themselves in Terminal Services Configuration module I am unable to Join a farm in TS Session Broker. When I open up the settings everything is Grayed out and I am unable to click anything. I have no idea why?
Odpovědi
- A grayed-out setting means that a Group Policy is configured for this setting.Check this one:Administrative Templates\Windows Components\Terminal Services\Session Directory"Join Session Directory"_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net"mgladding" <=?utf-8?B?bWdsYWRkaW5n?=> skrev i meddelandet news:318f26da-d2b1-4b7 d-b2ba-9c134636e09f...Got some more information. We're setting up a third terminal server. If you go into the Session Broker settings before it's joined to the domain it's not grayed out. If you go into it after you join the domain it is grayed out and I can't enter anything. So something in the domain is blocking it. Like a said it's a 2003 domain so is that maybe the problem?- Označen jako odpověďChrista AndersonMSFT, Moderátor15. června 2009 17:20
Všechny reakce
Is there anything specified in your Group Policy that over-rides the local settings?
Computer Config>Policies>Admin Templates>Windows Components>Terminal Services>Terminal Server>TS Session Broker.
Check the 'Join TS Session Broker' policy, if it is not configured then you could always configure it and see if that helps.- That's another issue... there in a strictly 2003 domain (no 2008 DC). Might that be the issue? As far as anything set in Group Policy I don't see anything, but again it's a 2003 domain so those settings aren't there.
Edit: Also setting it in group policy wouldn't allow to control the Weight of each server... - No one has any answers here? I really need to figure this out and I can't find anything anywhere that is set that would block my ability to set these things.
nvm
- Got some more information. We're setting up a third terminal server. If you go into the Session Broker settings before it's joined to the domain it's not grayed out. If you go into it after you join the domain it is grayed out and I can't enter anything. So something in the domain is blocking it. Like a said it's a 2003 domain so is that maybe the problem?
- A grayed-out setting means that a Group Policy is configured for this setting.Check this one:Administrative Templates\Windows Components\Terminal Services\Session Directory"Join Session Directory"_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net"mgladding" <=?utf-8?B?bWdsYWRkaW5n?=> skrev i meddelandet news:318f26da-d2b1-4b7 d-b2ba-9c134636e09f...Got some more information. We're setting up a third terminal server. If you go into the Session Broker settings before it's joined to the domain it's not grayed out. If you go into it after you join the domain it is grayed out and I can't enter anything. So something in the domain is blocking it. Like a said it's a 2003 domain so is that maybe the problem?- Označen jako odpověďChrista AndersonMSFT, Moderátor15. června 2009 17:20
- A grayed-out setting means that a Group Policy is configured for this setting.Check this one:Administrative Templates\Windows Components\Terminal Services\Session Directory"Join Session Directory"_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net"mgladding" <=?utf-8?B?bWdsYWRkaW5n?=> skrev i meddelandet news:318f26da-d2b1-4b7 d-b2ba-9c134636e09f ...Got some more information. We're setting up a third terminal server. If you go into the Session Broker settings before it's joined to the domain it's not grayed out. If you go into it after you join the domain it is grayed out and I can't enter anything. So something in the domain is blocking it. Like a said it's a 2003 domain so is that maybe the problem?
I checked that setting and it's completely disabled. And these are 2008 terminal servers in a 2003 domain so might that be the problem? - The setting is Disabled or Not configured? Big difference.
- Hi;
Is your terminal servers running windows server 2003? If it is, Windows Server 2003 based terminal servers cannot use the TS Session Broker Load Balancing feature.
