Typically this is a result in the differences of the security/profile context that is executing the install. The differences can be in permissions, environment variables, etc.
What I would do is modify your tem.bat file so
1) echo is on
2) execute the set cmd in the second line
update your package with this new tem.bat file and re-test.
Now you should see all of the output etc in the channel's log file.
thanks for your answers
The test about if it is running under the SYSTEM account failed.
Siemens which is the producer if that application, tells us that they will try to make it ready in a previous version.
This will not help us for the actual problem.
can someone tell me how to install with marimba an application we a specific admin account?
In that case you can build a file/custom package for the .exe/.msi and define that the setup needs to be copied to a temporary folder.
Afterwards you can create a post script which triggers runasspc for the setup files after it is copied to the workstation.
You also need to specify that the script runs under logged in user credentials as you already said that the given command/application cannot be started with SYSTEM ACCOUNT.
yes, but the problem i see is.
this application will have to be installed when no user logged in becuase this clients will be installed in our deployment room. so i'm looking for a skript which i can place in a channel which makes a logon with for example localhost\administrator.
i found a tool whoch can do taht but only on machines where someone else is logged in but in my case there is nobody logged in.
it's interessting to hear form collegues which are working with altiris or SystemCenter they can run setups under a specific user :-(.
is this a .exe install? msi? or exe wrapping a msi?
There are a couple areas in the documentation to highlight: Application Packager page 155 - Working with packages that contain user-specific files
and registry entries
I am curious as to what's in the package that is preventing it from installing properly. Is it a 64bit OS? wondering if using the snap shot feature will help determine what's the specific hang up. At least you'd get to see where everything is being placed.
I mean that you need to create a scheduled task through a script. You can check the syntax for creating a scheduled task, by running the below command on command prompt:
schtasks /create /?
Use the arguments as per your requirement.
Also, if you want to debug the the package installation, above is a nice suggestion by Jake.