Known Issues with ASP.Net for Server upgrade - Windows 2000 to 200

  • Thread starter Thread starter dinoo
  • Start date Start date
D

dinoo

We are currently in the process of upgrading our web server from Windows 2000
advanced server to Windows 2003 SP2.
We have few ASP.Net applications built with .NET framework 1.1 running on
the web server.

I am looking for the known issues that I need to go over before we start the
upgrade.

Appreiciate your help.

Thanks
 
Basically, you shouldn't have any problems.

Things to watch out for :

1. In Windows 2003, you have to specifically enable ASP.NET 1.1.

2. You must keep all your 1.1 apps in separate application pools than 2.0 apps.

If you have an especially sensitive 1.1 app, setup an application pool exclusively
for that app. Otherwise, you can lump all 1.1 apps in the same application pool.

3. While Windows 2000's ASP.NET account is the ASPNET account,
in Windows 2003 Server the ASPNET account is "NT Authority\Network Service".

If you are not impersonating, that's the account which
needs ACL permissions to all directories.

See this MSDN page for specific info regarding the critical directories:
http://msdn.microsoft.com/en-us/library/kwzs111e(VS.71).aspx

....and remember that the "NT Authority\Network Service" account
must have ACL permissions to mthe whole wwwroot directory structure,
or to any custom directory which you may have configured.

4. Make sure you install the .Net Framework Service Pack 1:
http://www.microsoft.com/downloads/...F7-2CB7-4864-8623-A1038563DF23&displaylang=en

Something good you don't have to worry about :

Windows 2003 comes out-of-the-box with the .Net Framework 1.1 pre-installed.
All you need to do is apply the .Net Framework SP1 and Windows Server SP2.




Juan T. Llibre, asp.net MVP
asp.net faq : http://asp.net.do/faq/
foros de asp.net, en español : http://asp.net.do/foros/
======================================
 
Back
Top