Photoshop y Terminal Server

Hola a todos:
Tengo un problema con Photoshop CS2.
Lo tengo instalado en el servidor (Windows 2003 server) y ahí me funciona sin ningún problema.
El problema surge cuando cuando lo quiero ejecutar a través de Terminal Server, que me da un error de que tiene problemas con una librería que necesita y que reinstale el programa para intentar solucionarlo. Pero tampoco dice qué librería es.
¿Alguien sabe algo de este tema? ¿Sabéis si hay alguna restricción para ejecutar Photoshop CS2 por Terminal Server?
Gracias

yo tengo u problema similar con el cs3... cuando trabajo premiere se ejecuta tambien el photoshop server y se cuelga el premiere... alguien tiene alguna idea? es la primera vez que me pasa...

Similar Messages

Problem with Photoshop hangs/freezing for users on a terminal server

Dear Forum!
I'm having some trouble with Photoshop freezing over a period of ~20 minutes when you (1.) user the eraser with special brushes and (2.) copy and paste material from a PDF to Photoshop. As you might notice by the size of this post i'm getting quite depserate over here and need some help.
A Little background information...
Photoshop CS6 is installed on a terminal server with ~25 Active users where 3 of them are using Photoshop.
The operating system on the server is Windows Server 2012 R2.
There are no additional add-ons just a plain installation of Photoshop in that matter.
The server uses 40-60% of the memory most of the time (mostly a bit less, some times a bit more but never 100%) and 40% of the CPU.
There's enough space free on the disc.
The problem in detail...
There are two occasions where the freezing has occured most of the time. After it hangs for the first time, it will happen everytime you do any of the operations over a period of ~20 minutes and it's Mutual for all users. When it freezes, the whole terminal session freezes but the program i still responding (it's not getting set to "not responding") when viewed from Another user through the task manager. Ending the process as an administrator sometimes work, although from the moment i end he proces it takes about 10-60 seconds Before the program actually Closes and the user gets back Control. The easiest thing to do most of the time is if an administrator forces them to log out.
1. The first occasion is when you use the eraser with a brush that's not standard but manually added. The names of the brush packages used are:
Extacy__Elemental
KKC_Fractal
Kornkid's_Grunge_Set
and the problem is with all brushes inside those packages. The way i evoke the problem is the following:
     1. Start Photoshop
     2. Create new
     3. Fill the background with any color
     4. Select the eraser tool
     5. Change the brush to one of the ones mentioned above
     6. Program freezes
2. The second scenario when the problem occurs is when the users copy something from a PDF to Photoshop. The way i evoke this is:
     1. Open a PDF
     2. Select area and copy it
     3. Open Photoshop
     4. Create new
     5. Paste into Photoshop
     6. Program freezes
Solutions we have tried so far...
I've been working on this for several round now and i'm not entirely sure on what exactly i have done. I will try and do the following solutions once more but i'm pretty sure that i have tried most of them.
Update graphic card drivers.
Resetting all Tools:
     1. Select options for a tool
     2. choose "Reset all Tools"
Resetting presets:
     1. Hold ctrl + shift + alt while Photoshop is starting
     2. select "yes"
Tested if it matters if i have a pen connected or not, which it doesn't.
Removed the special brushes (but it still freezes when copy/paste from PDF)
Removed "save in background" and "automatically save recovery information" options
Updated to latest version.
Turned off OpenGL
Solutions i haven't, but will try...
Reinstall Photoshop
Change font preview size
     1. Go to "type"
     2. select "Font prview size"
     3. select "none"
Delete system font cache
Close all Adobe applications including the Creative Cloud desktop app (if installed).
Navigate to \Windows\ServiceProfiles\LocalService\Appdata\Local
Delete the *FNTCACHE*.DAT or *FontCache*.dat files.
NOTE: The asterisk (*) indicates various numbers, letters, or words, such as FontCache-S-1-5-21.dat or COFFfntCache.dat.
Delete Photoshop font cache
Exit Photoshop and the Creative Cloud desktop app (if installed).
Navigate to the appropriate folder
Photoshop CS6 and earlier.
Windows XP: \Documents and Settings\Local Settings\Application Data\Adobe
Windows 7: \Users\[user name]\AppData\Local\Adobe
Photoshop CC and CC 2014
Windows 7 and 8: \Users\[user name]\AppData\Roaming\Adobe\Adobe Photoshop CC or CC 2014
     3. Delete the TypeSupport folder (Photoshop CS6 and earlier) or the CT Font Cache folder (Photoshop CC and CC 2014), and empty the trash.
