I am on my personal Adobe Account so that I don't have reply e-mail going to the entire team but I digress.
In preparation for offering Adobe CS6 to our users, I have been working with Adobe's Application Manager Enterprise Edition for both PC and mac, producing deployment packages for installation on user's machines. To do this, I created a serialized install pkg of Design Standard, Design and Web Premium, and Master Collection CS6 from the volume install optical media. I have not tested this with the Design Standard Mac package or PC flavors yet, but I've confirmed the issue on both Design Premium and Master Collection for Mac.
For whatever reason, it seems like when InDesign CS6 starts up it gives some errors that plugins are invalid, and asks you to re-install them. Upon further investigation, it's all of the InCopyWorkflow plugins. This causes all the InCopy elements for InDesign to be missing (InCopy Document export, Assignments Panel, etc).
Does anyone know if this is a known bug in InDesign CS6? I can't imagine it was a corrupted installer as it's the exact same issue that's arisen from two separate install disks, and I need to be sure this is fixed before we start widely rolling out Adobe CS6 suites.
That said, I have found a workaround. Get a copy of the InCopyWorkflows Plugin folder from InCopy (Either from another system that has it or temporarilly install the InCopy CS6 trial) and replace the folder in the InDesign Plugins folder. That seems to have done the trick.
I'm going to continue poking around and see how widespread this issue is, and I'll report back what I find.
I've had the same problem after installing CS6. Mine is part of Pratt Institute's Faculty and Staff license, and I downloaded the installer directly from Adobe. After installation, all the InCopy plug-ins are being flagged on each InDesign CS6 launch.
I'll try the suggested fix, and will report back.
My workflow was as follows:
Rip volume DVDs to ISO
Extract install folder to desktop
Run AMEE, create serial package
At that point, I tossed the .pkg files up on the server. I suspect at this point it got corrupted.
I re-did my packaging doing everything on a virtual machine. The following worked for us:
1. Extract Installer from Volume DVD (For every version but MC, you could also save $$ and download a trial).
2. Run AMEE, build serial package
3. I used DropDMG to take folder with _install.plg and _uninstall.pkg and make it a read-only DMG that's password protected. This is a serialized package install, and we can't risk it getting left out.
North America
Europe, Middle East and Africa
Asia Pacific