Quick question ....
Quick question ....
(OP)
.. would it work if you installed SMS 2.0 on a pdc or a bdc? Never mind about the load on the DC etc etc, but would it be able to contact itself, as a logon point, to pick up logons as they get authentication from the DC. I'm thinking its impossible, am i right?
RE: Quick question ....
RE: Quick question ....
If you are thinking about automated client discovery and the SMS server discovering clients as they log on, you might see some increase in performance if the BDC/PDC is the only DHCP server (Using the DHCP discovery method in Network discovery),however; as it is unlikely you have only one DHCP server, you most likely wouldn't notice an improvement here either.
The other issue that comes to mind is the SQL database. Although you can run SQL on a different box (v7.0) than the SMS server, any performance increase you might have received from the DC you would most likely lose as the SMS server has to communicate with the SQL box across the network. You could choose to run SQL on the DC, but then you will have major performance issues relating to the SQL server.
RE: Quick question ....
I guess the problems i had stemmed from the fact Windows Network logon discovery and installation were my discovery and installation methods. And with that, all the DCs are made site systems (logon points)
Once they are site systems, you can no longer use them as a secondary site server (as they are site systems in the primary site)
Well the good thing is, the server crashed and i lost everything .. had to restart .. this time, didnt use Windows Networking Logon Discovery or installation .. and im happy to say .. all my other DCs are left alone. They are not made site systems and i can now use them as secondary site servers!
Thanks guys!
RE: Quick question ....
One other thought; if you have multiple domains you could configure SMS for only one of them. Then SMS would only configure that domain, leaving the others alone.
What problems were you having and what are you trying to do?
RE: Quick question ....
Well i had great difficulty turning a logon point into a secondary server, and i concluded its an impossible task. As soon i insert the installation CD, it says the server is a site system of another SMS site and hence, all it enables me to install is the admin console, everything else is grayed out.
As for disabling Win Network Logon Discovery and not being able to install clients via logon script - well that's fine. My new install has both those disabled and the clients are installed via Win NT Remote Client Installation.
I would like to hear from anyone who had Network Logon Discovery enabled, had all the DCs turned into site systems and was able to turn one of the DCs into a secondary site server - just so i can confirm that it is possible, if it is.
In anycase .. my new SMS installation is behaving well and doing everything the way i want it to. <fingers crossed> :)
RE: Quick question ....
It is possible to install Secondary Site server on a site system. I did it in the lab but not in the way you tried. I posted test results to your other post. Basically the only difference is that I initiated the Secondary Site install from the Primary Site server, over the wire install. You say that you tried to install Secondary from cd-rom mounted locally. I did not do this. If you are concerned with bandwidth, you can initiate the install from the Primary and use the local media as source.
Donah, you are close again. You can use an install script to install clients with only the "Windows Network Logon Installation" method enabled. This creates the necessary smslogon points that are required for this install method. This method is also highlighted in Lola's other thread.