Jump to content

MDT error code 1639 and 1619 while deploying applications


Recommended Posts

Posted

Hi :)

I have been away from MDT for around 2-3 years so i can't even remember basic stuff.

I have build a vmware environment, with a windows server 2012r2 and im trying to deploy some application out to a virtual win 10.

 

Msiexec.exe /i QuickTime.msi /q Norestart ALLUSERS=2

\\xxx.xxx.xxx.xxx\DeploymentShare$\Applications\Apple QuickTime 7.76.80.95

 

 

 

Msiexec.exe /i fscs-12.00.648-exported-publikumsnet.msi /quiet

\\xxx.xxx.xxx.xxx.\Deploymentshare\Applications\f-secure 12.00.648

I have check that the client can see the application folder in the Deploymentshare

 

On the client i got two errors.

Applications Apple quicktime 7.76.80.95 returned an unexpected return code:1639

WARNING - unable to set working directory: (-2147024829)

Application F-secure F-secure 12.00.648 returned an unexpected return cod: 1619

 

 

i can see that 1639 is:

Invalid command line argument. Consult the Windows Installer SDK for detailed command line help

 

and 1619:

 

[TABLE=width: 557]

[TR]

[TD]This installation package could not be opened. Verify that the package exists and that you can access it, or contact the application vendor to verify that this is a valid Windows Installer package[/TD]

[/TR]

[/TABLE]

I don't understand why i'm getting this erros.?

 

Any help would be helpfull. :) ?

 

 

[TABLE=width: 557]

[TR]

[TD]This installation package could not be opened. Verify that the package exists and that you can access it, or contact the application vendor to verify that this is a valid Windows Installer package[/TD]

[/TR]

[/TABLE]

Posted

quiet is /QN for msiexec

after the msiexec /i id put the full path to where the installer is as you appear to put the path in after calling the quicktime.msi

 

check that the applications added to MDT that the paths to the installers are correct / the packages are present on the MDT server (depending on how you have added them to MDT)

Posted

I know it shouldn't affect it but can you try shorter path names without spaces, I had a few issues there before, very rarely though.

 

A useful thing is that MDT mounts the deployment share as the z: drive, sometimes it is worth declaring the path as z:\applications\......

 

Personally, I tend to make little batch files and run them with the command in pointed to the z: drive and then I can mount and test those work on a regular machine and then test them in an MDT task sequence.

 

I hope that makes sense

Posted
Msiexec.exe /i QuickTime.msi /q Norestart ALLUSERS=2

\\xxx.xxx.xxx.xxx\DeploymentShare$\Applications\Apple QuickTime 7.76.80.95

Shouldn't ALLUSERS=2 be ALLUSERS=1 so that QT is installed per machine rather than per user?

Posted

Sorry my bad.

 

I should have written it this way

 

This is how it looks in MDT

 

Quiet install command: Msiexec.exe /i QuickTime.msi /q Norestart ALLUSERS=2

Working directory:\\xxx.xxx.xxx.xxx\DeploymentShare$\Applications\Ap ple QuickTime 7.76.80.95

 

 

 

Quiet install command: Msiexec.exe /i fscs-12.00.648-exported-publikumsnet.msi /quiet

Working directory: \\xxx.xxx.xxx.xxx.\Deploymentshare\Applications\f-secure 12.00.648

Posted

Try these install commands...

 

msiexec.exe /i QuickTime.msi ALLUSERS=1 REBOOT=ReallySuppress /qn[/Code]

 
[code]msiexec.exe /i fscs-12.00.648-exported-publikumsnet.msi /qn

Posted
Try these install commands...

 

msiexec.exe /i QuickTime.msi ALLUSERS=1 REBOOT=ReallySuppress /qn

 

msiexec.exe /i fscs-12.00.648-exported-publikumsnet.msi /qn

 

 

Yes that worked. :) Thank you.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...