printing windows 2003 server

Hi ,

i have a windows 2003 server that will not boot.  i have pretty much given up on trying to fix that issue!

i do howerver have access to  a non image based backup which contains all of the files (windows partitiion included)

the main funtion of this machine was to act a s a print server for about 30 printers..

is there any way i can retieve the printer "database" - printer name/drives/share names etc from the backup that i have...?  it would save me a LOT of work!

i know if windows was running i could run the print migration utility to give me what i need but dont how if there is any "magic" file i can recover and move to a newly built server to do the same thing...

Who is Participating?
gerpaqitConnect With a Mentor Author Commented:
i'm afraid i had to rebuild the server and reinstall all of the printers manually... thank you all for your responses.  i ma not sure what the etiquette it regarding the awarding of points in this situation....if any knows please let me know.

thanks again to all for the responses..
Print Migrator 3.1

- Print Migrator provides complete backup, restore and migration operations for
Windows NT-based operating systems from Windows NT 4 to Windows 2003.


More info:

Print Migrator ceates a .CAB file with all of the server's printer drivers & 
port information when you backup the printers.  If you copy this file to the
new 2003 server and run the Print Migration utility again (restoring from the
original .cab file) the same "print server" configuration should result.  
You can manually uninstall any printers that result from the restore process
Michael PfisterCommented:
You would need to restore part of the registry (HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Print) and the files located under C:\WINDOWS\system32\spool
Davis McCarnOwnerCommented:
mpfister is close; but, the correct key is HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print which contains the ports, drivers, and controls of the installed printers.  Since it won't boot, you'll need to inspect ControlSet001, and any other ControlSets after loading the hive.
Once you locate the correct Print keys, export them to a reg file, globally replace ControlSet00x with CurrentControlSet, merge the resulting file, copy the contents of the Windows\System32\Spool folder to the new setup, reboot, and pray a little!
You may need to copy some of the Program Files\HP, Lexmark, yada yada folders,  possibly some additional files in Windows\System32, and may need to remount the old registry to do the same process on HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\SharedDlls to get it fully operational; but, it is doable.
Make sure you name the key you load the hive to something like OLD_SERVER_SYSTEM or you can train wreck everything and, if you get a registry backup beforehand, you can save yourself if you give up:
gerpaqitAuthor Commented:
no other answer
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.