Re: Print Cluster
From: Mike Rosado [MSFT] (mikeros_at_online.microsoft.com)
Date: 03/12/05
- Next message: Uhway: "Re: SQL Server 2 Node cluster"
- Previous message: Patrick: "Re: Print Cluster"
- In reply to: Patrick: "Re: Print Cluster"
- Next in thread: Patrick: "Re: Print Cluster"
- Reply: Patrick: "Re: Print Cluster"
- Messages sorted by: [ date ] [ thread ]
Date: Sat, 12 Mar 2005 07:51:59 -0600
Patrick,
Make sure to have all the prints on the one node everyone can print too, the
use PrintMig tool to create a CAB and restore it to the Virtual Node Name.
Print Migrator 3.1 Windows Print Migrator 3.1 (download location for tool)
Backup, Restore and Migrate printers on Windows-based print servers
http://www.microsoft.com/downloads/details.aspx?FamilyID=9b9f2925-cbc9-44da-b2c9-ffdbc46b0b17&DisplayLang=en
Whitepaper:
http://www.microsoft.com/WindowsServer2003/techinfo/overview/printmigrator3.1.mspx
-- Hope this helps, Mike Rosado Windows 2000 MCSE + MCDBA Microsoft Enterprise Platform Support Windows NT/2000/2003 Cluster Technologies ==================================================== When responding to posts, please "Reply to Group" via your newsreader so that others may learn and benefit from your issue. ==================================================== This posting is provided "AS IS" with no warranties, and confers no rights. <http://www.microsoft.com/info/cpyright.htm> -----Original Message----- "Patrick" <Patrick@discussions.microsoft.com> wrote in message news:54F803AE-AD67-4359-9363-F84981D11F2D@microsoft.com... > yes, > > missing drivers and ports > > so i think that node 2 has all the drivers and ports, but the shared storage > has not?? > > can i just copy the drivers directory from node 2 over the shared storage? > > > > "Mike Rosado [MSFT]" wrote: > > > Patrick, > > > > Any details in the Cluster Log once it's failed over to the node the > > printers are missing? > > > > -- > > Regards, > > Mike Rosado > > Windows 2000 MCSE + MCDBA > > Microsoft Enterprise Platform Support > > Windows NT/2000/2003 Cluster Technologies > > > > ==================================================== > > When responding to posts, please "Reply to Group" via your newsreader so > > that others may learn and benefit from your issue. > > ==================================================== > > > > This posting is provided "AS IS" with no warranties, and confers no rights. > > <http://www.microsoft.com/info/cpyright.htm> > > > > -----Original Message----- > > > > "Patrick" <Patrick@discussions.microsoft.com> wrote in message > > news:9366BD57-B241-4AD1-B147-C8CB4AB8C8BA@microsoft.com... > > > Mike, thanks for the response, > > > > > > yes we did that, i thought that that was the problem, the log size is now > > > 8192, big enough, but the same problem > > > > > > BR > > > > > > "Mike Rosado [MSFT]" wrote: > > > > > > > Hi Patrick, > > > > > > > > Have you tried bumping up the Quorum Log Size? I know it's Windows > > Server > > > > 2003 and you're already at 4096KB, but just for the heck of it move > > > > everything to the node that all the printers show correctly and increase > > the > > > > Quorum Log Size to 16384KB and test failover. > > > > > > > > 257897 MSCS Printer Shares May Not Come Online If Quorum Log Is Too > > Small > > > > http://support.microsoft.com/?id=257897 > > > > > > > > -- > > > > Hope this helps, > > > > Mike Rosado > > > > Windows 2000 MCSE + MCDBA > > > > Microsoft Enterprise Platform Support > > > > Windows NT/2000/2003 Cluster Technologies > > > > > > > > ==================================================== > > > > When responding to posts, please "Reply to Group" via your newsreader so > > > > that others may learn and benefit from your issue. > > > > ==================================================== > > > > > > > > This posting is provided "AS IS" with no warranties, and confers no > > rights. > > > > <http://www.microsoft.com/info/cpyright.htm> > > > > > > > > -----Original Message----- > > > > > > > > "Patrick" <Patrick@discussions.microsoft.com> wrote in message > > > > news:107ECC53-0F47-413D-9067-7909662EE3CF@microsoft.com... > > > > > We have the following problem on a W2003 print cluster with 300 > > printers. > > > > > First cluster was working fine, also failover, no problem. We had to > > > > > reinstall node 1. Now when we do a failover 70 printers are missing. > > If we > > > > > failback to node 2, all the printers are ther > > > > > > > > > > There is one strange thing....The driver directory on node 2 is 220 > > Mb. On > > > > > the shared storage and on node 1 it is 170 Mb. > > > > > > > > > > In an article I read that you may not copy the local driver dirctory > > over > > > > th > > > > > shared storage directory, > > > > > > > > > > anybody an idea????? > > > > > > > > > > > > > > > > > >
- Next message: Uhway: "Re: SQL Server 2 Node cluster"
- Previous message: Patrick: "Re: Print Cluster"
- In reply to: Patrick: "Re: Print Cluster"
- Next in thread: Patrick: "Re: Print Cluster"
- Reply: Patrick: "Re: Print Cluster"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
Loading