Hey all, I am in a bit of a bind... My company finally rolled out our new intranet version this weekend and I have spent all day today herding cats. The site performance is lackluster at best. At worst, people are complaining of timeouts and authentication seems to be taking several minutes (SP1 issue?).

My webserver is Windows Server 2003 SP1 with 2 3.0GHz Xeon processors and 4GB of RAM. My Database server is Windows Server 2003 SP1 running SQL 2000 SP4 with 4 2.8 GHZ Xeon processors and 4GB of RAM. The servers are running in an Enterprise level network architecture with Active Directory, DNS, and so on running on respective servers in a redundant cluster configuration. All systems are treated as mission critical here - seperate redundant power sources, redundant power supplies, seperate hvac and the servers are all installed in an APC "hot isle" rack configuration. In short our stuff is really tight...

We followed the upgrade paths in a test environment and created our own upgrade documentation which we ran to the letter this past Saturday and tested to make sure our AD was working and that the navigation stuff was all set.

When I came in this morning, it was mass chaos. Our 2000+ users were unable to authenticate against the AD while loading the site, and people were having to manually delete their cookies in order to get in.

I ran aspnet_regiis -ir -enable and aspnet_regiis -s "W3SVC\<identifier>" to reregister the .NET framework with IIS and to rebuild the scriptmaps for our intranet site, and things got alot better but the site is still slow as... well its super slow...

While I am waiting for a reply, I plan to use SQL Profiler to look at SQL calls, but I don't expect to find anything dramatic as this was just an upgrade. We are also looking at the server logs to see if we are running into that old w3wp.exe issue that Windows Server 2003 SP2 is supposed to fix. Does anyone have any other idea's that I could look at to see what may be happening?

Thanks!

John Valentine