Location based printing and terminal server

[Guest Jeff]

I have a NLB TS farm that NLB's to 5 TS Enterprise nodes. Our company uses

location based printing which works well but now I have an issue. A printer

at a remote site is installed on my terminal nodes that points via Standard

IP port from my corporate office directly to the printer. Now the remote

site server controls the same printer at the remote site for their local

users. This remote server's instance of the printer has the Location

settings that corresponds to our AD subnets, this allows their local users to

quickly navigate to their location in the AD Search and find the printers at

their local site. Now the problem :(, each node that prints via IP doesn't

retain the location settings since it prints directly to the printers IP

address. Each nodes instance of the printer shows up in the AD search if you

leave the location field blank when you search. This is very confusing for

users since the printers share name shows up 6 times since there are 6

instances of the printer.

 

How can I exclude the terminal nodes instances of the printers from the AD

Search without blocking the entire subnet (since it is required for the local

instance of the printer)? Another cog in the wheel, there are approx 160

printers on each node and i don't really want to open each printers settings

and blank or change the location entry on each node's printer instance.

 

make any sense? I was thinking of changing one nodes printers to use a

blank location or some other value and then printer migrate to each other

node. Will this work? I also don't want to remap each printer to the

\\server\printer and get rid of the IP printing, this will degrade

performance. What to do??

[Guest Jeff]

RE: Location based printing and terminal server

 

I think sometimes posting here makes the mind search avenues not always

thought of. I found an easy answer and I can't believe I didn't think of

it....

 

Don't allow printer shares publich to Active Directory through GPO for the

terminal servers OU. On the printer shares remove the option then

printmigrate to the other nodes. Sorry to waste space here on this question.

 

"Jeff" wrote:

> I have a NLB TS farm that NLB's to 5 TS Enterprise nodes. Our company uses

> location based printing which works well but now I have an issue. A printer

> at a remote site is installed on my terminal nodes that points via Standard

> IP port from my corporate office directly to the printer. Now the remote

> site server controls the same printer at the remote site for their local

> users. This remote server's instance of the printer has the Location

> settings that corresponds to our AD subnets, this allows their local users to

> quickly navigate to their location in the AD Search and find the printers at

> their local site. Now the problem :(, each node that prints via IP doesn't

> retain the location settings since it prints directly to the printers IP

> address. Each nodes instance of the printer shows up in the AD search if you

> leave the location field blank when you search. This is very confusing for

> users since the printers share name shows up 6 times since there are 6

> instances of the printer.

>

> How can I exclude the terminal nodes instances of the printers from the AD

> Search without blocking the entire subnet (since it is required for the local

> instance of the printer)? Another cog in the wheel, there are approx 160

> printers on each node and i don't really want to open each printers settings

> and blank or change the location entry on each node's printer instance.

>

> make any sense? I was thinking of changing one nodes printers to use a

> blank location or some other value and then printer migrate to each other

> node. Will this work? I also don't want to remap each printer to the

> \\server\printer and get rid of the IP printing, this will degrade

> performance. What to do??