S
shadowtuck
We are testing out Exchange 2016 and trying to get Symantec VIP working like we have in our Exchane 2010
production server. Symantec VIP prompts for a security token in webmail etc...
Part of the procedure from Symantec is adding their third party module to IIS on the Exchange 2016 server.
We were able to add the module at the top level just above Sites, and the module is available under the Site
Exchange Back End but not Default Web Site.
Is Default Web Site locked down so you cannot add any third party modules to it? Since the OWA virtual directory
under Default Web Site is what's used, the module needs to be added in this Site.
Continue reading...
production server. Symantec VIP prompts for a security token in webmail etc...
Part of the procedure from Symantec is adding their third party module to IIS on the Exchange 2016 server.
We were able to add the module at the top level just above Sites, and the module is available under the Site
Exchange Back End but not Default Web Site.
Is Default Web Site locked down so you cannot add any third party modules to it? Since the OWA virtual directory
under Default Web Site is what's used, the module needs to be added in this Site.
Continue reading...