RDS Printing Issues (Looking for a solution that works)

-

can please before lose mind on this.

we have 5 server rds farm approx 400 users , major headaches printing.

we have tried easy print driver start useless lot of our users access farm via wan links destroyed 80mb print jobs caused driver. therefore have set gpo settings not use easy print driver first , rely on native printer drivers.

we installed numerous printer drivers servers , created registry entries for a printermappinginfname file copied of ts servers. not work. if there not native matching driver client on server, go straight easy print driver without seemingly looking @ custom mapping file. (nothing in event log either)

does know order 2008 r2 driver/printer mapping or how force read custom mapping file?

we keen use mapping file manually updating , trying match client server drivers 400 clients going take lot of work , doubt smooth ride of interaction services messages pop without explanation.

or better still has implemented full working rds solution works , can offer insight on how printers approached.

many thanks

hi,

 

thank posting.

 

by default, easy print enable on windows 2008 r2. , order looking printer driver on windows 2008 r2 : built-in printer driver -> custom printer mapping file -> easy print .

  

for more information:

printer redirection

http://technet.microsoft.com/en-us/library/ee791784(ws.10).aspx

 

 

personally, think may make wrong in inf file, so let’s divide procedures 2 parts create or modify .inf file & configure registry.

 

the following microsoft technet article creating custom printer mapping file.

 

http://technet.microsoft.com/en-us/library/ff519149(ws.10).aspx

 

 

hope helps.

 



Windows Server  >  Remote Desktop Services (Terminal Services)



Comments

Post a Comment

Popular posts from this blog

DCOM received error "2147746132" from...

-
hi everybody, i have dc (my windows essentials 2012 server) , windows 2012 server in network.  the windows server 2012 inside domain. on server, got "non stopping" error says in event logs : ===> dcom received error "2147746132" fromd computer xxxx(my dc computer) while server trying activation : {6df8cb71-153b-4c66-8fc4-e59301b8011b} it never stops, got 11000+ new events :s i found : http://support.microsoft.com/kb/971153/fr i'm not sure should ? does got idea ? matthieu. hi, please try solution mentioned in below link: http://www.eventid.net/display-eventid-10006-source-dcom-eventno-272-phase-1.htm regards, cicely Windows Server  >  Windows Server 2012 General ...
Read more

DFSR RPC replication errors 5014 1726 with large files over VPN

-
i have similar issue ryan in reply http://social.technet.microsoft.com/forums/en-gb/winserverfiles/thread/6d49fd71-2236-4fcb-9763-bf1c03459ee8 cited below. start additional thread here because other 1 related windows server 2003 (r2) , i'm (as ryan) on windows 2008 r2 x64. here first of post ryan: i've got same problem on 2008 r2 dfsr server.  the spoke server has 2x intel 1 gigb on-board nics in active/standby teamed configuration. the hub server (running on vmware using 10gbit vmnet3 nic driver) logs dfsr event 5014 every 2-15mins (usually around 5mins). the spoke server not log event. replication running slowly. initial sync/replication. had re-configure replication folder because of lost dfsr database on spoke server.  could teamed nic on spoke causing error on host? a note: last time did initial sync on folder processed @ 30k files , hour. time it's doing few hundred and hour. another note: hub server has several replication groups , conne...
Read more

ADFS 3.0 Event ID 4625 | An Error occurred During Logon | Status: 0xC000035B

-
we're getting these random errors on our adfs security logs, how can track down generating them? an account failed log on. subject: security id: null sid account name: - account domain: - logon id: 0x0 logon type: 3 account logon failed: security id: null sid account name: account domain: failure information: failure reason: an error occured during logon. status: 0xc000035b sub status: 0x0 process information: caller process id: 0x0 caller process name: - network information: workstation name: - source network address: - source port: - detailed authentication information: logon process: kerberos authentication package: kerberos transited services: - package name (ntlm only): - key length: 0 event generated when logon request fails. generated on computer access attempted. subject fields indicate account on local system requested logon. commonly service such server service, or local process such ...
Read more