Remote Desktop local printer redirection problem - Server 2012 Foundation

Hi,
I am trying to print from Windows Server 2012 Foundation to my local printer hosted on Windows 7.
When I enable local resources in the RDP client, I can see my printers on the server like redirected. All seems like no problem occured. But only print does not work. ;-)
I can see the document name in the queue with Error status.
I tried set up GP with disabling Easy print, the drivers are identical on both machines, event logs are clear.
The server is freshly installed, running only File server role. No Domain controller role is set. No Terminal Service is set (i think in Foundation is it not possible), only allowed RDP.
RDP client is the newest. I have not any problem to print from other servers (WS2003, WS2008R2) using this printer. Everytime is the printer automatically redirected to TS*** port and works.
I spent few hours searching solution with no effect.
Any idea? Many thanks!

Hi,
Did you find any error message during this issue?
Please check you have enabled necessary port for printer redirection on server side. You can check “Do not allow client print redirection” is disable under GPO setting. Also the user must have enough permission to print the document. Please check below link
for more information.
1. Terminal Server and Printer Redirection
2. Five reasons printer redirection causes Windows printing problems in RDS
Hope it helps!
Thanks,
Dharmesh

Similar Messages

  • Remote Desktop Services Printer Redirection with easy print not working as Desired

    Hi,
     I have a Terminal Server Farm with a number of Windows Server 2008 R2 Remote Desktop Session Host Servers in the Environment. There is also a RD Gateway server which is used to connect to the RD Session host servers in the environment. We
    had configure the policy "Use Terminal Services easy Print Driver First" for all the RD Session Host servers. Everything was working well untill a couple of users Complaint about slow printing on Easy Print. While trying to troubleshoot the issue we came
    to know that when we by-pass the RD Gatewat and make a Direct connection to the RD Session Host Servers we are able to Print Really fast using Easy Print. Only When we use the RD gateway server we get the problem with the Printing.
     As we could not get through this problem and we are not in a condition to by-pass RD Gateway for connections we decided to put the TS Easy print Driver as a Second option. We went ahead and identified the 3 printers for which printing was slow. we
    Installed the Drivers for the same printers on all the Terminal Server and Disabled the policy "Use Termianl Server Easy print Driver First". After this we were able to print fast on the 3 printers having Slow printing issues. All the other Printers were using
    Easy print.
    After a day we realised that there were more than 20 drivers for Different printers installed in the Print Server Properties. We started getting viered problems with the Printing on all the Terminal servers like, Print Spooler Service Crashing, Hanging,
    Users not able to redirect printers at all. To avoid this we Removed the Driver Packages but they came back the very next day.
     I am not sure what could be causing this kind of behavior. I would really appriciate if someone can help he with these two problems
    1) Easy print Working Slow only when using RD Gateway Server
    2) Printer Drivers Getting installed on Terminal Servers when Easy Print Policy is disabled.

    1) Easy print Working Slow only when using RD Gateway Server
    > Difficult to track down especially through forum. Looking for some known issues/hotfixes
    954743 FIX: After you apply hotfix 954744, printing performance may be significantly slower when you print documents by using Terminal Services Easy Print
    http://support.microsoft.com/?id=954743  
    The Remote Desktop Easy Print (RD Easy Print or TS Easy Print) uses the XPS print driver that ships with .NET Framework.
    2) Printer Drivers Getting installed on Terminal Servers when Easy Print Policy is disabled.
    > If Easy print is not the first driver then it installs the driver if they are InBox drivers
    > If these are non-inbox drivers - This is because administrators are RDPing to the server from another PC with several printer/drivers installed.
    When they RDP with printer redirection enabled, the drivers get automatically installed.
    To avoid this, either turn off printer redirection at server level from RDP-TCP properties - might not be feasible if users need redirected printers
    Else make sure that when admins RDP, printer redirection is turned off so that drivers are not automatically installed
    This was a major issue in 2k3, i havent tested it in 2k8 though
    This behavior is related to the change you made in Easy print driver behavior
    Sumesh P - Microsoft Online Community Support

  • How to enable printer redirection in server 2012 (client printer should map in server 2012)

    Hello All
    I have 3 new 2012 servers by default client printer should map in 2012 server i have enabled in RDP properties but no luck can any one have the idea about this issue.

    Hi Mohan,
    You can refer below links to configure Printer redirection in Windows Server 2012.
    Print and Document Services Overview
    Configuring Printer Redirection Settings
    Printer Redirection
    Regards,
    Manjunath Sullad

  • How to allow more than two users on remote desktop on windows server 2012 foundation?

    i have a dell server power edge T300 with windows server 2012 foundation. I am unable to connect more than two remote desktop at once.

    Hi,
    Add to Brain, you cannot have more than 15 user accounts in Windows Server 2012 Foundation.
    In order to access a hosted application, such as Microsoft® Office, a license for Windows Server 2012 Remote Desktop Services is required for each user account (not to exceed 15 user
    accounts) that directly or indirectly uses RD Gateway to host a graphical user interface, including using Remote Desktop Connection (RDC) client. When using Remote Desktop Services, you may not install or use Remote Desktop Connection Broker or Remote
    Desktop Virtualization Host role services. For more information about Remote Desktop CALs , see http://go.microsoft.com/fwlink/?LinkId=140238.
    http://technet.microsoft.com/en-us/library/jj679892.aspx
    Hope this helps.
    Jeremy Wu
    TechNet Community Support

  • Printer redirection using Server 2008 R2 RDS

    Hi
    I have a server 2008 R2 (not a domain controller) running as a remote desktop session host with 2 remote XP SP3 client PCs connecting to it. Up until Friday last week these client PCs could successfully print via the redirected printer using the RD Easy
    Print Driver. As from this week though all printing has ceased! No updates have been installed on either server or clients in the interim. When I try to send a test print from the server (logged on using RD 7 for XP) it tells me that the test print has failed,
    do I want to run the troubleshooter? If I say yes then the troubleshooter fails with an unexpected error, the details of which include error code 0x80070057. If i try to print from the server using notepad I get the error "the parameter is incorrect". If I
    print from wordpad the document appears briefly in the queue but nothing prints. If I manually add a printer (using specific printer driver - not easy print driver) and choose the correct redirected port and then print using this printer, the print job appears
    briefly in the queue and then disappears - nothing appears in the print queue on the client PC and nothing prints. Initially printing like this caused the client TsWpfWrp.exe to fail but upgrading the version of TsWpfWrp.exe stopped this problem. I have tried
    updating to .net 4.0 on the client PC, upgrading from RD 6.1 to 7.0, XP SP2 to SP3 all to no avail.
    Does anyone know the solution to this problem? I am at a complete loss as to the way forward. I have checked all group policies and set all the correct permissions on the spool and PRINTERS folder in system32 on the server and nothing seems to help.
    Thanks for your help!

    Hi,
    Please try to check the following items.
    1.      
    Remove the Remote desktop easy print from Print Management console.
    2.      
    Remove the complete package.
    3.      
    Then install the Remote desktop easy print driver again.
    Please also check if the
    fenableRDR key still exists in the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\Wds\rdpwd.
    Technology changes life……

  • Remote Desktop Farm Printing

    Hello,
    I am setting up a new 2008 R2 RDS load balancing Farm.  I have seen other 2008 R2 Farms with identical print servers setup on each RDSH server.  Each user gets an identical list of printers no matter which server they log into. 
    They use rdp profiles to follow them to each server.
    Is it best to setup print server on each server or is there a different way to do this?  It worked pretty well at other site.  I just want to do it the best way.  If there is any documentation thats good too.
    Thanks!

    Hi,
    The best practice for setting printer in office environment depends on company’s requirement and many other factors. You can install printer or each server and then assign to use by users or make printer redirection setting for client to use as specified printer
    is allocate to the users session. If you want then also try to RD Easy print service for your case. For more information you can go through beneath link.
    1. The Ultimate Guide to Terminal Server Printing - Design and Configuration
    2. Using Remote Desktop Easy Print in Windows 7 and Windows Server 2008 R2
    3. How to configure Microsoft RDS Universal Printing
    Hope it helps!
    Thanks.
    Dharmesh Solanki
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

  • Remote Desktop cannot verify that this server belongs to the same server farm

    Hello Team,
    I am running Windows Server 2012 in my environment. I have 2 RDS Servers which are configured for load balancing. RDP to these hosts works just fine. But when i connect to any published remoteapplication , it gives me an error
    Remote Desktop cannot verify that this server belongs to the same server farm.
    What am i missing here, kindly suggest.
    Binu Kumar Small Business Server Support

    Hi Binu,
    Do you have any progress?
    If not, please make sure that the RD web access URL is configured as the farm name on each Remote Desktop Session Host server.  
    Here are some related threads below for you:
    TS Web with TS Farm on W2K8 servers
    https://social.technet.microsoft.com/Forums/windowsserver/en-US/09715e58-6e52-4c39-b445-4aa8fbc31cb0/ts-web-with-ts-farm-on-w2k8-servers?forum=winserverTS
    RD Session broker issue; Cannot connect to one of the host servers through RDC
    https://social.technet.microsoft.com/Forums/sharepoint/en-US/b9c15a01-a9cb-4793-8758-acd2e60ae7a5/rd-session-broker-issue-cannot-connect-to-one-of-the-host-servers-through-rdc?forum=winserverTS
    RemoteApp - Cannot verify computers belong to the same server farm
    https://social.technet.microsoft.com/forums/windowsserver/en-US/40be1eda-f752-4b64-bb47-dbe2156218f9/remoteapp-cannot-verify-computers-belong-to-the-same-server-farm
    Best Regards,
    Amy
    Please remember to mark the replies as answers if they help and un-mark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
    [email protected]

  • Windows Server 2012 Foundation, in a Workgroup - "The server did not finish checking the license compliance. If the server is joined to a domain, make sure that the server can connect to a domain controller"...

    Every few days we see two dialogs with the following messages:
    Dialog 1, title: Check for Licensing Compliance is Incomplete
    The server did not finish checking the license compliance. If the server is joined to a domain, make sure that the server can connect to a domain controller.
    Dialog 2, title: Check for Licensing Compliance is Incomplete
    The server did not finish checking the license compliance. If the server is joined to a domain, make sure that the server can connect to a domain controller. If the license compliance check cannot be completed, the server will automatically shut
    down in 8 day(s) 23 hour(s) 0 minute(s).
    The server is not (and never has been) joined to a domain or had any DC roles installed. In fact its still connected to the default Workgroup.
    The server was configured in our office and never showed this message until it was installed on site. The main difference from what I can see is that when installed on site it was given a static IP address and does not have any DNS settings in the network
    adapter properties. 
    I have scoured a number of forums on this error but in almost every other instance of this error message the servers are connected to a Domain Controller and the solutions generally are linked to dis-joining and rejoining the domain. Unfortunately this is
    not an option for this scenario.
    I initially thought that adding some relevant DNS server IP address may resolve the issue, however, we have the exact same model server configured exactly the same running at a different site that does not experience this problem. This server also has no
    DNS server configured.
    I have seen a post that suggests turning off the servers "Foundation Checking", but I'm unsure how to do this.

    Thanks for your response Vivian.
    I can confirm that this server is not (and never has been) a member of any active directory, it is configured as a Workgroup server. It was initially configured on a network that does have an active directory, but was never joined to it. During that time it
    never displayed these messages.
    The server was moved into production on a different site and network and setup with a static IP address.The site network does have its own active directory but the server was not joined to it. It is whilst on this new network that these messages began.
    Since my original post DNS servers have been added and the Microsoft activation has been verified, however, the messages are still appearing.
    There are only 2 user accounts configured on this server. The local admin account and another local admin user.
    The remote desktop services roles have been installed but not yet configured. I don't think that has any bearing on this scenario though.
    The description of this error in the above "Introduction to Windows Server 2012 Foundation" link states:
    This error occurs when the server cannot finish checking the requirements for the root domain, forest trust configuration, or both. It usually happens when the server cannot connect to a domain controller. If the situation persists, the server will
    shut down 10 days after the first time the compliance check failed. Each time this error message occurs, it will state the actual time remaining before the server will shut down. If you restart the server after it has shut down because of non-compliance, the
    server will shut itself down again in 3 days.
    The above description leads me to the following question - In a Workgroup environment, does the server still try to contact a domain controller to establish a level of trust? If this is the case could it be that the server can no longer see the initial DC
    on its new network and this is what is triggering the messages?
    Am I clutching at straws here?

  • Hyper-v Role in Windows Server 2012 foundation and Essentials

    Hello,
    I have seen that the two low cost version of Windows Server 2012 essential and Foundation) will not support hyper-v. Can you please tell me what it means exactly :
    Can you please tell me what is possible :
    -The server can not be installed as a hyper-v  guest (probably yes)
    -The hyper-v role can not be installed on the server (so I have to rely on vmware)?
    - Hyper-v role can be installed but there is no free license included with the server.
    Thank you
    Marc

    I suppose then, you would have to install Windows 8 and Hyper-V as your guest or core.
    Then run your Server 2012 Foundation under Win8.  which has 512GB Memory Limit.
    It seems asinine that you cannot install this role on Foundation, but seemingly you could work around it with Win8.  (Or Sun Virtual Box (free) (or VmWare(Free).
    So load up a dozen Win8Pro virutal sessions on that Win8 VirtualBox with up to 512GB Memory and Create your own Ghetto Remote Desktop Server with Foundation and Windows 8.   ;)
    What good is it if your can't run Hyper-V and Remote desktop services?  Those are the two apps small business need most.  But Microsoft strips it out, calls it a DEAL  (Essentials and Foundation) , yet if you want the good stuff, you're gonna
    have to buy Server 2012 Standard anyhow, + the CALs.
    So you are hooked into this "deal" by Microsoft Special Offer.   Its special alright, because you get to buy it twice.  The stripped down version that come with your server, then the full version when you discover Foundatoin and Essentials gives
    you AD, and thats it.  Nothing Else.  No "deal"
    Remember:
    All you get with Foundation or Essentials is AD and Group Policy.
    You cannot load RDP on Foundation or Essentials
    You cannot load Exchange on a DC, or Foundation or Essentials
    You cannot load Exchange and RDP on the same box.
    You cannot have Remote Web Apps if you load RDP on your DC.
    You cannot win with Microsoft.  No worthwhile "deal" has ever come out of the city of Redmond.
    The internet is a one-way money pipeline to Microsoft.
    Its three times the work, three times the cost and requires three servers licenses to do with 2012, what you could do with one 2008R2 license.  
    Might as well purchase 2 Server 2013 Standard Editions if you want:
    1.) Active Directory
    2.) Remote Desktop and Remote Apps
    3.) Your own Exchange Server
    You are better off installing a NAS if all you need is a file server. 
    Why bother with Foundation or Essentials?  Its a "Gimmick-ware"

  • Windows Server 2012 Foundation

    For a really small company I selected Server 2012 Foundation to meet their requirements:
    - 3 permanent Users (plus me as an external Administrator)
    - just a fileserver to store common data
    So, in my opinion, a workgroup installation would satisfy all requirements and RDS Services are required  for administration only (for me).
    As I found a lot of inconsistent Statements about installation environments on different web pages I would like to get a specific answer to my individual problem.
    Which Server role do I have to choose to implement an Administrator remote Access without getting in conflict to other restrictions of the 2012 Foundation characteristics or policies.
    Thank you

    Hello,
    As this is a German forum I would kindly ask you to either translate your Post in German or to post it again on the English Forum.
    Da wir uns in einem deutschsprachigen Forum befinden, würde ich Sie gerne bitten wollen, dass Sie entweder alle Ihre Beiträge ins Deutsche übersetzen oder die
    Thematik erneut im englischsprachigen Forum veröffentlichen.
    Best Regards/ Mit freundlichen Grüßen,
    Michaela
    Bitte haben Sie Verständnis dafür, dass im Rahmen dieses Forums, welches auf dem Community-Prinzip „IT-Pros helfen IT-Pros“ beruht, kein technischer Support geleistet werden kann oder sonst welche garantierten Maßnahmen seitens Microsoft zugesichert werden
    können.

  • RDP client nuber in server 2012 foundation

    Hi,
    I need to know how many RDP user can be connected to server 2012 foundation. I want to use domain controller, backup and some app via rdp. In the documentation what I found was that the foundation has limited to 15 users, but no need to cal licenses. It
    is real? 15 users can use RDP connection?

    Hi,
    Thank you for posting in Windows Server Forum.
    Yes, agree with words of diramoh that we need to have RDS CASL installed for user to access the server remotely. You can go through following article (RD Gateway “Note” Section).
    Introduction to Windows Server 2012 Foundation
    http://technet.microsoft.com/en-us/library/jj679892.aspx
    Hope it helps!
    Thanks.
    Dharmesh Solanki
    TechNet Community Support

  • Does windows server 2012 foundation ed. support sharepoint?

    does windows server 2012 foundation ed. support sharepoint?

    Based on the feature set, yeah it would support SharePoint 2010, but I wouldn't recommend it. Server 2012 Foundation must be a Domain Controller or in a Workgroup, neither of which are good scenarios for a SharePoint installation.
    Trevor Seward
    Follow or contact me at...
    &nbsp&nbsp
    This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

  • Server 2012 foundation cd download exist ??

    i know there was an server 2008 cd but i need 2012 cd download  .
    i searched the internet and didnt understand is it exist or not .
    i found on microsoft a download of standard,datacenter,essential and that it 
    maybe the foundation is combined now with other version ?
    if i have a license of 2012 foundation it will work on other version ?

    Foundation is not a downloadable software.  It is only available to OEMs.
    http://technet.microsoft.com/en-us/library/jj679892.aspx 
    "Because Windows Server 2012 Foundation comes pre-installed with your server hardware, you do not need to separately obtain and then install the hardware and operating system."
    .:|:.:|:. tim

  • Acrobat Pro XI, Server 2012 r2 Remote Desktop, cannot print until server reboot, No Pages Selected

    Ever since we migrated to terminal services (remote desktop) this problem has plagued us.
    We are a terminal services environment with 25 users.
    Our version of Adobe is 11.0.10
    I've believe I have traced the issue to temp files in \users\username\appdata\local\temp\XX
    There are [email protected] files that the system locks.
    Once those files are written out and the server locks them down the user cannot print .pdf files any longer.
    ALL OTHER APPLICATIONS WORK PERFECTLY!
    The only way to clear the situation is to reboot the server (not optimal).
    And even then the problem reappears within a day.
    I have read many different versions of this problem and tried many different solutions.
    I have tried having the users go the advanced tab when printing and choose "print as image"
    FAIL!
    I have put a acroct.ini with the following parameters in the windows directory
    [WinFntSvr]
    TTToSysPrintDisabled=1
    T1ToTTDisabled=1
    FAIL!
    I have tried to remove Microsoft security updates related to this issue and 3rd party fonts.
    FAIL!
    I've tried the "Disable Protected Mode at Startup"
    FAIL!
    I have rebuilt our print server with the latest drivers.
    FAIL!
    Since we deal with thousands of .pdf files on a daily basis this has become CRITICAL!
    Please Help!

    Please see this thread: No Pages Selected RDS Server 2012r2

  • Redirected printers using Remote Desktop Easy Print driver work only once during session

    Hello all
    We are running Windows Server 2012 R2 Remote Desktop Services Sessions hosts with printer redirection allowed using only the Easy Print Driver, we have no other drivers installed on the servers. All client printers are redirected and can print fine, but
    only once per session! We have tested with several different client printers and they all work a single time in each session. After that the user needs to log off and then back on again to be able to print once again, but only once. Needless to say, our users
    are annoyed. If I look at the c:\windows\system32\spool\printers folder while jobs are printing, but failing, I can see the spool files appearing and disappearing as jobs are spooled. No errors in the event logs accompany the behaviour. Our clients are running
    Windows 7, 8 and 8.1. All exhibit the same problem. The error looks a little like what is described here:
    http://support.microsoft.com/kb/2925429
    While similar, this problem describes a scenario where Easy Print is not used, but XPS is, and since Easy Print is based on XPS and the behaviour is very similar, I am tempted to make a connection.
    I have checked all the usual stuff with permissions etc, and no manufacturer provided drivers are present. The problem appears on newly installed systems as well as one that have been running for some time. Restarting the spooler services does not resolve
    the problem. Actually I do not think it is related to the spooler service or driver framework at all, but rather is an Easy Print driver issue that is occurring much later in the process, if not I would see some errors in the logs and no jobs would print at
    all.
    Anyone ever heard of something like this?
    Thanks
    Morgan

    Hi Morgan,
    Based from your description, users can only print once during single RDP session, I suggest you check if this issue also happens locally.
    In addition, after the first print attempt, does any other issue exist on the RDP session?
    Is the server fully patched? If there are any available driver updates, please also apply them. If there are any third party software installed, try disable/uninstall them to see if the issue persists.
    You can also enable print auditing to get more detailed information about this issue.
    More information for you:
    Auditing Printing Events
    https://technet.microsoft.com/en-us/library/cc976774.aspx
    Logging Spooler Events
    https://technet.microsoft.com/en-us/library/cc976746.aspx
    Best Regards,
    Amy
    Please remember to mark the replies as answers if they help and un-mark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
    [email protected]

Maybe you are looking for