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

Discussion in 'ASP .Net' started by dinoo, Jun 5, 2008.

  1. dinoo

    dinoo Guest

    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
     
    dinoo, Jun 5, 2008
    #1
    1. Advertising

  2. dinoo

    dinoo Guest

    Appreciate if some one has any information on this.

    "dinoo" wrote:

    > 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
     
    dinoo, Jun 9, 2008
    #2
    1. Advertising

  3. 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/
    ======================================
    "dinoo" <> wrote in message news:...
    > Appreciate if some one has any information on this.
    >
    > "dinoo" wrote:
    >
    >> 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
     
    Juan T. Llibre, Jun 9, 2008
    #3
  4. dinoo

    dinoo Guest

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

    That was very valuable information. Thank you very much.

    "Juan T. Llibre" wrote:

    > 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/
    > ======================================
    > "dinoo" <> wrote in message news:...
    > > Appreciate if some one has any information on this.
    > >
    > > "dinoo" wrote:
    > >
    > >> 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

    >
    >
    >
     
    dinoo, Jun 9, 2008
    #4
  5. Re: Known Issues with ASP.Net for Server upgrade - Windows 2000 to

    On Jun 9, 9:42 pm, dinoo <> wrote:
    > That was very valuable information. Thank you very much.
    >
    >
    >
    > "Juan T. Llibre" wrote:
    > > 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/details.aspx?FamilyId=AE7EDEF7-2CB....

    >
    > > 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/
    > > ======================================
    > > "dinoo" <> wrote in messagenews:...
    > > > Appreciate if some one has any information on this.

    >
    > > > "dinoo" wrote:

    >
    > > >> 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- Hide quoted text -

    >
    > - Show quoted text -


    I agree with Juan, you shouldn't have any problems on Win2003
     
    Alexey Smirnov, Jun 9, 2008
    #5
    1. Advertising

Want to reply to this thread or ask your own question?

It takes just 2 minutes to sign up (and it's free!). Just click the sign up button to choose a username and then you can ask your own questions on the forum.
Similar Threads
  1. Jack
    Replies:
    7
    Views:
    630
  2. C Did
    Replies:
    3
    Views:
    4,036
    Chris Lithgow
    Jun 20, 2006
  3. =?Utf-8?B?U2VudGhpbCBSYWo=?=

    unable to run,debug ASP.NET 1.1 web project in windows server 200

    =?Utf-8?B?U2VudGhpbCBSYWo=?=, Dec 19, 2006, in forum: ASP .Net
    Replies:
    0
    Views:
    332
    =?Utf-8?B?U2VudGhpbCBSYWo=?=
    Dec 19, 2006
  4. Adhik
    Replies:
    1
    Views:
    258
    Manohar Kamath [MVP]
    Sep 5, 2003
  5. Schwartzberg
    Replies:
    1
    Views:
    229
Loading...

Share This Page