Some links i have been using...
http://blogs.adobe.com/crawlspace/2012/07/photoshop-basic-troubleshooting-steps-to-fix-mos t-issues.html
http://helpx.adobe.com/photoshop/kb/photoshop-cs6-gpu-faq.html#troubleshoot
http://helpx.adobe.com/photoshop/kb/troubleshoot-fonts-photoshop-cs5.html

Hi Mylenium!
Thanks for your reply but since the users work on the terminal server via remote dektop the only data sent through the network is a "Picture" of what is happening on the server. All the operations are handled on and by the server and nothing is executed on the users local machine. Also all files are stored on the server therefore the load on the network is minimum.
We are not the first in the World to run this setup and i know that this is possible to do since i've read about others running PS like this.
Kind Regards,
J. Alm

Install Adobe Photoshop Elements on Terminal Server

Hi, if i want to install Adobe Photoshop Elements on a Terminal Server so 5 people can use it at the same time, what kind of licence do i need?
Thanks

I dont think this workflow is suppoted.
You will have to install PSE on all the 5 machines and buy a Volume Licensing serial number for using same serial number on all the machines.
Regards,
Ankush

Photoshop Elements on Terminal Server

Hello
We try to install PSE7 on a 2008 Terminal Server. Is PSE able to work on a Terminal Server?
If yes, how can we install it properly?
Thanks for your response.

Never got a response from your side..I hope you figured out the answer or relevance of question all by yourself...
Regards,
Ankush

Phtoshop with Terminal Server

Hello.
We are using different products:
Photoshop
6.01
Photoshop CS
2.0
Photoshop CS
4.0
Photoshop   Elements
1.0
Photoshop   Elements
2.0
First question: Is it possible to run all of them with a terminal server? With terminal server I mean every user starts it's own session on the server when starting the programm. It doesn't matter on which kind of server (Windows, Citrix). We just want to know, if it is possible.
If we change our running systems to Windows 7 we have to change our products, too.
Adobe   Photoshop CS5
Adobe   Photoshop CS5
Adobe   Photoshop CS5
Adobe   Photoshop Elements 9
Adobe   Photoshop Elements 9
Can these programms be used with a terminal server?
Thanks a lot for the answer and the heldp.
David

I don't have Elements 1.0, so I can't answer for that version, though as I recall it was pretty closely related to Photoshop 6.0 or 7.0, so it should work.
For all other versions of Photoshop, I have brought them up over RDP and tested them, and they do run.
Note that OpenGL cannot be enabled over an RDP connection for Photoshop CS4 and CS5.x (not even with W7 SP1 and Server 2008 R2), so people expecting to use the several good features ONLY available when OpenGL is enabled may miss them. As with the other versions, the interactivity is generally diminished by remoting the relatively high bandwidth graphics operations across a link, because no matter how fast a link is it's nowhere near as direct as the PCIe buss to a local graphics card.
Generally speaking, Photoshop can be both extremely compute-intensive and put a lot of data out to the UI, so it's not a very good fit to running via Terminal Services. I certainly would prefer running it locally.
I do hope you have a good, responsive LAN between your terminal server and your clients, and a very healthy server.
-Noel

DS XI 3.0 on Terminal Server

Hi All,
We setup DS XI 3.0 on a Windows 2003 Terminal Server. 6 developers are now using the designer tool. For each of them a MySQL Database has been setup and local repositories were created.
One problem occurs: when one developer opens the Designer he always sees the repository information that was last used from ANY of them. Is there any way to solve this issue?
Thanks and Kind Regards,
Ingo Taraske

Hi Ingo,
As discussed in this forum recently, Designer is not supported for use by multiple concurrent users via Terminal Services -- the application was never designed to support this. The application was designed to support Citrix, though. Please install the Designer tool on individual Windows installations for each of your users.
Thanks,
~Scott

How do I connect to a terminal server with my mac book pro

How do I connect to a terminal server with my mac book pro

Use the Remote Desktop icon on the tray and make sure to use the Fully Qualified Domain Name (FQDN) on the 'name of server' field. If that does not work then use the IP address to connect.

Audio lag in video while on Terminal Server

Hi Everyone,
We are having an issue with audio being out of sync when viewing flash video on a terminal server. The terminal server is running Windows 2008r2. The audio seems to lag behind the video by about 1 sec. We are planning to rollout training videos
and about half our users are on Terminal servers.
Here are some of the things we tried:
http://blogs.msdn.com/b/rds/archive/2009/05/11/what-s-new-in-remote-audio-for-windows-7.aspx?PageIndex=2#comments
On the server policy:
Computer Configuration ? Administratrative Templates ? Windows Components ? Remote Desktop Dession Host ? Device and Resource Redirection ? Limit Audio Playback Quality (Enabled, Audio Quality: Medium)
In the RDP file add a line that says:
audioqualitymode:i:1
thanks...
Mark

Hi Mark,
Thank you for posting in Windows Server Forum.
Can you please check which version of RDP client installed on your system? For better feature suggest you to install RDP 8.1.
Remote Desktop Protocol 8.1 Update for Windows 7 SP1 released to web
http://blogs.msdn.com/b/rds/archive/2013/11/12/remote-desktop-protocol-8-1-update-for-windows-7-sp1-released-to-web.aspx
Meanwhile go through beneath article for information.
Multimedia Redirection Improvements in Windows 7 and WS2008 R2 – Part 1
http://blogs.msdn.com/b/rds/archive/2009/07/24/multimedia-redirection-improvements-in-windows-7-and-ws2008-r2-part-1.aspx
Hope it helps!
Thanks.
Dharmesh Solanki

On Windows 2012 Terminal Server Outlook fails to connect to Exchange 2013

I have a new install of Windows 2012.  I have two physical servers. One is a W2012 std Domain Controller ("DC"). The Second is configured as W2012 HyperV  ("HV"). Under HV I have
two VMs. One VM is W2012/Exchange 2013 ("ExchVM) and the other is W2012/Terminal Server ("VMTS"). All systems are behind a firewall appliance. Exchange is working via Outlook and OWA internally and externally. The self
created SSL must be installed manually on external machines since it comes up as an untrusted certificate. Once installed remote outlook works and OWA works. I have configured the terminal server and I am able
to login remotely as various users under my "TS group". The problem is when ever I attempt to open Outlook for the 1st time, it fails to connect to the exchange server.   (Open Outlook 2013, click next
on the splash screen, "Yes" Add an Email Account splash screen, click next, Auto Account screen populates NAME and Email Address correctly, click next, Searching for mail server settings..., check on establishing network connection, check on searching
for alias@ domain, then fails the logging on to the mail server) The error reads: "Outlook cannot log on. Verify you are connected to the network and are using the proper server and mailbox name. The
connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action."   I am connected in RDS from offsite, and from the RD session I can access shared folders on ExchVM and DC. I have
tried have verified the server Exchange server name is correct via "Get=ClientAccessServer" command. I have also tried to use the guid via "Get-Mailbox
ALIAS | fl name, exchangeguid. Keep in mind all desktop users on the network are connecting to Outlook without issue.
I would appreciate any thoughts on solving this issue.

Hi,
According to your workaround, it seems that the Outlook Anywhere configuration in Outlook client is not correct when using the Autodiscover service.
Once you connected to Exchange server by manually settings, please run Test E-mail AutoConfiguration tool in external Outlook client to check the autodiscover service:
open Outlook - press CTRL key - right click on the Outlook icon from right bottom corner taskbar - Test Email AutoConfiguration. Put your email address - uncheck use guessmart and secure guessmart authentication - click Test to check your Autodiscover service.
Please check the Log tab and confirm whether the Autodiscover service is connected successfully. Also confirm if the connection issue happens to all external users when they open Outlook for the 1st time. In Exchange server, please make sure
autodiscover.domain.com has been included in your Exchange certificate which is assigned with IIS service.
Regards,
Winnie Liang
TechNet Community Support

Unable to Copy File From Terminal Server to Client Share

Hi
For years client have been able to copy files from our Windows 2003 Terminal Server to their local workstation using:
copy myfile \\tsclient\mydrive\myfolder
However we upgraded to Windows 2012 Server R2 and now Windows 7 Pro clients cannot copy files. The copy function creates the file name in their local folder but no content is sent after maybe 20 minutes or so the copy function times out and they get an
error message saying that the application was unable to write to the file. I have tried this function with my Windows 8.1 workstation and the file copies properly and it works fine for older Windows XP clients. Does anyone know why Windows 7 clients
are experiencing this issue.
Thanks
Simon

Hi Simon,
Initially please use latest RDP version 8.1 for windows 7 and check result.
What’s the file size which you are copying?
Does this happens for all users and on all computers?
You can try below method might resolve your case.
1. Login to remote computer using Remote Desktop (RDP).
2. Open Task Manager in the remote machine
3. Click the "Process" tab
4. Locate a program called "rdpclip.exe"
5. Right click and select "End process" to kill this program
6. Click on "File" menu in the task manager and select "New Task (Run)"
7. Type rdpclip.exe and press the button to start the process.
By killing existing instance of the rdpclip.exe and restarting the program, you can get your copy paste work again in your remote desktop.
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]

