Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 4776
  • Last Modified:

Unable to save to local desktop from RDP connection

We are running our Point of Sale software on a hosted Windows 2008 R2 Enterprise server. Our agents use Remote Desktop (primarily the app, but there are a select few using the full RDP) to access the software.

Recently, while making tweaks to the app, we accidentally disabled the ability for our users to save items to their own local desktops. After going into RD Session Host Config and re-checking Drive access, as well as re enabling on the Remote App, we are still unable to save to our local machines.

I have rebooted the server, as well as restarted the Remote Desktop Services UserMode Port Redirector service that allows the redirection of Printers/Drives/Ports for RDP connections.

It seems notable that this server was configured prior to our installation of our PDC, which is running Windows Server 2012 R2 Standard back in December, however, there have been no issues accessing local folders and drives until this past weekend when we made those couple changes that we have since changed back to their original configuration.

Has anyone experienced this, and/or no how to get our local drive access back?

Thanks!
0
botsadmins
Asked:
botsadmins
  • 2
1 Solution
 
Michael MachieFull-time technical multi-taskerCommented:
How are you launching the RDP session? Are any Group Policies created applied to the TS (RDS) server disallowing local saves?

If you are using a custom RDP shortcut then you can change the options, or create a new session icon, to allow local saves to any drive you want, to C: for example. You can also allow or disallow the desktop and printers etc.

1) Open a RDP session by clicking Start and typing 'mstsc' into the run/search field.
2) On the screen for the server name click 'Options' at the bottom left.
3) Choose 'Local Resources' tab.
4) Select 'More' under the 'Local Devices and Resources' section
5) Select 'Drives' and expand to select the drives you want to have available.

Review the other options in those menus and customize as needed o add clipboard, printers, sound and video pass-through etc.
0
 
botsadminsAuthor Commented:
Thanks for getting back to me. I have actually already gone through those steps as well, both prior to, and after restarting the RDS Port Service. We were actually using the clipboard as a work around (save to POS desktop, then copy/paste to local), but the Drives option has been enabled ever since Monday when we first realized our initial error, it just isn't resolving.

As far as Group Policies, I never made any changes, so I'm assuming there shouldn't be any explicitly disallowing local saves. I'm digging through every setting I can find in Local Group Policy Editor on our POS server, and I did find in Computer Config>Windows Settings>User Config>Administrative Templates>Shared Folders, there are "Allow DFS roots to be published," and "Allow shared folders to be published," both of which are not configured.

Would either of these help our situation, since we now have DFS configured on our PDC here locally? I don't have a ton of experience with these particular settings.
0
 
Michael MachieFull-time technical multi-taskerCommented:
I don't have a lot of experience with them either but I would say those settings may help, or even resolve your issue, if you started experiencing your problems at the time you configured/started DFS services.
0
 
MaheshArchitectCommented:
DFS name space and publishing is not related to your issue
Check if you have any GPO configured for RDS server
Check on the OU in which RDS server exists
Also run rsop.msc on RDS server to find out any applied settings

Also check on users workstation who access RDS server if there is any GPO configured
Run gpresult \ rsop.msc on those machine to fin out any settings via any GPO

If you found anything related to clip board, local drives, you need to revert that settings

If none found, you can try below
Create one new OU and move your terminal server in that OU
If you already have separate OU for RDS server then just create new GPO
In GPO navigate to Computer configuration\administrative templates\windows components\Remote desktop services\remote desktop sessions host\device and resource redirection and disable below two options.
Do not allow clipboard redirection
Do not allow drive redirection

Run Gpupdate /force on RDS server, if required take one reboot and then ask users to logoff RDP session once and log back on with local resources selected from there RDP connection.
They should get the access back

Mahesh
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now