Questions about Remoteapp Programs that take over client extensions

[Guest Pharismod]

I've installed Word 2003 as a Remoteapp program on a Vista

workstation, with the 'take over client extensions' option enabled.

There are a few limitations/frustrations that I've encountered and I

want to make sure that they're 'as intended' before I give up.

 

On a Windows Vista workstation, I have a network drive letter S:

mapped to \\servername\Documents, inside which are several .doc files.

I also have a WSS3 site that hosts some documents and is accessible

via both the workstation and the TS session. Also, my TS session also

has S: mapped to \\servername\Documents.

 

- If I navigate to the files on the Documents share by UNC path and

double click, the Remoteapp version of Word launches correctly without

issue.

- If I navigate to these files by using the S: drive letter and double

click, I get an error stating that the Remoteapp Program was not

found.

- If I navigate to the files on the Sharepoint site using IE and

attempt to open a file from there, I get an error stating that the

Remoteapp Program was not found.

- If I launch the Word Remoteapp first then I can open files from any

of the above sources by going to File/Open without issue.

- If I attempt to launch Word documents from my local hard disk (C:)

then I get an error stating that the Remoteapp Program was not found.

 

The problems make some sense. I suspect that the TS server would have

a heck of a time opening a Word file on my local workstation.

 

That said, what's the point in integrating with client extensions? It

seems that this feature will be far more confusing to a user than to

simply not have it available at all, especially if it can't even

launch a file from a Sharepoint site or mapped network drive.

 

Could the error messages not be more descriptive? Why won't the

Sharepoint documents launch from the local workstation? These problems

are counter-intuitive and the error messages given by Remoteapp are

completely uninformative.

[Guest Jeff Pitsch]

Re: Questions about Remoteapp Programs that take over client extensions

 

Is there anything in the event logs?

 

Jeff Pitsch

Microsoft MVP - Terminal Services

 

 

"Pharismod" <pharismod1@shaw.ca> wrote in message

news:1d87ce16-1c13-4f43-bba0-722a84f2e7c0@g16g2000pri.googlegroups.com...

> I've installed Word 2003 as a Remoteapp program on a Vista

> workstation, with the 'take over client extensions' option enabled.

> There are a few limitations/frustrations that I've encountered and I

> want to make sure that they're 'as intended' before I give up.

>

> On a Windows Vista workstation, I have a network drive letter S:

> mapped to \\servername\Documents, inside which are several .doc files.

> I also have a WSS3 site that hosts some documents and is accessible

> via both the workstation and the TS session. Also, my TS session also

> has S: mapped to \\servername\Documents.

>

> - If I navigate to the files on the Documents share by UNC path and

> double click, the Remoteapp version of Word launches correctly without

> issue.

> - If I navigate to these files by using the S: drive letter and double

> click, I get an error stating that the Remoteapp Program was not

> found.

> - If I navigate to the files on the Sharepoint site using IE and

> attempt to open a file from there, I get an error stating that the

> Remoteapp Program was not found.

> - If I launch the Word Remoteapp first then I can open files from any

> of the above sources by going to File/Open without issue.

> - If I attempt to launch Word documents from my local hard disk (C:)

> then I get an error stating that the Remoteapp Program was not found.

>

> The problems make some sense. I suspect that the TS server would have

> a heck of a time opening a Word file on my local workstation.

>

> That said, what's the point in integrating with client extensions? It

> seems that this feature will be far more confusing to a user than to

> simply not have it available at all, especially if it can't even

> launch a file from a Sharepoint site or mapped network drive.

>

> Could the error messages not be more descriptive? Why won't the

> Sharepoint documents launch from the local workstation? These problems

> are counter-intuitive and the error messages given by Remoteapp are

> completely uninformative.

[Guest Pharismod]

Re: Questions about Remoteapp Programs that take over clientextensions

 

Re: Questions about Remoteapp Programs that take over clientextensions

 

On Jul 5, 5:55 am, "Jeff Pitsch" <j...@jeffpitschconsulting.com>

wrote:

> Is there anything in the event logs?

>

> Jeff Pitsch

> Microsoft MVP - Terminal Services

>

> "Pharismod" <pharism...@shaw.ca> wrote in message

>

> news:1d87ce16-1c13-4f43-bba0-722a84f2e7c0@g16g2000pri.googlegroups.com...

>

> > I've installed Word 2003 as a Remoteapp program on a Vista

> > workstation, with the 'take over client extensions' option enabled.

> > There are a few limitations/frustrations that I've encountered and I

> > want to make sure that they're 'as intended' before I give up.

>

> > On a Windows Vista workstation, I have a network drive letter S:

> > mapped to \\servername\Documents, inside which are several .doc files.

