Question Locked

Server 2003 Terminal Services User Access Problem

0 helpful
9 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Since installing the latest batch of Security updates on our 2003 Server, any user created since the update, or that has never logged on to Terminal Services before the update, can not execute a file over a network drive in a Terminal Services session. Local files (on the server) are OK.

These are the updates that were applied:

KB923694 - Cumulative Security Update for Outlook Express
KB928843 - Vulnerability in HTML Help ActiveX Control Could Allow Remote Code Execution
KB928255 - Vulnerability in Windows Shell Could Allow Elevation of Privilege
KB926436 - Vulnerability in Microsoft OLE Dialog Could Allow Remote Code Execution
KB918118 - Vulnerability in Microsoft RichEdit Could Allow Remote Code Execution
KB924667 - Vulnerability in Microsoft MFC Could Allow Remote Code Execution

The error message received is:

"Windows cannot access the specified device, path, or file. You may not have the appropriate permissions to access the item."

The affected users do not have the access problem from their desktop workstations, only in a TS session.

Since users that have established TS sessions already do not have the problem, it seems to me it must be something new - i.e. the recent security updates - adding something to the Terminal services user's profile when it is created.

We will try rolling back the security updates, but need to do so when other users are not logged on and, of course, at a time when we can reboot the server. That won't be for several days, unless this becomes an emergency, which is not likely. We are not 100% certain one or more of the security updates generated the problem, but have not come up with an alternative scenario.

Any suggestions that do not require a reboot or interruption of other users working are most welcome.

3/1/07 We rolled back the updates, to no effect.

9 replies

by xt john

are trying to run a Windows program? or third party? Do yo have the TS users in a particular Organizational Unit under Active Directory? There is a setting under Group Policy that enables/disables execution of programs. Edit the Group Policy for the Terminal Services users. Get to the User Configuration\System section. The two options you'd be interested in are 'Run only allowed Windows applications' and 'Don't run specified Windows Aplications'. In order to run third party utilities... we needed to set the 'Run only allowed Windows applications' to disabled. We also disabled the ability to run Internet Explorer by adding that rule to the 'Don't run specified Windows applications'.

by piurivar

I edited the group policy of the OU this user is a member of, disabling "Run only allowed Windows Applications", but it had no effect. I wonder how a Group Policy could be causing this because it only affects users who did not have a TS profile before 2/16/07. Other users in the same OU who have previously established TS sessions do not have any problems.

I did not disclose this previously, but the Domain Controller is Windows 2000 Server, while the Terminal Server is Server 2003.

Thank you for your advice, every piece adds to the picture.

by piurivar

I have found I can work around the problem by copying the profile of a user without the problem over the profile of a user with the problem. I still need to know what the problem is, though, to prevent it from occuring every time we add a user who will need to use Terminal Services.

by piurivar

The workaround does not work as I thought. I had copied my own user, a Domain Admin. When I moved the copied user from Domain Admins to Domain Users, the problem resurfaced. Copies of other accounts are not meeting the same success I had with the copy of my account. We can't make all new users Domain Administrators. Again, previously existing accounts who are members of Domain Users with no special priveleges do not have this problem.

My sincere thanks to anyone spending time to consider this problem.

by notsochiguy

...have you checked the settings for the RDP connector? This has some check boxes that could impact the users.

It is listed under the Terminal Services Configuration in the Administrative Tools folder.

by piurivar

I found nothing untoward there. also, changes there affect users at each new session, I believe. So a problem setting there should affect all users.

by piurivar

The problem was a result of Internet Explorer Enhanced Security settings.

The decision was made to uninstall the feature, resulting in the reseolution of this matter.

Again, my thanks to those who considered this issue.

by gadism

the solution we (finally) found was to include the name of the server with the share in the "allowed sites" of the intranet security settings in internet explorer 7. thanks, Microsoft for a week spent on research.
ciao ciao, Michel - Gadis

This discussion is closed to new replies.