08-30-2019 11:53 AM
All we want to do is NOT have the Cisco pop-up appear upon opening Outlook the first time after the Plug-in is installed. The only way to do that is using the UseCustomConfig=. The instructions use a UNC for the path. Is this required? We are trying to use a local path (for example: C:\temp\) and it is not working. We deploy via a Cloud program and cannot relay on a UNC path. We rather just copy the files locally and run the install.
09-02-2019 04:43 AM
09-03-2019 03:28 AM
Thanks, for the response, but that didn't answer my question. My question was more of a confirmation that the only a UNC is allowed; and that a direct path would not work. A modern installer, such as Microsoft's Office Deployment Tool, which uses an XML file for its configuration, allows you to us any path, local or network. That does not seem to be the case here.
The Cisco installer should be updated to not requiring a UNC path to its configuration file.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide