1st:A:
Quote:
First. We've already got a "Primary Domain Controller" but, if we were to change this new server to a "Secondary Domain Controller" would tha be neccessary? Or should we add this server to it's own domain?
No major reason to. Give us some more information about your network if you want my opinion on it. Secondary Domain Controllers can confuse when replication occurs. But major reason for a Secondary Domain Controller is if its running in another site. Ie PDC in New York, BDC in London. But that comes into Active Directory Domains and Trusts
1st:B:
Quote:
In addition to that, we wanted to take the "L: Drive" off of our new server and share it- Which would be the most simple way to do that? So everyone has access, we are trying to avoid "recreating" numerous amounts for people to login, basically just want them to log onto windows and a "Batch-DOS Prompt" loads giving them the drive. We won't have to authiniticate the drive.
Either setup a home drive .... Active Directory Users and Computers .... Home Path: \\Server\LDriverShare\ OR \\Server\LDriveShare\%username%
OR
Net Use Script: Type all your net commands here .... net use z: \\Server\LDriveShare /user:username password. Then to execute on clients machine:
1) On your PDC server, explore c:\winnt\system32\repl\export\scripts
2) Place your batch file there ie: my.bat
3) From the menu on the PDC select programs|administrative tools| manager for domains| to open the client list.
4) Select the desired users profile and click the <Profile> button.
5) Under the Logon Script Name type in My.bat
6) Wait for replication if you have multiple servers.
7) Test.
2nd:A:
Quote:
Second. Now that the server has switched over all of our "Savin Laser Scanners" won't refresh correctly. If the server is shut down the Savin's have to be as well, so that the list will populate on them again. Not sure why it is forcing us to do that, it's supposed to have an automated refresh. That's why were guessing it started with the "Server" because it happened when we changed Operating Systems.
NFI mate, try google for other users problems.
2nd:B:
Quote:
Also, I do know that "Windows 2000 Server" gives you the option of using a "Wizard" which will actually setup as a "Secondary Domain Controller". Another question, what exactly does the operation of the "Secondary Domain Controller" entail?
Are you talking about 'dcpromo' ? Migrating a Member Server into a Secondary Domain Controller is a point of usefulness. Unless the PDC is running a thousand Services and clients keep timing out, then load share it with a Secondary Domain Controller. Many other uses, mainly as a backup, but you already should have a backup solution running.
Also, can anyone clarify for me if there is a difference between a Secondary Domain Controller and a Backup Domain Controller. I know what a member server is, and by definition BDC and SDC are the same thing, even if the BDC isnt EXACTLY doing any backups ???
