Windows 2008 Terminal Server, Acrobat 7, 9

Hello,
I have Acrobat 7 installed on a Windows 2008 terminal server. Anyone with a terminal session that has Acrobat 7 installed on the local workstation is able to create Acrobat documents. Why is it that anyone with a terminal session that has Acrobat 9 installed on the workstation is not able to create Acrobat documents?
Thank you,
techctzn808

I replied to your other message
http://forums.adobe.com/thread/536492?tstart=0

Similar Messages

Acrobat 9 Reader with Windows 2008 Terminal Server

I am setting up a Windows 2008 Terminal Server and i need to have the Adobe Acrobat Reader installed. I downloaded and installed the Vista version and it worked from the console but when i try to access it via a terminal server session the application just crashes. If i try and run it as administrator in the same terminal server session it launches fine.
Any suggestions????
Jason
p.s The associated event log error is:
Log Name:      Application
Source:        Application Error
Date:          7/31/2008 1:17:57 PM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      Comet.invera.com
Description:
Faulting application AcroRd32.exe, version 9.0.0.332, time stamp 0x4850f0a3, faulting module Annots.api, version 9.0.0.332, time stamp 0x4850e57f, exception code 0xc0000005, fault offset 0x001bd9e0, process id 0x1458, application start time 0x01c8f3316002e3b7.
Event Xml:
    1000
    2
    100
    0x80000000000000
    3663
    Application
    Comet.invera.com
    AcroRd32.exe
    9.0.0.332
    4850f0a3
    Annots.api
    9.0.0.332
    4850e57f
    c0000005
    001bd9e0
    1458
    01c8f3316002e3b7