Copy File from Terminal Server to Workstation Failure

Hi
For years client have been able to copy files from our Windows 2003 Terminal Server to their local workstation using:
copy myfile \\tsclient\mydrive\myfolder
However we upgraded to Windows 2012 Server R2 and now Windows 7 Pro clients cannot copy files. The copy function creates the file name in their local folder but no content is sent after maybe 20 minutes or so the copy function times out and they get
an error message saying that the application was unable to write to the file. I have tried this function with my Windows 8.1 workstation and the file copies properly and it works fine for older Windows XP clients. Does anyone know why Windows 7
clients are experiencing this issue.
Thanks
Simon

Hi Simon,
The copy command should also work on the Windows 7 clients. Please provide the detailed error message when run the command on the Windows 7 clients.
You could also use robocopy command to achieve this.
Robocopy
https://technet.microsoft.com/en-us/library/cc733145.aspx?f=255&MSPPError=-2147217396
Best Regards,
Mandy
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 Subscriber Support, contact [email protected]

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

VPN Client and Terminal Server

We have several clients that allow us to vpn into their systems and it has come to the point that we are getting software incompatabilities. What I am trying to do is set up "compatable" connections on a Terminal server box and let our people access this from their workstations. The problem is when the acuall connection thru the vpn client is made they loose connection to the terminal server. I have tried putting in 2 nic's into the terminal server and am able to allocate one for the terminal server but can not find a way to allocate the other to the VPN CLient. Is this possable or is there another way to accomplish this?
Thanks

Close,
What I have is one machine with 2 nic's
NIC #1 = Terminal Server Access (local lan only) Locked in via registry settings to use ONLY this NIC
NIC #2 = I would like to "LOCK" the Client software to use ONLY this nic (has a dynamic IP for local lan and access to the Inet via a router.
Problem: When you connect to the T-Server all is fine UNTIL you start up the client software to access our clients systems via the web connection to the T-Server on the local side stops and gives the appearance of a frozen screen.
manualy disconnect person from the T-Server and kill the cisco client software then you can re-connect to the T-Server (and it all starts over again)
The Cisco software acualy makes the connection to our clients system but we can not tell because it want BOTH the NIC's for itself and stops access via NIC#1 to the T-Server.

Can't install LabVIEW Run-Time Engine 6.1 on Windows Terminal Server

With my system admin, we tried to install the LabVIEW Run-Time Engine 6.1 on our Windows Terminal Server NT4. And we get an error all the time:
-install using the plugin
-install using LVRTE.exe
-install after rebooting the server
But I remember that we could install the Run-Time Engine 6.0 on another Windows Terminal Server NT4.
Is there any compatibility issues with the new Run-Time Engine 6.1 ??
Thanks for your help
Cyrille

Cyrille,
What is the error that you get when trying to install the run-time engine?
Are you installing it from the LabVIEW CD, or did you download it from the web site?
To further troubleshoot this problem, it would be best if you send us an email to [email protected] and send the above information.
Also, try running the installer from the command prompt window, and use the following syntax:
setup.exe/l*v
This will save the error log to the file you specify. Send us also this file to help us troubleshoot.
Thanks
Zvezdana S.
National Instruments

This copy of Microsoft Office 2013 cannot be used on a computer running Terminal Services" error message when you try to open the Click-to-Run version of an Office 2013 program or suite on a terminal server

Hi All,
I have Citrix VDI (Virtual Desktop Infrastructure) Implemented
in my company and installed few Applications on App Server lets say.... MS Office 2013, filzialla, putty, etc...
I assigned these apps to the users through CITRIX STUDIO, when I try to use these apps. on VDI everything is working fine only when i tried to open Word, Excel or Powerpoing, outlook it throws error as
""This copy of Microsoft Office 2013 cannot be used on a computer running Terminal Services" error message when you try to open the Click-to-Run version of an Office 2013 program or suite on
a terminal server"" and apps gets closed.
Please help me on this ASAP.
Thanks & Regards,
Sachin Shinde

Hi,
As mentioned in ths article below, run for Office 365 products on to a Remote Desktop Session Host server is not supported. You can install Office products for Office 365 to a virtual desktop, but the virtual desktop must be assigned to a single user.
http://technet.microsoft.com/en-us/library/jj219423(v=office.15).aspx
Regards,
Melon Chen
TechNet Community Support

Photoshop y Terminal Server

Similar Messages

Maybe you are looking for