3 Replies Latest reply on Jul 1, 2010 4:10 PM by jstanley

    How to disable the outlook Addin by using EPO

      I want to disable the Outlook Scan Addin global in my company.

      I think that should work via the policy you can see in my attachment.

       

      Is that right?

       

      best regards and thank you for your help - thomas

        • 1. Re: How to disable the outlook Addin by using EPO
          Sk1dMARK

          That is correct.  If you uncheck that box, the scanner should no longer scan email.

           

          EDIT:  Also, if you decide that you will never use that feature, you can exclude it from future VSE installs by inserting "ADDLOCAL=ALL REMOVE=EmailScan" (no quotes, of course) into the command line box under the VSE entry in the deployment task.

           

          Hope this helps.

           

           

          Regards,

           

          Mark

           

           

          Message was edited by: Sk1dMARK on 7/1/10 12:45:06 PM EDT
          • 2. Re: How to disable the outlook Addin by using EPO
            rmetzger

            thomas.bugl wrote:

             

            I want to disable the Outlook Scan Addin global in my company.

            I think that should work via the policy you can see in my attachment.

             

            Is that right?

            Hi Thomas,

             

            Sk1dMARK's reply will help greatly, but you may still have an error message at the client side due to the design flaw (in my humble opinion) built into Outlook (Extend.Dat).

             

            Outlook stores the 'add-ins' in a cache file called Extend.dat locally. It's purpose is to increase performance of Outlook during the launch process. The improvement is suppose to be faster than reading the registry for the same information. However, after removing or changing an add-in, the Extend.Dat file may not be in-sync with the information in the registry. Outlook uses the info in Extend.dat in preference to the info listed in the registry without a check for correctness. At that time or sometimes a bit later, Outlook may complain that the Outlook is not working correctly and incorrectly suggest that Outlook needs to be rebuilt. (Other bogus messages as well.)

             

            In reality, Extend.Dat needs to be deleted. Extend.Dat is automatically rebuilt the next time Outlook is launched. Outlook rebuilds Extend.dat by using the correct list of Add-ins listed in the registry. Now, Extend.dat is in-sync with the actual add-ins installed.

             

            Unfortunately, Outlook cannot be  running when the deletion is attempted as Extend.dat may be locked.

             

            To that end, I have successfully  deleted the Extend.Dat file as part of the 'upgrade' process. I usually  install VSE as part of a batch file. After the VSE setup is run, I  follow up with the deletion of Extend.Dat. This could also be added to a Login Script. In order to clean up multiple  users (profiles) I use a command like this:

            del /f /s /q "%UserProfile%\..\Extend.dat"

            Note  that this command deletes Extend.Dat from multiple user (profile)  directories to which the logged in user has sufficient rights.

             

            ePO can be  used to upgrade VSE. As Sk1dMARK suggested, unchecking that box, will disable the currently installed add-in, but Extend.dat may not be up to date with that change. Yes, a MID version can be constructed to install  VSE without the email scanner Add-on. But even if you upgrade  successfully from ePO, the Extend.Dat file may still list the old add-on  which still needs to be removed. So, deleting Extend.Dat may be needed.

             

            Hope this is helpful.

            Ron Metzger