Changing IIS authentication setting for one application will change this for a different application

Version 5

    Verified Product Versions

    Service Desk 2016.x


    IIS v6.0 - v8.0



    Changing the authentication method for one application in IIS changes the authentication method for another also. This causes issues when trying to use two different login policies that require different authentication methods since changes in IIS effect both apps.


    Solution / Workaround:

    This is caused by the physical path of the virtual directory being the same for both applications, we can change the physical path of one of these apps and the changes will now be independent of each other.


    1.       Find the physical path of the virtual directory. Select one of the two sites and go to Basic Settings under Actions. Here you will find the physical path.

    2.       We need to change the physical path but first need to copy the data within the original path. Go up one folder to see the folder containing the full application settings.

    Ex. For C:\Program Files (x86)\LANDESK\Service Desk\WebApp\WebAccess\
           Go to C:\Program Files (x86)\LANDESK\Service Desk\WebApp\

    Make a duplicate of this folder with a new name:



    3.       Now change the physical path of the second application. Select the second application and go to the Basic Settings under Actions. Change the locations of the physical path to reflect the one that you just created (duplicated), you can see how the previous path was the same as what was set for the first application.

    4.       You should now be able to change the authentication method(s) of your new application without having it affect the authentication of another application.