|
| | | Junior Member
 
Group: Forum Members
Last Login: 7/25/2007 6:29:22 AM
Posts: 16, Visits: 19 |
| | Hi, We're having problems packaging Microsoft Activesync 4.2. For some reason, Picturetaker adds the complete content of the c:\windows\$hf_mig$-folder to the package, although none of the files have changed in any way. It also adds a lot of folders and registrykeys, all related to Windows Updates. This happens on both a VMWare- and a physical machine with Automatic Updates turned off and is the only installation that behaves like this. Is this a known problem? Regards, Raymond |
| |
| | | 
Supreme Being
Group: Moderators
Last Login: 8/8/2008 12:14:02 PM
Posts: 657, Visits: 793 |
| We will do some testing and post our findings and recommendations.
New Boundary Technologies Support
support@newboundary.com |
| |
| | |
Supreme Being
Group: Moderators
Last Login: 8/8/2008 12:14:02 PM
Posts: 657, Visits: 793 |
| | We were able to successfully create a package for Microsoft ActiveSync 4.2. The $hf_mig% was not captured in our package. If it is being captured in yours, Prism must be detecting some change. Perhaps a time stamp is changing, or permissions on the folder? You could add a line to Prism's rules.ini file to ignore the folder. This is done on the system where you're building the Package. Make sure the Editor is closed. Then open C:\Program Files\Prism Suite\rules.ini. Go to the [Ignore Folders] section. Add this line: key=$hf_mig%. Save the file and reopen the Editor. Now when you take your baseline picture, that folder will not be captured.
New Boundary Technologies Support
support@newboundary.com |
| |
| | | Junior Member
Group: Forum Members
Last Login: 7/25/2007 6:29:22 AM
Posts: 16, Visits: 19 |
| | Thank you for your research. There was a change in permissions indeed. This happened because the Windows installation was originally built in FAT32 file system and later converted to NTFS. Some folder permissions were not standard and Activesync setup changed the permissions back into the default permissions used by a full NTFS Windows install. This leads to a feature request: would it be possible to show folders and files that have their permissions changed in a different colour in the package editor? It would save us a huge amount of time discovering were permissions are set in a package. Regards, Raymond |
| |
| | |
Supreme Being
Group: Moderators
Last Login: 8/8/2008 12:14:02 PM
Posts: 657, Visits: 793 |
| I will pass your feature request along to our product management team. Thanks for your input!
New Boundary Technologies Support
support@newboundary.com |
| |
|
|