Jason...
Make Certain that you Had the Server In "TS-Install" Mode When you Installed Acrobat. It Is In your Control Panel. I Have Pasted the MS Help File Below.
Install Programs on a Terminal Server
You should install the Terminal Server role service on the computer before you install any programs that you want to make available to users. If you install the Terminal Server role service on a computer that already has programs installed, some of the existing programs may not work correctly in a multiple user environment. Uninstalling and then reinstalling the affected programs may resolve these issues.
To ensure that an application is installed correctly to work in a multiple user environment, you must put the terminal server into a special installation mode before you install the application on the terminal server. This special installation mode ensures that the correct registry entries and .ini files that are needed to support running the application in a multiple user environment are created during the installation process.
You can put a terminal server into this special installation mode by using either of the following:
Install Application on Terminal Server tool under Programs in Control Panel. This tool will run a wizard to help install the application.
Change user /install command at a command prompt. You will have to start the installation of the application manually.
After the application is installed, you must put the terminal server into execution mode before remote users begin using the application. The Install Application on Terminal Server tool will automatically put the terminal server into execution mode when it is finished running. To put the terminal server into execution mode from a command prompt, use the change user /execute command.
Additional considerations
Some programs may require minor setup modifications to run correctly on a terminal server.
If you have programs that are related to each other or have dependencies on each other, you should install the programs on the same terminal server. For example, you should install Microsoft Office as a suite on the same terminal server instead of installing individual Office programs on separate terminal servers.
You should consider installing individual programs on separate terminal servers in the following circumstances:
The program has compatibility issues that may affect other programs.
A single program and the number of associated users may fill server capacity.
For more information about the change user command-line tool, see the Terminal Services Command Reference (http://go.microsoft.com/fwlink/?LinkId=89674).
For more information about deploying programs on a terminal server, see the Terminal Server page on the Windows Server 2008 TechCenter (http://go.microsoft.com/fwlink/?LinkId=79608).

Add Windows 2008 Terminal Server to RWW/RWA

I would like to add our Windows 2008 Terminal Server (not R2) to RWW in Windows 2012R2 Essentials. The connect computer wizard did not work on the Windows 2008 server, returning Win32 error.
How do I add the 2008 TS to the devices listing in RWW without using the connector wizard (as it does not work). The Windows 2008 server has been join to the same domain manually.

You cant add it as a tile device in the way you could in SBS 2011 Standard.
You can create an RDP file, and save that so it is accessible via the RWA then add a link to the RWA to that file.
You may need to tweak IIS to allow .rdp files.
Robert Pearman SBS MVP
itauthority.co.uk |
Title(Required)
Facebook |
Twitter |
Linked in |
Google+

Windows 2008 Terminal Server issue after swapping modem/router

Hi, I have a problem I just can't crack.
Windows 2008 Terminal Server, all patched and up to date. The IP Address is 192.168.1.11 (on a teamed intel controller). Terminal services enabled and working ok.
TP-Link Modem 192.168.1.1, RDP Port forwarded ok.
Set the Windows gateway to 192.168.1.1 and external access to RDP is not a problem.
We had some modem speed issues, so we got a much faster connection, but it can't be used for incoming RDP, so left the TP-Link in place. So added a 3G modem at 192.168.1.5 and set that as the gateway.
External RDP access still works perfectly, and now users have much faster internet.
The TP-Link is giving some reliability issues, so I swapped it over for another modem, a Billion modem. Same 192.168.1.1 IP address, same port forwarding. External RDP access is no longer possible.
Swap back to the TP-Link and everything is fine. Test the modem on another site, everything works as expected.
If I set the gateway on the terminal server to 192.168.1.1 with the Billion attached then external RDP access is no problem. If I set it to 192.168.1.5 then it stops working again.
I tried with a new TP-Link modem of the same model with exactly the same settings and this also had the same problem. External RDP access will only work the existing TP-Link modem, which is a problem as the modem appears to be faulty.
It's almost like it hasn't worked out that it's a new network, and when Windows does that it seems to lock down RDP. That is only my assumption from experience of moving computers to new networks and RDP won't work until windows prompts you with the new
network screen to select home, office or public.
Has anyone experienced anything like this before or can shed some light on the problem?
Thanks.

Hi,
How is the issue going now? Is there any update?
Thanks.
Jeremy Wu
TechNet Community Support

Windows 2008 Terminal Server "user must change password at next logon" problem with Windows 7 client.

Hi,
I have a fully patched Windows 2008 SP2 Terminal Server and a fully patched Windows 7 client.
I have logged into the Windows 2008 SP2 Terminal Server server with a test account via RDC before.
When I try to log in via RDC to the 2008 TS with a test account which has been marked with the setting "User must change password at next logon" I get the RDC message "You must change your password before logging on the first time. For assistance, contact your system administrator or technical support." I need to force the user to change their password once it has been issued, any ideas on how this can be done?
Thanks,
Dan

This does not resolve my issue all the way. I'm having the same problem; When i'm "deploying" users, i always want the users to set their own passwords. Ok, so I then set the auth mode to "RDP Security layer". It seemed to work fine, and it does for that
special purpose.
Just like Daniel, my clients are connecting to our terminal server from several/different "customer-domains" So, they can't logon locally(on their local computer) and change their password, it has to be done THROUGH the terminal server.
But if I turn on RDP Security Layer, users can't use remoteapp through tsgw they only get: "Your Remote Desktop Connection Failed because the remote computer cannot be authenticated" Any ideas?
Also, our terminal servers is round robin based in a farm. So users connect to: tsfarm.domain.com(yes, public a-record which resolves to two internal adresses) This is because, we're using a wilcard *.domain.com as SSL certificate.
But, when i'm using this, our clients sometimes get double auth when they login. I only get the double auth when tsfarm.domain.com resolves to server A, but the session broker wants the user to be on server B.(load balancing)
This does not occur when SSL is enforced, any ideas?

Cannot install Office 2010 on Windows Server 2008 terminal server

Hello
I have a Windows 2008 terminal server which has Office 2007 Professional Plus on it. We want to upgrade it to Office 2010 Professional Plus.
Following steps from Technet, I made sure all users were out of the terminal server, then selected "Install Application on Terminal Server", then ran the setup.exe file for Office 2010.
The splash screen comes up for Office 2010 but then disappears and the install does not progress, although the setup.exe is still running in Task Manager. The "install Application on Terminal Server" window is still open, waiting for me to click
Next, Finish or Cancel and nothing else happens.
I also tried putting the server into install mode from command prompt and rebooting the server and re-attempting but no good.
How can I go about troubleshooting this issue?
Many thanks
Luke Dunster

Hi Luke,
Are you using a volume license version of Office 2010 for Remote Desktop Services/Terminal
Services? I may be wrong but I think that only this version of Office 2010 will work on a Terminal
Server. The Retail Version will just not work in this case.
I had similar problem where I tried to upgrade from Office 2007 to Office 2010 on a Terminal Server (Windows
2008) but wasn't successful with the upgrade/installation.
Also take a look at this post:
http://social.technet.microsoft.com/Forums/windowsserver/en-US/e09ee781-82c2-4399-85f4-1b90ae690ccb/office-2010-licensing-for-windows-2008-rdsterminal-services-pkc-ok?forum=winserverTS
Jale01

Redirect Printer is not working in windows 2008 R2 Server( Server Running as AD and Terminal Service(both role in single server))

Dear Team
i need solution from Microsoft for the issue;
My infrastructure
- Windows Server 2008 R2 (Role - AD and Terminal Service)- Updated
- Client Machine running with windows 7 pro (Updated)
- Client Using RDP Client to connect Windows 2008 Terminal Session
- All are working fine, but Redirect Printing is not working (Through Windows 7 Pro) ... (HP Laser Jet 1020 plus - attached in Client PC)
- it is working fine from Windows XP
- i was done All terminal setting in both end, also try RDP Login with Administrator User, but issue is not resolve;
What Microsoft can say about the issue;
Thanks & Regards,
VIMAL PRAJAPATI | 09824111686

Have you checked the Print Service log in event viewer?
Here's How.
I have the Microsoft XPS driver on my clients, so I use that fact to my advantage below.
Click Start Button/Administrative Tools/Remote Desktop Services/Remote Desktop Services Manager on the RDSH server
Click the Sessions tab. PC’s are listed Under Client Name by their computer name. Take Note of the corresponding
ID. We will use this to locate the Printer information in the Event Log.
In the Event Log open Application and Services Logs/Microsoft/Windows/Print Service/Admin/ and Find the Event ID 823 entry that has the corresponding ID from the sessions tab you previously noted.
This Event Log Entry is created at Logon and you can only get the session ID when they are logged in.
This tells you what client printer was mapped for the client. The name that appears is the name of the Printer that was set on the client when the printer was installed.
See if you see any errors here.
If you see Event Id 823 with the following message “The default printer was changed to Microsoft XPS Document Writer,winspool,Ne00:. See the event user data for context information.” Twice in a row with no other messages in between, and the first occurs
at the time the user logged in, then their printer was not properly redirected.
You see the Microsoft XPS driver mapped for each session prior to Easy Print redirecting the client machine’s Default Printer.
Since your printer is the HP 1020 I would bet the driver on the client does not work with Easyprint. I would try the the HP Universal Print Driver or the driver for a printer that is very close, like the HP 1018.
Thanks,
Jeremy

Cannot find m1212nf multifunction printer driver to install on w/2008 terminal server (64bit).

Cannot find m1212nf multifunction printer driver to install on w/2008 terminal server (64bit). The existing driver wants me to connect the printer using USB. The printer is in another facility I am trying to support.

Hi,
The HP M1212nf used the Host-Based printing language, such printing language is not recommended Citrix or Terminal Services envoirnment and not officially supported.. you may try using the Citrix UPD on the server by installing the basic driver for yor printer on the client:
http://h10025.www1.hp.com/ewfrf/wc/softwareCategory?cc=us&dlc=en&lc=en&product=3965849&task=&
(ii) HP does not recommend installing these host-based LaserJet drivers on the Citrix server; however, the devices may function by using the Citrix UPD on the Citrix server with the HP host-based driver installed on the client. Print drivers for your product may be available within the Windows 7 operating system.
http://support.citrix.com/servlet/KbServlet/download/10498-102-693211/Citrix%20Supported%20HP%20Prin...
Say thanks by clicking the Kudos thumb up in the post.
If my post resolve your problem please mark it as an Accepted Solution

Wyse Thin client not connecting to Windows 2008 R2 server

Configuration
SBS 2011 Server
Windows 2008 R2 server with Remote Desktop Services installed, License Manager installed.
WYSE WT3125SE thin clients with Windows CE 5
I setup the Windows 2008 with Remote Desktop Services and was able to successfully connect the Thin client. Then I installed the License Manger and applied my Open license using User Cals. Was able to login. Next day I get the following
error-"Because of a security error, the client could not connect to the remote computer. Verify that you are logged onto the network and then try connecting again" I still can connect fine from other machines even Windows Home Ed.
I remove license server and still was unable to connect. Built a second Windows 2008 R2 server with RDS on it. Was able to connect without issue. Pointed it to the first RDS server license manager and have still been able to connect with
the Thin Client. The thin client can rdp to the SBS server without issue in admin mode, can connect to RDS2 server but not RDS1 with the license manger. So my issue is with the license and so my question is what is it with the license server
running on that server that is keeping thin client from connecting. I even did a reload of RDS1 and tested connecting throughout the process and it worked up until I applied the license and then it stops. And then if I uninstall the license, rds, remove
from domain still not able to connect. Any help would be appreciated.

We had the same problem with older terminals after cloning a 2008R2 rds server and sysprep it.
The original rds server worked fine but when the old terminals connect to the new 1 they come up with the error : Because
of a security error, the client could not connect to the remote computer. Verify that you are logged onto the network and then try connecting again"
After reading all of the postings about this issue and tried the reactivate solution of the license server,
I was sure that it had something to do with the x509 certificates that are generated the first time you connect to a valid license server.
What I did, I installed a new license server activate it but did not install licenses on it.
I pointed the defective rds server to the newly installed license server and deleted the following registry keys:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\RCM
Certificate
X509 Certificate
X509 Certificate ID
X509 Certificate2
Then reboot.
After the reboot all old terminals can connect fine again. As final step I pointed the rds server to the same license server as the other ones,
reboot and all worked fine.
So conclusion is that when you pont a rds server to a license server that has the new type of licenses on it it will generate the wrong x509 certificates
that are not supported by the older clients, by pointing it first to 1 without any rds calls on it, it generates the older x509 certificates which are compatible with the older rdp clients then the switch to new license server will then not regenerate the
x509 certs so it keeps working.
I hope this helps someone
This issue was driving me crazy so very happy that it is resolved now
Cheers Frits

OS X Leopard and Windows 2008 file server mount_smbfs

Hello
I am unable to use the command mount_smbfs to mount a share on a Windows 2008 file server in OS X 10.5.8 Leopard.
Here is what I am trying to do:
I have a Mac Mini running OS X 10.5.8 that is joined to a Windows 2003 Active Directory domain. I also have a stand alone Windows file server running Windows Server 2008.
I want to mount a share on the Windows 2008 file Server using the command line and not Finder. I do have a reason for wanting to do this which I wont bore you with.
On the Mac Mini, I log in with an Domain account that has permission to access the file shares on the Windows 2008 file server. In Terminal I do the following:
cd /Users/username
mkdir mountpoint
mount_smbfs //windows2008server/fileshare /Users/username/mountpoint
This command should mount the share "fileshare" hosted on server "windows2008server" in the folder "mountpoint" on the Mac Mini.
Here is the problem:
When I execute this command, I get:
Password: so I put in my password
then I get:
mount_smbfs: mount error: /Users/username/mountpoint: Broken pipe
Analysis of the problem:
I tried exactly the same commands to mount a share on a Windows 2003 file server. I am not asked for my password and the share mounts perfectly. I also tried the same command in OS X 10.6 to mount a share on a Windows 2008 file server, again, I was not asked for my password and the share mounted perfectly.
So the problem is only mounting Windows 2008 file shares using mount_smbfs in OS X 10.5.8. I am not sure quite what is going wrong here, as the Mac is joined to the domain, it is granted a Kerberos ticket so should not be asking for my password. Is this a known bug in OS X 10.5? Is there a fix/workaround for it?
Many thanks
Richard.

Not sure what user the mount command defaults to. You may want to specify your user name in the mount command (you can also specify the password). Try using this:
mount_smbfs //username@windows2008server/fileshare /User/username/mountpoint
Of course substituting the Windows 2008 account name you are mounting with for the username.
Cheers,
Dave

BO XI 3.1 SP2 error while installing in Windows 2008 ENT Server 32 Bit

Hi
We have windows 2008 enterprise edition 32 Bit SP2 , While installing BO 3.1 SP2 we are getting the following error.
"Some files could not be created.
Please close all applications, reboot Windows and restart this installation."
1.we do have enough space as well as we are installing it through administrator account.
2.I increase the virtual memory size from 2 GB to 4 GB, still same error.
3.we downloaded the software in two diffrent machines. We tried extracting the "exe" file in two machine but still getting the same error.
4.We dont have any firewall connected and windows firewall is off.
Is there BO 3.1 Sp2 is available for windows 2008 ent server 32-Bit?
Because In the download site there is Windows Server on IA32 32-bit.
is it the correct version?
Please help us to solve this problem
Thanks

We have opened a ticket for this. After subsequent discussion with the forum support person we have installed BO Enterprise 3.1 SP2 fixed pack 2.5 on the server (Windows Server 2008 SP2). On the client side, we have also installed BO Enterprise 3.1 SP2 fixed pack 2.5 and Live Office SP2 fixed pack 2.5.
Once we tried to use the Web Intelligence document based on OLAP Universe in excel through Live Office it gives the following error.
"Failed to get the document information. (LO 26315) A database error occured. The database error text is: Failed to set properties (The component Microsoft® OLE DB Provider for Analysis Services returned server error (Database 'Sales' does not exist.)). (WIS 10901)(6315)".

Unable to login to Report Service on Windows 2008 R2 server

I have reporting services installed on a Windows 2008 R2 server, When I make and RDP connection to the server and go to http://servername/Reports everything works fine. When I try to connect from another client to the web service, it asks for username and
password. it fails 3 times and the shows a blank page.
When I see the Event Viewer in the server (Windows Logs --> Security, I can see an Audit Failure:
Log Name:      Security
Source:        Microsoft-Windows-Security-Auditing
Date:          9/4/2014 11:46:25 AM
Event ID:      4625
Task Category: Logon
Level:         Information
Keywords:      Audit Failure
User:          N/A
Computer:      MI-SWACO-DB.houston.livequest.net
Description:
An account failed to log on.
Subject:
   Security ID:       NULL SID
   Account Name:       -
   Account Domain:       -
   Logon ID:       0x0
Logon Type:           3
Account For Which Logon Failed:
   Security ID:       NULL SID
   Account Name:       Administrator
   Account Domain:       HOUSTONLQ
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:   MI-SWACO3
   Source Network Address:   -
   Source Port:       -
Detailed Authentication Information:
   Logon Process:
   Authentication Package:   NTLM
   Transited Services:   -
   Package Name (NTLM only):   -
   Key Length:       0
This event is generated when a logon request fails. It is generated on the computer where access was attempted.
The Subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe.
The Logon Type field indicates the kind of logon that was requested. The most common types are 2 (interactive) and 3 (network).
The Process Information fields indicate which account and process on the system requested the logon.
The Network Information fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases.
The authentication information fields provide detailed information about this specific logon request.
   - Transited services indicate which intermediate services have participated in this logon request.
   - Package name indicates which sub-protocol was used among the NTLM protocols.
   - Key length indicates the length of the generated session key. This will be 0 if no session key was requested.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
    <Provider Name="Microsoft-Windows-Security-Auditing" Guid="{54849625-5478-4994-A5BA-3E3B0328C30D}" />
    <EventID>4625</EventID>
    <Version>0</Version>
    <Level>0</Level>
    <Task>12544</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8010000000000000</Keywords>
    <TimeCreated SystemTime="2014-09-04T16:46:25.247229500Z" />
    <EventRecordID>8917</EventRecordID>
    <Correlation />
    <Execution ProcessID="504" ThreadID="1344" />
    <Channel>Security</Channel>
    <Computer>MI-SWACO-DB.houston.livequest.net</Computer>
    <Security />
</System>
<EventData>
    <Data Name="SubjectUserSid">S-1-0-0</Data>
    <Data Name="SubjectUserName">-</Data>
    <Data Name="SubjectDomainName">-</Data>
    <Data Name="SubjectLogonId">0x0</Data>
    <Data Name="TargetUserSid">S-1-0-0</Data>
    <Data Name="TargetUserName">Administrator</Data>
    <Data Name="TargetDomainName">HOUSTONLQ</Data>
    <Data Name="Status">0xc000035b</Data>
    <Data Name="FailureReason">%%2304</Data>
    <Data Name="SubStatus">0x0</Data>
    <Data Name="LogonType">3</Data>
    <Data Name="LogonProcessName">
    </Data>
    <Data Name="AuthenticationPackageName">NTLM</Data>
    <Data Name="WorkstationName">MI-SWACO3</Data>
    <Data Name="TransmittedServices">-</Data>
    <Data Name="LmPackageName">-</Data>
    <Data Name="KeyLength">0</Data>
    <Data Name="ProcessId">0x0</Data>
    <Data Name="ProcessName">-</Data>
    <Data Name="IpAddress">-</Data>
    <Data Name="IpPort">-</Data>
</EventData>
</Event>
The firewall is OFF in both client and server.
I saw a similar question and the answer is related to firewall which is not may case.

Hi Mario,
According to your description, when you try to access the Report Manager in another client, a login dialog prompt. After typing a valid username and password 3 times, a blank page displays.
Generally, the issue is always caused by the Report Server is configured to use Kerberos authentication, while the Service Principal Name(SPN) is not configured correctly. To fix this issue, please refer to the following methods:
Register an SPN for the Report Server service under the domain user account.
Change the service account to run under a built-in account such as Network Service.
Remove RSWindowsNegotiate and ensure RSWindowsNTLM is specified in the rsreportserver.config file.
Besides, the issue can also be caused by the Internet Explorer (IE) didn't pass the user's credential to the Report Server automatically or the IE is not Windows Integrated enabled. For more detail steps about how to address this issue, please refer to the
following steps:
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/184c4f6c-b292-4f9a-beca-80b70f4392fe/report-manager-prompts-3-or-4-times-for-usernamepassword-before-letting-users-in?forum=sqlreportingservices
Reference:
Resolving Kerberos Authentication Errors When Connecting to a Report Server
Solving the Reporting Services Login issue in the February CTP of SQL Server 2008
If there are any other questions, please feel free to ask.
Thanks,
Katherine Xiong
Katherine Xiong
TechNet Community Support

Unable to list SFTP Directory on windows 2008 r2 server from internet

Hi experts,
I have configured a SFTP on windows 2008 r2 server. And i am using the Filezilla on client machine to connect to SFTP server.
The connection works properly on internal network but it displays error when i connect from internet.
Error: GnuTLS error -53: Error in the push function.
Response: 550 Data channel timed out.
Error: Failed to retrieve directory listing
This machine is publish with public IP and port22. The connection and authorization process gets complete but stops are Directory Listing.
PLease suggest the troublshooting steps..
Let me know if any more info is rquired.

Hi,
Do you also use the Filezilla to configure SFTP server? Since you use Filezilla on client machine to connect to SFTP server, I would suggest you ask for help from Filezilla forums for better and accurate answer.
https://forum.filezilla-project.org/
Best Regards,
Mandy
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Does WCS run on Windows 2008 R2 server?

Can anybody share his/her experience with running WCS on Windows 2008 R2 server?
Is it possible and did you experience any problems with it? (during installation or during normal usage)
Is it supported by Cisco already?
Our distributor is a little bit vague about that, that's is why I am asking it here.

From WCS 7 release notes :
Operating Systems Requirements
The following operating systems are supported:
•Windows 2003/SP2 and Windows 2003 R2/SP2 32-bit installations with all critical and security Windows updates installed.
Windows 2003/SP2 64-bit installations are not supported. A 32-bit operating system running on a 64-bit capable hardware is supported.
Windows 2003 32-bit installations provide support for up to 64 GB of RAM if Physical Address Extension (PAE) is enabled. See the Windows documentation for instructions on enabling this mode.
•Red Hat Linux Enterprise Server 5.X 32-bit operating system installations.
Red Hat Linux Enterprise Server 5.X 64-bit operating system installations are not supported. A 32-bit operating system running on a 64-bit capable hardware is supported.
•Windows 2003 and Red Hat Linux version support on VMware ESX version 3.0.1 and above with either local storage or SAN over fiber channel.
Individual operating systems running WCS in VMware must follow the specifications for the size of WCS that you intend to use.
No Windows 2008 ! I know lots of people have been crying for it and it should be coming in next releases but no promises as of now :-(
Nicolas

SAPSprint installation on Windows 2008 R2 Server 64-bit

Dear Gurus,
as we change our print server to Windows 2008 R2 Server 64-bit I need to install SAPSprint for SAP printing with connection type 'S' out of a NW7.0 based system on HP-UX.
Till now we used SAPlpd on a 32-bit Windows Server......
1) Do I simply need to install the xSPrint.exe or can this happen only in combination with the whole SAPGui?
2) According to note 66971 for Windows 2008 R2 Server 64-bit only SAPGui 7.20 is supported.
Does this mean that I also have to use SAPSprint release 7.20 or can I use any other release as well.
On our Windows clients we run SAPGui 7.10.
Is there any correlation between the SAPGui running on the clients and the SAPGui / SAPSprint release running on the print server or can I simply install the highest SAPSprint release 7.20 on the print server to be sure that it will work with WK8 R2 64-bit?
I hope I could explain my problem and I am looking forward to your reply.
Thanks a lot in advance!
Günter

Dear Günter.
Your question is spread over some different areas. Let me point out some tracks to follow:
There is only a 32-bit version of SAPSprint but that one works also under 64-bit; please refer to SAP note 894444.
Regarding SAPgui, in general it is recommended to have the last version as it is downwards-compatible with older versions.
But specially, let me highlight that Windows 2008 R2 is not yet listed in the PAM - and hence not yet supported. The technical prerequisites are met (with a special kernel patch) but not all software is released.
In fact, and just to provide you further details it is not possible to expect the 710 products released for Windows Server 2008 R2 before around four weeks; 700 products will be released even after 710.
See SAP note 1383873 ("Windows Server 2008 R2 Support").
You can be always up to date with the latest Windows news at:
--> Support of Microsoft Windows Server 2008 R2
Cheers!

Windows 2008 Terminal Server, Acrobat 7, 9

Similar Messages

Maybe you are looking for