Score:0

Editing IIS with shared config through the Microsoft.Web.Administration namespace

lv flag

We are having a problem, and it's probably something completely stupid. We have the following setup:

WebCluster1 (A cluster of IIS web servers running a administration site) WebCluster2 (A Cluster of IIS web servers running another site) NAS (A Nas containing web configs for the servers)

A user has the option to create users on the sites hosted on WebCluster1, and these users are then written into the webconfig on WebCluster2. However we have had a problem with this for some time now. Since the workflow goes like this:

User creates a user on WebCluster1 --> WebCluster1 contacts a server in WebCluster2 by using the Microsoft.Web.Administration namespace and tries to add the user to the webconfig --> WebCluster2 tries to write the change to the config on the NAS and fails.

The setup works if we remove the NAS and it works if we try to edit the webconfig directly on the servers in WebCluster2. This leads to us believing it's a double hop issue, but is there any way to solve this? Have we just made the dumbest decision? Is there a better way to do this?

I sit in a Tesla and translated this thread with Ai:

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.