RE: Adobe 6.1 launches Windows Installer

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Bret (Bret_at_discussions.microsoft.com)
Date: 02/23/05 

Date: Wed, 23 Feb 2005 13:33:01 -0800

That’s not the answer that I was hoping for (hoping for a hotfix), but thank
you for it anyway. I don’t have SMS as of yet. I deployed messenger 5.1 with
a GPO, as an upgrade to 5.0. I'll play around with redeploying it or try some
scripting; meanwhile my desktop guy is running around like a mad man fixing
it upon request. You’d think that during beta testing of 5.1 someone would
have discovered this problem, especially since there was recently the same
problem with the journal viewer.
Thanks for your help.

"jcfarme" wrote:

> Bret, i have been working with Microsoft for the last 4 days to get a
> resolution or a work around. i have been testing their workaround and it
> seems to work but I am still not comfortable deploying it. They are saying
> that it could be anywhere from 2 days to 3 weeks before a hotfix is released
> or a product upgrade. In the meantime the workaround with an SMS deployment
> is to install using their msi and then launch Messenger through the start
> menu which will allow the Windows installer to self heal when a user launches
> it and bypass the configuration process. I am still seeing 2 errors in
> eventviewer but the configuration seems to finish and I haven't seen any more
> problems with Adoibe.
>
> "Bret" wrote:
>
> > I too would like to see an enterprise fix, not a home user work-around to the
> > Windows Installer “bug” that is affecting Adobe and Windows Messenger. After
> > all the main reason for me to upgrade to Windows Messenger 5.1 is for
> > compatibility with my Live Communications Server 2005 which is an enterprise
> > product...
> > It is not feasible for me to ask users to type “msiexec /x
> > {1F0BD960-6525-4FEE-B577-2473F77F1277}” it’s also not feasible to walk around
> > and manually fix it on hundreds of computers.
> >
> >
> > "jcfarme" wrote:
> >
> > > I am having the same problem with Windows Messenger and Abobe 6.1 though I am
> > > in an enterprise environment where it is not feasible to go and uninstall and
> > > reinstall the application on 50000 + machines. Since this is not just an
> > > application, but also fixes a security vulnerability, is there any effort
> > > underway to resolve the Windows installer issue.

Relevant Pages

  • Re: SMS Report displaying Winsows Installer Source
    ... Souce that you can define in SMS programs. ... report allowing me to list all programs and the Windows Installer Source. ...
    (microsoft.public.sms.admin)
  • Re: Force Push ALL SMS Packages
    ... SMS, so given the user are in the correct user group you only need one user ... But I think you will get better performance if you (from a script) ... If I was deploying applications using ...
    (microsoft.public.sms.swdist)
  • Re: Old workstation objects left in SMS after reimaging PC
    ... collections in SMS. ... Then, after deploying it to a user, he renames the machine based on ... Could you create an arbitrary prefix to the non-deployed machine name ...
    (microsoft.public.sms.admin)
  • Re: what is SMS self heal links
    ... The only thing I can think of the Windows Installer and MSI packages where applications "heal" reinstall when there is an error with it. ... Stefan Olsson ... System Management Blog: www.msfaq.se ... Kim Oppalfens - Sms Expert for lack of any other expertise ...
    (microsoft.public.sms.admin)
  • Is Messenger available for use via SMS anymore?
    ... I have recently aquired a windows mobile6 phone and would like to use ... messenger via SMS like i was able to do from ... I downloaded an older version of messenger so now at least I ... I have unlimited messages and all I really need is MSN via SMS! ...
    (microsoft.public.pocketpc)