Error during packaging GOOGLE DESKTOP 5.9
I am trying to package google desktop 5.9. During capturing I am getting errors that some LOCALAPPDATA folder files could not be copied. These files are required for packaging. Also in the .irp file I have a lot of registry entries which I am not able to see in the .ism file. These entries are from the HKCR registries and are related to shell extenstions.
After having packaged the application when i install the application I am not able to add or even see any gadget.The default gadgets in google desktop are the analog clock and the weather. When i try to add these I get an error that "the gadget failed to register check the manifest file".
Please help me with this.
After having packaged the application when i install the application I am not able to add or even see any gadget.The default gadgets in google desktop are the analog clock and the weather. When i try to add these I get an error that "the gadget failed to register check the manifest file".
Please help me with this.
0 Comments
[ + ] Show comments
Answers (5)
Please log in to answer
Posted by:
anonymous_9363
13 years ago
No, he's not.
BTW, who on God's green Earth let's this kind of junk loose on corporate desktops? And isn't there a different corporate version which is a) already packaged as an MSI and b) licensed differently? (Google Desktop Enterprise, or something like that?)
BTW, who on God's green Earth let's this kind of junk loose on corporate desktops? And isn't there a different corporate version which is a) already packaged as an MSI and b) licensed differently? (Google Desktop Enterprise, or something like that?)
Comments:
-
Yeah there is Enterprise version is available, it a MSI .... you just need to creat MSt to make the changes for .... corporation ..... - amjadrehman24 12 years ago
Posted by:
mahendraKumar
13 years ago
Hi ,
I believe the application requires reboot.
If u check in advance settings in IRP there is an checkbox for converting registry data to Appropriate COM tables. so if this option is checked then the Installsheild during the conversion of IRP to ISM it remove COM datas from reg keys and add same to tables.
Try to do a gap capture for the application to find out what are the missing components between your MSI and source.
That will give u more information.
Thanks,
MahendraKumar
I believe the application requires reboot.
If u check in advance settings in IRP there is an checkbox for converting registry data to Appropriate COM tables. so if this option is checked then the Installsheild during the conversion of IRP to ISM it remove COM datas from reg keys and add same to tables.
Try to do a gap capture for the application to find out what are the missing components between your MSI and source.
That will give u more information.
Thanks,
MahendraKumar
Posted by:
Apsawhney
13 years ago
Posted by:
amjadrehman24
12 years ago
Posted by:
amjadrehman24
12 years ago
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.