Re-Staging current print server

C

calvinj

[H]ard|Gawd
Joined
Mar 2, 2009
Messages
1,738
Hey Guys, Never thought I've had to see the day, but our print server is acting up, running out of disk space (the previous guy made a raid 1 and then let 2003 split it in to 2 small drives) and just over all a pain in my hind. We are going to wipe it clean and do a fresh install of server 2003 std sp2. This server is currently our print server. If I backup all of the printers with print mig, redo the machine and then restore all of the printers I should be fine correct? Will it restore all of the shares again for me as well? Any help would be appreciated.


Thanks
 
Last time I used it I believe there is an option to back up the shares as well. Just remember to name your server the same and IP the same lol.

You may also need to enable kernel mode driver installs.
 
Easius said:
Last time I used it I believe there is an option to back up the shares as well. Just remember to name your server the same and IP the same lol.

You may also need to enable kernel mode driver installs.
Click to expand...



LOL That's a given. I just don't want to have to run around to 180+ machines to redo all ofthe printers.. I know I could script it too, but the easier the better at this point!
 
Print migrator backups up shares drivers and everything.

Backup the printers. Rebuild the server (Keep the same PC name) and restore the printers. All should be fine.

Note: take a backup of the current machine incase the build fails
 
Or just clean up what's on the D drive, empty it....and use a partition resizing software like Paragon Disk Director to stretch C to use up what got freed up.
 
YeOldeStonecat said:
Or just clean up what's on the D drive, empty it....and use a partition resizing software like Paragon Disk Director to stretch C to use up what got freed up.
Click to expand...

I like the idea, but it's been acting funny for way to long. unexplained network issues and other random things.

This box also use to be a dc, backup exec server, dns/wins, and still is currently the symantec corp av server. When it's restored it will be just the print server and symantec end point server..
 
k1pp3r said:
Print migrator backups up shares drivers and everything.

Backup the printers. Rebuild the server (Keep the same PC name) and restore the printers. All should be fine.

Note: take a backup of the current machine incase the build fails
Click to expand...

duely noted.
 
calvinj said:
I like the idea, but it's been acting funny for way to long. unexplained network issues and other random things..
Click to expand...


Ahh OK... makes sense if you think it's acting wonky due to other reasons...and not just the C drive being full..thus swapfile....and spooler...being cramped and puking due to drive space issues. Sometimes only have a hundred megs free on a server can cause lotsa wonky things, and freeing at least a 1/4 of the partition can get her running smoothly again.;)
 
Well lets hope for the best I just broke the raid 1 right now and it's rebuilding :D May the force be with me tonight
 
YeOldeStonecat said:
Crossing me fingers for ya!
Click to expand...



Thanks... Just one note is that IBM Server Guide is my friend. Server 2003 finishing up as we speak and the actual drive is the way that it should have been in the first place.

Now on to sp2, sep 11, printers back in place and updates updates updates
 
Whoever made print mig i would like to thank them for again saving my hind in something like this.
 
WARNING: Printmig is no longer supported as of SP2 for Server 2003. It will not properly backup your printers and drivers is certain configurations. Such as drivers that include cab files. Its not supported on x64.

It has been replaced by PRINTBRM.EXE which requires vista or Server 2008.
 
You must log in or register to reply here.
Back
Top