Hello again,
Okay, got it going now. I reinstalled the client on one of the dc's and it picked up the other site's info correctly (as I had enabled this domain in the site's logon discovery/install setups). I wonder if this would have eventually happened on its own if I'd waited longer...
But how can I make it so I can add clients to the secondary site? Both sites are served by the same domain controllers, which are only members of the primary site. Can I add the DCs to the secondary site as well? How do I do that?
Right now, if I look in the smslogon share on the DCs...
Hello,
I have a single domain environment with a remote site that I'd like to set up a secondary site server for (without making it a DC). The clients at the remote site use the primary site's domain controllers. How can I have these logon points service both sites?
Greg
I am a monkey, I just needed to wait longer. I set up discovery to find dc's and remote install to push to them, and the windows logon discovery method for the domain. After an hour they hadn't picked up, so I went to lunch confused. They just picked up as logon points for me. Don't know why...
Hello,
My apologies if this is a horrifically stupid question, but I'm installing a new SMS 2.0 environment for testing and I have the following problem:
I built the primary site server on a member server (not a dc) in an NT 4.0 domain (I've always done it on a dc in the past). Now...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.