Have you deployed PNtools to the managed desktop?

Hi,

To be clear, I'm using a Windows 2003 R2 TS farm. The client accessing the published application is Windows 7 (with fill vWorkspace Connector) and Windows XP SP3 (with Web Client). If the W7 PC connects via the AppPortal, Integrated Desktop Shortcuts, or Web Access the client starts connects then nothing happens...

1. AppPortal reports app is lanching
2. Client pops up and says 'Starting '
3. Nothing happens but when you click 'Details >>' the desktop is there waiting... no app launched
4. Note the title of the window is still 'Connecting to '
5. After logging off the session I get this...

Thanks for looking at this thread!

Caleb, 

     When the "starting HES" popup appears, click on the "details" button.  What do you see?  An error? 

Hello Caleb,

Can you provide us with a screenshot of the following?

1. In the vWorkspace Management Console expand “vWorkspace_Farm” | “Resources”
2. Right click your Published Application and select Properties
3. Select the “Defaults” tab

What values are entered for the Path, arguments and Working Dir?

Hi Roman

For Outlook 2010 I have the following

Path:     c:\Program Files\Microsoft Office\Office14\OUTLOOK.EXE

Arguments:

WorkingDir:

Yes, I just published notepad and exactly the same happens

Caleb,

Do you get the same error when publishing Notepad or MSPaint from your terminal server as a seamless application?

Firewall off?  Or correct ports open?

When I click the Details button I see the usual Windows Logon bit... and the PNShell app running through then it sits on the desktop...

No Firewalls in place... Very odd as the published desktop on the same servers work fine...

Looks like I'll log a ticket with support on this one.

Correct! Shame that when I remove this policy it brings back my oldl problem of the Notification Try Icon for our most important application being hidden... I guess I'll log a ticket with them