Interesting. I've seen some fails like that, but it's been a long time - circa w2k. I've assumed it was due to my over-aggressive cleaning of local files. I've not kept any non-active install msi files for about the same time period.
I can't point to any documentation one way or the other, but I'm not aware of any changes to packaging that would affect this behavior, but I'm certainly interested in hearing about any. Sent from my Palm Pre on the Now Network from Sprint ________________________________ On Oct 31, 2011 6:50 PM, Ben Scott <[email protected]> wrote: On Mon, Oct 31, 2011 at 7:41 PM, Crawford, Scott <[email protected]> wrote: > The original install msi gets cached locally so you don't need to keep the old > versions on the network for an uninstall... That's definitely not always the case. I've had updates and uninstalls prompt for original install sources before. I think it has something to do with the way the package is built and/or the version(s) of MSI involved, but don't know for sure. I haven't seen such a prompt in a while, but I've also adopted a strict policy of only installing from "permanent" network locations, so I wouldn't see them anyway. -- Ben ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe ntsysadmin ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe ntsysadmin
