Prev: session printers
Next: Profile Issues
From: george hardy on 14 Apr 2008 14:38 i just went into the dcpromo utility, demoted it to a non-active directory computer, and joined it the old fashion way. connectcomputer isn't working per the previous post. george "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 > >
From: Merv Porter [SBS-MVP] on 14 Apr 2008 14:47 Any help here? (The goal would be to have the TS show on the RWW application server page for easy access to the TS). Member server cannot join domain with connectcomputer http://groups.google.com/group/microsoft.public.windows.server.sbs/browse_thread/thread/cc5484653548741/0f879d7a8e899a58?hl=en&lnk=st&q=join+server+The+Small+Business+Server+Networking+Wizard+was+not+installed#0f879d7a8e899a58 -- Merv Porter [SBS-MVP] ============================ "george hardy" <nospam(a)nospam.com> wrote in message news:%23NL0j6lnIHA.4372(a)TK2MSFTNGP05.phx.gbl... >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 >> >> >
From: Larry Struckmeyer on 14 Apr 2008 17:07 I don't see from anything you have said that indicates the second server (old DC) is in the same domain as the SBS. How did you add the SBS? Created a new domain or with one of the "install SBS into an existing AD domain" techniques. If you created a new domain, even with the same name as the SBS, the old server will have to be brought into the same domain. The only way I know to do this to a server is to flatten and reinstall the OS adding it to the domain during the install after the server has been created with the add a server wiz in server management on the SBS. -- Larry Please post the resolution to your issue so that others may benefit. "george hardy" <nospam(a)nospam.com> wrote in message news:%23G4XB8lnIHA.4292(a)TK2MSFTNGP04.phx.gbl... >i just went into the dcpromo utility, demoted it to a non-active directory >computer, and joined it the old fashion way. > > connectcomputer isn't working per the previous post. > > george > > > "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 >> >> >
From: george hardy on 14 Apr 2008 18:14 no, i made a the sbs domain as ACME, and the old domain was ACMECO...I just demoted the ACMECO from a domain controller and attached it to ACME. now, to figure out the intracacies of group policies and connecting the server with ConnectComputer. :) thanks for the help everyone! "Larry Struckmeyer" <lstruckmeyer(no spam)@mis-wizards-dot-com> wrote in message news:DB1ADABD-7844-4055-8005-A10527FD574B(a)microsoft.com... >I don't see from anything you have said that indicates the second server >(old DC) is in the same domain as the SBS. How did you add the SBS? >Created a new domain or with one of the "install SBS into an existing AD >domain" techniques. > > If you created a new domain, even with the same name as the SBS, the old > server will have to be brought into the same domain. The only way I know > to do this to a server is to flatten and reinstall the OS adding it to the > domain during the install after the server has been created with the add a > server wiz in server management on the SBS. > > -- > Larry > Please post the resolution to your > issue so that others may benefit. > > > "george hardy" <nospam(a)nospam.com> wrote in message > news:%23G4XB8lnIHA.4292(a)TK2MSFTNGP04.phx.gbl... >>i just went into the dcpromo utility, demoted it to a non-active directory >>computer, and joined it the old fashion way. >> >> connectcomputer isn't working per the previous post. >> >> george >> >> >> "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 >>> >>> >> >
From: Merv Porter [SBS-MVP] on 14 Apr 2008 18:34
Maybe some references George... Add and Manage Additional Servers in a Windows Small Business Server Domain http://thesource.ofallevil.com/downloads/details.aspx?FamilyID=6f4015f2-7606-4eaa-828a-00b8df6bd999&displaylang=en How to configure licensing on an additional Windows server in an SBS network http://support.microsoft.com/kb/327644 Deploying Windows Server 2003 Terminal Server to Host User Desktops in a Windows Small Business Server 2003 Environment http://thesource.ofallevil.com/downloads/details.aspx?FamilyID=0a06e845-57ef-43eb-802f-f274fd937400&DisplayLang=en Deploying Windows Server 2003 Terminal Server to Host User Desktops http://www.microsoft.com/technet/prodtechnol/sbs/2003/deploy/adstrmsr.mspx -- Merv Porter [SBS-MVP] ============================ "george hardy" <nospam(a)nospam.com> wrote in message news:uy2zf0nnIHA.484(a)TK2MSFTNGP06.phx.gbl... > no, i made a the sbs domain as ACME, and the old domain was ACMECO...I > just demoted the ACMECO from a domain controller and attached it to ACME. > now, to figure out the intracacies of group policies and connecting the > server with ConnectComputer. > > :) > > thanks for the help everyone! > > > "Larry Struckmeyer" <lstruckmeyer(no spam)@mis-wizards-dot-com> wrote in > message news:DB1ADABD-7844-4055-8005-A10527FD574B(a)microsoft.com... >>I don't see from anything you have said that indicates the second server >>(old DC) is in the same domain as the SBS. How did you add the SBS? >>Created a new domain or with one of the "install SBS into an existing AD >>domain" techniques. >> >> If you created a new domain, even with the same name as the SBS, the old >> server will have to be brought into the same domain. The only way I know >> to do this to a server is to flatten and reinstall the OS adding it to >> the domain during the install after the server has been created with the >> add a server wiz in server management on the SBS. >> >> -- >> Larry >> Please post the resolution to your >> issue so that others may benefit. >> >> >> "george hardy" <nospam(a)nospam.com> wrote in message >> news:%23G4XB8lnIHA.4292(a)TK2MSFTNGP04.phx.gbl... >>>i just went into the dcpromo utility, demoted it to a non-active >>>directory computer, and joined it the old fashion way. >>> >>> connectcomputer isn't working per the previous post. >>> >>> george >>> >>> >>> "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 >>>> >>>> >>> >> > |