Terminal server 2008 / Windows 7 printing

Hi, is the HP universal print driver supported on these platforms?
I've got it setup on this server/client, but I'm having problems printing to the right trays using Word 2010.
Any suggestions?
Or what's the alternative to using HP universal print driver?
Thanks,
JG

BPC 7.0M SP08 was released on September 1st and now supports the client install on both Server 2008 and Windows 7 so yes, you should be able to use terminal server in Windows 2008 if you install SP08. It also has limited support for Office 2010, full support will come with SP09. SAP Note 1490544 is the central SP08 note, and 1504400 is the download note.
-Brian

Similar Messages

Bug: CR XI on Windows Terminal Server 2008

We have a problem when printing a report for example with 2 columns, where the 1st column's content is larger than the width of that column, then the content is printed through colum 2.
But only when:
working on remote on Terminal Server 2008
when printing on a remote printer (redirected)
There's no problem:
in the preview window
when printing to a local printer of the server
on Terminal Server 2003
Any ideas?
Tx
Patrick

You mentioned it worked fine in the preview window, so does the issue only show up when not printing with data?

Cannot quit Visual FoxPro (Windows Terminal Server 2008 + Citrix XenApp 5 + VMWare vCenter 5.1)

Hi everybody:
This is not the typical question about this error, because the problem here is not about how to quit (CLEAR EVENTS then QUIT). The really and weird problem is that our application do no execute the error trapping routines (Try/Catch and ON ERROR) and tries
to directly Quit.
I have never seen something like this before, error trapping routines not executed.
I try to explain the problem better:
- The user click on the Citrix icon of our App
- Citrix shows the executed processes (establishing connection, applying user config, loading profile, etc)
- The Application (VFP 9 SP2) is started and in any moment, while loading, occurs an error that is not handled by error handlers, and it executes a "kind" of a Quit command, that we detect because have a ON SHUTDOWN to catch it, then the App shut
down and the user must click the Citrix icon and start all over again, up to 7 times, when the App really load and work.
- I think that it is useful to make clear that no QUIT command is really causing this, just the behaviour of the QUIT when an error occurs, but just while loading. If the App get completely loeaded, then everything works as expected
Infraestructure:
- Windows Terminal Server 2008 + Citrix XenApp 5 + VMWare vCenter 5.1
- There are up to 50 concurrent users max in every virtualized server
- More than 10 GB of free disk space / Up to 4 GB ram
- RAM Memory is never used to the max
- CPU (Intel Xeon) is never used to the max (up to 90% in some cases)
- Data (DBFs for temporal work) ar on local drive, not over network (to avoid network known problems with smb2-3)
- There are connection to a Oracle 11 database for permanently storing the data
About the errors:
- They are not always the same or in the same place. In example, in one execution could fail the query of SET("Printer",2), in other execution could fail a SET PROCEDURE TO xxx ADDITIVE (sometimes already loaded), in other could fail a "DO
WHILE .T." in a init event.... completely crazy, and in all cases the errors are not thrown, not a single error code, the App just try to quit, as if ALT+F4 where pressed.
- All this does not happen allways to everyone, but happens many times in the day to many many users as to be worried
- The same user can have this error many times a day, but not allways
- Some of the problems started when migrating to Windows Terminal Server 2008, but didn't notice nothing special in the beginning, but a year later (last 2014) problems tend to go worse
Tried solutions:
- For the "SET PROCEDURE TO xxx ADDITIVE" error, a "IF xxx $ SET('PROCEDURE')" check was added
- The "SET('Printer',2)" check was moved out of initialization code, so it executes when user want to print the first time. In this case was neccesary to talk with IT guys to map a default printer after the App runs, and not in background, as it
was.
- Other checks and modifications was made to minimize posibility of errors
- Adding a timeout of 5 secs in the start of the program, to force a wait
- Restart of virtual servers (not the phisical) every 3 weeks
What I suspect:
- Some Microsoft optimization (memory?, process execution?) in WTS-2008 may interfere?
- Some VMWare memory management may interfere with WTS-2008?
- Some Citrix management may interfere with both?
- Server degradation because of day to day use
Results until now:
- Apparently, adding the timeout to force 5 secs delay and the restart of the server have made a notable enhancement in App start and running
with far fewer
errors
Has
this happened to anyone?
Thanks! o_O
Fernando D. Bozzo / Madrid (Spain)

I never had this type of problems, but somewhat similar start up problems. I'd say it indicates resource problems. Low RAM can cause many unpredictable things. In my case loading much data at the begin of an application caused out of memory errors, which
were reported and logged normally, though.
I made a small tool using Windows API functions GetPerformanceInfo and GetProcessMemoryInfo, you'll find declaration and usage like usual at the News2News site. It's a bit lengthy and cluttered, but pretty much what you find there anyway, so I'll not post
my utility code.
I could quite clearly see how many users degraded available memory per session and at some time no further instance of the application was possible on the server. In my case RDP was used to start the app, Citrix will be quite the same, in the end the application
runs on some server and users see the remote running application.
Bye, Olaf.
Olaf Doschke - TMN Systemberatung GmbH
http://www.tmn-systemberatung.de

Is BPC 7.0 compatible with Windows Terminal Server 2008?

Is BPC 7.0 compatible with Windows Terminal Server 2008? We are having printing issues when on WTS 2003.

BPC 7.0M SP08 was released on September 1st and now supports the client install on both Server 2008 and Windows 7 so yes, you should be able to use terminal server in Windows 2008 if you install SP08. It also has limited support for Office 2010, full support will come with SP09. SAP Note 1490544 is the central SP08 note, and 1504400 is the download note.
-Brian

Installing SBO 2007A PL47 for use on Windows Terminal Server 2008

SAP has announced it supports Windows Server 2008 32 bit. Does this mean it will also support Windows Terminal Server 2008 32 bit for hosted clients? Any input will be appreciated

Hi,
There is annoucment only of Windows Server 2008. You can check the status on service Market place under Supported platforms.
https://websmp101.sap-ag.de/~form/sapnet?_SHORTKEY=01100035870000705857&_SCENARIO=01100035870000000183&_ADDINC=011000358700001192682007E&
Under Product Availablity
Regards
Vikas
SAP Business One FOrums Team
Edited by: Vikas Rastogi on Mar 12, 2009 10:22 PM

Cpeaut32: error in formula when print CR rpt 8.5 on terminal server 2008

I have had this similar error in the past when I tried to run an older version of cr (5.0) on a newer pc (xp)and then I had to update some dll's and register them.
Now the same kind of error but different versions of CR and pc software.--CR 8.5 and terminal server 2008
The error reads the same: error in formula (and then code from function in the report where the error occured). "A number, currency amount, boolean or string is expected here... "
The report runs fine on the older terminal server . The program is a VAM application. Any attempt to print report fails (using the preview, print or printer icons)
A solution for a similar problem ( from the sap library ) using CR 8.5 in a Citrix or Terminal Server enviornment was to copy all files from   <systemroot>\Crystal
to
                                                  <systemroot>\System32
But before doing anything i wanted to find out if I needed to update some dlls.   or what is needed to detemine which dll's are causing the problem and what to do about it.

Cpeaut32 is very very old legacy SDK and will not likely ever work on newer operating systems. Upgrade to .NET to get support with recent OS's.

Terminal Server (2008 Standard) stops communicating randomly with printers. Have to reboot TS to temporarily fix issue.

