Hi t.ly,

Have you tried the the following?

When using Web Access (Web-IT), application cannot be launched with no error returned. User is presented with Internet Explorer "Save" dialog.

Vista and Windows7 users are prompted to save PIT file instead of launching application

Please let me know if it helps.  You can find more solutions like this in Quest's SupportLink Knowledgebase.

Thanks Dax and Andrew.

@Dax, IE settings is as suggested and I've reinstalled the client with local administrator but same problem happened.

@Andrew, we use App-V to publish our apps so App-V client existed on our workstations. I also have App-V client on TS and Managed Desktops. I also tried changing the content to launch on the client but made no difference.

Thanks

Hi,

This thread might be useful http://en.community.dell.com/techcenter/virtualization/vworkspace/f/4827/t/19551438

Cheers

Paul

Hello,

Dax's links will help with PIT file errors.

For the OSD errors, currently when publishing AppV apps through Quest, you don't want the AppV client installed on the Client machines, you want it installed on the Terminal Server/Managed Desktop as it launches the Content from the Server/Desktop you've published the AppV app to.

So, if the Terminal Server (or managed desktop) doesn't have the AppV client installed, it won't know what to do with the OSD file.

Alternatively, you can manually modify the published app. Right click on the App in the vWorkspace Management Console, Click on application type and change the Content to "Launch Content on Client"

This will launch the AppV app using the AppV client installed on the end user computer.

Cheers, Andrew.

Thanks all for helping even though I still can't get it to work. May be I just don't know what I'm doing. We're just doing a test drive for this vWorkspace.

I tried suggestions in the thread provided by Paul but still getting .pit

Need some sleep for now.

thanks

Hi,

You have to look at it as 2 seperate issues.

PIT file errors are caused by 1. Not have the vWorkspace Connector installed on the Client. 2. Incorrect Web Site settings. 3. Some of the other stuff Dax sent through.

OSD issues are fixed by Pauls suggestion/Mine/Something else.

Feel free to log a case with support once you've had a sleep. If you do, post the CaseID on here so I can take a look at it too (As I'll be asleep by the time you raise the case)

Thanks, Andrew.