Relevant mostly to OS X admins
As I prepared to upgrade my workplace’s Creative Cloud installations to CC 2014, I built a virtual machine in Fusion 6 using the same methods I would use to deploy a machine to a new creative hire- because snapshots make life easier for testing installs and configurations. On a separate build machine, I grabbed Creative Cloud Packager, and used it to build an installer for the full suite.
In order to save time, I copied the CCP output .pkg to the same external USB3 storage as the VM, and used Fusion’s Shared Folders feature to share that directory. The VM was happy to see the installer there, and run it from the GUI. The install started out as normal, but unexpectedly halted with a “The installation failed, contact vendor for assistance” dialog.
I started digging into /Library/Logs/Adobe/Installers, and saw that Adobe InDesign CC 2014 10.0 <datestamp>.log was the most recently written to log, so I examined it for details about the fail. Looking in the log, the following caught my attention
10/07/14 19:35:07:861 | [ERROR] | | OOBE | DE | | | | 63746 | DS015: Unable to read symlink target of source file “/Volumes/VMware Shared Folders/SeagateUSB3/Adobe CC 2014-all but Acrobat/Build/Adobe CC 2014-all but Acrobat_Install.pkg/Contents/Resources//Setup/IDSN10.0en_US/payloads/AdobeInDesign10AppBase-mul/OEM_/Adobe InDesign CC 2014/Plug-Ins/InCopyWorkFlow/Assignment UI.InDesignPlugin/Assignment UI”(Seq 11962)
So I see we couldn’t find the target of a simlink. Digging down that path in the pkg from the VM, we see
Yep, Assignment and Resources are broken. So what if we look at the same path from the mac that hosts the VM?
Assignment has the same icon, but if I follow the symlink while viewing the content in the host OS, it resolves to:
You can see the icon difference between Resources, and it too works.
To move on, I copied the .pkg onto the VM’s boot disk, which had to be done via an AFP share- a copy from the shared folder failed with an Error 41. That copied pkg installed without errors.
Bottom line: things can go wrong with your testing VM if your source .pkg is stored on a shared folder in VMWare Fusion.