ActiveSync 4.1 Re-package & File Conversion
Hi,
Problem with file conversion types not listed.
I've successfully recreated the ActiveSync 4.1 MSI using Wise 6.1 which updates all previous versions and can be installed using group policy as a locked down user. Everything appears to be working except for file conversion. There are 2 entries listed in the Device to Computer convert screen with generic icons and nothing in the Computer to Device list. I know on the same machine with the original MSI there is 12 entries in one and 13 in the other. Installing the program as an Admin makes no difference to the list.
It seems my MSI has the correct information listed in:
HKCU\Software\Microsoft\Windows CE Services\[parnership]\.....
HKLM\Software\Microsoft\Windows CE Services\Filters\
I suspect there could be a problem with some of the HKCR\CLSID entries. But I'm unsure how Activesync is reading the registry to populate the list. I haven't spent much time using regmon as yet. Has anyone come accross this or a similar problem and how can I go about fixing it?
cheers
techbot.
Problem with file conversion types not listed.
I've successfully recreated the ActiveSync 4.1 MSI using Wise 6.1 which updates all previous versions and can be installed using group policy as a locked down user. Everything appears to be working except for file conversion. There are 2 entries listed in the Device to Computer convert screen with generic icons and nothing in the Computer to Device list. I know on the same machine with the original MSI there is 12 entries in one and 13 in the other. Installing the program as an Admin makes no difference to the list.
It seems my MSI has the correct information listed in:
HKCU\Software\Microsoft\Windows CE Services\[parnership]\.....
HKLM\Software\Microsoft\Windows CE Services\Filters\
I suspect there could be a problem with some of the HKCR\CLSID entries. But I'm unsure how Activesync is reading the registry to populate the list. I haven't spent much time using regmon as yet. Has anyone come accross this or a similar problem and how can I go about fixing it?
cheers
techbot.
0 Comments
[ + ] Show comments
Answers (3)
Please log in to answer
Posted by:
wiseapp
18 years ago
Hi techbot:
Would suggest that you should login as locked down user (with little rights to run and edit registries/regmon) run regmon and in the filter dialog of regmon enter "Access Denied" run your application along with the mobile device connected and see what all registries hives do not have permissions. If there are enteries which do not have sufficient rights then run cacles or subinacles to give the particular subregistry the rights. Hope this should be of some help to you...
Would suggest that you should login as locked down user (with little rights to run and edit registries/regmon) run regmon and in the filter dialog of regmon enter "Access Denied" run your application along with the mobile device connected and see what all registries hives do not have permissions. If there are enteries which do not have sufficient rights then run cacles or subinacles to give the particular subregistry the rights. Hope this should be of some help to you...
Posted by:
techbot
18 years ago
Hey WiseApp,
The thing is, even installing it as an admin and logged on as admin the File Conversion list still doens't list all the file types.
Under Device to Desktop, there is currently just
InkWriter Template *.pdt *.pdt
Pocket Word Template-H/PC *.pwt *.pwt
Under Desktop to Device, there is nothing listed
cheers
techbot
The thing is, even installing it as an admin and logged on as admin the File Conversion list still doens't list all the file types.
Under Device to Desktop, there is currently just
InkWriter Template *.pdt *.pdt
Pocket Word Template-H/PC *.pwt *.pwt
Under Desktop to Device, there is nothing listed
cheers
techbot
Posted by:
wiseapp
18 years ago
Hi Techbot:
This seems to me a problem of repackaging, have tried repackaging the app again with snapshot and smartmonitor on a clean build? Since this seems that there are certain registry entries that have been missed while repackaging. One more suggestion have you tried putting the registry entries manually (the one's that are not appearing)?
This seems to me a problem of repackaging, have tried repackaging the app again with snapshot and smartmonitor on a clean build? Since this seems that there are certain registry entries that have been missed while repackaging. One more suggestion have you tried putting the registry entries manually (the one's that are not appearing)?
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.