![]() ![]() HKEY_LOCAL_MACHINE\Software\Wow6432Node\Microsoft\Office\Outlook\Addins\PdfmOutlook.PDFMOutlookĮxit Registry Editor, and then start Outlook.įind and select the following key in the registry:.HKEY_LOCAL_MACHINE\software\microsoft\office\Outlook\addins\PdfmOutlook.PDFMOutlook.If the PdfmOutlook.PDFMOutlook key does not exist, go to step 2.If the PdfmOutlook.PDFMOutlook key exists, modify the Load Behavior value under the key to 0, and then go to step 2.HKEY_CURRENT_USER\software\microsoft\office\Outlook\addins\PdfmOutlook.PDFMOutlook HKEY_LOCAL_MACHINE\Software\Wow6432Node\Microsoft\Office\\Addins\PDFMaker.OfficeAddinĮxit Registry Editor, and then start the Office program.HKEY_LOCAL_MACHINE\Software\Microsoft\Office\\Addins\PDFMaker.OfficeAddin.Repeat step 1 with each of the following registry keys: If the PDFmaker.Addin key does not exist, go to step 2.If the PDFmaker.Addin key exists, modify the Load Behavior value under the key to 0, and then go to step 2.HKEY_CURRENT_USER\software\microsoft\office\\addins\Pdfmaker.OfficeAddin Locate and select the following registry key: The placeholder represents the name of the Office program that you're having issues with when the PDFMaker add-in was installed. If you cannot disable the add-in by following these steps, use one of the following methods. Clear the Acrobat PDFMaker Office COM Addin check box, as follows (Office 2010 screen shot), and then select OK.In the Manage drop-down list, select COM Add-Ins, and then select Go.Open the Office program, and then select File > Options > Add-ins.If you have administrative permissions, you can also disable the add-in by following these steps in each Office program: Method 2: Manually disable Acrobat PDFMaker Office COM Add-in Supported PDFMaker add-in versions (check PDFMOfficeAddin.dll version) If you're an advanced user and want to check the PDFMOfficeAddin.dll version compatibility, see the following table. If your version isn't compatible, try to upgrade your Adobe product to a later version that's compatible with your Office version. See Compatible web browsers and PDFMaker applications to determine which version of the Adobe Acrobat PDFMaker Office COM add-in is compatible with your Office version. Then create a collection like below - having a check for Acrobat being installed prevents false negatives as described in Chuck's entry.Fees may apply when you upgrade your Adobe product. New-ItemProperty -Path $registryPath -Name InstalledVersion -Value $Version -PropertyType String -ForceĪfter the registry has an entry, set up a Scan Profile in PDQ for "SOFTWARE\Adobe\Adobe Acrobat\2017\InstalledVersion". $registryPath = "HKLM:\SOFTWARE\Adobe\Adobe Acrobat\2017\" ![]() If you have a different Acrobat product the file path and name may be different. I just wrote a quick script to take the Adobe SWID serial number and translate it to Pro/Standard. This thread just reminded me I was going to get around to this problem. If I don't see Acrobat DC installed, I go back and deleted the swidtag file. In my case, I just look at the installed apps on a suspicious computer. Thus, you may get some false positives in your dynamic group. when Acrobat is uninstalled on a pc it does not appear the files in the folder are removed . You should see them roll right on into your dynamic groups.įilenames or paths listed above may change on future Acrobat version but this works as of today 4/4/18. Test by scanning a few computers you have Pro or Std installed on. > Name > Equals > _AcrobatPro-AS1-Win-GM-MUL.swidtagĬ:\ProgramData\\_AcrobatStd-AS1-Win-GM-MUL.swidtagĬ:\ProgramData\\_AcrobatPro-AS1-Win-GM-MUL.swidtag In each dynamic group, add two value filters.įile > Path > equals > c:\ProgramData\įile > Name > Equals > _AcrobatStd-AS1-Win-GM-MUL.swidtagįile > Path > Equals > C:\ProgramData\įile. Star by creating a dynamic group for each. std) installed but I found they have added that info to the swidtag filename which makes it much easier to break them out into dynamic groups, pro or standard. The Adobe Acrobat Admin Guide says you have to find the serial number in the swidtag file to determine the version (pro vs. We have a volume license and need to be sure we are in compliance. We really need ot break out the DC installs by Pro or Standard so we can keep track of our licenses. I know this post is kind of old but I encountered the same issue and found a way to resolve it so I figured I'd share. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |