This post originated from an RSS feed registered with .NET Buzz
by Duncan Mackenzie.
Original Post: ClickOnce and "locked down" systems
Feed Title: Code/Tea/Etc...
Feed URL: /msdnerror.htm?aspxerrorpath=/duncanma/rss.aspx
Feed Description: Duncan is the Visual Basic Content Strategist at MSDN, the editor of the Visual Basic Developer Center (http://msdn.microsoft.com/vbasic), and the author of the "Coding 4 Fun" column on MSDN (http://msdn.microsoft.com/vbasic/using/columns/code4fun/default.aspx). While typically Visual Basic focused, his blogs sometimes wanders off of the technical path and into various musing of his troubled mind.
re: Reading Blogs... 11/2/2003 9:59 AM Ron Krauter
Hi,
I read your excellent article about ClickOnce on msdn. One of the problems we are having is deploying applications to users machine that have user only access. Unfortunately, the users are not able to install the application as they do not have admin priviledges. We, the admins, end up going to the client machine and installing the application by using "RUNAS". Is there an easier way to do this with clickonce where admins don't have to go to client workstations. Thanks
Well, Ron... and anyone else who is wondering about the exact same thing; I have some good news for you. Locked down desktops are one of the key scenarios that ClickOnce is designed to deal with. ClickOnce applications are installed and run on a per-user basis, allowing them to be launched/deployed without administrative level privileges.So no more running to each machine to do a 'RUNAS' administrative install.
It is worth pointing out though, that installing the framework is an 'impactful' install, using a standard .msi, so getting the framework out ahead of your ClickOnce applications will likely require higher privileges.
Previous Topic
