Terminal Server Session Management: why do we need a rdp session to take control of a terminal session?

Hi all,
As title, I have this question: why do we need a rdp session to take remote control of a terminal server session?
I copied tsadmin and related file to a windows 8.1 pc and I'm able to see for every terminal server the list of users logged in, but the option "take control" is greyed out... why? is not possible to avoid this block?
Thanks in advance
Davide

Hello, Davide_ita.
Also tried to use RDSM to "Remote Control" user's sessions, but in this thread
Remote Control
with Remote Desktop Services Manager - error Access is denied (Windows Server 2012 R2)
I get the recommendation to use RDP or Remote Assistance.
The quote of
TP []:
Hi,
You cannot remote control a session on a 2012 R2 RDSH server using Remote Desktop Services Manager. You need to use the RDP 8.1 mstsc.exe or the RDS gui in Server Manager on 2012 R2. The command you would use with the RDP 8.1 client would be
this:
mstsc /shadow:<sessionid> /control
-TP

Similar Messages

Outlook 2007 on Terminal Server cannot manage Public Folder Favorites after Migration to Exchange 2013

Hi,
we are running a Server 2008 R2 as a Terminal Server with Outlook 2007 SP3 (incl Nov 2012 Update 12.0.6665.5000) which is known as fully supported with Exchange 2013.
With Exchange Server 2007 we did not have any issues. But after having successfully migrated to Exchange 2013 we cannot manage our public folders favorites from these clients anymore.
As we are running Outlook 2007 on a WTS we can not use Exchange Cache Mode and so we can also not download Public-Folders-Favorites as an option. Whenever we try to delete existing favorites or when we try to delete public folders with content or subfolders
there will be an error msg that says that it cannot be deleted and that there may be no sufficient permissions. But this IS NOT the issue NOR the solution as I have full admin rights and am owner of the public folders.
On single fat clients with Outlook 2007 with Exchange Cache Mode enabled we can manage the favorites and the public folders without problem.
We need to be able to manage the favorites of all users (circa 50-60 users) from the WTS with Outlookm 2007. I have no more ideas right now. Does anyone know how to get this settled?
Thanks, Paula

Hi,
Based on the description, users could access public folders successfully, but when they tried to manage public folder favorites or wanted to remove specified folders, they got error message of no sufficient permissions.
Is it right?
You mentioned on single fat clients with Outlook 2007 with Exchange Cache Mode enabled, user can operate normally. Is this a WTS with Outlook 2007 installed?
If possible, please switch this Outlook client from cached mode to online mode to check result.
Best regards,
Belinda Ma
TechNet Community Support

Central Output Server View Manager on Windows 7, need patch for jfPreview.exe

Where can I obtain the latest version of JfPreView.exe?
According to the following webpage:
http://helpx.adobe.com/legacy/kb/central-central-pro-output-server-1.html
Adobe Central and Central Pro Output Server 5.7, Windows support extended to Windows 7 (32/64 bit) and Windows Server 2008 R2 (64 bit)
Issue 2 on this page is the problem that I am having:
Issue 2
View manager is a client application for Central Pro. When it is installed on Windows 7 (32/64 bit) and Windows Server 2008 (64 bit), it doesn't work properly.
For Windows 7 and Windows Server 2008R2, IPv6 is installed and enabled by default. On a machine running the Central Preview Agent with IPv4 protocol, the Preview Agent fails to transfer the files. The Preview Agent also reports the following error in the jfserver.log.
“Fails. Exception: [1005] Connect to <host> failed: 10060”
Solution
A patch for JfPreView.exe.exe is available from Adobe enterprise support to address this issue.
I need this patch.
Thank you

