In Dave’s previous post he talked about the back-end for our delivery of remote programs. I’m going to explain how we then surfaced this through SharePoint.
For those of you that have set up remote programs you will probably be aware of the web part for it, we found that using this didn’t give us very much flexibility in which programs are surfaced. So we came up with a couple of other methods.
The first is by far the simplest; the good old content editor web part! Just put your .rdp files in an accessable location along with some icons. Add the content editor part to the page and add the images, hyperlinked to the rdp file. Simple.
The way we now deliver remote programs is to store the rdp file, the icon and any description or meta data in a sharepoint list. We give them categories to enable us to group them and just render the list with xslt. Again very simple but very effective.
Of course all this transfers to SharePoint 2010 without issue.
You may also be interested in reading:
- Remote Program Delivery through SharePoint Mike Herrity recently did a post on delivering programs to...
- Media streaming through SharePoint part 3 Now that we had all of our media files in...
- SharePoint 2010 Powershell Commands Help Yesterday i did a post The first steps to SharePoint...
- Easy Access To STSADM Hands up who is fed up with navigating to “c:\program...
- Media streaming through SharePoint part 1 As I said in a previous post I would cover...
- The First Post Myself and Chris McKinley have been posting the occasional...