I'm using Windows 2008 Standard, remoteApp feature to run applications at our branch offices (8 locations). All of our printers are HP laserjet printers (mainly 4015 model). All are setup as IP printers. The printers at each branch
are installed locally on the terminal server using the universal PCL5 driver. A majority of the time all works well. However, randomly a printer will change it's status to "offline" on the terminal server.
When that happens the printer itself is fine. Local users can print directly to the printer, and I can access the printer and print to it remotely.
From the terminal server however, it shows that printer as offline. I can't communicate with that printer from TS or even ping that printer's IP address. I can ping all other IP's at that branch, just not the one belonging to the printer from
TS. From any other computer besides the TS I can ping the printer's IP
It's not always the same printer/branch that does this, and there seems to be no pattern to when or where this happens, and I have to reboot the terminal server to get it to talk to that printer again.
Any insight into this or a way to fix it without bringing the terminal server down would be appreciated.

Hello,
Thanks for your feedback.
Based on the situation you described, I recommend you to use a typical solution for Windows Server 2008-based Terminal Server and Networking Printing:
Connect the printers to a Printing Server located in domains.
Install the often-used printers on the client sides, using Easy Print enabled drivers on the client sides.
When the client user remotely access the Terminal Server with Printer Redirection enabled, the client printer can be redirected and work seamlessly.
Most of the community members in this forum are using this solution and the result is satisfying. This method allow the users to print with the same printers both
in local and remote sessions. For more information on Easy Print, please refer to:
Terminal Services Printing
http://technet.microsoft.com/en-us/library/cc753853(WS.10).aspx
TechNet Webcast: Terminal Services Easy Print (Level 300)
https://msevents.microsoft.com/cui/WebCastEventDetails.aspx?culture=en-US&EventID=1032355423&CountryCode=US
Is this solution acceptable in your environment? Thanks.
Lionel Chen
TechNet
Subscriber Support in forum
If you have any feedback on our support, please contact
[email protected]
This posting is provided "AS IS" with no warranties, and confers no rights.

User gets "This network connection does not exist" when she tries to log on to Terminal Server (2008 R2)

User gets "This network connection does not exist" when she tryes to log on to Terminal Server (2008 R2)
I got more than 100 users. Shes the only one getting is. We tried four computers (All Windows 7 Pro)
Nothing useful in event viewer to mention.

Hi,
Thank you for posting in Windows Server Forum.
Does that user able to login previously?
From your comment, it seems that there is some permission issue with that user. As you have checked that user with different system also. Please check that user is added under “Remote Desktop User” local group and also allowed “Allow log on through
Remote Desktop service” permission under group policy. Also please check that when user tries to login it uses “Domainname\Username” format.
In addition for a try, also check by disabling firewall on one particular system.
To add users and groups to the Remote Desktop Users group by using Local Users and Groups snap-in:
1. Click Start > Administrative Tools, Open Computer Management.
2. In the console tree, click the Local Users and Groups node.
3. In the details pane, double-click the Groups folder.
4. Double-click Remote Desktop Users, and then click
Add.
5. In the Select Users dialog box, click Locations to specify the search location.
6. Click Object Types to specify the types of objects you want to search for.
7. Type the name you want to add in the Enter the object names to select (examples) box.
8. Click Check Names.
When the name is located, click OK.
More information:
Remote Desktop disconnected or can’t connect to remote computer or to Remote Desktop server (Terminal Server) that is running Windows Server 2008 R2
http://support.microsoft.com/kb/2477176/en-us
Hope it helps!
Thanks,
Dharmesh

Printing issues when printing to Server 2008 R2 Print Server