I have loaded KB2937636 to the server2012 wsus/sup but that still did not fix the communication issue. I have since removed the KB2937636 from the 2012 server, because when the KB2937636 is installed on the sup server once the 7.6.7600.256 computers
communicate with the server the WUA 7.6.7600.320 gets installed on the clients and then they stop communicating. Very Frustrating!
Please any help would be greatly appreciated.
Thanks
~ZbWinMan
I have attached my WindowsUpdate.log file. When I used CMTrace.exe you can clearly see that the computer talks fine at the beginning, then I installed WUA 7.6.7600.320 and All Communication breaks, then I uninstall to get back to 7.6.7600.256 and communication
works again.
If I uninstall 7.6.7600.320 then the computer communicates back to the SUP server.
so you're using SSL? (port 8531)
weird things might happen when in SSL if hastily configured, causing this weird error, like this for example:
http://social.technet.microsoft.com/Forums/en-US/5d6ae350-9714-471f-aa67-375e657caa11/windows-update-cant-connect-to-wsus-server-which-happens-to-be-itself-after-switch-to-ssl?forum=winserverwsus
Don
(Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

Windows terminal server 2003 cluster

We have a FOG with three Solaris 10 x86 servers, SRSS 4.2, SRWC 2.3 with the latest SRSS 4.2 patches. All Sunrays have the latest firmware.
Kiosk settings points to a windows 2003 terminal server cluster. The two nodes in the windows cluster have latest SRWC 2.0.
The cluster entitles, two terminal servers and a session manager server, we use roaming profiles.
When pointing kiosk settings to the cluster FQDN the sunray sessions are routed to just one server in the windows cluster. But if we RDP to Cluster's FQDN from a regular desktop the windows cluster load balances properly.
I do need help understanding how SRSS handles sessions? specifically if nodes are behind a cluster with session manager. Could it be that the session manager it's incompatible with SRSS in kiosk mode since it tries to route sessions at the mean time SRSS is doing the same task?
Thanks,
RE
Edited by: estrar on Dec 5, 2010 5:43 PM

Hi Estrar,
Short answer: 2003 Session Directory does not do load balancing.
Long answer (to the above and your other questions):
The Sun Ray Server doesn't do anything with regards to load balancing the windows sessions. To the Sun Ray Server, or more appropriately the windows connector, it's just making the connection you tell it to.
With regards to the windows client "working", am I correct in guessing that you ran subsequent instances of MS-RDC to "prove" that it worked?
Most likely what happened there is that the PC, thus MS-RDC, received different IP addresses back from DNS for the FQDN with each launch. This is basically round robin, not load balancing. But I'd have to understand how you've done the FQDN of the cluster in DNS.
The most common initial reaction is that the DNS server is setup incorrectly (I'll plead guilty that I've had the same reaction). It is true that some DNS servers can be configured will return the same IP on the first dns query. This is called a cyclic ordering and results in the IP address of the resolved name every client to be identical. For example, if a DNS server is set for cyclic ordering, every first request for the IP of server A for xyz.com will be the same on all clients. The second query from the same client should result in server B being resolved, if not, then you do have a DNS problem.. However, in the case of Sun Ray Server, the "second query from the same client" would be the second session coming up, since, as far as the DNS server is concerned, all the Sun Ray session are coming from the same client. Therefore, even with cyclic ordering, round robin should work even better in a Sun Ray environment then a "fat" client environment. You can check the documentation for specific DNS servers on how to set a random order for round robin (which should be the default), but chasing down cyclic ordering of RR entries as a cause to this "issue" is basically a red herring in a Sun Ray environment.
More than likely the same IP being returned everytime is a side effect of the name service caching daemon (nscd). The job of nscd is to speed up name resolution. However, ncsd will break any round robin scheme as it caches the first server returned by the first query from the caller (i.e. the host doing the name lookup, aka the Sun Ray server) and all applications on the caller will use that address for the lifetime of the cache. The default lifetime of the nscd cache is 3600 seconds (an hour). To disable the name service caching daemon, run the following command on every Sun Ray server in the host group (aka FOG): svcadm disable system/name-service-cache
An über smart colleague mentioned the possibility of another problem that could exist even if nscd is disabled and the hosts are on the same subnet as the caller . This has to do with default behavior of the Solaris resolver library putting servers that reside on the same subnet as the caller at the top of the sort order. You can read the notes in the man page for "gethostbyname" and also the man page for nss(4) for more information, but both reference how this behavior can break round robin. The fix is to edit /etc/default/nss and uncomment (or add) the statement SORT_ADDRS=FALSE
While those two things will allow a Solaris based Sun Ray server (or any Solaris client) to properly recognize round robin entries, it still holds true that 2003 Session Directory does not do load balancing. The only role of session directory is to ensure that you don't get routed to a different terminal server in case you have an existing session on another server. Round Robin + Session Directory may be all you need, but bear in mind that it is not "load balancing". Users could still connect directly to one of the IP addresses vs the round robin DNS name and that would defeat the round robin scheme in place.
Load balancing is a separate component in 2003, either using an external device like F5's BigIP or using Windows Network Load Balancing (NLB) service.
The type of load balancing solution that can be used depends on what is meant when you use the term "cluster". If the cluster is a real implementation of Windows 2003 Clustering (i.e.the type of cluster you'd use for SQL, Exchange, etc) then you can't use NLB and would have to use an external load balancer. Sun Ray Windows Connector supports either IP based or token based load balancers, though we don't certify any third party products in this regard.
"Cluster confusion" occurs because Session Directory itself is supported by Windows 2003 Clustering in order to provide a highly available directory service. Easy to see how this would be desirable with a large number of terminal servers. However, NLB does not work, nor is it supported on Windows 2003 Cluster.
To further the confusion, when NLB is enabled on the NIC that is handling RDP traffic, one of the configuration tabs is "Cluster Parameters". But it is important to realize that this has nothing to do with Windows 2003 Clustering and is in fact incompatible with it. NLB makes use of independent servers (i.e. not clustered), which the primary requirement of those servers is that they are on the same subnet.
Finally, it is easy to get confused between 2003 and 2008 session directory when it comes to load balancing, but they are very different. 2008 "session directory" does do load balancing. In fact, to underscore this distinction/feature, Microsoft has renamed Session Directory to TS Session Broker. (See http://technet.microsoft.com/en-us/library/cc772418%28WS.10%29.aspx)
To summarize, with Windows 2003 you have two choices when it comes to load balancing and session directory.
1) Have a HA implementation of Session Directory and use an external load balancer
2) Have non-HA implementation of session directory and use NLB to do load balancing.
Good how to article on setting NLB on 2003 with terminal services here:
http://www.brianmadden.com/blogs/brianmadden/archive/2004/11/29/how-to-configure-windows-network-load-balancing-for-pure-terminal-server-environments.aspx

Print Dialog Box for Addon is not showing in Terminal Server

Dear All,
I have created a addon for Automatic Sales Invoice printing that prints the crystal report directly to the printer bu opening a
print dialog box for printer selection through SDK code.
The Same addon works fine on the server with print dialog box being showing through SDK code.
But while running on Terminal Server , print dialog box is not showing any printer though printers are redirected to that
terminal server.I am not getting whether the problem is in my addon or in the terminal server printer settings.
Please suggest as i need to know the reason urgently.
Thanks
Amit

Hello Edward,
Thanks for your reply .
But the problem is that while running on normal server the print dialog box appear with the printer name in my addon for printer selection .
But while using terminal server , the print dialog box is not getting any printer in the dialog box .That's the major concern for me
is their any way to check that why the printers are not showing in print dialog box.
Thanks ,
Amit

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).

