dov08
Posts: 10
Joined: 3/27/2009 Status: offline
|
Forget it, i've finally found what was going wrong. So for those who have the same issue as me packaging with appdeploy repackager and failed to deploy via GPO, here what you need to do ! First of all, in order to see if it's really the same issue as me, use wininstall LE. open your MSI, open the advanced tab in the general one ! Go to sequence > publication > execution. If you have nothing there, it's normal you can not deploy. There is also nothing under administration > execution. I do not know why when packaging with appdeploy, these tables are not populated. In a second time, use ORCA in order to export the two following tables (i'm exporting 4 templates : AdminExecuteSequence, AdminUISequence, AdvtExecuteSequence, AdvtUISequence. The 2 ExecuteSequence should by sufficient) of a package that you are able to deploy (for exemple, create a basic package with wininstall LE). The ORCA tool will create 2 .idt files that you'll store where you wish. After that step, open the appdeploy package you're unable to deploy via GPO and import the 2 tables you've just exported ! And let's try now to redeploy your MSI ! Hopefully, That should work ! Personnaly i prefer doing that that way as i've many less issues creating Basic MSIs using appdeploy repackager tool. When using a full wininstall LE packaging, i've troubles with multiple users as each time a user logs in, the install tries to reach the original MSI stored in the LAN server. I let you imagine if you wish to login as a local user or disconnected from the LAN ! BRGDS every one ...
|