I have a deployment package that opens an application when the instalation has finished.
On opening, this application validates a connection to a database using Integrated windows security.
The Problem is that when it calls
Process.Start(XXXXXXXXXX)
The application is opened under the machine account, the one that actualy does the install under UAC in Windows 7.
I know i can use the ProcessStartInfo object to ask the user to specify their password etc however this will be really annoying for them when they are already logged onto the machine.
I have tried using ProcessStartInfo, WinAPI etc but to no avail.
Has anyone else encountered this type of issue and/or have a suggested solution.
In summary I am trying to call
Process.Start........
Under the credentials of the logged on user as the last action of an deployment package under Windows 7
VB.NET application developed in VS2010 using Windows Installer Deployment.
Related
I've got one for you thats been bugging me for a bit.
If you run a Windows Service as Local System, how can that service display forms or prompts on the user desktop?
I tried this in one of my previous apps and couldn't get it to work; I settled on having an 'invisible' app running in the user context to handle any user interaction. But as time has passed, I've seen some apps that have nothing more than a service running as local system and yet they produce prompts and forms on the user desktop.
Thanks in advance for any info :)
We have developed an office add-in. Its working fine with every other system except one. In that particular system when we try to load the app, it fails with a generic error (This app could not be started. Close this dialog to ignore the problem or click "Restart" to try again.). Event viewer has the following details
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
and APPID
{9BA05972-F6A8-11CF-A442-00A0C90A8F39}
to the user STC\inmchandr SID (S-1-5-21-2779513660-4158667818-3257731910-104078) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
The specified CLSID points to ShellWindows component, which is running with "Interactive User" account. I am unable to change the other security permissions like launching permissions for that component in DCom config. I tried to change the permission for the corresponding registry entry (as suggested in this link) But, nothing worked out.
The winword.exe is running as the same user who logged in. This system and the other systems (where it is working) are in the same network and I tried running gpupdate as well.
(In that problematic system) The same app is loading when we tried to run Word as administrator. The URL used for that taskpane app is launching without any issues from browsers
OS: Windows 8.1
Processor: 64 bit
Office: 2013
Could anyone help us out to resolve the issue?
So, we're trying to setup an integration test server which will run the certification kit on a Windows Store app. However, we're having problems in that appcert.exe just freezes. No errors or anything is logged, it just sits there until our 1 hour timeout is hit.
We're trying to run the certification kit from a Windows Service and with administrative priveldges.
Is this possible to do?
The app cert kit runs interactively and therefore I suspect it would work properly as a Windows Service. Even if you schedule it to run as a Windows task, it doesn't seem to work.
By default the app certification kit (current version 2.2) is installed at "C:\Program Files (x86)\Windows Kits\8.0\App Certification Kit\appcertui.exe". If you run it from the command line, it runs as a Windows program with user interface and asks you to select one of the three options: Validate Windows Store App, Validate Desktop App, and Validate Desktop Device App. If you select the first option, the program lists all the apps installed on the testing computer. Once you can select one ore more apps, it actually starts the app(s) you selected, and goes through the testing process.
Hy,
I've create a setup for my vb application with visual studio.
At the end of the install I want to launch the application so i've add a custom action and used the chell to launch it. It's work but... the application is launch as SYSTEM user...
is there a way to launch it in normal user (on win7 as administrator)?
Thanks for your help
If you are installing the application as an Administrator and launching the application, then it will start under that identity.
Try installing the application as a non Admin user and see under what identity the application launches.
If it still requires Admin access, then look at the privileges requested in your config file.
I'm looking for suggestions on keeping a program that is running on a network updated. Installation consists of 15 users, each have the program on their local pc, but they all access same date from sql server.
I am looking for a clean method that would allow me to update one folder on the network and for each computer to get updated when they run the program and the programs sees a later ver on that folder on the network. (Obviously I can do this inside the program itself since it won't allow being overwritten while opened.)
You should have a look at
ClickOnce is a deployment technology
that enables self-updating
Windows-based applications that can be
installed and run with minimal user
interaction.
Using ClickOnce Deployment in
VB.NET
ClickOnce - A new VB.NET 2005 Deployment Tool
ClickOnce Deployment for Windows Forms Applications
ClickOnce Deployment in .NET Framework 2.0
Another option is to create a second program that will check the network for an updated version of your application. Let's call this program "updater.exe".
You can run updater.exe on system startup like Adobe Reader or Sun Java do.
Or, when your application is started it can load updater.exe. If updater.exe finds an update, it can close/unload your application, download the newer version, restart your application and close itself.
astander's answer above is correct, you can use ClickOnce for this. Another option is creating this application as a web application.
Web applications basically work the way you described, the application's files reside in a web server, all the users connect to it using a browser, and to update the application you only need to update the files in the server.