Hi David - I am reaching back to you about your previous issue with RDP and TMS2010 reports.
I finally got a chance to finish installing TMS2010R2.
Were you able to resolve this issue?
From: The Museum System (TMS) Users [mailto:[log in to unmask]] On Behalf Of Parsell, David
Sent: Thursday, August 04, 2011 12:49 PM
To: [log in to unmask]
Subject: Re: Using a terminal server to connect all users to TMS 2010?
OK, great. Thanks for all your input and suggestions.
I suspect this problem might go away if the users had Win7 workstations, or at least I would like to experiment, but Yale doesn't support Win7 so nothing available to test with.
I hope you have better luck than me. Also, at what museum are you working?
Thanks for your help, David
From: The Museum System (TMS) Users [mailto:[log in to unmask]] On Behalf Of Lopez, Noel
Sent: Thursday, August 04, 2011 12:32 PM
To: [log in to unmask]
Subject: Re: Using a terminal server to connect all users to TMS 2010?
David - I will be installing 2010 to a RDP server next week. I will let you know if I run into the same issue.
Noel
From: The Museum System (TMS) Users [mailto:[log in to unmask]] On Behalf Of Parsell, David
Sent: Thursday, August 04, 2011 12:16 PM
To: [log in to unmask]
Subject: Re: Using a terminal server to connect all users to TMS 2010?
Hi Noel,
We gave two users with the problem, admin rights to the TS and had them RDP to the TS and try the TMS reports, but it didn't fix the problem for them. They were given membership in the network admin group which has admin rights on the box.
Thanks for your help, David
From: The Museum System (TMS) Users [mailto:[log in to unmask]] On Behalf Of Lopez, Noel
Sent: Thursday, August 04, 2011 12:08 PM
To: [log in to unmask]
Subject: Re: Using a terminal server to connect all users to TMS 2010?
Hi David - Ok so that sounds like an OS issue. Another issue that might cause problems is installing the application under the C:\Program Files (x86) folder; however, your comments about some users being able to see the dropdown and some can't discards this possibility.
Have you try giving the user Local Administrator rights to the box? Of course this is not a permanent solution if it works.
Also, Login to the box as local administrator and have the user login to TMS.
From: The Museum System (TMS) Users [mailto:[log in to unmask]] On Behalf Of Parsell, David
Sent: Wednesday, August 03, 2011 3:01 PM
To: [log in to unmask]
Subject: Re: Using a terminal server to connect all users to TMS 2010?
Yes, I did the login for me (I see the drop downs OK), same result works fine for me.
I tried another netID where it always works. The login worked for that user as well.
Third, I tried the login for another user that cannot see the drop downs on his workstation, same result, he still cannot see the drop downs.
Regarding roaming or remote profiles, I sent an email to the admin that set up the server. No answer back yet.
Thanks for your help, David
From: The Museum System (TMS) Users [mailto:[log in to unmask]] On Behalf Of Lopez, Noel
Sent: Wednesday, August 03, 2011 2:51 PM
To: [log in to unmask]
Subject: Re: Using a terminal server to connect all users to TMS 2010?
Yes, mstsc.exe launches the remote desktop client. Did you try to login using the client? Did you get the same result?
Windows 2008 allows for Remote Profiles and Roaming profiles. I have found that some applications do not work well with roaming profiles so I assign users remote profiles.
RDPApp.rdp is just a example for a Remote App .rdp file. It should not be in your system. Sorry for the confusion.
From: The Museum System (TMS) Users [mailto:[log in to unmask]] On Behalf Of Parsell, David
Sent: Wednesday, August 03, 2011 1:43 PM
To: [log in to unmask]
Subject: Re: Using a terminal server to connect all users to TMS 2010?
Hi Noel,
Mstsc.exe is the Remote Desktop application in Windows XP.
I don't believe RDPApp.rdp is a Windows app, but I may be wrong.
Every users' netid has a profile in the Active directory. No one has any remote desktop features turned on in their profile.
Thanks for your help, any other suggestions?
David
David Parsell
Systems Manager Collections Information and Access
Yale Center for British Art
[log in to unmask]<mailto:[log in to unmask]>
2034329603
From: The Museum System (TMS) Users [mailto:[log in to unmask]] On Behalf Of Lopez, Noel
Sent: Wednesday, August 03, 2011 11:49 AM
To: [log in to unmask]
Subject: Re: Using a terminal server to connect all users to TMS 2010?
David - Do you have user profiles enable on your network?
What happens if the user connects to the RDP server directly using mstsc rather than using the RDPApp.rdp file?
Do they get the same result?
From: The Museum System (TMS) Users [mailto:[log in to unmask]] On Behalf Of Jay Hoffman
Sent: Wednesday, August 03, 2011 11:43 AM
To: [log in to unmask]
Subject: Re: Using a terminal server to connect all users to TMS 2010?
David,
We are using Windows Server 2008 R2 as a remote application server. I am forwarding your email to our support team. They will take a look at the problem.
Regarding re-writing report: do you use database views for your reports? That is the recommended best practice. This way, revising the database views should make it easier to update existing reports.
Best,
Jay
From: The Museum System (TMS) Users [mailto:[log in to unmask]] On Behalf Of Parsell, David
Sent: Wednesday, August 03, 2011 10:43 AM
To: [log in to unmask]
Subject: Using a terminal server to connect all users to TMS 2010?
I would like to hear from any museum using a terminal server to connect users to TMS 2010.
I am implementing the terminal server configuration for our 2010 upgrade and have run into a serious problem.
I am using Win server 2008 R2 on the terminal server. All of the workstations connecting to the TS are running Win XP.
In the interests of not having to rewrite all of our 935 reports for 2010, I want to use the 2010 reports, which is the problem.
Many of the 2010 reports present a window with drop downs for variable and sort selections, which is great but this is the cause of my problem.
Many of my users can't run the 2010 reports and are presented with blank drop down menus when the 2010 report is run. While other users don't have a problem. For users that get the blank drop downs, they can't run the report or even exit the drop down window.
This is a very random problem, but always the same for each user. Any user that cannot see the drop downs on their own workstation, can log onto any other workstation and still not see the drop downs. So, the problem follows the user to every workstation.
It's not a security configuration problem as all users are in the same network security group and even users with TMS sys.admin rights have the problem.
I know I can downgrade the terminal server to Win server 2003 and most likely the problem will go away (experiments with the Yale Art Gallery 2003 TS has proven this), but I need a solution for the Win server 2008 R2.
Does anyone have this configuration installed and working correctly?
Or not working correctly?
Further info;
The same users can attach to 2010 TMS the 'old fashioned' way with TMS installed on their workstation and the reports work fine.
If I remove the 2010 report window with the drop downs, the report works fine for every user.
The new 2010 reports are great and the drop downs are very useful, therefore I hate to remove the new functionality just to make them usable to all of our TMS users.
Any thoughts on this subject will be greatly appreciated.
Thanks for your help,
David Parsell
Systems Manager Collections Information and Access
Yale Center for British Art
[log in to unmask]<mailto:[log in to unmask]>
2034329603
To unsubscribe, send an email to [log in to unmask]<mailto:[log in to unmask]> with the following commands in the body of the email:
signoff TMSUSERS
// eoj
You will receive a confirmation that your subscription has been removed.
To unsubscribe, send an email to [log in to unmask]<mailto:[log in to unmask]> with the following commands in the body of the email:
signoff TMSUSERS
// eoj
You will receive a confirmation that your subscription has been removed.
To unsubscribe, send an email to [log in to unmask]<mailto:[log in to unmask]> with the following commands in the body of the email:
signoff TMSUSERS
// eoj
You will receive a confirmation that your subscription has been removed.
To unsubscribe, send an email to [log in to unmask]<mailto:[log in to unmask]> with the following commands in the body of the email:
signoff TMSUSERS
// eoj
You will receive a confirmation that your subscription has been removed.
To unsubscribe, send an email to [log in to unmask]<mailto:[log in to unmask]> with the following commands in the body of the email:
signoff TMSUSERS
// eoj
You will receive a confirmation that your subscription has been removed.
To unsubscribe, send an email to [log in to unmask]<mailto:[log in to unmask]> with the following commands in the body of the email:
signoff TMSUSERS
// eoj
You will receive a confirmation that your subscription has been removed.
To unsubscribe, send an email to [log in to unmask]<mailto:[log in to unmask]> with the following commands in the body of the email:
signoff TMSUSERS
// eoj
You will receive a confirmation that your subscription has been removed.
To unsubscribe, send an email to [log in to unmask]<mailto:[log in to unmask]> with the following commands in the body of the email:
signoff TMSUSERS
// eoj
You will receive a confirmation that your subscription has been removed.
To unsubscribe, send an email to [log in to unmask]<mailto:[log in to unmask]> with the following commands in the body of the email:
signoff TMSUSERS
// eoj
You will receive a confirmation that your subscription has been removed.
To unsubscribe, send an email to [log in to unmask]<mailto:[log in to unmask]> with the following commands in the body of the email:
signoff TMSUSERS
// eoj
You will receive a confirmation that your subscription has been removed.
To unsubscribe, send an email to [log in to unmask] with the following commands in the body of the email:
signoff TMSUSERS
// eoj
You will receive a confirmation that your subscription has been removed.