TrueTechSolutions

R2 gives you the ability to install printers via group policy. First though, if your DCs are not running R2 you will need to update the schema. On disk 2 of the R2 install navigate to the \cmpnents\r2\adprep folder. Run the forest prep first - adprep /forestprep. If you have only one domain this is all you have to do. If you have more than one doamin, run adprep /domainprep on all domains. Then follow the instructions below:

On Brian Puhl's blog he summarized the importance of each FSMO role and how urgent it is to get the roles online again.

I have posted a clip below...

The original is here.

Microsoft published an excellent article on best practices regarding setting the client DNS settings on various servers. Pay close attention to the settings for the DCPROMO process.

Read it here.

Technically it should work. I have never seen this though. A better way would be to set up AD as a "child" domain to the BIND DNS domain name.
For example if the BIND DNS domain name is corp.com, install the first DC as a new DC in a new Forest. Give the Forest/Domain name something like AD.corp.com. Make AD DNS is authoritative for AD.corp.com (it will be by default), configure AD DNS to forward queries for corp.com to the BIND DNS servers for CORP.com.

Keep in mind it is best practice to seperate your internal domain name (AD) from your external domain name.

I found a way to add bulk A records as well as PTR records. If you use dnscmd and only add A records, PTR records are not created automatically. So here is a way to add them in one fell swoop..... (this is based on someone's original script, but I do not remember who... sorry!)

Here is a handy way to add many A records. This uses dnscmd and a csv file. The first column should have the hostname, the second should have the ip address. Save it as a bat or cmd file.

  FOR delims=","" "tokens="1,2" (serverlist.csv) do dnscmd dnsserver /RecordAdd domain %%a A %%b<>

Here is a nifty little script I cobbled together from various sources. You just need to have excel installed on the computer that is running the script and edit the script with your parameters.

View it.

From Microsoft's site:

_Overview

_{System Requirements}

• _{Supported Operating Systems: Windows Server 2003}

Sophia's first bath at home!!

This CMD line will allow you to shut down a computer/server remotely. THis uses the runas command and can be useful if you delegate the ability to shutdown servers, but don't want the person logging on locally.

C:\>runas /netonly /user:domain\administrator "shutdown /s /m \\computername /t 10"

This script will extract the necessary information out of an Excel spreadsheet and create sites based on that information.

Overview

Here are a few examples using the SetAcl (http://setacl.sourceforge.net/) program to manges share and folder permissions

This is a useful reference for Windows logon types. You will see these referenced in the Security Event Logs.