I had a server fail and needed to get the various file shares (department and home directories) as well as numerous printers back on line as soon as possible.
For the printers I had previously used Printer Migration Utility to capture all the printer settings so I ran a print migration import on the new server. This created all the printers and associated info, i.e. ports, shares, etc.
I reloaded all the share data and set all the appropriate permissions and for the shares mappings that are handled by the logon script, they changed appropriately. .
The one trick I tried was to make a DNS alias for the failed server to the new server. The theory being, if any of the users had any hard mappings to server1, the alias would send them to server2. If I ping the old server by name, the new server responds. The ip address is not the same however as the old address. All the printer share names, file shares etc were identical between the old server and new server. Theory and reality however did not match. If the new server printers and shares are accessed directly, they work with no problem, but trying to redirect any hard mappings using a dns alias was a no go. I am wondering why this theory will not work or if there is some step that I missed that would make it work.
Jim
Elegant solutions are nice, but right now I'll settle for whatever works.
For the printers I had previously used Printer Migration Utility to capture all the printer settings so I ran a print migration import on the new server. This created all the printers and associated info, i.e. ports, shares, etc.
I reloaded all the share data and set all the appropriate permissions and for the shares mappings that are handled by the logon script, they changed appropriately. .
The one trick I tried was to make a DNS alias for the failed server to the new server. The theory being, if any of the users had any hard mappings to server1, the alias would send them to server2. If I ping the old server by name, the new server responds. The ip address is not the same however as the old address. All the printer share names, file shares etc were identical between the old server and new server. Theory and reality however did not match. If the new server printers and shares are accessed directly, they work with no problem, but trying to redirect any hard mappings using a dns alias was a no go. I am wondering why this theory will not work or if there is some step that I missed that would make it work.
Jim
Elegant solutions are nice, but right now I'll settle for whatever works.