Syncing iPhone on microsoft terminal server

Our corporate IT installed iTunes on our terminal server in order to be able to sync our iPhones with Microsoft Outlook on the terminal server. I can see in the device manager on the server that the iPhone is detected and forwarded to the terminal session as a Apple mobile device, but when I start iTunes on the terminal server, the iPhone is not detected by the iTunes software. What else do I have to do to be able to sync my iPhone in the terminal server session with Microsoft Outlook installed there?

We have the same problem and we still looking for a solution.
Did you solve your problem yet?
Tjnak you for a promt answer

Users can only connect to RD farm website and cannot remote into terminal server , when connected via VPN

Hello,
I have a RD farm using 3 Win 2012 servers (1 broker and 2 session host), for internal use only, have not
configured gateway for internet access.
Users are able to connect to RD farm website and remote into terminal server, within office
but can only connect to RD farm website and cannot remote into terminal server , when connected via VPN
Its takes long time at securing connection and fails.
Thanks

Hi,
Thank you for your posting in Windows Server Forum.
First of all I would suggest you to configure RD gateway role on your server and pass all the connection through it because it’s a best practice to use RD Gateway in RDS Farm.
Apart from this, if you are not using RD Gateway then you must check that you have successfully forwarded port 3389 for RDS to access via VPN. Also check that you have made configuration under IIS Manager to enable Forms Authentication. Please check
this link.
In addition, please refer beneath article for additional details.
1. How to Access Windows Remote Desktop Over the Internet
2. Remote Desktop Services in Windows 2008 R2 – Part 3 – RD Web Access & RemoteApp
(For reference)
Hope it helps!
Thanks,
Dharmesh

Problem with Adobe Pro and Reader on terminal server

