Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I am setting up a new infrastructure with multiple web servers with a single shared config and files. The servers are Windows Server 2012, not on a domain.

I have set up a user iisconfig on both machines, with the same password. That user also has the 'log on as a batch job' rights assignment.

I have a share on FS01 called IISConfig, "iisconfig" has full control, "users" has full control.

WEB01 is set up with shared config to \\FS01\IISConfig, with creds of "iisconfig" and the password. Seems to work fine, config files show up on the share.

However, if I try to edit any configuration in IIS now, I get an error

There was an error performing this operation.
Filename \\?\UNC\FS01\IISConfig\applicationHost.config
Error: Cannot write configuration file.

Weird thing is, if I manually go to that share in Explorer, and authenticate with the same username and password, I can see and edit the files, and after that IIS will save config. But only until a restart clears the manually-entered cached credentials.

It's almost like IIS isn't using the credentials I've given it.

share|improve this question
Just a suggestion but I often find it much easier to setup a mapped network drive and store the credentials for the connection there and then simply point IIS to the mapped drive. It often eliminates a lot of the authentication headaches in IIS. – Brent Pabst Jan 21 '13 at 11:56
Would that have to be mapped using a scheduled task for SYSTEM to make sure it is available for all users and services? – Cylindric Jan 21 '13 at 12:05
Crap, good question. Forget I mentioned it, won't work in this scenario. – Brent Pabst Jan 21 '13 at 23:48
Heh, I have done similar before, it probably would work, as long as it was mapped by SYSTEM at startup. Anyway, odd thing is that it's just writing config that doesn't seem to work unless I manually poke the credentials first. – Cylindric Jan 22 '13 at 10:17
Did you export out the applicationHost.config file, or simply copy it to that location? If you did export it, this same issue is happening from either machine? – Brettski Sep 16 '14 at 16:31

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.