Program Fails when ran as System user SCCM 2007 R3/ W7 Clients

Re:Program Fails when ran as System user SCCM 2007 R3/ W7 Clients (colin)

Tue, 24 Apr 2012 06:40:57 GMT

Update.....having enabled the log, this let me get an exact error message out;
MoveFile failed; code 5.
Which I then googled - although I didn't find an answer, I found someone who was adamant that their AV was causing the problem - despite having sort of ruled this out so far (because it installs ok as another user) I followed up on this & scoured our EPO to find anything likely - and there it was - bold as brass. HIPS was blocking the install action for winvnc.exe.

Then discovered an allow rule for any IT users! That pretty much explains it - now hopefully I can get this sorted. Not sure why this only affected some clients - supposedly we should all be standard, but obviously not quite!

Thanks for any head scratching done on my behalf.
Colin

Re:Program Fails when ran as System user SCCM 2007 R3/ W7 Clients (colin)

Tue, 24 Apr 2012 04:28:50 GMT

Thanks gjones. I ve seen some of it before, but not all. I hadn't come accross the /log switch - im trying that now.

The new msi is interesting too, but that will mean me reinventing what I have done so far, so Im a bit hesitant to try that yet.

Regards

Colin

Re:Program Fails when ran as System user SCCM 2007 R3/ W7 Clients (gjones)

Mon, 23 Apr 2012 18:21:40 GMT

Have you seen this?
http://itninja.com/question/ultravnc-1-0-8-silent-install

Program Fails when ran as System user SCCM 2007 R3/ W7 Clients (colin)

Mon, 23 Apr 2012 09:36:48 GMT

Hi,

I have a frustrating problem that I am struggling to make any progress on at the moment. Hoping someone here may be able to point me in the right direction.

I have program that I am using to install Ultra VNC that is unpredictably timing out on some machines (45 %) . It uses a custom setup.exe made using INNO IDE, called using a vbscript (that does a few other things). As far as I can see the setup.exe is process is being created as well as a setup.tmp process & between them they start the install operations, but then come to a stop. These processes do not close, so the script never completes. Originally this seemed to me like there was a dialogue popping up somewhere under system context & so it was waiting a response. However when ran as the user, no dialogue appears.

In trying to further diagnose (on the same machine) I used PSEXEC to run the program remotely under my admin credentials - this succeeded. I then retried running the program using psexec as SYSTEM and that failed.

I don't understand that - Can any one suggest why the SYSTEM account might fail where a user account succeeds ?

I have also tried running procmon on an affected system tosee what's going on - only thing I noticed was an' Access Denied' showing up towards the tail off inactivity from the 2 setup processes (after which they don't do anything at all). Sadly I had to look at this in a hurry & I did not get round to making accurate notes/ taking a save of the capture. Needless to say I will do when I next recreate!

Any help appreciated.

Thanks

Colin