![]() I though I had a solution, I managed to put together a powershell script that determined what to do based on the installed app version, it would import the correct xml file using DISM (same net result as using Group Policy from what I understand?), however How would you expect it to be handled if there were thousands of desktops with the same problem I described? ![]() I cannot create an alias of the computers in an OU, Quite the dilemma.Ĭould I install the same version of Reader on each computer, yes, but why should I? Why should I solve one problem only to create a different problem? Either way the end user still cannot just double click on a PDF and edit the document. How do propose I handle different versions, since from an AD perspective I cannot use targeting for this, and I cannot use the GP objects that allow targeting. If they have Foxit or Acrobat, they may or may not have a version of Reader installed, and if they do, it may be Reader XI, Reader 2015, or Reader DC Lets say you have a domain, some computers have Foxit Phantom, some have Adobe Acrobat, and some have Adobe Reader. ![]() What about those of us that need different associations depending on what application is installed. ![]() Yan Li, in regards to the link you posted: ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |