IIS - Machine Key, registry keys between servers are not consistent

Hi everyone,
We have two front-end servers that are load balanced.  Server 2008 R2.  IIS is serving a couple web apps, specifically web forms.  We've been experiencing viewstate errors during onSubmit so we configured a static Machine Key for each web app in the IIS gui and web.config's, consistently across both servers.  We're still facing viewstate problems so we took a closer look at the registry keys.

We found a discrepancy on one of the servers in production.  Our development environment is configured alike and does not contain the discrepancy.  

server1 contains a few keys that server2 doesn't.  We're not positive this is an issue but these servers should be consistent.  

Our question is, how can we learn more about these keys?  This is prod so we don't want to delete them without more research.  Highlighted below is the discrepancy between servers.

Screenshots capture HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ASP.NET

Production Server1:
prod-server1.png
Production Server2:
prod-server2.png
Development Server1:
dev-server1.png
Development Server2:
dev-server2.png

Thanks in advance for your help!
bmsandeAsked:
Who is Participating?
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.

David Johnson, CD, MVPOwnerCommented:
Best way is to add a machineKey element into each of the web server's web.config and define the same keys and algorithm. The machineKey goes under the System.web node.
i.e. in your web.config
<machineKey validation="SHA1" validationKey="A1B2C3D4E5F6F6E5D4C3B2A1A1B2C3D4E5F6F6E5D4C3B2A1A1B2C3D4 E5F6F6E5D4C3B2A1A1B2C3D4E5F6F6E5D4C3B2A1A1B2C3D4E5F6F6E5D4C3B2A1B2C3D4E5"
decryption="Auto" decryptionKey="A1B2C3D4E5F6F6E5D4C3B2A1A1B2C3D4E5F6F6E5D4C3B2A1" /> 

Open in new window


http://www.codeproject.com/Questions/769391/What-is-mean-by-Validation-of-viewstate-MAC-failed
0
bmsandeAuthor Commented:
That was done already.  Web.config sections match with a static machine key.  But we're trying to understand these registry keys... and trying to correct the inconsistency highlighted above.
0
bmsandeAuthor Commented:
Does anyone know how to identify where these registry keys come from?  We have several web servers that we keep consistent, but this server in particular has some registry keys that are not expected.  We'd like to remove this keys but need to learn more about them before we proceed.
0

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
David Johnson, CD, MVPOwnerCommented:
they were probably generated before you added the machine keys into the web.config
0
bmsandeAuthor Commented:
resolved
0
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
Microsoft IIS Web Server

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.