[THIN] Re: Printer Driver replication Queue
- From: "Ron Oglesby" <roglesby@xxxxxxxxxxxx>
- To: <thin@xxxxxxxxxxxxx>
- Date: Tue, 29 Apr 2003 09:37:43 -0500
I have that with MF, Exploding server and one broken farm!
Ron Oglesby
Senior Technical Architect
=20
RapidApp
Office 312.372.7188
Mobile 815.325.7618
email roglesby@xxxxxxxxxxxx
=20
-----Original Message-----
From: Davey [mailto:DB1001@xxxxxxxxxxxxxxx]=20
Sent: Tuesday, April 29, 2003 8:38 AM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: Printer Driver replication Queue
Thanks for the explanation Ron. I just wish that the people who write
admin guides would explain the likely affect of going against their
advise. In the late 70's as a youngster we got our first microwave - it
said Don't put whole eggs in it.. but never gave a reason..so I just had
to try it - result ? - exploding egg and one broken microwave.
On Tue, 2003-04-29 at 15:13, Ron Oglesby wrote:
>=20
> The limit is 1500 (or so I have been told by Citrix Test Engineering.
> After that your entries will most likely not get placed in the queue.
> With that said we need to look at what this queue really is (for those
> that don't know, since this really is infrequently discussed topic)...
>=20
> This queue is the number of print drivers awaiting replication RIGHT
> NOW. That doesn't mean the auto replication list.
>=20
> Example. You have 15 new servers coming online at once. And 100
drivers
> in the auto replication list, that's 15x100 =3D3D 1500 you just hit =
the
> driver limit. At this point the drivers will not replicate and if you
> try to replicate them you will get errors in the queue. (or hung
drivers
> in the queue that will not be flushed for 24 hours)
>=20
> If you deal in a small environment this is probably not a big deal as
> most of the time you will only bring on 1 or 2 servers at a time. But
in
> an enterprise farm that may have 600-700 drivers per server and it is
> easy to bring up 5-10 servers at a time you could be in trouble.=3D20
>=20
> For this type of env I would recommend either building the drivers
into
> the image (if you image) or scripting them to install AFTER MF is
> installed...
>=20
> WHY after MF? Easy just for kicks build a MF server, after the OS is
on
> put about 600-800 drivers on it, then install MF into a Farm (along
with
> having a BIG mapping file in the CMC) when the IMA serv starts the
first
> time it will sit at starting the service hung on the MFPRINTSS.DLL for
> like 20 or 30 minutes..... Fun huh...
>=20
> Ok I rambled on. Enjoy.
>=20
> Ron Oglesby
> Senior Technical Architect
> =3D20
> RapidApp
> Office 312.372.7188
> Mobile 815.325.7618
> email roglesby@xxxxxxxxxxxx
> =3D20
>=20
********************************************************
This Week's Sponsor - Emergent Online
EOL's Universal Printer new Features include:
Network Printing, Pagestreaming, 2400 DPI.
No Client Software Required!
http://www.go-eol.com/
**********************************************************
For Archives, to Unsubscribe, Subscribe or=20
set Digest or Vacation mode use the below link:
http://thethin.net/citrixlist.cfm
********************************************************
This Week's Sponsor - Emergent Online
EOL's Universal Printer new Features include:
Network Printing, Pagestreaming, 2400 DPI.
No Client Software Required!
http://www.go-eol.com/
**********************************************************
For Archives, to Unsubscribe, Subscribe or
set Digest or Vacation mode use the below link:
http://thethin.net/citrixlist.cfm
Other related posts: