Not deployed to Windows 7, but in the past any 1603 errors I had were to do with permissions. I would install using domain\administrator account.

Steve.

I don't know if this is the same problem but when I was testing our deployment process on vista the only way I could do the software installs was to set up an autologin for the same user that was doing the installs.  I haven't had a chance to test this in Windows 7 yet, but I would not be surprised if it was the same.

We have determined that software will successfully install if a user is logged on. Any ideas what changes to the system need to be made to allow software to be installed without a user logged in?

Is there something in the registry we can change to fix this? We would like a solution that does not involve changing to SCCM.

I hate SCCM.  I don't suggest going to it just yet.  They still have some growing up to do.  We are also having issues.  If you delete out the current user keys for the msi by editing the MSI with Wise, you get better results and it appears to work more often than not.  I am still currently testing it so I will let you know when I am done.

I had the same issue and disabled IPV6, and now I can deploy software pretty seemlessly to Windows 7. I have done it with both an Admin accont settings as well as using the system account.

Windows 7

If UAC is on, we have been using the "Default (Local System Account) option with reasonable sucess. We have only been able to get "run scripts" to run as a Domain account if UAC is turned off.

Hoping to help.

We are using DS 6.9 SP2, and I have found by disabeling IPV6 I can deploy software via an admin account or system account. Apparently the new DAgetn is supposed to work with IPV6, but I havent upgraded to SP3 yet to confirm.

Hope some of this helps.

can i upgrade altiris 6.8 to 6.9 sp3.what about the licenses?will they work?

I believe you should be able to upgrade.  As for the licenses, if you have an active AUP, you should be able to get an updated license file.