We have a problem with netwok printing that encompasses many different areas and versions of Windows OSes so I will be posting this in a few different places.
Let me lay this out for you. We have a single Server 2008 R2 print server with 300 printers of various models. This print server has both 32 and 64-bit drivers installed for every printer. For the HP printers we are using the HP Universal Printing PCL 6
(version 61.94.3.37) and for the Ricoh printers we are using their PCL6 driver for universal printing version 3.5. All drivers run in Isolation mode and no printer gets published to AD.
We have a mix of Windows clients printing to these printers, both XP Pro and Windows 7 32 and 64-bit.
Now for the problems: The other day one Isolation host on the server went crazy, processing was hitting 100% and memory was fluctuating and growing a lot. After investigating a little that isolation host was having issues accessing the Ricoh Driver (which
was 3.4 at the time). In an attempt to resolve the issue we updated the driver to V. 3.5. This seemed to fix the isolation issues and things calmed down however this is the beginning of many other issues for the clients. Both Windows OS versions (XP and 7)
don't seem to be either downloading and installing the updated driver and/or doing so correctly. Clients are now experiencing extremely slow printing, applications such as Word, Outlook, Excel and others open slowly and it can take 2-3 minutes for print dialog
boxes to open. In all cases it seems that we have to have a tech delete the printer(s), delete the driver and then re-install the printer to make things better but for some reason, which is really unknown, this process doesn't work for every machine and on
some we can't even remove the old drivers at all without booting into SafeMode and doing it that way.
With all of that said, are there any suggestions as to why the clients aren't downloading and installing the drivers from the server correctly? How to avoid these issues when we need to upgrade the drivers on the server in the future? Most importantly right
now, are there any recommendations or scripts on how to force the deletions of the printer, driver, reset the print spoolers and then re-add the printers in a more automated fashion?
I have played with both wmic, pnputil and printuidll and am trying to put something together but without a set solution that will work consistently it becomes a lot more difficult.

We are experiencing a very similar issue.
Windows Server 2008 R2. Printers are deployed over group policy.
Clients range from Windows 7 to Windows 8. Citrix XenDesktop and XenApp environment also connects to these endpoints.
We have A wide assortment of HP printers, and Ricoh Printers.
For the ricoh's we have been historically using the PCL6 drivers for the individual device type (not universal print). Up till recently, it all was working fine, until about some time in the middle of june, when everything just seemed to go crazy.
The issue was resolved by moving off from the PCL 6 drivers and using the PCL5e driver counterparts on all of our ricoh printers.
It would crash XenDesktop applications, it would crash office applications.
The print spooler would lock up, even if the ricoh printers were not actually used, just as long as they were loaded.
Even after loading PCL5 on the servers, some of the clients would simply not download the PCL5 version of the driver from the print server. In order to resolve this, I have created the steps below. Be advised, this may possibly cause damage on your system.
We just found it worked great for us. Local printers will likely have to be manually reinstalled after this.
Directions
Stop the print spooler
Open C:\Windows\System32\Spool and delete the following
All files in SERVERS
All files in PRINTERS
All files in drivers
All files in prtprocs
Start the print spooler
Open a command prompt as administrator, and run the following command
Cscript C:\windows\system32\Printing_Admin_Scripts\en-US\prndrvr.vbs -x
This should further delete all print drivers.
Open a command prompt as a standard user (not administrator) and run the following
Gpupdate
Now wait. It takes a while, but the printers will slowly start to repopulate.
I am still not sure what is going on with the PCL6 drivers for ricoh, and why this issue is happening. I'm guessing it has something to do with the Ricoh auto update that is included in their pcl6 drivers. Maybe some sort of auto update happened recently.

Attempted to perform an unauthorized operation sql server 2008 ( Windows 7 )

Dear All,
I am facing following error Sql 2008 setup "Attempted to perform an unauthorized operation sql server 2008 ( Windows 7 )"
I tryed to run setup as administrator
I tryed to run setup to create new user as an administrator and login in new user then run setup
I tryed to run in compatible mode windows xp sp3.
I tryed to login in Administrato account and run setup
in this all time same error came i am tired too much. because of this i format my pc and install windows 7 but still it is same please help me.
Thanks is advance
Regards
Uday
[email protected]

Hi,
Can you locate summary.txt file and details.txt file from location
C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log
Upload these to files on some shared location like dropbox, onedrive etc and post link here I would analyze and see where actually problem is coming.
This link would also help you in searching log files.
PS: Dont reply to duplicate thread you posted
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it
My Technet Wiki Article
MVP