Hi,
We have have a Terminal Server environment with Adobe Pro and Reader. We have security for Adobe Pro, so only certain user has access to Adobe Pro and all users has access to Adobe Reader.
Some users receive many email with pdf's attachments in Outlook and need to print these attachments. They use the Outlook function to print email and attachment automatically. The users who has access to Adobe Pro can print attachment automatically with no problem.
The problem is user who only have access to Adobe Reader. The user can't print attachment automatically with the email, only the email is printed. But, they can open attachment and print with Adobe Reader. But, it's impossible to open each attachment because there are so many.
Thanks for your help.
Jonathan

Hi,
So if I understand correctly,
1. You have installed Acrobat Pro & Reader on a Terminal server.
2. You have created a security group in your Active Directory Users & Computers for users having access to Acrobat
3. You have set permissions on C:\Program Files\Adobe\Acrobat 11.0\Acrobat\Acrobat.exe and C:\Program Files\Adobe\Acrobat 11.0\Acrobat\Acrotray.exe on the terminal server and provided access only to the security group created above.
4. Users are accessing the Terminal server through RDWeb or connecting remotely through MSTSC (RDP) or using a .RDP file
5. Users get emails with PDF attachments and print the mail directly without opening the PDF in Reader.
Users check the box to print the attachments with the mail (see snapshot below):
Some questions:
1. What is the OS and platform (x86 or x64) of the terminal server?
2. What are the versions of Acrobat & Reader on the terminal server?
Thanks,
Vinod

Network printer or local printer with terminal server

Hello
We have a technical issue I believe on invoices we want Business One to automatically generate a printout document but nothing happens although settings are correct
The only thing I do not handle very well is we have busines one running on terminal server ad the printers are local
Can someone advise if automatic printout on local printers is possible with a terminal server ?
thank you in advance

Sap Business One uses the windows printing architecture to print, so.. as long as you can print via windows on the terminal server, SB1 should be able to print it.
One thing to remember is, if you are using RDP, make sure you are using the latest RDP Client, I believe it's version 6.5 at the moment, but a check on windows update should confirm that.
If you want to print locally, you'll need the following to be true:
1. Printer redirection box in the RDP Settings is ticked.
2. The Policy on the terminal server, or terminal server gateway allows you to connect printers via RDP
3. The drivers for your particular printer must be installed on the terminal server (One for your IT Dept).
If all those are met, you should then see, when you go to print, something like <Printer> on <workstaiton>, where printer is the name of your local printer, and the workstation is your local workstation ID.
With a bit of luck, you can then print.
T.

My membership is activated, why I still need to provide a serial number??

My membership is activated, why I still need to provide a serial number??

A chat session where an agent may remotely look inside your computer may help
Creative Cloud chat support (all Creative Cloud customer service issues)
http://helpx.adobe.com/x-productkb/global/service-ccm.html
Cancel http://helpx.adobe.com/x-productkb/policy-pricing/return-cancel-or-change-order.html

App-V 5.0 client on terminal server: specific config (f.e. location files)?

Hi,
We installed App-v 5.0 SP2 client on a terminal server. I now wonder if we should have set specific install parameters on a terminal server.
We used: SETUP.EXE /q /ACCEPTEULA /CEIPOPTIN=0 /MIGRATIONMODE=1/ENABLEPACKAGESCRIPTS=1 /S1GLOBALREFRESHENABLED=1 /S1GLOBALREFRESHONLOGON=1 /S1USERREFRESHENABLED=1 /S1USERREFRESHONLOGON=1
Pls advise.
J.
Jan Hoedt

