Deployment Solution

I am having a problem only with some programs and deployment to Win7...

If I use the Default (local System account it sits and does not install). This only happens with some programs. If I log in as this account it works fine or run as user (assuming logged in user is a admin)

We are a enterprise network with well in excess of 80,000 Workstations. So admins being logged in to a computer for many installs is very impractical.

Any advanced setting or commands that might ease the proccess or even wise old altiris sage advice.

Thanks,

Rob

Just a bit more information. Some installs work great...

But it seems that anything I have issues making Silent and become non-silent it will not allow it to install.

Thanks for any help.

Copy the install files local to the client, then copy a batch file local to the client to install the software with silent mode.

The batch file coul remove the install files after install.

Nelo

Hallo Maveriiik

First off you could try Nelo's suggestion, but i must admit i earlier have seen a problem on win7 with the Dagent, and some c++ runtime errors (this specific software was a citrix plug-in).

Just to rule out that this is the problem, try uninstalling the dagent, and then install the old aclient, i'm not saying this a solution, but it could help you in the testing. ;)

Kind Regards
Morten Leth

Have you taken a look at the Event logs. We have found out that when a machine records a registry entry for a need to reboot by the MSi installer, the altiris job will not install. But rather gives a status of complete when infact the job did not run.

Hallo Maveriiik,

Have you progressed any? I admit I am not clear from your posts whether you've managed to get your software packaged appropriately to that it installs silently (without dialogues).

Can you let us know what software you have a problem with, how you are installing it, and what happens if you run the install script manually?

It might be that you just need to spend a bit more time packaging the product.

Kind Regards,
Ian./

I noticed something similar and at times, you may have to unblock the installer first before copying it over to the client (right click, select properties and at times you have an "Unblock" button). This mostly happens if you download an installer from the Internet (i.e. standalone installers for JRE, Flash, etc).

An alternative to find out what is happening is to run the script / command in console user session against a single machine and you will be presented with either an error, UAC prompt or other messages.

As the others mentioned, some feedback would be appreciated,

-BBC

I think we had this problem when we first started moving to Windows 7.  I would suggest using the Security context - Specific User and use a domain account that has admin rights on the computer.  The problem might have something to do with the fact that if you try to run the program locally it will tell you that you need to be an admin to install this, even if you are logged in as an admin, but if you do a right click and Run as Administrator, the install will work. 

We have been deploying Windows 7 computers for about a year now without any problems with any software installs.  With the Specific user, we do always use the Run Script task instead of the Distribute Software task as it usually runs better and will wait for the install to finish (on most installs) before moving to the next task/job. Also all our installs are run directly from the server instead of copying them locally.