log on termincal server not working
in [Terminal Services]
|
Prev: session printers
Next: Profile Issues
From: george hardy on 14 Apr 2008 13:50 Hello All, * I have a SBS2003 that is my main machine now (new computer), and I am now using it for my Domain Controller (AD). * I have another 2003 Server Standard (old computer) that WAS the domain controller, but i attached it to the SBS2003 Domain--this way I can manage the user accounts in one place, instead of creating them on the old and the new computer. On the older computer (2003Standard) I have my terminal server licensing server (unlimited). I was hoping that now that computer is hooked up to the SBS2003 domain, that all the users would be able to login to the terminal server (the old computer) without problem. It is giving me the message when a user tries to login, they get: "To logon to this remote computer, you must have Terminal Server User Acces permissions on this computer. By default, members of the Remote Desktop Users group have these permissions. If you are not a member of the Remote Desktop users group or another group that has these permissions, or if ....blah blah blah...you must grant them manually" I have added all the users in my domain to the Remote Desktop Users group, and still no luck. I'm no Group Policy expert by any means, but i even tried granting "Allow lon on through Terminal Services" in the section 1 - Small Business Server Windows Firewall -enforced yes - link enabled yes-gpo status Enabled anyone have an idea what im doing wrong? I have had to created local user accounts on the old computer to get my employees working again. Please help! thanks, george h
From: Vera Noest [MVP] on 14 Apr 2008 14:26 You have to add the domain accounts of the users to the *local* built-in Remote Desktop Users group on the Terminal Server itself. _________________________________________________________ Vera Noest MCSE, CCEA, Microsoft MVP - Terminal Server TS troubleshooting: http://ts.veranoest.net ___ please respond in newsgroup, NOT by private email ___ "george hardy" <nospam(a)nospam.com> wrote on 14 apr 2008 in microsoft.public.windows.terminal_services: > Hello All, > > * I have a SBS2003 that is my main machine now (new computer), > and I am now using it for my Domain Controller (AD). > * I have another 2003 Server Standard (old computer) that WAS > the domain controller, but i attached it to the SBS2003 > Domain--this way I can manage the user accounts in one place, > instead of creating them on the old and the new computer. > > On the older computer (2003Standard) I have my terminal server > licensing server (unlimited). I was hoping that now that > computer is hooked up to the SBS2003 domain, that all the users > would be able to login to the terminal server (the old computer) > without problem. > > It is giving me the message when a user tries to login, they > get: "To logon to this remote computer, you must have Terminal > Server User Acces permissions on this computer. By default, > members of the Remote Desktop Users group have these > permissions. If you are not a member of the Remote Desktop > users group or another group that has these permissions, or if > ...blah blah blah...you must grant them manually" > > I have added all the users in my domain to the Remote Desktop > Users group, and still no luck. > > I'm no Group Policy expert by any means, but i even tried > granting "Allow lon on through Terminal Services" in the section > 1 - Small Business Server Windows Firewall -enforced yes - link > enabled yes-gpo status Enabled > > anyone have an idea what im doing wrong? I have had to created > local user accounts on the old computer to get my employees > working again. Please help! > > thanks, > george h
From: Merv Porter [SBS-MVP] on 14 Apr 2008 14:32 Did you use ConnectComputer (you should) to join the TS server to the SBS domain? -- Merv Porter [SBS-MVP] ============================ "george hardy" <nospam(a)nospam.com> wrote in message news:uPZrAhlnIHA.5160(a)TK2MSFTNGP05.phx.gbl... > Hello All, > > * I have a SBS2003 that is my main machine now (new computer), and I am > now using it for my Domain Controller (AD). > * I have another 2003 Server Standard (old computer) that WAS the domain > controller, but i attached it to the SBS2003 Domain--this way I can manage > the user accounts in one place, instead of creating them on the old and > the new computer. > > On the older computer (2003Standard) I have my terminal server licensing > server (unlimited). I was hoping that now that computer is hooked up to > the SBS2003 domain, that all the users would be able to login to the > terminal server (the old computer) without problem. > > It is giving me the message when a user tries to login, they get: > "To logon to this remote computer, you must have Terminal Server User > Acces permissions on this computer. By default, members of the Remote > Desktop Users group have these permissions. If you are not a member of > the Remote Desktop users group or another group that has these > permissions, or if ...blah blah blah...you must grant them manually" > > I have added all the users in my domain to the Remote Desktop Users group, > and still no luck. > > I'm no Group Policy expert by any means, but i even tried granting "Allow > lon on through Terminal Services" in the section > 1 - Small Business Server Windows Firewall -enforced yes - link enabled > yes-gpo status Enabled > > anyone have an idea what im doing wrong? I have had to created local user > accounts on the old computer to get my employees working again. Please > help! > > thanks, > george h
From: george hardy on 14 Apr 2008 14:32 that was too easy. "Vera Noest [MVP]" <vera.noest(a)remove-this.hem.utfors.se> wrote in message news:Xns9A80CFF3FD880veranoesthemutforsse(a)207.46.248.16... > You have to add the domain accounts of the users to the *local* > built-in Remote Desktop Users group on the Terminal Server itself. > _________________________________________________________ > Vera Noest > MCSE, CCEA, Microsoft MVP - Terminal Server > TS troubleshooting: http://ts.veranoest.net > ___ please respond in newsgroup, NOT by private email ___ > > "george hardy" <nospam(a)nospam.com> wrote on 14 apr 2008 in > microsoft.public.windows.terminal_services: > >> Hello All, >> >> * I have a SBS2003 that is my main machine now (new computer), >> and I am now using it for my Domain Controller (AD). >> * I have another 2003 Server Standard (old computer) that WAS >> the domain controller, but i attached it to the SBS2003 >> Domain--this way I can manage the user accounts in one place, >> instead of creating them on the old and the new computer. >> >> On the older computer (2003Standard) I have my terminal server >> licensing server (unlimited). I was hoping that now that >> computer is hooked up to the SBS2003 domain, that all the users >> would be able to login to the terminal server (the old computer) >> without problem. >> >> It is giving me the message when a user tries to login, they >> get: "To logon to this remote computer, you must have Terminal >> Server User Acces permissions on this computer. By default, >> members of the Remote Desktop Users group have these >> permissions. If you are not a member of the Remote Desktop >> users group or another group that has these permissions, or if >> ...blah blah blah...you must grant them manually" >> >> I have added all the users in my domain to the Remote Desktop >> Users group, and still no luck. >> >> I'm no Group Policy expert by any means, but i even tried >> granting "Allow lon on through Terminal Services" in the section >> 1 - Small Business Server Windows Firewall -enforced yes - link >> enabled yes-gpo status Enabled >> >> anyone have an idea what im doing wrong? I have had to created >> local user accounts on the old computer to get my employees >> working again. Please help! >> >> thanks, >> george h
From: george hardy on 14 Apr 2008 14:36
I get this: The Small Business Server Networking Wizard was not installed. You may not be a member of the local Administrators security group on this computer or your Local Intranet security settings may be set to High. Click Connect to the network now to try again and click Yes when prompted. If the wizard fails to install, contact the person responsible for your network. "Merv Porter [SBS-MVP]" <mwport(a)no_spam_hotmail.com> wrote in message news:es2On3lnIHA.3780(a)TK2MSFTNGP06.phx.gbl... > Did you use ConnectComputer (you should) to join the TS server to the SBS > domain? > > -- > Merv Porter [SBS-MVP] > ============================ > > "george hardy" <nospam(a)nospam.com> wrote in message > news:uPZrAhlnIHA.5160(a)TK2MSFTNGP05.phx.gbl... >> Hello All, >> >> * I have a SBS2003 that is my main machine now (new computer), and I am >> now using it for my Domain Controller (AD). >> * I have another 2003 Server Standard (old computer) that WAS the domain >> controller, but i attached it to the SBS2003 Domain--this way I can >> manage the user accounts in one place, instead of creating them on the >> old and the new computer. >> >> On the older computer (2003Standard) I have my terminal server licensing >> server (unlimited). I was hoping that now that computer is hooked up to >> the SBS2003 domain, that all the users would be able to login to the >> terminal server (the old computer) without problem. >> >> It is giving me the message when a user tries to login, they get: >> "To logon to this remote computer, you must have Terminal Server User >> Acces permissions on this computer. By default, members of the Remote >> Desktop Users group have these permissions. If you are not a member of >> the Remote Desktop users group or another group that has these >> permissions, or if ...blah blah blah...you must grant them manually" >> >> I have added all the users in my domain to the Remote Desktop Users >> group, and still no luck. >> >> I'm no Group Policy expert by any means, but i even tried granting "Allow >> lon on through Terminal Services" in the section >> 1 - Small Business Server Windows Firewall -enforced yes - link enabled >> yes-gpo status Enabled >> >> anyone have an idea what im doing wrong? I have had to created local >> user accounts on the old computer to get my employees working again. >> Please help! >> >> thanks, >> george h > > |