We include Acrobat and many other Adobe CC suite products in our image, The Creative Cloud Packaging tool has the ability to make the licensing package with an XML and EXE you can run to re-activate to software after deployment. Have to update it periodically as they update the CC suite but it has worked fine for us this way since the CC suite was released, though it is easier to create now.
On Thu, Jan 19, 2017 at 1:19 PM, Sean Chapman <schap...@coilcraft.com> wrote: > Yeah that’s way too much work. Unless you need a zero touch deployment I > would just activate the software after deployment. > > > > *From:* listsad...@lists.myitforum.com [mailto:listsadmin@lists. > myitforum.com] *On Behalf Of *Wood, Sandy > *Sent:* Thursday, January 19, 2017 12:00 PM > > *To:* mdtosd@lists.myitforum.com > *Subject:* [MDT-OSD] RE: Capturing an image with Adobe Acrobat > > > > I’ve been going over a post that looks to detail the steps of deploying > Acrobat in this way… > > > > https://roozbeh.io/adobe-acrobat-dc-2015/ > > > > > > > > *From:* listsad...@lists.myitforum.com [mailto:listsadmin@lists. > myitforum.com <listsad...@lists.myitforum.com>] *On Behalf Of *Sean > Chapman > *Sent:* Thursday, January 19, 2017 9:35 AM > *To:* mdtosd@lists.myitforum.com > *Subject:* [MDT-OSD] RE: Capturing an image with Adobe Acrobat > > > > Not that its one of the worst ones to figure out the quiet install command > but hopefully this is helpful for you to put into MDT. This is for Reader, > just change the msi for Acrobat > > > > msiexec /i AcroRead.msi EULA_ACCEPT=YES /qn > > > > > > *From:* listsad...@lists.myitforum.com [mailto:listsadmin@lists. > myitforum.com <listsad...@lists.myitforum.com>] *On Behalf Of *Wood, Sandy > *Sent:* Thursday, January 19, 2017 11:14 AM > *To:* mdtosd@lists.myitforum.com > *Subject:* [MDT-OSD] RE: Capturing an image with Adobe Acrobat > > > > I’m in the process of redoing the deployment to install it at the time of > deployment, not as part of the captured reference .wim. > > > > *From:* listsad...@lists.myitforum.com [mailto:listsadmin@lists. > myitforum.com <listsad...@lists.myitforum.com>] *On Behalf Of *Sean > Chapman > *Sent:* Thursday, January 19, 2017 8:37 AM > *To:* mdtosd@lists.myitforum.com > *Subject:* [MDT-OSD] RE: Capturing an image with Adobe Acrobat > > > > Adobe claims you have to unregister Acrobat before reusing the license on > another PC and for 4 years now I have checked before uninstalling Acrobat > to move to a different PC and it has always been greyed out except for 1 > time. I would imagine that prov.xml would be so that it doesn’t lock that > registration to a certain PC but I don’t think their system works how they > want it to and that prov.xml wouldn’t REALLY be needed, until it bites you > in the butt one day when the system actually works how it is supposed to. > > > > Imo I would just have it inject Acrobat DC as part of your OSD and not > include it preinstalled in the image and I would bet this would not be an > issue then for you to even worry about in the future. > > > > *From:* listsad...@lists.myitforum.com [mailto:listsadmin@lists. > myitforum.com <listsad...@lists.myitforum.com>] *On Behalf Of *Wood, Sandy > *Sent:* Thursday, January 19, 2017 10:11 AM > *To:* mdtosd@lists.myitforum.com > *Subject:* [MDT-OSD] Capturing an image with Adobe Acrobat > > > > We’ve been deploying some Win 10 tablets with Acrobat Pro DC on them. > We’ve installed most of the apps, including Acrobat, on a reference image > and then deployed that image to our tablets. We’ve not had any issues with > Acrobat so far. > > > > Today I read that If you image a machine with Acrobat I must first > generate a prov.xml file and then create a permanent offline exception that > is not machine specific. Sounds like I’ve been doing this all wrong. > > > > Is anyone doing this with their Acrobat deployments? > > > > Sandy Wood > > Network Engineer > Orange County District Attorney > (714) 347-8775 > (714) 824-0864 mobile > > > > > ------------------------------ > > > CONFIDENTIALITY NOTICE: This communication with its contents may contain > confidential and/or legally privileged information. It is solely for the > use of the intended recipient(s). Unauthorized interception, review, use or > disclosure is prohibited and may violate applicable laws including the > Electronic Communications Privacy Act. If you are not the intended > recipient, please contact the sender and destroy all copies of the > communication. > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > The information contained in this communication and all accompanying > documents from Coilcraft may be confidential and/or legally privileged, and > is intended only for the use of the recipient(s) named above. If you are > not the intended recipient you are hereby notified that any review, > disclosure, copying, distribution or the taking of any action in reliance > on the contents of this transmitted information is strictly prohibited. If > you have received this communication in error, please return it to the > sender immediately and destroy the original message or accompanying > materials and any copy thereof. If you have any questions concerning this > message, please contact the sender. > > > ------------------------------ > > > CONFIDENTIALITY NOTICE: This communication with its contents may contain > confidential and/or legally privileged information. It is solely for the > use of the intended recipient(s). Unauthorized interception, review, use or > disclosure is prohibited and may violate applicable laws including the > Electronic Communications Privacy Act. If you are not the intended > recipient, please contact the sender and destroy all copies of the > communication. > > > ------------------------------ > > > CONFIDENTIALITY NOTICE: This communication with its contents may contain > confidential and/or legally privileged information. It is solely for the > use of the intended recipient(s). Unauthorized interception, review, use or > disclosure is prohibited and may violate applicable laws including the > Electronic Communications Privacy Act. If you are not the intended > recipient, please contact the sender and destroy all copies of the > communication. > -- Isaac Holmes IT Engineering Specialist University of Notre Dame 320 IT Center Notre Dame, IN 46556 (574) 631-3254
