Client Management Suite

Ok I'm positive u26 we did not have this problem but now we are all of a sudden having issues deploying this package.  Currently trying u29 and works just fine on our xp systems but will not deploy on our 7 boxes.

Basically it is the strangest thing I have seen so far with package deployment.  I get 1619 error codes I have logging enabled in the command line to see what is going on but it never gets far enough to log.  So I started a run that is not silent.

Here is what happens:

The first two images are what happens when run by altiris Quick Delivery basically as you can see the Java setup runs and you click install and it gives that second image failure and altiris returns 1619.

The bottem image with the command  window shows the exact command altiris runs but it runs successfully under my user account.

If the EXE was downloaded from the internet, the file attributes will reflect this source and your Win 7 security may be preventing installation in case it is a virus. If I recall correctly, copying such EXE files to a FAT32 USB key or file system will remove the attributes, after which you can copy the file back and give it another try.

You can also run the EXE and look in the Application Data (Appdata) folder for the unpacked MSI installer that is inside the EXE, and use that for installation along with any MST transform file you want to add to configure the install (eg to turn off auto updates).

More details on www.appdeploy.com/packages

if the attributes was the issue then why can I run the exe manually from my account?  Also if I right click on the file I do not have the unblock option available.  So if it is an attribute please give me more details.

Also if it was an attribute I would think it would prevent the exe from ever running which it does not.  It allows the exe to run as you can see from my images.  It just fails once the Install is kicked off on the exe options.

Logs from Install Attempt:

Log Name:      Application
Source:        MsiInstaller
Date:          10/24/2011 10:09:42 AM
Event ID:      1040
Task Category: None
Level:         Information
Keywords:      Classic
User:          SYSTEM
Computer:      ber-lt-1073.domain.com
Description:
Beginning a Windows Installer transaction: C:\Windows\system32\config\systemprofile\AppData\LocalLow\Sun\Java\jre1.6.0_29\jre1.6.0_29.msi. Client Process Id: 504.

Log Name:      Application
Source:        MsiInstaller
Date:          10/24/2011 10:09:42 AM
Event ID:      1042
Task Category: None
Level:         Information
Keywords:      Classic
User:          SYSTEM
Computer:      ber-lt-1073.domain.com
Description:
Ending a Windows Installer transaction: C:\Windows\system32\config\systemprofile\AppData\LocalLow\Sun\Java\jre1.6.0_29\jre1.6.0_29.msi. Client Process Id: 504.

Ok I may have found the issue but I have no idea how to fix it:

The log says it is running the install from:

C:\Windows\system32\config\systemprofile\AppData\LocalLow\Sun\Java\jre1.6.0_29\jre1.6.0_29.msi

If I go to this location while the first dialog is up (Welcome) this above location is blank.  So the MSI appears to not exist.

If I go to:

C:\Users\jlawson\AppData\LocalLow\Sun\Java\jre1.6.0_29

There is an msi file but I think this is left over from my local install.

Found a potential fix:

http://community.landesk.com/support/message/62547

 I was speaking about this issue with our Microsoft rep that is onsite and he sent me a link that cleared my issue up.  Here is the link and the issue that seems to have been causing my problem.

 

"\Using procmon I found it was getting this path -
%systemroot%\system32\config\systemprofile from HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList\S-1-5-18. Likewise there is a similar key HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows NT\CurrentVersion\ProfileList\S-1-5-18 which is also set to %systemroot%\system32\config\systemprofile. If I set the wow6432node one to %systemroot%\syswow64\config\systemprofile instead, then the Java installer runs as the SYSTEM account. I'll do more testing, but more is welcome.

This is what is going on.  If I look the msi file gets put here:

C:\Windows\SysWOW64\config\systemprofile\AppData\LocalLow\Sun\Java\jre1.6.0_29\jre1.6.0_29.msi

not:

C:\Windows\system32\config\systemprofile\AppData\LocalLow\Sun\Java\jre1.6.0_29\jre1.6.0_29.msi

where it is looking.

Unless someone as a suggestion it looks like I may have to go to using the MSI for this install.