December, 2016

Deploying Creative Cloud Packages 2017

Quick Post on the install order of  - Use your favourite App Packaging Wrapper / PSADT

Update: CloseApp Line for PSADT: 

  1. If package has Exceptions
    Exceptions\ExceptionDeployer.exe --workflow=install --mode=pre --installLanguage=en_US
    Don't do en_GB - seems to break acrobat
  2. If package has Acrobat
    Build\Setup\APRO15.0\Adobe Acrobat\setup.exe
    Always do this where applicable or acrobat may break
    If you want to customize Acrobat customize the msi in here using the Acrobat DC Customization Wizard
  3. Run main setup
    Build\setup.exe --silent
    If you don't use silent, it never exits
  4. If package has exceptions
    Exceptions\ExceptionDeployer.exe --workflow=install --mode=post --installLanguage=en_US
  5. Firewall Exceptions
    Node.exe: netsh advfirewall firewall add rule name="Adobe Node"  dir=in action=allow program="%Programfiles%\adobe\adobe dreamweaver cc 2017\node\node.exe" enable=yes
    Scout.exe: netsh advfirewall firewall add rule name="Adobe Scout"  dir=in action=allow program="%Programfiles%\adobe scout cc\scout.exe" enable=yes
  6. Disable CC startup and set all office addins to only load if user chooses to
    regedit.exe /s AcrobatAddinReg.reg
    https://1drv.ms/t/s!Apq2Xflj18I1wGkFeyX_T3lbtM5G
  7. Remove shortcuts bat
    REM Delete Shortcuts
    del "%ALLUSERSPROFILE%\Microsoft\Windows\Start Menu\Programs\Adobe Creative Cloud.lnk" /F /Q
    del "%PUBLIC%\Desktop\Adobe Creative Cloud.lnk" /F /Q

 

If you are putting the apps in a base image you may need to run the main setup.exe if you want to avoid Acrobat crashing on first use.

Adobe CC Design 2017:
- No exceptions
- Has Acrobat DC

Adobe CC Enterprise 2017:
- Has exceptions
- Has Acrobat DC
- FW exclusion for Scout.exe
- FW exclusion for Node.exe

Adobe CC Exclusives 2017:
- Has exceptions
- FW exclusion for Scout.exe

Adobe CC Web 2017:
- Has exceptions
- FW exclusion for Node.exe

Acrobat Single Package
- No exceptions
- Has Acrobat DC

Disabling (Adobe's) Office Add-ins

I don't think outlook should be making PDFs.. You can disable the add-ins with group policy

Download Office ADMX files
2013: https://www.microsoft.com/en-au/download/details.aspx?id=35554

2016: https://www.microsoft.com/en-au/download/details.aspx?id=49030

Copy the files under ADMX to your policy central store

Now create a group policy, browse to

User Configuration > Administrative Template > Microsoft Outlook 2016 > Miscellaneous > List Of Manage add-ins

Edit the policy setting, click show

Then specify the add-ins you want to disable with a value 0

To block other add-ins you need to find the progID for the addin, they can be found in the registry for each app in the suite:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\Outlook\Addins or HKEY_CURRENT_USER\SOFTWARE\Microsoft\Office\Outlook\Addins

To block Adobe out of Office altogether:

Admin Templates - For each List of manage Add-ins

Microsoft Excel 2016:
PDFMaker.OfficeAddin 0

Microsoft Excel 2013:
PDFMaker.OfficeAddin 0

Microsoft Word 2016:
PDFMaker.OfficeAddin 0

Microsoft Word 2013:
PDFMaker.OfficeAddin 0

Microsoft Powerpoint 2016:
PDFMaker.OfficeAddin 0

Microsoft Powerpoint 2013:
PDFMaker.OfficeAddin 0

Microsoft Outlook 2016:
AdobeAcroOutlook.SendAsLink 0
PDFMOutlook.PDFMOutlook 0

Microsoft Outlook 2013:
AdobeAcroOutlook.SendAsLink 0
PDFMOutlook.PDFMOutlook 0

 

 

Another option (less harsh) is to change the load behaviour to 2 via registry after install or possibly a preference. This makes the plugin not loaded by default but allows the user to load it manually.

Example Reg https://1drv.ms/t/s!Apq2Xflj18I1wGkFeyX_T3lbtM5G