about Shared Content Store
the command line parameters appear to be right, but you may want to have additional/other settings. However this could lead to a 'general RDS+App-V Design' conversation. Detailes then depend on your infrastructure (RDS with/without Citrix, User Profile Management,
AppData redirection and a bunch of other stuff. Again: using the above settings should lead to a working App-V client
Falko
Twitter
@kirk_tn   |   Blog
kirxblog   |   Web
kirx.org   |   Fireside
appvbook.com

How does Session Manager work?

Is anyone else using Session Manager? It is a relatively new tool. I think it came out with TestStand 2.0. It is used to manage instrument handles. At first I thought it would allow us to share handles between Labview and CVI (the documentation hints at this) but after reading the fine print I found that it cannot share handles that run in different processes (i.e. Labview and CVI). It is still useful because it keeps a handle open so that a new handle does not need to be opened everytime TestStand calls a Labview or CVI module. Unfortunately, the only documentation for Session Manager is a help file. There is no reference to it in the TestStand documentation, although there are a couple of examples in the TestStand\Examples directory. I
find that I need to experiment with Session Manager to figure out how it behaves. In particular, I'm trying to figure out how it works with a mix of Labview and CVI modules being called from TestStand. Does anyone know of any app notes or other documentation explaining the proper use of Session Manager?

Mark,
Unfotunately the only help available is the help file of the Session Manager and the TS examples.
You mentioned that Session Manager cannot share handles between processes. In fact, Session Manager is capable of sharing handles between processes, it is the C DLL drivers that are not capable of sharing their handles between processes. There are some ActiveX instrument drivers out there that are capable of sharing their ActiveX session handles between processes, and more ActiveX instrument drivers are due for release. With these drivers, the Session Manager will be able to manage the instrument handles between different processes.
Because of the limitation of C style DLL drivers, you cannot create a instrument handle in a VI called by TS and use the handle in a DLL called by TestStand. The VI is executed in a LabVIEW process while the DLL is called in the Sequence Editor or you operator interface process. There are 2 solutions to overcome this limitation. Both are based in running the VI and DLL in the same process:
1) You can have your operator interface written in LabVIEW. When you build you operator interface into an executable, you can configure the LV adapter in TestStand to use the LV opeator interface to run the VIs that your sequence calls (see NIDZ document "Overview of Distributing TestStand when your Sequences use the LabVIEW Standard Prototype Adapter"). In this case both the DLLs and VIs called by your sequence will be executed in the same process and can share C DLL instrument handles.
2) You can build your VIs into DLLs using LV 6.0 or later. You can then configure your sequence to call these DLLs instead of calling the VIs. This means rewriting your sequence to use the DLL Flexible adapter to call the LV DLL instead of using the LV adapter to call your VIs. In this case your LV DLLs and other DLLs called by your sequence are executed in the same process and can share C DLL instrument handles.
Are there specific questions that you have regarding the Session Manager? Perhaps your questions can lead to examples and App Notes. There have not been very many questions regarding to the Session Manager so it is difficult to determine what customers need.

Session Manager with i3/Awesome/Xmonad?

Hello, First post here so let me know if I am doing anything wrong,
I recently started using i3 and I could not recommend it more, I have given xmonad a shot and was a big fan and I know a lot of people seem to like Awesome, my only question is...
Are there any session managers that would work for any of them?
I love them but I spend a lot of time getting things just right so I have a nice flow at work (I loooooove i3 once I have everything where I want it). Before switching to xmonad from xfce4 I always had my work from office session, my work from home session, and one or two others. Anyone know of any way to save sessions in one of the mentioned window managers? Or are there any other window managers I should look into for this feature?
Thanks!!

I think this session thing is about stopping the applications in a way that you can start them again.
1. Different users/computers - It's very static and doesn't really scale.
2. Any X11 Session Manager - You have to log out of X11 and you can only have one session open.
3. My super script - For sessions on a tag/workspace level. Sorry for the bad english and bash. I'm about to rewrite it, it will support i3 and openbox. But maybe I should wait for wayland.
I have read that systemd article more than once, but I didn't understand if it's limited to 2 or not?

Users not showing in Terminal Server Under Remote desktop services manager and Task Manager

Hi All,
I have a problem here in Terminal Server. I can not see the users logged in to Server but i know users are accessing the files and currently working.
1. From the Task Manager-- Show processes from all users displayed all the processes accessing by users.
2. From the Task Manager-- From Users Tab--No users list at all
3. From the Command Prompt- Query users-- No information
4. From the Remote desktop services Manager-- used with IP/Host name-- Still can not see the users list and processes. So i can not kill the session if needed.
Enviroment:
TS CALS 20 currently accessing 15 users
VM-WARE GUEST: 2008 RS Terminal Services/Remote Desktop services installed
Windows up to date-- Just updated last month
Problem is here for long time. Just couldn't find the time to trouble shoot.
UMESH DEUJA MCP,MCTS,MCSA,CCNA

Hi,
Thank you for posting in Windows Server Forum.
As you have tried many steps, I suggest you to try below command line and power shell command if successful in your case. Please try below command with Admin access:
qwinsta /server:<servername>
To kill a session use rwinsta to delete the session specifying the ID number:
rwinsta /server:computer01 3
Here's the list of command line tools for Remote Desktop Or, you can use PowerShell:
Get-RDUserSession and Disconnect-RDUser
Please check the list of Power Shell command from
this link.
Hope it helps!
Thanks,
Dharmesh

Terminal Server Session Management: why do we need a rdp session to take control of a terminal session?

Similar Messages

Maybe you are looking for