ClickOnce deployment and Terminal Services

[=?Utf-8?B?R29yZG9uUw==?=]

I have a windows form application being deployed using ClickOnce on Terminal
Services.

I am experiencing a problem where by the first user to run up the
application is successful and the app downloads and launches successfuly,
however if a second user logs on to terminal services and attempts to launch
the app then the "Verifying applications. This may take a few moments"
message does appear briefly and then disappears but no application is
launched.

I assume this is a configuration issue but don't really know where to look,
any ieads gratefully recieved.

--
Gordon Smith

[Linda Liu[MSFT]]

Hi Gordon,

however if a second user logs on to terminal services and attempts to

launch the app then the "Verifying applications. This may take a few
moments" message does appear briefly and then disappears but no application
is launched.

Do you see a launch error dialog showing at this time? If yes, could you
please show us the detailed error messages?

What version of IIS you publish the ClickOnce application to?

I performed a test based on your description but didn't reproduce the
problem. The following are my test steps:

1. Publish a ClickOnce application to a web server with IIS 7.
2. Remote desk to a machine A from a machine B.
3. Launch the ClickOnce application via the url
"http://servername/TestApplication/TestApplication.application".
4. The ClickOnce application is installed and launched properly.
5. Remote desk using another user account to the machine A from the machine
B.
6. Launch the ClickOnce application via the url
"http://servername/TestApplication/TestApplication.application".
7. The ClickOnce application is installed and launched properly.
Sincerely,
Linda Liu
Microsoft Online Community Support

==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscripti...ult.aspx#notif
ications.

Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscripti...t/default.aspx.
==================================================

This posting is provided "AS IS" with no warranties, and confers no rights.

[Linda Liu[MSFT]]

Hi Gordon,

How about the problem now?

If the problem is still not solved, please feel free to let me know.

Thank you for using our MSDN Managed Newsgroup Support Service!

Sincerely,
Linda Liu
Microsoft Online Community Support

[=?Utf-8?B?SnVzdGlu?=]

I am experiencing the same problem. I followed the same steps that you
described above with different results. If one user is running the app, the
second user cannot open it (same behavior as Gordon described above). The
only difference in my environment from your test is that I published to a
Windows 2003 server with IIS6. I also tried publishing to and installing from
a network share with the same results. Any help is appreciated.

"Linda Liu[MSFT]" wrote:

Hi Gordon,

How about the problem now?

If the problem is still not solved, please feel free to let me know.

Thank you for using our MSDN Managed Newsgroup Support Service!

Sincerely,
Linda Liu
Microsoft Online Community Support

[=?Utf-8?B?SnVzdGlu?=]

Nevermind. I found code in my app that was making sure only one instance of
itself was running. Oops! Works fine now.

"Justin" wrote:

I am experiencing the same problem. I followed the same steps that you
described above with different results. If one user is running the app, the
second user cannot open it (same behavior as Gordon described above). The
only difference in my environment from your test is that I published to a
Windows 2003 server with IIS6. I also tried publishing to and installing from
a network share with the same results. Any help is appreciated.

"Linda Liu[MSFT]" wrote:

Hi Gordon,

How about the problem now?

If the problem is still not solved, please feel free to let me know.

Thank you for using our MSDN Managed Newsgroup Support Service!

Sincerely,
Linda Liu
Microsoft Online Community Support

[Ravindran Thangavelu]

Hi,
I try to deploy my application in clickonce server. The server is Windows server 2008 and iis 7.0. I created a sample application in windows server 2008 server and try to configure that application, its configure well, but i try to devlop my application through http://, its asking user id and password, i entered the user id(Administrator) and password of the server but it is not accepting.

My server is another domain, my system is in another domain, but both the system are connected in global domain.

My settings in IIS 7.0

For my virtual directory the IIS manager permission not having users but in Default web site its having users of Administrator.

For virtual directory shared users are Administrator and Every one both the users are having the same full rights.

I dont know what happen for this, Can you please help me to solve this issues?

If possible please sent what are the configuration is needed to publish our application in IIS 7.0

Thanks in advance.