Re: Not all printers are showing up using RemoteAPP
I tried a couple. I tried PDFcreator(free) and Adobe Acrobat PDF installed
on the client. They both produce the known issue. I tried PDFcreator and
CutePDF on the server. PDFcreator doesn't work on TS. CutePDF does but I
am getting folder locations on the server in my Save dialog.
"Jeff Pitsch" <jeff@jeffpitschconsulting.com> wrote in message
news:u%23ZHSPu$IHA.6132@TK2MSFTNGP04.phx.gbl...
> That may be the pdf software you've chosen doesn't follow "best practices"
> when it was designed. There are a bunch of free pdf writers. It's just a
> matter of finding the right one. Which one are you testing by the way?
>
> --
> Jeff Pitsch
> Microsoft MVP - Terminal Services
>
> "Saucer Man" <saucerman@nospam.com> wrote in message
> news:48a58830$0$24590$cc2e38e6@news.uslec.net...
>> Ok, I tried hiding the drives with GP but the SAVE dialog still shows
>> locations on the Terminal Server such as the user profile name, desktop,
>> public, etc. Is there a way to only show the local environment?
>>
>>
>> "Jeff Pitsch" <jeff@jeffpitschconsulting.com> wrote in message
>> news:eDFDvFt$IHA.4760@TK2MSFTNGP03.phx.gbl...
>>> Hav eyou hidden the drives through Group Policy?
>>>
>>> --
>>> Jeff Pitsch
>>> Microsoft MVP - Terminal Services
>>>
>>> "Saucer Man" <saucerman@nospam.com> wrote in message
>>> news:48a56bd1$0$24544$cc2e38e6@news.uslec.net...
>>>> Thanks a lot for all your help. Is there a way I can prevent any of
>>>> the TS drives from showing up when someone opens up a Save dialog box
>>>> through RemoteAPP? If so, I will install the PDF software on the TS
>>>> instead of the client PC.
>>>>
>>>>
>>>> "Jeff Pitsch" <jeff@jeffpitschconsulting.com> wrote in message
>>>> news:OdEcLgk$IHA.3396@TK2MSFTNGP03.phx.gbl...
>>>>> Bad news Saucer.
>>>>>
>>>>> This is a known issue with Easy Print. There are no plans on fixing
>>>>> it until the next Windows release. if you want, you can log a call on
>>>>> the issue and give a deeper explanation of what problems this is
>>>>> causing and the business justification for fixing it. That's the best
>>>>> I can tell you. sorry
>>>>>
>>>>> --
>>>>> Jeff Pitsch
>>>>> Microsoft MVP - Terminal Services
>>>>>
>>>>> "Saucer Man" <saucerman@nospam.com> wrote in message
>>>>> news:48a41d8a$0$24585$cc2e38e6@news.uslec.net...
>>>>>> This is the first time we implemeting TS. The user is testing it
>>>>>> before we go into production. The application creates a document
>>>>>> with a very unique name that the users will not be able to guess.
>>>>>> Having the document named System.Windows.Documents.pdf every time
>>>>>> will mean I will need to find another solution before we go into
>>>>>> production. I tried installing a PDF writer on the TS itself. That
>>>>>> names the document correctly BUT it shows all the drives on the TS in
>>>>>> the Save Dialog Box. That will confuse the user also and they will
>>>>>> end up losing documents by not saving them in their own local drive.
>>>>>> The EasyPrint would be the best if it didn't rename the documents.
>>>>>> Thanks.
>>>>>>
>>>>>> "Jeff Pitsch" <jeff@jeffpitschconsulting.com> wrote in message
>>>>>> news:OP2Vy4Z$IHA.3392@TK2MSFTNGP03.phx.gbl...
>>>>>>> Saucer, is this actually breaking something in the environment or is
>>>>>>> it just an annoyance?
>>>>>>>
>>>>>>> --
>>>>>>> Jeff Pitsch
>>>>>>> Microsoft MVP - Terminal Services
>>>>>>>
>>>>>>> "Saucer Man" <saucerman@nospam.com> wrote in message
>>>>>>> news:48a036af$0$24535$cc2e38e6@news.uslec.net...
>>>>>>>> OK thanks. I want to hold off a bit before spending the $260 on a
>>>>>>>> Microsoft call.
>>>>>>>>
>>>>>>>> "Jeff Pitsch" <jeff@jeffpitschconsulting.com> wrote in message
>>>>>>>> news:%23bneP06%23IHA.1040@TK2MSFTNGP03.phx.gbl...
>>>>>>>>>I haven't heard anything back yet. still waiting.
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Jeff Pitsch
>>>>>>>>> Microsoft MVP - Terminal Services
>>>>>>>>>
>>>>>>>>> "Saucer Man" <saucerman@nospam.com> wrote in message
>>>>>>>>> news:48a02b13$0$24519$cc2e38e6@news.uslec.net...
>>>>>>>>>> Hi Jeff, did you get any other information on this?
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> "Jeff Pitsch" <jeff@jeffpitschconsulting.com> wrote in message
>>>>>>>>>> news:uPlyT4J%23IHA.5284@TK2MSFTNGP04.phx.gbl...
>>>>>>>>>>> My guess would be it's related to how easy print handles pdf
>>>>>>>>>>> printers. This may require a call into MS to log a bug if it is.
>>>>>>>>>>> I'll try to ping MS on this as well.
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> Jeff Pitsch
>>>>>>>>>>> Microsoft MVP - Terminal Services
>>>>>>>>>>>
>>>>>>>>>>> "Saucer Man" <saucerman@nospam.com> wrote in message
>>>>>>>>>>> news:489b0a59$0$19657$cc2e38e6@news.uslec.net...
>>>>>>>>>>>> OK. I installed the latest .NET framework on the pc and now
>>>>>>>>>>>> all the printers are appearing. However, when the user prints
>>>>>>>>>>>> to the pdfcreator printer, the name of the file is not related
>>>>>>>>>>>> to the print job like it is suppoded to be. Instead, the
>>>>>>>>>>>> filename is system.windowsuments.fix document sequence. It is
>>>>>>>>>>>> supposed to be name based on the job he is printing. Is this a
>>>>>>>>>>>> TS issue orelated to easy print?
>>>>>>>>>>>>
>>>>>>>>>>>> "Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se> wrote
>>>>>>>>>>>> in message
>>>>>>>>>>>> news:Xns9AF3919D9694Fveranoesthemutforsse@207.46.248.16...
>>>>>>>>>>>>> No, that's not how it works. You have to either install the
>>>>>>>>>>>>> drivers
>>>>>>>>>>>>> on the server or -better- enable EasyPrint.
>>>>>>>>>>>>>
>>>>>>>>>>>>> WS2008: Terminal Services Printing
>>>>>>>>>>>>> http://blogs.technet.com/askperf/archive/2008/02/17/ws2008-
>>>>>>>>>>>>> terminal-services-printing.aspx
>>>>>>>>>>>>> _________________________________________________________
>>>>>>>>>>>>> Vera Noest
>>>>>>>>>>>>> MCSE, CCEA, Microsoft MVP - Terminal Server
>>>>>>>>>>>>> TS troubleshooting: http://ts.veranoest.net
>>>>>>>>>>>>> ___ please respond in newsgroup, NOT by private email ___
>>>>>>>>>>>>>
>>>>>>>>>>>>> "Saucer Man" <saucerman@nospam.com> wrote on 07 aug 2008 in
>>>>>>>>>>>>> microsoft.public.windows.terminal_services:
>>>>>>>>>>>>>
>>>>>>>>>>>>>> I haven't installed any printers on the terminal server. I
>>>>>>>>>>>>>> thought RemoteAPP would use the printers and printer software
>>>>>>>>>>>>>> installed on the client it's running on. Is this not the
>>>>>>>>>>>>>> case?
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> "Jeff Pitsch" <jeff@jeffpitschconsulting.com> wrote in
>>>>>>>>>>>>>> message
>>>>>>>>>>>>>> news:eYubbhB%23IHA.4020@TK2MSFTNGP03.phx.gbl...
>>>>>>>>>>>>>>> You can manually setup a pdf printer on the terminal server.
>>>>>>>>>>>>>>> Do you hae the correct print drivers installed to support
>>>>>>>>>>>>>>> his
>>>>>>>>>>>>>>> printers? Or enabled easy print?
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>> Jeff Pitsch
>>>>>>>>>>>>>>> Microsoft MVP - Terminal Services
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> "Saucer Man" <saucerman@nospam.com> wrote in message
>>>>>>>>>>>>>>> news:489a0f74$0$19730$cc2e38e6@news.uslec.net...
>>>>>>>>>>>>>>>> We are using RemoteAPP with Server 2008. At a remote
>>>>>>>>>>>>>>>> location, our user is trying to print from the app but when
>>>>>>>>>>>>>>>> he
>>>>>>>>>>>>>>>> goes to select the printer from the app, only a few of his
>>>>>>>>>>>>>>>> printers are showing up. If he goes to
>>>>>>>>>>>>>>>> START-SETTINGS-PRINTERS, all his printers are there. I
>>>>>>>>>>>>>>>> can't
>>>>>>>>>>>>>>>> find anything in common with the printers that do show up
>>>>>>>>>>>>>>>> in
>>>>>>>>>>>>>>>> the RemoteAPP. One of the printers lives at the office,
>>>>>>>>>>>>>>>> another lives at his remote location, the other are the
>>>>>>>>>>>>>>>> Microsoft Document Writers. He really needs to printer to
>>>>>>>>>>>>>>>> a
>>>>>>>>>>>>>>>> PDFPrinter that is on his laptop. This PDF printer
>>>>>>>>>>>>>>>> converts
>>>>>>>>>>>>>>>> the documents to a PDF File. Anyone know how to correct
>>>>>>>>>>>>>>>> this?
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>> Thanks!
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>>
>>
>>
>
>
Re: Not all printers are showing up using RemoteAPP
I just published Wordpad. The Save dialog box is also showing locations on
the TS such as the Public folder, the user folder, etc.
"Saucer Man" <saucerman@nospam.com> wrote in message
news:48a96345$0$24596$cc2e38e6@news.uslec.net...
>I tried a couple. I tried PDFcreator(free) and Adobe Acrobat PDF installed
>on the client. They both produce the known issue. I tried PDFcreator and
>CutePDF on the server. PDFcreator doesn't work on TS. CutePDF does but I
>am getting folder locations on the server in my Save dialog.
>
>
>
> "Jeff Pitsch" <jeff@jeffpitschconsulting.com> wrote in message
> news:u%23ZHSPu$IHA.6132@TK2MSFTNGP04.phx.gbl...
>> That may be the pdf software you've chosen doesn't follow "best
>> practices" when it was designed. There are a bunch of free pdf writers.
>> It's just a matter of finding the right one. Which one are you testing
>> by the way?
>>
>> --
>> Jeff Pitsch
>> Microsoft MVP - Terminal Services
>>
>> "Saucer Man" <saucerman@nospam.com> wrote in message
>> news:48a58830$0$24590$cc2e38e6@news.uslec.net...
>>> Ok, I tried hiding the drives with GP but the SAVE dialog still shows
>>> locations on the Terminal Server such as the user profile name, desktop,
>>> public, etc. Is there a way to only show the local environment?
>>>
>>>
>>> "Jeff Pitsch" <jeff@jeffpitschconsulting.com> wrote in message
>>> news:eDFDvFt$IHA.4760@TK2MSFTNGP03.phx.gbl...
>>>> Hav eyou hidden the drives through Group Policy?
>>>>
>>>> --
>>>> Jeff Pitsch
>>>> Microsoft MVP - Terminal Services
>>>>
>>>> "Saucer Man" <saucerman@nospam.com> wrote in message
>>>> news:48a56bd1$0$24544$cc2e38e6@news.uslec.net...
>>>>> Thanks a lot for all your help. Is there a way I can prevent any of
>>>>> the TS drives from showing up when someone opens up a Save dialog box
>>>>> through RemoteAPP? If so, I will install the PDF software on the TS
>>>>> instead of the client PC.
>>>>>
>>>>>
>>>>> "Jeff Pitsch" <jeff@jeffpitschconsulting.com> wrote in message
>>>>> news:OdEcLgk$IHA.3396@TK2MSFTNGP03.phx.gbl...
>>>>>> Bad news Saucer.
>>>>>>
>>>>>> This is a known issue with Easy Print. There are no plans on fixing
>>>>>> it until the next Windows release. if you want, you can log a call
>>>>>> on the issue and give a deeper explanation of what problems this is
>>>>>> causing and the business justification for fixing it. That's the
>>>>>> best I can tell you. sorry
>>>>>>
>>>>>> --
>>>>>> Jeff Pitsch
>>>>>> Microsoft MVP - Terminal Services
>>>>>>
>>>>>> "Saucer Man" <saucerman@nospam.com> wrote in message
>>>>>> news:48a41d8a$0$24585$cc2e38e6@news.uslec.net...
>>>>>>> This is the first time we implemeting TS. The user is testing it
>>>>>>> before we go into production. The application creates a document
>>>>>>> with a very unique name that the users will not be able to guess.
>>>>>>> Having the document named System.Windows.Documents.pdf every time
>>>>>>> will mean I will need to find another solution before we go into
>>>>>>> production. I tried installing a PDF writer on the TS itself. That
>>>>>>> names the document correctly BUT it shows all the drives on the TS
>>>>>>> in the Save Dialog Box. That will confuse the user also and they
>>>>>>> will end up losing documents by not saving them in their own local
>>>>>>> drive. The EasyPrint would be the best if it didn't rename the
>>>>>>> documents. Thanks.
>>>>>>>
>>>>>>> "Jeff Pitsch" <jeff@jeffpitschconsulting.com> wrote in message
>>>>>>> news:OP2Vy4Z$IHA.3392@TK2MSFTNGP03.phx.gbl...
>>>>>>>> Saucer, is this actually breaking something in the environment or
>>>>>>>> is it just an annoyance?
>>>>>>>>
>>>>>>>> --
>>>>>>>> Jeff Pitsch
>>>>>>>> Microsoft MVP - Terminal Services
>>>>>>>>
>>>>>>>> "Saucer Man" <saucerman@nospam.com> wrote in message
>>>>>>>> news:48a036af$0$24535$cc2e38e6@news.uslec.net...
>>>>>>>>> OK thanks. I want to hold off a bit before spending the $260 on a
>>>>>>>>> Microsoft call.
>>>>>>>>>
>>>>>>>>> "Jeff Pitsch" <jeff@jeffpitschconsulting.com> wrote in message
>>>>>>>>> news:%23bneP06%23IHA.1040@TK2MSFTNGP03.phx.gbl...
>>>>>>>>>>I haven't heard anything back yet. still waiting.
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> Jeff Pitsch
>>>>>>>>>> Microsoft MVP - Terminal Services
>>>>>>>>>>
>>>>>>>>>> "Saucer Man" <saucerman@nospam.com> wrote in message
>>>>>>>>>> news:48a02b13$0$24519$cc2e38e6@news.uslec.net...
>>>>>>>>>>> Hi Jeff, did you get any other information on this?
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> "Jeff Pitsch" <jeff@jeffpitschconsulting.com> wrote in message
>>>>>>>>>>> news:uPlyT4J%23IHA.5284@TK2MSFTNGP04.phx.gbl...
>>>>>>>>>>>> My guess would be it's related to how easy print handles pdf
>>>>>>>>>>>> printers. This may require a call into MS to log a bug if it
>>>>>>>>>>>> is. I'll try to ping MS on this as well.
>>>>>>>>>>>>
>>>>>>>>>>>> --
>>>>>>>>>>>> Jeff Pitsch
>>>>>>>>>>>> Microsoft MVP - Terminal Services
>>>>>>>>>>>>
>>>>>>>>>>>> "Saucer Man" <saucerman@nospam.com> wrote in message
>>>>>>>>>>>> news:489b0a59$0$19657$cc2e38e6@news.uslec.net...
>>>>>>>>>>>>> OK. I installed the latest .NET framework on the pc and now
>>>>>>>>>>>>> all the printers are appearing. However, when the user prints
>>>>>>>>>>>>> to the pdfcreator printer, the name of the file is not related
>>>>>>>>>>>>> to the print job like it is suppoded to be. Instead, the
>>>>>>>>>>>>> filename is system.windowsuments.fix document sequence. It is
>>>>>>>>>>>>> supposed to be name based on the job he is printing. Is this
>>>>>>>>>>>>> a TS issue orelated to easy print?
>>>>>>>>>>>>>
>>>>>>>>>>>>> "Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se>
>>>>>>>>>>>>> wrote in message
>>>>>>>>>>>>> news:Xns9AF3919D9694Fveranoesthemutforsse@207.46.248.16...
>>>>>>>>>>>>>> No, that's not how it works. You have to either install the
>>>>>>>>>>>>>> drivers
>>>>>>>>>>>>>> on the server or -better- enable EasyPrint.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> WS2008: Terminal Services Printing
>>>>>>>>>>>>>> http://blogs.technet.com/askperf/archive/2008/02/17/ws2008-
>>>>>>>>>>>>>> terminal-services-printing.aspx
>>>>>>>>>>>>>> _________________________________________________________
>>>>>>>>>>>>>> Vera Noest
>>>>>>>>>>>>>> MCSE, CCEA, Microsoft MVP - Terminal Server
>>>>>>>>>>>>>> TS troubleshooting: http://ts.veranoest.net
>>>>>>>>>>>>>> ___ please respond in newsgroup, NOT by private email ___
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> "Saucer Man" <saucerman@nospam.com> wrote on 07 aug 2008 in
>>>>>>>>>>>>>> microsoft.public.windows.terminal_services:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> I haven't installed any printers on the terminal server. I
>>>>>>>>>>>>>>> thought RemoteAPP would use the printers and printer
>>>>>>>>>>>>>>> software
>>>>>>>>>>>>>>> installed on the client it's running on. Is this not the
>>>>>>>>>>>>>>> case?
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> "Jeff Pitsch" <jeff@jeffpitschconsulting.com> wrote in
>>>>>>>>>>>>>>> message
>>>>>>>>>>>>>>> news:eYubbhB%23IHA.4020@TK2MSFTNGP03.phx.gbl...
>>>>>>>>>>>>>>>> You can manually setup a pdf printer on the terminal
>>>>>>>>>>>>>>>> server.
>>>>>>>>>>>>>>>> Do you hae the correct print drivers installed to support
>>>>>>>>>>>>>>>> his
>>>>>>>>>>>>>>>> printers? Or enabled easy print?
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>> Jeff Pitsch
>>>>>>>>>>>>>>>> Microsoft MVP - Terminal Services
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> "Saucer Man" <saucerman@nospam.com> wrote in message
>>>>>>>>>>>>>>>> news:489a0f74$0$19730$cc2e38e6@news.uslec.net...
>>>>>>>>>>>>>>>>> We are using RemoteAPP with Server 2008. At a remote
>>>>>>>>>>>>>>>>> location, our user is trying to print from the app but
>>>>>>>>>>>>>>>>> when he
>>>>>>>>>>>>>>>>> goes to select the printer from the app, only a few of his
>>>>>>>>>>>>>>>>> printers are showing up. If he goes to
>>>>>>>>>>>>>>>>> START-SETTINGS-PRINTERS, all his printers are there. I
>>>>>>>>>>>>>>>>> can't
>>>>>>>>>>>>>>>>> find anything in common with the printers that do show up
>>>>>>>>>>>>>>>>> in
>>>>>>>>>>>>>>>>> the RemoteAPP. One of the printers lives at the office,
>>>>>>>>>>>>>>>>> another lives at his remote location, the other are the
>>>>>>>>>>>>>>>>> Microsoft Document Writers. He really needs to printer to
>>>>>>>>>>>>>>>>> a
>>>>>>>>>>>>>>>>> PDFPrinter that is on his laptop. This PDF printer
>>>>>>>>>>>>>>>>> converts
>>>>>>>>>>>>>>>>> the documents to a PDF File. Anyone know how to correct
>>>>>>>>>>>>>>>>> this?
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>> Thanks!
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>
Re: Not all printers are showing up using RemoteAPP
Ah, save locations vs drives. got it. I misunderstood what you were
saying. Try User config\admin templates\windows components\windows
explorer\common open file dialog and see if that helps.
--
Jeff Pitsch
Microsoft MVP - Terminal Services
"Saucer Man" <saucerman@nospam.com> wrote in message
news:48a9657a$0$24570$cc2e38e6@news.uslec.net...
>I just published Wordpad. The Save dialog box is also showing locations on
>the TS such as the Public folder, the user folder, etc.
>
>
> "Saucer Man" <saucerman@nospam.com> wrote in message
> news:48a96345$0$24596$cc2e38e6@news.uslec.net...
>>I tried a couple. I tried PDFcreator(free) and Adobe Acrobat PDF
>>installed on the client. They both produce the known issue. I tried
>>PDFcreator and CutePDF on the server. PDFcreator doesn't work on TS.
>>CutePDF does but I am getting folder locations on the server in my Save
>>dialog.
>>
>>
>>
>> "Jeff Pitsch" <jeff@jeffpitschconsulting.com> wrote in message
>> news:u%23ZHSPu$IHA.6132@TK2MSFTNGP04.phx.gbl...
>>> That may be the pdf software you've chosen doesn't follow "best
>>> practices" when it was designed. There are a bunch of free pdf writers.
>>> It's just a matter of finding the right one. Which one are you testing
>>> by the way?
>>>
>>> --
>>> Jeff Pitsch
>>> Microsoft MVP - Terminal Services
>>>
>>> "Saucer Man" <saucerman@nospam.com> wrote in message
>>> news:48a58830$0$24590$cc2e38e6@news.uslec.net...
>>>> Ok, I tried hiding the drives with GP but the SAVE dialog still shows
>>>> locations on the Terminal Server such as the user profile name,
>>>> desktop, public, etc. Is there a way to only show the local
>>>> environment?
>>>>
>>>>
>>>> "Jeff Pitsch" <jeff@jeffpitschconsulting.com> wrote in message
>>>> news:eDFDvFt$IHA.4760@TK2MSFTNGP03.phx.gbl...
>>>>> Hav eyou hidden the drives through Group Policy?
>>>>>
>>>>> --
>>>>> Jeff Pitsch
>>>>> Microsoft MVP - Terminal Services
>>>>>
>>>>> "Saucer Man" <saucerman@nospam.com> wrote in message
>>>>> news:48a56bd1$0$24544$cc2e38e6@news.uslec.net...
>>>>>> Thanks a lot for all your help. Is there a way I can prevent any of
>>>>>> the TS drives from showing up when someone opens up a Save dialog box
>>>>>> through RemoteAPP? If so, I will install the PDF software on the TS
>>>>>> instead of the client PC.
>>>>>>
>>>>>>
>>>>>> "Jeff Pitsch" <jeff@jeffpitschconsulting.com> wrote in message
>>>>>> news:OdEcLgk$IHA.3396@TK2MSFTNGP03.phx.gbl...
>>>>>>> Bad news Saucer.
>>>>>>>
>>>>>>> This is a known issue with Easy Print. There are no plans on fixing
>>>>>>> it until the next Windows release. if you want, you can log a call
>>>>>>> on the issue and give a deeper explanation of what problems this is
>>>>>>> causing and the business justification for fixing it. That's the
>>>>>>> best I can tell you. sorry
>>>>>>>
>>>>>>> --
>>>>>>> Jeff Pitsch
>>>>>>> Microsoft MVP - Terminal Services
>>>>>>>
>>>>>>> "Saucer Man" <saucerman@nospam.com> wrote in message
>>>>>>> news:48a41d8a$0$24585$cc2e38e6@news.uslec.net...
>>>>>>>> This is the first time we implemeting TS. The user is testing it
>>>>>>>> before we go into production. The application creates a document
>>>>>>>> with a very unique name that the users will not be able to guess.
>>>>>>>> Having the document named System.Windows.Documents.pdf every time
>>>>>>>> will mean I will need to find another solution before we go into
>>>>>>>> production. I tried installing a PDF writer on the TS itself.
>>>>>>>> That names the document correctly BUT it shows all the drives on
>>>>>>>> the TS in the Save Dialog Box. That will confuse the user also and
>>>>>>>> they will end up losing documents by not saving them in their own
>>>>>>>> local drive. The EasyPrint would be the best if it didn't rename
>>>>>>>> the documents. Thanks.
>>>>>>>>
>>>>>>>> "Jeff Pitsch" <jeff@jeffpitschconsulting.com> wrote in message
>>>>>>>> news:OP2Vy4Z$IHA.3392@TK2MSFTNGP03.phx.gbl...
>>>>>>>>> Saucer, is this actually breaking something in the environment or
>>>>>>>>> is it just an annoyance?
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Jeff Pitsch
>>>>>>>>> Microsoft MVP - Terminal Services
>>>>>>>>>
>>>>>>>>> "Saucer Man" <saucerman@nospam.com> wrote in message
>>>>>>>>> news:48a036af$0$24535$cc2e38e6@news.uslec.net...
>>>>>>>>>> OK thanks. I want to hold off a bit before spending the $260 on
>>>>>>>>>> a Microsoft call.
>>>>>>>>>>
>>>>>>>>>> "Jeff Pitsch" <jeff@jeffpitschconsulting.com> wrote in message
>>>>>>>>>> news:%23bneP06%23IHA.1040@TK2MSFTNGP03.phx.gbl...
>>>>>>>>>>>I haven't heard anything back yet. still waiting.
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> Jeff Pitsch
>>>>>>>>>>> Microsoft MVP - Terminal Services
>>>>>>>>>>>
>>>>>>>>>>> "Saucer Man" <saucerman@nospam.com> wrote in message
>>>>>>>>>>> news:48a02b13$0$24519$cc2e38e6@news.uslec.net...
>>>>>>>>>>>> Hi Jeff, did you get any other information on this?
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> "Jeff Pitsch" <jeff@jeffpitschconsulting.com> wrote in message
>>>>>>>>>>>> news:uPlyT4J%23IHA.5284@TK2MSFTNGP04.phx.gbl...
>>>>>>>>>>>>> My guess would be it's related to how easy print handles pdf
>>>>>>>>>>>>> printers. This may require a call into MS to log a bug if it
>>>>>>>>>>>>> is. I'll try to ping MS on this as well.
>>>>>>>>>>>>>
>>>>>>>>>>>>> --
>>>>>>>>>>>>> Jeff Pitsch
>>>>>>>>>>>>> Microsoft MVP - Terminal Services
>>>>>>>>>>>>>
>>>>>>>>>>>>> "Saucer Man" <saucerman@nospam.com> wrote in message
>>>>>>>>>>>>> news:489b0a59$0$19657$cc2e38e6@news.uslec.net...
>>>>>>>>>>>>>> OK. I installed the latest .NET framework on the pc and now
>>>>>>>>>>>>>> all the printers are appearing. However, when the user
>>>>>>>>>>>>>> prints to the pdfcreator printer, the name of the file is not
>>>>>>>>>>>>>> related to the print job like it is suppoded to be. Instead,
>>>>>>>>>>>>>> the filename is system.windowsuments.fix document sequence.
>>>>>>>>>>>>>> It is supposed to be name based on the job he is printing.
>>>>>>>>>>>>>> Is this a TS issue orelated to easy print?
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> "Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se>
>>>>>>>>>>>>>> wrote in message
>>>>>>>>>>>>>> news:Xns9AF3919D9694Fveranoesthemutforsse@207.46.248.16...
>>>>>>>>>>>>>>> No, that's not how it works. You have to either install the
>>>>>>>>>>>>>>> drivers
>>>>>>>>>>>>>>> on the server or -better- enable EasyPrint.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> WS2008: Terminal Services Printing
>>>>>>>>>>>>>>> http://blogs.technet.com/askperf/archive/2008/02/17/ws2008-
>>>>>>>>>>>>>>> terminal-services-printing.aspx
>>>>>>>>>>>>>>> _________________________________________________________
>>>>>>>>>>>>>>> Vera Noest
>>>>>>>>>>>>>>> MCSE, CCEA, Microsoft MVP - Terminal Server
>>>>>>>>>>>>>>> TS troubleshooting: http://ts.veranoest.net
>>>>>>>>>>>>>>> ___ please respond in newsgroup, NOT by private email ___
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> "Saucer Man" <saucerman@nospam.com> wrote on 07 aug 2008 in
>>>>>>>>>>>>>>> microsoft.public.windows.terminal_services:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> I haven't installed any printers on the terminal server. I
>>>>>>>>>>>>>>>> thought RemoteAPP would use the printers and printer
>>>>>>>>>>>>>>>> software
>>>>>>>>>>>>>>>> installed on the client it's running on. Is this not the
>>>>>>>>>>>>>>>> case?
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> "Jeff Pitsch" <jeff@jeffpitschconsulting.com> wrote in
>>>>>>>>>>>>>>>> message
>>>>>>>>>>>>>>>> news:eYubbhB%23IHA.4020@TK2MSFTNGP03.phx.gbl...
>>>>>>>>>>>>>>>>> You can manually setup a pdf printer on the terminal
>>>>>>>>>>>>>>>>> server.
>>>>>>>>>>>>>>>>> Do you hae the correct print drivers installed to support
>>>>>>>>>>>>>>>>> his
>>>>>>>>>>>>>>>>> printers? Or enabled easy print?
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>> Jeff Pitsch
>>>>>>>>>>>>>>>>> Microsoft MVP - Terminal Services
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> "Saucer Man" <saucerman@nospam.com> wrote in message
>>>>>>>>>>>>>>>>> news:489a0f74$0$19730$cc2e38e6@news.uslec.net...
>>>>>>>>>>>>>>>>>> We are using RemoteAPP with Server 2008. At a remote
>>>>>>>>>>>>>>>>>> location, our user is trying to print from the app but
>>>>>>>>>>>>>>>>>> when he
>>>>>>>>>>>>>>>>>> goes to select the printer from the app, only a few of
>>>>>>>>>>>>>>>>>> his
>>>>>>>>>>>>>>>>>> printers are showing up. If he goes to
>>>>>>>>>>>>>>>>>> START-SETTINGS-PRINTERS, all his printers are there. I
>>>>>>>>>>>>>>>>>> can't
>>>>>>>>>>>>>>>>>> find anything in common with the printers that do show up
>>>>>>>>>>>>>>>>>> in
>>>>>>>>>>>>>>>>>> the RemoteAPP. One of the printers lives at the office,
>>>>>>>>>>>>>>>>>> another lives at his remote location, the other are the
>>>>>>>>>>>>>>>>>> Microsoft Document Writers. He really needs to printer
>>>>>>>>>>>>>>>>>> to a
>>>>>>>>>>>>>>>>>> PDFPrinter that is on his laptop. This PDF printer
>>>>>>>>>>>>>>>>>> converts
>>>>>>>>>>>>>>>>>> the documents to a PDF File. Anyone know how to correct
>>>>>>>>>>>>>>>>>> this?
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>>> Thanks!
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>
Re: Not all printers are showing up using RemoteAPP
I configured the "Items displayed in the Places bar" property to show
MyDocuments. This doesn't seem to have any affect on the 2008 Save As/Open
dialog that appears...even in Notepad. I was hoping this would default the
Save As location to the user's My Documents on his local PC but it is still
defaulting to the user's document folder on the TS. I also tried to
configure it without providing any places but still nothing.
"Jeff Pitsch" <jeff@jeffpitschconsulting.com> wrote in message
news:%23LP9%236SAJHA.4312@TK2MSFTNGP02.phx.gbl...
> Ah, save locations vs drives. got it. I misunderstood what you were
> saying. Try User config\admin templates\windows components\windows
> explorer\common open file dialog and see if that helps.
>
> --
> Jeff Pitsch
> Microsoft MVP - Terminal Services
>
> "Saucer Man" <saucerman@nospam.com> wrote in message
> news:48a9657a$0$24570$cc2e38e6@news.uslec.net...
>>I just published Wordpad. The Save dialog box is also showing locations
>>on the TS such as the Public folder, the user folder, etc.
>>
>>
>> "Saucer Man" <saucerman@nospam.com> wrote in message
>> news:48a96345$0$24596$cc2e38e6@news.uslec.net...
>>>I tried a couple. I tried PDFcreator(free) and Adobe Acrobat PDF
>>>installed on the client. They both produce the known issue. I tried
>>>PDFcreator and CutePDF on the server. PDFcreator doesn't work on TS.
>>>CutePDF does but I am getting folder locations on the server in my Save
>>>dialog.
>>>
>>>
>>>
>>> "Jeff Pitsch" <jeff@jeffpitschconsulting.com> wrote in message
>>> news:u%23ZHSPu$IHA.6132@TK2MSFTNGP04.phx.gbl...
>>>> That may be the pdf software you've chosen doesn't follow "best
>>>> practices" when it was designed. There are a bunch of free pdf
>>>> writers. It's just a matter of finding the right one. Which one are
>>>> you testing by the way?
>>>>
>>>> --
>>>> Jeff Pitsch
>>>> Microsoft MVP - Terminal Services
>>>>
>>>> "Saucer Man" <saucerman@nospam.com> wrote in message
>>>> news:48a58830$0$24590$cc2e38e6@news.uslec.net...
>>>>> Ok, I tried hiding the drives with GP but the SAVE dialog still shows
>>>>> locations on the Terminal Server such as the user profile name,
>>>>> desktop, public, etc. Is there a way to only show the local
>>>>> environment?
>>>>>
>>>>>
>>>>> "Jeff Pitsch" <jeff@jeffpitschconsulting.com> wrote in message
>>>>> news:eDFDvFt$IHA.4760@TK2MSFTNGP03.phx.gbl...
>>>>>> Hav eyou hidden the drives through Group Policy?
>>>>>>
>>>>>> --
>>>>>> Jeff Pitsch
>>>>>> Microsoft MVP - Terminal Services
>>>>>>
>>>>>> "Saucer Man" <saucerman@nospam.com> wrote in message
>>>>>> news:48a56bd1$0$24544$cc2e38e6@news.uslec.net...
>>>>>>> Thanks a lot for all your help. Is there a way I can prevent any of
>>>>>>> the TS drives from showing up when someone opens up a Save dialog
>>>>>>> box through RemoteAPP? If so, I will install the PDF software on
>>>>>>> the TS instead of the client PC.
>>>>>>>
>>>>>>>
>>>>>>> "Jeff Pitsch" <jeff@jeffpitschconsulting.com> wrote in message
>>>>>>> news:OdEcLgk$IHA.3396@TK2MSFTNGP03.phx.gbl...
>>>>>>>> Bad news Saucer.
>>>>>>>>
>>>>>>>> This is a known issue with Easy Print. There are no plans on
>>>>>>>> fixing it until the next Windows release. if you want, you can log
>>>>>>>> a call on the issue and give a deeper explanation of what problems
>>>>>>>> this is causing and the business justification for fixing it.
>>>>>>>> That's the best I can tell you. sorry
>>>>>>>>
>>>>>>>> --
>>>>>>>> Jeff Pitsch
>>>>>>>> Microsoft MVP - Terminal Services
>>>>>>>>
>>>>>>>> "Saucer Man" <saucerman@nospam.com> wrote in message
>>>>>>>> news:48a41d8a$0$24585$cc2e38e6@news.uslec.net...
>>>>>>>>> This is the first time we implemeting TS. The user is testing it
>>>>>>>>> before we go into production. The application creates a document
>>>>>>>>> with a very unique name that the users will not be able to guess.
>>>>>>>>> Having the document named System.Windows.Documents.pdf every time
>>>>>>>>> will mean I will need to find another solution before we go into
>>>>>>>>> production. I tried installing a PDF writer on the TS itself.
>>>>>>>>> That names the document correctly BUT it shows all the drives on
>>>>>>>>> the TS in the Save Dialog Box. That will confuse the user also and
>>>>>>>>> they will end up losing documents by not saving them in their own
>>>>>>>>> local drive. The EasyPrint would be the best if it didn't rename
>>>>>>>>> the documents. Thanks.
>>>>>>>>>
>>>>>>>>> "Jeff Pitsch" <jeff@jeffpitschconsulting.com> wrote in message
>>>>>>>>> news:OP2Vy4Z$IHA.3392@TK2MSFTNGP03.phx.gbl...
>>>>>>>>>> Saucer, is this actually breaking something in the environment or
>>>>>>>>>> is it just an annoyance?
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> Jeff Pitsch
>>>>>>>>>> Microsoft MVP - Terminal Services
>>>>>>>>>>
>>>>>>>>>> "Saucer Man" <saucerman@nospam.com> wrote in message
>>>>>>>>>> news:48a036af$0$24535$cc2e38e6@news.uslec.net...
>>>>>>>>>>> OK thanks. I want to hold off a bit before spending the $260 on
>>>>>>>>>>> a Microsoft call.
>>>>>>>>>>>
>>>>>>>>>>> "Jeff Pitsch" <jeff@jeffpitschconsulting.com> wrote in message
>>>>>>>>>>> news:%23bneP06%23IHA.1040@TK2MSFTNGP03.phx.gbl...
>>>>>>>>>>>>I haven't heard anything back yet. still waiting.
>>>>>>>>>>>>
>>>>>>>>>>>> --
>>>>>>>>>>>> Jeff Pitsch
>>>>>>>>>>>> Microsoft MVP - Terminal Services
>>>>>>>>>>>>
>>>>>>>>>>>> "Saucer Man" <saucerman@nospam.com> wrote in message
>>>>>>>>>>>> news:48a02b13$0$24519$cc2e38e6@news.uslec.net...
>>>>>>>>>>>>> Hi Jeff, did you get any other information on this?
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> "Jeff Pitsch" <jeff@jeffpitschconsulting.com> wrote in message
>>>>>>>>>>>>> news:uPlyT4J%23IHA.5284@TK2MSFTNGP04.phx.gbl...
>>>>>>>>>>>>>> My guess would be it's related to how easy print handles pdf
>>>>>>>>>>>>>> printers. This may require a call into MS to log a bug if it
>>>>>>>>>>>>>> is. I'll try to ping MS on this as well.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> --
>>>>>>>>>>>>>> Jeff Pitsch
>>>>>>>>>>>>>> Microsoft MVP - Terminal Services
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> "Saucer Man" <saucerman@nospam.com> wrote in message
>>>>>>>>>>>>>> news:489b0a59$0$19657$cc2e38e6@news.uslec.net...
>>>>>>>>>>>>>>> OK. I installed the latest .NET framework on the pc and now
>>>>>>>>>>>>>>> all the printers are appearing. However, when the user
>>>>>>>>>>>>>>> prints to the pdfcreator printer, the name of the file is
>>>>>>>>>>>>>>> not related to the print job like it is suppoded to be.
>>>>>>>>>>>>>>> Instead, the filename is system.windowsuments.fix document
>>>>>>>>>>>>>>> sequence. It is supposed to be name based on the job he is
>>>>>>>>>>>>>>> printing. Is this a TS issue orelated to easy print?
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> "Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se>
>>>>>>>>>>>>>>> wrote in message
>>>>>>>>>>>>>>> news:Xns9AF3919D9694Fveranoesthemutforsse@207.46.248.16...
>>>>>>>>>>>>>>>> No, that's not how it works. You have to either install the
>>>>>>>>>>>>>>>> drivers
>>>>>>>>>>>>>>>> on the server or -better- enable EasyPrint.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> WS2008: Terminal Services Printing
>>>>>>>>>>>>>>>> http://blogs.technet.com/askperf/archive/2008/02/17/ws2008-
>>>>>>>>>>>>>>>> terminal-services-printing.aspx
>>>>>>>>>>>>>>>> _________________________________________________________
>>>>>>>>>>>>>>>> Vera Noest
>>>>>>>>>>>>>>>> MCSE, CCEA, Microsoft MVP - Terminal Server
>>>>>>>>>>>>>>>> TS troubleshooting: http://ts.veranoest.net
>>>>>>>>>>>>>>>> ___ please respond in newsgroup, NOT by private email ___
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> "Saucer Man" <saucerman@nospam.com> wrote on 07 aug 2008 in
>>>>>>>>>>>>>>>> microsoft.public.windows.terminal_services:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> I haven't installed any printers on the terminal server.
>>>>>>>>>>>>>>>>> I
>>>>>>>>>>>>>>>>> thought RemoteAPP would use the printers and printer
>>>>>>>>>>>>>>>>> software
>>>>>>>>>>>>>>>>> installed on the client it's running on. Is this not the
>>>>>>>>>>>>>>>>> case?
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> "Jeff Pitsch" <jeff@jeffpitschconsulting.com> wrote in
>>>>>>>>>>>>>>>>> message
>>>>>>>>>>>>>>>>> news:eYubbhB%23IHA.4020@TK2MSFTNGP03.phx.gbl...
>>>>>>>>>>>>>>>>>> You can manually setup a pdf printer on the terminal
>>>>>>>>>>>>>>>>>> server.
>>>>>>>>>>>>>>>>>> Do you hae the correct print drivers installed to support
>>>>>>>>>>>>>>>>>> his
>>>>>>>>>>>>>>>>>> printers? Or enabled easy print?
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>>> Jeff Pitsch
>>>>>>>>>>>>>>>>>> Microsoft MVP - Terminal Services
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> "Saucer Man" <saucerman@nospam.com> wrote in message
>>>>>>>>>>>>>>>>>> news:489a0f74$0$19730$cc2e38e6@news.uslec.net...
>>>>>>>>>>>>>>>>>>> We are using RemoteAPP with Server 2008. At a remote
>>>>>>>>>>>>>>>>>>> location, our user is trying to print from the app but
>>>>>>>>>>>>>>>>>>> when he
>>>>>>>>>>>>>>>>>>> goes to select the printer from the app, only a few of
>>>>>>>>>>>>>>>>>>> his
>>>>>>>>>>>>>>>>>>> printers are showing up. If he goes to
>>>>>>>>>>>>>>>>>>> START-SETTINGS-PRINTERS, all his printers are there. I
>>>>>>>>>>>>>>>>>>> can't
>>>>>>>>>>>>>>>>>>> find anything in common with the printers that do show
>>>>>>>>>>>>>>>>>>> up in
>>>>>>>>>>>>>>>>>>> the RemoteAPP. One of the printers lives at the office,
>>>>>>>>>>>>>>>>>>> another lives at his remote location, the other are the
>>>>>>>>>>>>>>>>>>> Microsoft Document Writers. He really needs to printer
>>>>>>>>>>>>>>>>>>> to a
>>>>>>>>>>>>>>>>>>> PDFPrinter that is on his laptop. This PDF printer
>>>>>>>>>>>>>>>>>>> converts
>>>>>>>>>>>>>>>>>>> the documents to a PDF File. Anyone know how to correct
>>>>>>>>>>>>>>>>>>> this?
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>>>> Thanks!
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.
