Windows Thread, psexec, msiexec, domain, permissions etc in Technical; Setup: RM Schoolshare with Storebox
Problem: I am trying to get WPKG up and running. All I now need to ...
27th February 2009, 11:09 AM #1
psexec, msiexec, domain, permissions etc
Setup: RM Schoolshare with Storebox
Problem: I am trying to get WPKG up and running. All I now need to do is push the client from the Storebox to the clients. I am using psexec and msiexec but think I am running into permission problems due to the fact that the Storebox is on its own domain but the clients are not members.
The client is on a share on the Storebox so I run the command
But this returns the error Code
psexec -i -u username
@hosts.txt -d msiexec /i "\\Storebox
\WPKG\WPKG Client 1.2.1.msi" /qb SETTINGSFILE=\\Storebox
As it runs ok from a local account I guess that this looks like a permissions problem. I assume the issue is that msiexec command runs it as the SYSTEM user which is not part of the Storebox domain? Error
"This installation error could not be opened. Verify that the package exists and you can acces it, or contact the application vendor to verify that this is a valid Windows Installer package"
So, is there anyway that I can run the command as a local user that is a domain account and could run the installer?
IDG Tech News
27th February 2009, 11:24 AM #2
psexec should run within the user context that you provide via -u if this is a domain admin account then it should be able to both run the task and grab the file.
I would test the permissions by attempting to use psexec to simply copy the file to the local hard drive. This will help you rule out file permissions to the storage box.
It looks like psexec has some issues with msi installs, some of which may be alleviated by adding the -e switch
PsTools: psexec - user credentials question
27th February 2009, 11:42 AM #3
Thanks for the reply.
Actually I have been trying to copy the file to test the permissions:
but fails with "Access denied" even when the -e flag is set. Code
>psexec \\target machine
/c copy "\\Storebox
\WPKG\WPKG Client 1.2.1.msi" "c:\WPKG install" -s
PsExec v1.94 - Execute processes remotely
Copyright (C) 2001-2008 Mark Russinovich
Sysinternals - Windows Sysinternals: Documentation, downloads and additional resources
Access is denied.
cmd exited on target machine
with error code 1.
Run locally this works, so I guess the profile isn't being loaded.
Last edited by sparkeh; 27th February 2009 at 11:45 AM.
27th February 2009, 11:46 AM #4
How about PSexecing a bat file that maps a drive with the required credentials then runs the setup then unmaps the drive.
Or for the most roundabout way you could try PSexecing the RUNAS command on the remote machine
You could also just try remotely scheduling it to run immediatly under your domain admin account:
How To Use the AT Command to Schedule Tasks
Last edited by SYNACK; 27th February 2009 at 11:50 AM.
27th February 2009, 03:52 PM #5
Might be clutching at straws/barking up the wrong tree here but if the MSI is failing, is that because you're starting the msiexec process as "you" but that then gets passed to the installer service which I think then runs in the context of the local machine account. Do "domain computers" have read access to the relevant share?
This could be a red herring because the copy doesn't work (but that "-s" at the end will cause problems, I think)
27th February 2009, 09:06 PM #6
Thanks for the input guys but after trying many approaches I realised I had spent too much time on it and put aside the rest of the day to manually install
I found that the problem wasn't limited to the msi, any psexec operation that involved just a 'read' operation to a file worked but any 'write' or 'execute' failed.
Have been wondering this myself, but I checked the profile that the commands is running under and it seems to be initiated by the correct user account with the correct domain permissions.
Originally Posted by srochford
After doing a fair bit of reading, I have seen a lot of people saying that using psexec to install an msi is hit and miss at best due to the complexity of them. Anyway, now I have WPKG installed, remote deployment of software shouldn't be a problem anymore.
Yeah not sure why that is there but also doesn't work without it
Originally Posted by srochford
By Ben_Stanton in forum Windows
Last Post: 17th June 2008, 01:41 PM
By galloshes in forum Windows
Last Post: 27th March 2008, 03:06 AM
By sqdge in forum Windows
Last Post: 23rd January 2008, 12:39 PM
By Halfmad in forum Windows
Last Post: 11th June 2007, 09:31 AM
By tosca925 in forum Windows
Last Post: 10th September 2005, 11:22 AM
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)