Windows 7 client can't connect to Server 2008 R2 Print Server VM (ESXi 5.5)

I have an issue today that is driving me bonkers.
I recently came on-board to a company in my area as the system administrator and this network has everything and the kitchen sink wrong with the network layout, probably the worst I've seen and I'm slowly but surely fixing it day by day.....
Well today I decided I was going to spin up another VM from a template and make a Print Server, seems harmless right? --- I thought so too, added all of the printers to the server and did test pages, all was dandy, but then I tried to add the printers to
clients and other server and the real fun has begun, I'm truly perplexed now...
I added a VM to my esxi 5.5 cluster at work that is a 2008 R2 server with only print management on it. I can map all of the printers on the network to the print server as-well as install the drivers correctly and I can resolve the IP and server name via
DNS. I can test printers directly from the print server successfully printing out test pages however whenever I try to map printers you know from the directory in 'devices and printers' from any of the Windows 7 clients or any of the other 2003/2008 servers
I get the classical "Windows cannot connect please check the network connection and make sure sure the printer is turned on". I disabled the windows firewall and I made the point to print GPO set to disabled and still no luck. Again I can print to
all of the printers internally inside of the VM (so I know it communicating to all of the printers), I just can't connect to the printers listed in the directory on any of external desktop/client, it's like so annoying. spent about 6 hours until my brain just
couldn't think anymore, was about to go BS on the VM.
The only thing I can think of, as I was driving home, is that there is a GPO on one of the DC that has a desginated print server policy set. But prior to last week the forest leve was 2000 and now it's 2003. I just don't know Server 2000 enough to know if GPO's
worked in the same way they do in 2003.
Right now printers are connected to other servers in a ad hoc mentality it seems, there has never been a true print server.
Anyone ever have this problem before?
I'm truly puzzled...

