Adding 2nd win2k3 Domain Controller for Print Server Backup

[Jay Bollyn]

I have 16 printers installed on DC1, shared, using IP. 20 winXP clients.

I would like my 2nd domain controller (DC2) to be a print server, so if I take DC1 out of service for a couple hours, DC2 will handle printing, transparent to the users.

Do I need to install all my printers on DC2? All the clients would have two logical printers in their printer folder, pointing to the same port (same physical printer).

When I take DC1 out of service, the default printer in the users printer folder will not be available. I would like the print job to automatically (transparent to the user) use the other logical printer, which is hosted by DC2. Is this possible?

Is there a better way to do this?

-- Jay

[Igor Karasik]

The best way is Print Server Clustering.
See
http://www.microsoft.com/windowsserver2003/techinfo/overview/printcluster.mspx
http://www.microsoft.com/technet/prodtechnol/windowsserver2003/library/ServerHelp/6b76f5e2-a9ea-4e5d-81a4-de51ff325021.mspx

But you cannot use print server clustering
on DC.

[Andre Thompson_1]

How long would the DC be down for?
Do you have another server that you can use to substiture for DC1?

[Jay Bollyn]

Andre,

My goal is to have as little unscheduled server down time as possible. Both DC1 and DC2 have the role of DNS server, so if I take DC1 down for an hour or so, the users will not see any DNS interruption.

All my printers are currently installed only on DC1, shared. My original plan was to install all the printers on DC2, shared, and have two logical printers in all the users printer folders, pointing to the same physical printer. The main problem with this arrangement is, if DC1 is down, the user needs to manually select the other printer. I was hoping to find a way for the print job to automatically use the other logical printer (hosted by DC2).

As Igor suggested, Print Server Clustering will do this, but PSC requires win2k3 EE or DCE. I am running Standard Edition.

-- Jay

[Andre Thompson_1]

Hi Jay

Because the users access the printers via the DC1 server and you want to have almost zero downtime then here is my suggesstion:

1. Get a temporary server named TS1, and add it as a member server on the domain. Configure all the printers exactly like you have it on DC1. I assume it is only printing that you are doing with this server (besides it being a DC).

2. Ensure that all FSMO roles, etc are seized by DC2 and that DC1 is backed up.

3. Demote DC1 and ensure all network services are still running - this shoulld have been a disaster recoevery excercise anyway.

Tricky steps:
4. Remove the DC1 server from the domain. (Users at this point will not be able to print). Rename TS1 to DC1 and ensure that it is added to the domain.

At this point your users should be able to print and not know the difference. You can service your server at this time.

5. Similar to step 4 except the other way round: Remove the temporary server from the domain, add back the original DC1 onto the domain. Test to ensure that users are printing.

6. Promote DC1 to a DC once more and seize necessary FSMO roles, etc.

Make sure you test in a test environment first.

Hope this helps.

[Jay Bollyn]

Thanks Andre,

What I am doing is MCSA exam prep. I was wondering if I had missed something, but it appears I have not missed an obvious way to do this on the cheap, and quickly/easily.

-- Jay