Server as BDC for Shutdown

If the BDC is the only one located in the situation, users will be authenticated be either the PDC or one of the other BDC's depending on how your WAN is established. If there is another BDC then the users would continue to be authenticated by the local BDC. All of this could result in unacceptable delays in logging on for the users and is probably going to load your WAN in excess of what it should be. As for shutting down the server, providing nothing is stored locally, there is no issue. Turnit off, delete it from server manager and it is done. Just remember the role of the server in authenticating users (and any other functions it may perform) BEFORE shutting it down permanently.

Completely. Well, except for a small green globule left on the seat, perhaps.

Ok... really... if you are going to shut down a BDC locally it would be a good idea to ask this question of whoever is responsible for your network worldwide. I wouldfind that person and ask them. I would be pretty upset if someone in one of our remote offices shut down a server because they read that it was ok at TR. I would expect them to ask the person in charge (Which would be me in our case). If it made sense I would agree, but I would want to be a part of this process.

In fact though, turn it off for a while and see... I mean its a BDC, right? At least until the PDC goes down and your users may find they can't work anymore.......

Just as others have said you will not see (or should not see, if all is built and connected ok) any real adverse affects until the PDC goes down (and yes at some point the PDC will go down -- law of IT). It may take users in some areas near the downed BDC may see slowness in logging on if your BDC is assisting with netlogon, but other than that the network should function alright until the PDC goes down.