"Server Error in '/' Application" when enabling older version of .NET and syprep was perfo

[TechMasterNate]

Today I made a mistake on one of my VM images. We have been developing websites in our new environment and I was going to take an image of the server and throw it up into Azure. The instructions to deploy it in Azure was to make sure .NET 3.5.1 was enabled and do a sysprep. I forgot to take a snapshot before doing this. The applications in IIS were using net 4.0 but I thought it wouldn't hurt to enable .NET 3.5.1 in the features of the 2008 R2 server then do a sysprep. When booting the server back up it took itself off our domain and all the websites in IIS were receiving a 503 error. I changed the identity account back to the right password so the application pools would stop locking out and am now receiving the error below. I tried taking the .NET 3.5.1 feature off the server but am still receiving the same error. I am unfamiliar with fixing these types of errors and know little about .NET. Does anyone have any ideas? Thanks



Server Error in '/' Application.
--------------------------------------------------------------------------------

Runtime Error
Description: An application error occurred on the server. The current
custom error settings for this application prevent the details of the
application error from being viewed.

Details: To enable the details of this specific error message to be
viewable on the local server machine, please create a <customErrors>
tag within a "web.config" configuration file located in the root
directory of the current web application. This <customErrors> tag
should then have its "mode" attribute set to "RemoteOnly". To enable
the details to be viewable on remote machines, please set "mode" to
"Off".


<!-- Web.Config Configuration File -->

<configuration>
<system.web>
<customErrors mode="RemoteOnly"/>
</system.web>
</configuration>


Notes: The current error page you are seeing can be replaced by a
custom error page by modifying the "defaultRedirect" attribute of the
application's <customErrors> configuration tag to point to a custom
error page URL.


<!-- Web.Config Configuration File -->

<configuration>
<system.web>
<customErrors mode="On" defaultRedirect="mycustompage.htm"/>
</system.web>
</configuration>