Configure RemoteApp and Desktop Connection on Windows 7 Clients

This script uses a RemoteApp and Desktop Connections bootstrap file(a .wcx file) to set up a connection in Windows 7 workstation. No user interaction is required.It sets up a connection only for the current user. Always run the script in the user's session.

 
 
 
 
 
4.4 Star
(29)
Add to favorites
2/2/2010
E-mail Twitter del.icio.us Digg Facebook
Sign in to ask a question


  • No longer works
    1 Posts | Last post April 19, 2019
    • I assume this worked in the past but it doesn't anymore.  A registry entry is created but nothing shows up in RemoteApp and Desktop Connections after a successful run of the script and subsequent attempts to run it only return the "already exists" error.
  • Update Connection
    1 Posts | Last post August 06, 2018
    • The script works fine adding the connection, but the updating the connection for task scheduler keeps failing till I update it manually, is there a way that I can configure the connection and make sure that the update works with any user interaction?
      Thanks,
  • Do I need to edit the script to specify the wcxpath?
    1 Posts | Last post August 17, 2017
    • I am not very familiar with Powershell and wanted confirmation on where to specify the WCX path and in what context of the script?
      
  • Stop prompting for credentials?
    1 Posts | Last post May 10, 2017
    • When I set up remoteapp connections with this script, the user is prompted for credentials each time they launch a new remoteapp session. How do I store their credentials so this doesn't happen?
      
      When I have them set up the remoteapp connection by just running the .wcx file, there's a checkbox for saving credentials that lets you do this. 
  • Deploy RemoteApp shortcuts to desktop
    2 Posts | Last post April 08, 2016
    • Is there a way to edit the powershell to then deploy the shortcuts to the users desktop?
      
      Thanks,
      Nathan
    • I've found the easiest way to accomplish this is to issue a command upon login to open the "Work Resources" folder (%USERPROFILE%\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\RemoteApp and Desktop Connections\Work Resources) and/or create a shortcut on the desktop that points to this folder, just in case.
  • Error while checking if the addition was successful
    1 Posts | Last post December 09, 2015
    • I've seen several solutions for this error below, but here is another one:
      if ( (($connectionKey -replace "HKEY_CURRENT_USER", "HKCU:") | Get-ItemProperty -Name URL).URL -eq $URL)
      
      Ciao
      Padre Pedro
      WinDoh (http://windoh.wordpress.com)
      
  • Got an error whule running it as well.
    1 Posts | Last post December 03, 2015
    • Hey all,
      
      I discovered an error in the aforementioned script for installing webfeeds on Win7 and Server 2008R2 targets.
      
      For some reason when Get-ItemProperty is invoke in the script it was applying my file path to the item it was trying to get properties on.  I ended up re-writing the line to properly call for a registry entry rather than trying to parse a file path.  (Not sure when this behavior changed.)  Someone might want to update the script.
      
      Offending line @ line 43 in the original script read:
      
      if ( ($connectionKey | Get-ItemProperty -Name URL).URL -eq $URL)
      
       
      
      Had to change it to the following:
      
      if ((Get-ItemProperty -path Registry::$connectionKey).URL -eq $URL)
      
      I figured I couldn't be the only one that has run into this.  
  • CMDKEY
    1 Posts | Last post October 14, 2015
    • I am deploying this script in the user context.  Does anyone know how I would go about adding cmdkey to cache the credentials being used to set up the connection? 
  • I get an error when running it
    1 Posts | Last post January 15, 2015
    • Maybe it's my version of PowerShell or maybe it's just me, but I'm receiving the following error:
      Get-ItemProperty : Cannot find path 'C:\Users\(user)\Desktop\HKEY_CURRENT_USER\Software\Microsoft\Workspaces\Feeds\{GUID}' because it does not exist.
      
      I found changing the line in the CheckForConnection function fixes it
      from:
      if ( ($connectionKey | Get-ItemProperty -Name URL).URL -eq $URL)
      to:
      if ( ('Registry::' + $connectionKey | Get-ItemProperty -Name URL).URL -eq $URL)
  • Update feed
    1 Posts | Last post December 03, 2014
    • The script works perfectly for creating connections the first time it is run.  What needs to happen to get the script to update a connection when there is a change/addition to the feed list?
1 - 10 of 20 Items