The concept once again is that you are working with a version of Dynamics NAV (particular build) installed in your machine of which you have already configured the Web Client and now you want to create a new NAV Web Instance for a different build (scenario of my previous post).
Under the hook
Let analyze, for example, the structure of the Web Client for NAV 2017. The following picture, from Internet Information Service (IIS) Manager, shows that there is a website called Microsoft Dynamics NAV 2017 Web Client that can contain one or multiple NAV Web Instances. In this case, it contains a NAV Web Instance named DynamicsNAV100 which is a Virtual Directory (we can notice it from the icon) that contains an Application called WebClient.
Right-click on DynamicsNAV100 and selecting Explore it will open the content of the virtual directory in a File Explorer window:
So now we know the content of the Virtual Directory, which includes actually two items, and the location where it is stored, at the path
What are these two items?
web.config is a file containing the configuration of the NAV Web Instance
WebClient, with an icon similar to a shortcut, is a Symbolic Link.
Right-click on the symbolic link WebClient shows in the properties, in the Shortcut tab, the path of the NAV Web Client folder as Target: