I have a 9 node web farm setup using IIS Shared Configuration. Instead of using a UNC Path for the shared configuration, I am using a folder on each of the server's D: drive. I am using DFS-R to replicate the shared configuration.
I have had this scenario working for 5+ years on Windows Server 2008.
This new setup is on Windows Server 2012 R2. The files are synchronized correctly, but whenever I add a new website or application pool to the primary configuration web server, the application pool has errors on some of the nodes.
The application pool will show with an "Unknown" status. If I just double click that application pool and bring up the edit box, hit OK in the dialog, the application pool enters the "Started" state.
The other thing that differs between this setup and my previous setup is that I need to close IIS Manager and re-launch it to see any changes made on another server. In my 2008 cluster, I just have to hit F5 to refresh the list of sites or application pools.
Has anyone seen this behavior before?