New DHCP server wont activate

Is the service running?  Try re-starting it.
Has the other DHCP server been stopped and are you sure there aren't any other DHCP servers around (favourite for for me was people using a router to increase the lan ports).
Have you got any messages in the event log as well?

Service is running.  and I've re-booted the server.  I originally unauthorized the existing server, but when the new server would authorize I had to re-authorize the original server.
No messages in the log

You have to be a member of the Enterprise Admins group to authorize DHCP- either by logging on with an account that has Ent.  Admins rights, or by using the  'run as' command , then right clicking the DHCP server icon and selecting authorize. Do you have this access? Is this what you did?

If yes, did you then create the scope and activate it? If yes, did this work fine? Also, is the previous DHCP still up and runnig? have you used a different scope? Have you received any errors? As above is the service running and do you have any errors in evnt vwr?

I'm logged in as Administrator.  Yes the scope activated.  Yes the previous DHCP is active but was unauthorized when I tried to set up the new server.  No I didn't use a different scope than the current one on the existing server.  No errors in the log and yes the service is running.

Have you removed DHCP from the new server, or have you left it as is? Do you want the new server to replace DHCP exactly as is on the old server, i.e, same scope settings etc?

If so, try this (bit of an old article but still the same):
http://support.microsoft.com/kb/130642

The priciple is still the same if you are introuducing a new DHCP server, must make sure services and DHCP are stopped on the old. I would suggest removing DHCP from the new and trying again. Setting up your scope and then authorizing.

I willl delete the new server settings.  And yes I want them to be identical to the old.  Your suggestion sounds good.  If I do this during the day when the users are logged in it won't have any effect, correct?  Then if I reboot all workstations after the new DHCP server is working, the workstations should then find the new server, correct?
I just want to make sure I don't need to do a "release" per workstation.  Or should I change the lease duration to am hour?

Correct it shouldn't have any affect if done correctly, but you will have to change the lease duration to an hour so when the clients request a new lease they will request it from the new server.

From experience, it's best to perform such maintenace 'out of hours' - get all user's to shutdown their workstations, delete the settings from your new server, export the database from the old, install DHCP on the new, import the database on the new, stop dhcp settings/ services on the old, and then authorize your new server.

Hope that helps.

OK, I'll work on this tomorrow.  I'll keep you posted.

I followed each step with no problems.  Except the "authorize" option is still not displaying when I choose the actions to perform on the new server.  Where do I go from here?

Has you account got Enterprise Admin rights to the root domain? DHCP admins is not enough.