Application Pool Status Unknown with IIS Shared Configuration with DFS for Config Sync

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?

IIS Screen Shot
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Greg HejlPrincipal ConsultantCommented:
Hi Justin,

I'm commenting here to save the thread.  I had 7.5 dfs'd like you have and will be doing 8.5 soon.

Have you been over to on this issue?

Greg HejlPrincipal ConsultantCommented:
Maybe they have fixed the shared config issue in 7.5?

This article points to a fileshare-maybe they fixed what was wrong with 7.5 to make this work for 8.5?

Maybe SMB 3 protocol fixes this.....?
justinlauckAuthor Commented:
I ended up having to re-install IIS on several of the nodes.  They then started behaving properly.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Greg HejlPrincipal ConsultantCommented:
Did you stick with DFS for sharing config xml's?
justinlauckAuthor Commented:
I ended up just starting from scratch.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2012

From novice to tech pro — start learning today.