> > I also have a WSS3 site that hosts some documents and is accessible

> > via both the workstation and the TS session. Also, my TS session also

> > has S: mapped to \\servername\Documents.

>

> > - If I navigate to the files on the Documents share by UNC path and

> > double click, the Remoteapp version of Word launches correctly without

> > issue.

> > - If I navigate to these files by using the S: drive letter and double

> > click, I get an error stating that the Remoteapp Program was not

> > found.

> > - If I navigate to the files on the Sharepoint site using IE and

> > attempt to open a file from there, I get an error stating that the

> > Remoteapp Program was not found.

> > - If I launch the Word Remoteapp first then I can open files from any

> > of the above sources by going to File/Open without issue.

> > - If I attempt to launch Word documents from my local hard disk (C:)

> > then I get an error stating that the Remoteapp Program was not found.

>

> > The problems make some sense. I suspect that the TS server would have

> > a heck of a time opening a Word file on my local workstation.

>

> > That said, what's the point in integrating with client extensions? It

> > seems that this feature will be far more confusing to a user than to

> > simply not have it available at all, especially if it can't even

> > launch a file from a Sharepoint site or mapped network drive.

>

> > Could the error messages not be more descriptive? Why won't the

> > Sharepoint documents launch from the local workstation? These problems

> > are counter-intuitive and the error messages given by Remoteapp are

> > completely uninformative.

 

Nothing at all in the event logs on either the workstation or the

server.

 

I get a dialog box titled RemoteApp Error that contains a message

stating: "The program TS Microsoft Office Word 2003 was not found. For

assistance, contact your system administrator".

[Guest Kyosho]

Re: Questions about Remoteapp Programs that take over client exten

 

Re: Questions about Remoteapp Programs that take over client exten

 

We just used the .msi installer maker on our 2008 TS server with the

RemoteApp Wizard and tried to do the same thing: click the check box to Take

oover client extensions. We installed on the local computer, double-clicked

the Excel icon and it worked great. Then we save a document to a local mapped

drive (X: for user data) and then closed out and double-clicked on the

document. Same error! Is this annoying or what? I don't want my users to come

running to me every time they try to open a document. What is wrong with this

picture!

 

"Pharismod" wrote:

> On Jul 5, 5:55 am, "Jeff Pitsch" <j...@jeffpitschconsulting.com>

> wrote:

> > Is there anything in the event logs?

> >

> > Jeff Pitsch

> > Microsoft MVP - Terminal Services

> >

> > "Pharismod" <pharism...@shaw.ca> wrote in message

> >

> > news:1d87ce16-1c13-4f43-bba0-722a84f2e7c0@g16g2000pri.googlegroups.com...

> >

> > > I've installed Word 2003 as a Remoteapp program on a Vista

> > > workstation, with the 'take over client extensions' option enabled.

> > > There are a few limitations/frustrations that I've encountered and I

> > > want to make sure that they're 'as intended' before I give up.

> >

> > > On a Windows Vista workstation, I have a network drive letter S:

> > > mapped to \\servername\Documents, inside which are several .doc files.

> > > I also have a WSS3 site that hosts some documents and is accessible

> > > via both the workstation and the TS session. Also, my TS session also

> > > has S: mapped to \\servername\Documents.

> >

> > > - If I navigate to the files on the Documents share by UNC path and

> > > double click, the Remoteapp version of Word launches correctly without

> > > issue.

> > > - If I navigate to these files by using the S: drive letter and double

> > > click, I get an error stating that the Remoteapp Program was not

> > > found.

> > > - If I navigate to the files on the Sharepoint site using IE and

> > > attempt to open a file from there, I get an error stating that the

> > > Remoteapp Program was not found.

> > > - If I launch the Word Remoteapp first then I can open files from any

> > > of the above sources by going to File/Open without issue.

> > > - If I attempt to launch Word documents from my local hard disk (C:)

> > > then I get an error stating that the Remoteapp Program was not found.

> >

> > > The problems make some sense. I suspect that the TS server would have

> > > a heck of a time opening a Word file on my local workstation.

> >

> > > That said, what's the point in integrating with client extensions? It

> > > seems that this feature will be far more confusing to a user than to

> > > simply not have it available at all, especially if it can't even

> > > launch a file from a Sharepoint site or mapped network drive.

> >

> > > Could the error messages not be more descriptive? Why won't the

> > > Sharepoint documents launch from the local workstation? These problems

> > > are counter-intuitive and the error messages given by Remoteapp are

> > > completely uninformative.

>

> Nothing at all in the event logs on either the workstation or the

> server.

>

> I get a dialog box titled RemoteApp Error that contains a message

> stating: "The program TS Microsoft Office Word 2003 was not found. For

> assistance, contact your system administrator".

>