Web Config File in IIS7 Windows 2008 Needs A look at.

I am having trouble with my server.  I am Pretty new with IIS .
Could someone that deals with this stuff all the time look at this file,
Attached is my web.config file from my Root Dir.  Can you tell me if it looks normal, and how many of the web.config pages should I have in my root Dir  folder and above?

Regards and thank you,
Selvol

web config IIs7 winblows 2008 ASP
<?xml version="1.0" encoding="UTF-8"?>
<configuration>
 
    <system.webServer>
        <defaultDocument>
            <files>
                <clear />
                <add value="Default.asp" />
                <add value="Default.htm" />
                <add value="index.htm" />
                <add value="index.html" />
                <add value="iisstart.htm" />
                <add value="default.aspx" />
                <add value="index.php" />
            </files>
        </defaultDocument>
        <directoryBrowse enabled="false" showFlags="Date, Time, Size, Extension" />
        <asp appAllowDebugging="false" codePage="1252" enableParentPaths="true" exceptionCatchEnable="true" scriptErrorSentToBrowser="false" bufferingOn="true">
            <limits bufferingLimit="4194304" />
            <comPlus appServiceFlags="EnableSxS" sxsName="True" executeInMta="true" />
            <session allowSessionState="true" />
        </asp>
        <cgi createProcessAsUser="true" timeout="00:15:00" />
        <caching>
            <profiles>
                <remove extension=".asp" />
                <add extension=".asp" policy="CacheUntilChange" kernelCachePolicy="CacheUntilChange" duration="00:00:30" />
            </profiles>
         </caching>
 
    </system.webServer>
    <system.web>
        <compilation maxBatchGeneratedFileSize="1000" maxBatchSize="1000" />
        <globalization enableClientBasedCulture="true" />
        <identity impersonate="false" />
    </system.web>
</configuration>

Open in new window

LVL 17
selvolAsked:
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.

dhlevineCommented:
Hello -

What specifically is wrong with your server?
0
selvolAuthor Commented:
I have experienced some of my error pages not showing. CGI, running very HEAVY on the resourceds, A question about why its running in "ASP Classic" Mode.  Basically someone and of course not me, changing some  settings in en effort to do what I am not sure at the moment. There has been some performance issues.

 OS: Windows Server 2008 Web  Processor: 2.8GHz e7400   Ram: 4 GB

SElvol
0
10 Tips to Protect Your Business from Ransomware

Did you know that ransomware is the most widespread, destructive malware in the world today? It accounts for 39% of all security breaches, with ransomware gangsters projected to make $11.5B in profits from online extortion by 2019.

Dave_DietzCommented:
Your file looks normal.

In IIS 7.0 all of the configuration is held in .config files - ther eis no Metabase anymore.

At the very least there should be an applicationhost.config at c:\windows\system32\inetsrv\config\applicationhost.config.

It would not be out of range to see a web.config file in each directory of each website, although unless you are doing a lot of custom configuration I would expect more along a web.config at the root of the site and another at each application root with perhaps a couple extras sprinkled around.

CGI is typically resource heavy which is why CGI use is generally discouraged with IIS.  If you can use applciations that are FASTCGI compliant you can use the FASTCGI interface in IIS 7 (also installable under IIS 6) and get *much* better performance - order of magnitude or better improvement generally.

Classic mode vs. Integrated will be in the Applicationhost.config file but effectively it means the difference between .Net being used as a request handler accessed by making a request that includes one of its mapped extensions (Classic) vs. .Net being available from the front of the pipeline to the end of the pipeline (Integrated).  Is there a reason your are particularly concerned with this setting?

Dave Dietz
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
selvolAuthor Commented:
Thank you I am will close this when I get back....

Regards,

Selvol
0
selvolAuthor Commented:
0
selvolAuthor Commented:
THank you............
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 Server OS

From novice to tech pro — start learning today.