51 lines
5.5 KiB
Plaintext
51 lines
5.5 KiB
Plaintext
{\rtf1\ansi\ansicpg1252\deff0\deflang1033{\fonttbl{\f0\fswiss\fcharset0 Arial;}{\f1\fswiss\fprq2\fcharset0 Arial;}{\f2\fnil\fcharset2 Symbol;}}
|
||
{\colortbl ;\red0\green0\blue0;\red0\green0\blue255;\red0\green0\blue128;}
|
||
\viewkind4\uc1\pard\fi-1800\li1800\tx1800\cf1\b\f0\fs20 From:\b0\tab Chris Steck (Exchange)\par
|
||
\b Sent:\b0\tab Wednesday, December 08, 1999 6:29 PM\par
|
||
\b To:\b0\tab Alex Armanasu (Exchange); Henry Lee (Exchange); Weiru Cai (Exchange); Murthy Srinivas (Exchange); Michele Freed (Exchange); John Delo (Exchange)\par
|
||
\b Cc:\b0\tab Craig Marl (Meridian Partners Ltd.) (Exchange)\par
|
||
\b Subject:\b0\tab Belated minutes from 12/2 manifest mtg.\par
|
||
\pard\cf0 Sorry for the delay in getting these out. If you have an action below, please reply to me with your status and I'll send an update. -Chris\par
|
||
=========================\par
|
||
Last week the To line met to discuss our course of action wrt manifests for legacy apps.\par
|
||
\par
|
||
We enumerated the issues and determined a continuing course of action, reviewed latest enhancements/fixes made to tools by John and assigned action items for next steps \par
|
||
\par
|
||
\b\fs24 Enumerated Issues and resultant action items\par
|
||
\b0\fs20\par
|
||
\b Tool related blocking issues/bugs\b0\par
|
||
\pard{\pntext\f2\'B7\tab}{\*\pn\pnlvlblt\pnf2\pnindent0{\pntxtb\'B7}}\fi-380\li380 Sysdiff will sometimes report a sharing violation, required a private build by Henry. \cf2\b AI:\b0 \b HenryLee\b0 , please elaborate to determine when/if we need to depend on the private build or not.)\cf0\par
|
||
{\pntext\f2\'B7\tab}Leaf nodes in registry can not be duplicates \par
|
||
\pard\li380\cf2\b AI: \b0 Fix by \b JohnDelo\b0 already code complete at time of meeting,\b All manifest creators\b0 should test.\cf0\par
|
||
\pard{\pntext\f2\'B7\tab}{\*\pn\pnlvlblt\pnf2\pnindent0{\pntxtb\'B7}}\fi-380\li380 MRU lists, cached paths of any kind can break when manifest run on target PC with different configuration. \par
|
||
\pard\li380\cf2\b AI:\b0 JohnDelo to add path relocation code to tools. -Status John?\par
|
||
\b AI: All manifests creators\b0 must go back and manually mark paths in manifests for conversion according to process \b John\b0 will outline.\par
|
||
\cf0\par
|
||
\pard\b Process related issues\b0\par
|
||
\pard{\pntext\f2\'B7\tab}{\*\pn\pnlvlblt\pnf2\pnindent0{\pntxtb\'B7}}\fi-380\li380 Takes minimum 1/2 to 1 day to generate a manifest using the current tools \par
|
||
{\pntext\f2\'B7\tab}Recognizing lists in the generated manifests and converting to a generic list type is a time consuming manual process requiring situational heuristics, and is subsequently highly prone to human errors both of execution and omission.\par
|
||
\pard\li380\cf2\b AI:\b0 We are just going to live with this for now, and \b ALL\b0 must manually munge the manifests they created to account for lists in the registry.\par
|
||
\pard{\pntext\f2\'B7\tab}{\*\pn\pnlvlblt\pnf2\pnindent0{\pntxtb\'B7}}\fi-380\li380\cf0 Unclear if we are all following the exact same procedures and using the same builds to create manifests.\par
|
||
\pard\li380\cf2\b AI: ChrisSte\b0 and \b Craig\b0 will generate brand new manifests using a "blessed" build of the tools. (no private builds!) \par
|
||
\b AI: ChrisSte\b0 to facilitate manifest check in process\par
|
||
\cf0\par
|
||
\pard\b Coverage holes (deficiencies in the tool's feature set and/or our process)\par
|
||
\pard{\pntext\f2\'B7\tab}{\*\pn\pnlvlblt\pnf2\pnindent0{\pntxtb\'B7}}\fi-380\li380\b0 How do we recognize and reflect dependencies on the order in which applications are installed in the manifests. \par
|
||
\pard\li380\i Example 1: Visio hooks into the Outlook Contacts if Outlook is present. If Outlook was installed prior to Visio on the source, those hooks will exist in its config.-But if user reinstalls Visio first via our manifest on the migration target, those hooks may also have migrated, but cause unexpected behavior in Visio since Outlook is not there.\i0\par
|
||
\pard{\pntext\f2\'B7\tab}{\*\pn\pnlvlblt\pnf2\pnindent0{\pntxtb\'B7}}\fi-380\li380 If an app normally installs a sub component, but doesn't if that component already exists, how do we reflect that logic in one generic manifest?\par
|
||
{\pntext\f2\'B7\tab}If config data is stored in a proprietary format and/or outside the profile, how do we know we are only extracting the stuff that is relative to the user? (and not say, the hardware)\par
|
||
\pard\li380\i Example: A graphic art app stores color settings for a particular video card/monitor pair on the user's PC. That info is stuffed in the same OLE stream in the registry as the user specific info. (like say his custom toolbar palette) -If the user moves to new hardware, how do we put back the toolbar without taking the monitor video card settings?\par
|
||
\cf2\b\i0 AI for all of above: Craig \b0 to investigate by comparing manifests created for Word 2k installed on a clean machine, and another created for Word 2k installed after the remainder of Office is already present.\par
|
||
\pard\par
|
||
\pard{\pntext\f2\'B7\tab}{\*\pn\pnlvlblt\pnf2\pnindent0{\pntxtb\'B7}}\fi-380\li380\cf0 We have not tried to create a manifest for a VB app.\par
|
||
\pard\li380\cf2\b AI: Craig will create manifest for Company Store app.\par
|
||
\par
|
||
\pard{\pntext\f2\'B7\tab}{\*\pn\pnlvlblt\pnf2\pnindent0{\pntxtb\'B7}}\fi-380\li380\cf0\b0 We need beta testers to beat on the tools\par
|
||
\pard\li380\cf2\b In addition to the rest of us, MurthyS, Mfreed and BShah\b0 will use manifests once they have been updated for lists and marked for paths.\cf0\par
|
||
\pard\par
|
||
\cf3\f1\fs28\par
|
||
\cf0\f0\fs20\par
|
||
\par
|
||
\pard\fi-1800\li1800\tx1800\cf1\par
|
||
}
|
||
|