Hi Mid.Hudson-IT,
Before we begin ,we should ensure we have configured the printer server correctly .
Here is a link for reference of configuring the printer server .
Print server role: Configuring a print server
https://technet.microsoft.com/en-us/library/cc775791(v=ws.10).aspx
"I can map all of the printers on the network to the print server as-well as install the drivers correctly and I can resolve the IP and server name via DNS"
From this sentence ,I can`t figure out whether you have tried to ping the server both with the IP adress and name adress from the client ?
If we can ping the print server from the client,we can ensure the connection to the printer server is good .
Then we can try to install the printer driver directly to have a check .In the adress bar of Windows Explorer ,input "\\server name \the printer name"
If we cannot ping the print server ,we should troubleshoot the network issue firstly.
We also can check the event viewer for more information to troubleshoot this issue .
Best regards

Adobe Acrobat X Pro - Windows Terminal Server 2008

Hi All,
Im hoping some one maybe able to help me on this, We have recently purchased the Adobe Acrobat X Pro for one of our clients and have just installed it onto their Windows 2008 x32 Terminal server. Inatall appeared to be fine, no errors reported and nothing logged into the event viewer. However we seem to be having issues with it... I did read a PDF guide early last week that said the X Pro should work fine on a Server 2008 - The install instructions where rather straight forward and I thought their would have been more to it than just installing it via the control panel.
The issue we have is the program opens up ok and is usable for about a min and it then crashes with no obvious reason, From looking in the event log it appears to report issues with the PDApp.exe and the Kernel32.dll - Has anyone come across any similar issues?
Many Thanks

Hi,
You can also send the crash dump by following the below mentioned steps:
Install WinDbg from http://www.microsoft.com/whdc/devtools/debugging/installx86.mspx
Launch WinDbg via the shortcut
Click File->Open Executable
Select Acrobat.exe from "C:\Program Files\Adobe\Acrobat 10.0\Acrobat\Acrobat.exe" and hit "OK"
Remember to press "g" and hit enter when you encounter the first breakpoint and then you will see a text "Debuggee is running" and Acrobat will be launched
Open whatever file is it that produces the crash in Acrobat.
When you have successfully reproduced the sceanrio causing the crash/freezing of Acrobat X, enter the below command in the WinDbg terminal
.dump /ma c:\temp.dmp (Hit enter)
This will produce the crash dump at C:\ by the name of temp.dmp
After that please upload the dump (compress the dump using WinZip or likewise) at some third party sites and provide the link for the same. Also, if it’s possible could you share the PDF as well, for which your application crashes on a consistent basis.

Windows Server 2008 R2 Printer Migration

Hi Guys,
This is more of a reassurance than a question but i just want to be 100% sure.
I'm a second line engineer trying to gain exposure into third line and i have been given a small project to migrate some printers from a Windows Server 2008 machine to a Server 2008 R2 machine which is an already established priner server hosting 95% of
our printers.
My (possibly silly) question is if i export the printers from the 2008 server can i import them onto the 2008 R2 server without overwriting whats already there.
I have seen printers migrated from scratch but i just wanted to make sure i can add the to whats allready there,
All the drivers x64 and x86 are already in place.
Thanks

Hi,
Sorry for my delay.
Based on your description, did you mean that migrate Print Servers from Windows Server 2008 to Windows Server
2008 R2?
You can use the Printer Migration Wizard or the Printbrm.exe command-line tool to export print queues, printer
settings, printer ports, and language monitors, and then import them on another print server that is running a Windows operating system. This is an efficient way to consolidate multiple print servers or replace an older print server.
Please refer to following articles and check if can help you.
Migrate Print Servers
Print Migration Tool
If anything I misunderstand, please don’t hesitate to let me know.
Hope this helps.
Best regards,
Justin Gu

Windows Server 2008 r2 printer access denied.

i have a windows server 2008 r2 PC with a printer installed and shared on it. when trying to access the printer from any other PC in the network i get "windows cannot connect to the printer. access is denied" this is from both a windows 7 and
windows 8 PC.

Helped me to set Security permissions on system with printer (Win 2008) of folder "C:\Windows\System32\spool\drivers" for group NETWORK to "Full control".

Weird issue with Windows Server 2008 R2 Print Server

I have an issue with Windows 2008 R2 (VMWare Hosted) running Windows Print Server.
Prior to a small network change, the print server was working well, hosting about 80 different networked printers from various vendors.
We made a change (that we ended up rolling back) to the Client's DHCP Scope OPT 006 (DNS Servers). The DNS servers never quite worked right and broke AD authentication to different servers, and was just a mess.
After rolling back we are not able to keep the printers online. If we ping them from the print server, the printer(s) never wake up, when a print job is submitted. If we ping them from one of the access switches, they work fine (until they fall back asleep),
to prevent this, if we start a ping on the server AFTER waking them up from the Switch Ping, they stay online and no problems.
If we stop the ping, they fall back asleep at some point, and again, won't wake up without intervention/switch side ping.
Has anyone experienced anything like this? Any tips on how I could possibly resolve it?
Thanks in advance.

Hi,
According to your description, the issue seems to be that the printers can't keep online. Sounds like a power managerment issue. Why these printers fall into sleep? Have you consulted this issue with the manufacturer of these printers? Do these printers
fall into sleep if them lose the contact with printer server? Have you tried to reset the printers?
>>We made a change (that we ended up rolling back) to the Client's DHCP Scope OPT 006 (DNS Servers).
DNS client will cache the recently queried records. If the DNS server has replied with a wrong records, communication issues will occur. To clear the DNS cache on a Windows device, please run the command below:
ipconfig /flushdns
Best Regards.
Steven Lee 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]

Terminal server 2008 / Windows 7 printing

Similar Messages

Maybe you are looking for