<div>
Thanks for replying.<br />
<br />
I quickly read the article and found some useful stuff. <br />
<br />
I have looked at other articles to see if there is any way of setting the prefered DC in the registry. Does anyone know of a way to do this? <br />
<br />
Thanks
</div>


Thanks for replying.

I quickly read the article and found some useful stuff.

I have looked at other articles to see if there is any way of setting the prefered DC in the registry. Does anyone know of a way to do this?

Thanks

<div>
<div class="content wysiwyg-content">
Hi<br />
<br />
Can anyone see an issue with using setprfdc to set workstations to their local bdc's? There are 5 domains, across numerous sites. All domains have a number of dc's they can connect to, but in the main the dc's that tend to be used for authentication are the PDC's, with a couple of them having between 850 and 1000 netbios connections at any given time. Obviously I want this number reduced and the load spread to the BDC's. <br />
<br />
I was thinking of creating a simple batch file (setprfdc domain_name DC1 DC2 )and putting it in the startup folders of all the clients(around 3500). I realise that even if this was done alot of clients will still connect to the PDC's when logging on, but after the batch file ran would connect to their closest BDC's. Could using setprfdc so widespread cause any issue's? Network overheads etc.<br />
<br />
I realise we probably have a WINS issue, which is also being looked at, but could this be a temporary fix?<br />
<br />
Thanks
</div>
</div>


Hi

Can anyone see an issue with using setprfdc to set workstations to their local bdc's? There are 5 domains, across numerous sites. All domains have a number of dc's they can connect to, but in the main the dc's that tend to be used for authentication are the PDC's, with a couple of them having between 850 and 1000 netbios connections at any given time. Obviously I want this number reduced and the load spread to the BDC's. 

I was thinking of creating a simple batch file (setprfdc domain_name DC1 DC2 )and putting it in the startup folders of all the clients(around 3500). I realise that even if this was done alot of clients will still connect to the PDC's when logging on, but after the batch file ran would connect to their closest BDC's. Could using setprfdc so widespread cause any issue's? Network overheads etc.

I realise we probably have a WINS issue, which is also being looked at, but could this be a temporary fix?

Thanks

Using setprfdc on workstations

Operating systems perform basic tasks, such as recognizing input from the keyboard, sending output to the display screen, keeping track of files and directories on the disk, and controlling peripheral devices such as disk drives and printers. For large systems, the operating system makes sure that different programs and users running at the same time do not interfere with each other. The operating system is also responsible for security, ensuring that unauthorized users do not access the system. Operating systems provide a software platform on top of which other programs, called application programs, can run.