WSS 2.0 to WSS 3.0

Discussion in 'Windows Small Business Server' started by Mick34, May 28, 2007.

  1. Mick34

    Mick34 Guest

    I posted in the Sharepoint managed newsgroups and they suggested that I post
    here.

    We recently updated our SBS 2003 R2 to Windows 2003 STD R2. We are running
    WSS 2.0, but would like to upgrade to WSS 3.0. I have read that upgrading
    WSS 2.0 to WSS 3.0 on an SBS 2003 can be a problem.
    It has to be installed parallel to each other. Something to do with the
    Admin modules that exist in SBS causing issues.
    We figured that after we upgraded to W2K3 STD, we wouldn't have to
    worry about that. But, it does look like there are some of the SBS modules
    still hanging around and working.
    We do not want to run it parallel, nor do we want to take the chance of just
    upgrading to WSS 3.0on the server without taking the steps suggested for
    SBS.
    So, we have a nother 2003 STD server which we just added to the domain.
    Can we install the WSS 3.0 on this other server and then stop the WSS 2.0
    running on the original server. The one issue is that we would have to leave
    SQL
    running on the original server for licensing issues.
    Essentially we want to move the WSS 3.0 to a seperate server with the SQL
    running on the original. Can we do this? Or does SQL and WSS 3.0 upgrade
    have to be running on the same server?

    Thanks in advance
     
    Mick34, May 28, 2007
    #1
    1. Advertisements

  2. Mick34

    Costas Guest

    WSS 3.0 is free and can be installed on any box that runs Windows Server
    2003. The database can exist on a different server, it doesn't have to be
    on the same server as WSS. During installation you will be asked to select
    the database server you will be using. One word of caution. When you
    install WSS 3.0, make sure you don't select the default option, but select
    the option that installs on a server farm. If you select the default
    option, WSS will install with the default SQL Express database on the
    server.

    Costas
     
    Costas, May 29, 2007
    #2
    1. Advertisements

  3. Mick34

    Mick34 Guest

    Tahnks for the reply.

    So are you referring to a fresh install of WSS 3.0? Can I use the same Db
    (data) as the WSS 2.0 was using?
     
    Mick34, May 29, 2007
    #3
  4. Hi Mick,

    Thanks for posting in our newsgroup and also for Costas's input.

    I'd like to give you the following suggestions:

    The correct procedure to bring in a WSS 2.0 database to 3.0 is to:

    1. Have the WSS 2.0 web site with the content database running on a server.

    2. Run WSS 3.0 setup and select not to upgrade at this time.

    3. Install the WSS 3.0 binaries.

    4. After the WSS 3.0 binaries are installed and before the Post Setup
    Configuration wizard is run, run prescan /all from
    %commonprogramfiles%\microsoft shared\web server extensions\12\bin. Review
    the prescan logs to make sure there
    aren't any issues from prescan.

    5. Run the WSS 3.0 Post Setup Configuration wizard.

    6. Open the WSS 3.0 Central Administration and create a new Web application.

    7. The newly created web application should be empty with no content.

    8. From the WSS 3.0 Central Administration, browse to the Manage Content
    Databases page, remove the empty content database.

    9. From the command line, go to the WSS 3.0 binaries folder
    (%commonprogramfiles%\microsoft shared\web server extensions\12\bin) and
    run stsadm -o addcontentdb to attach the WSS 2.0 content database to the
    WSS 3.0 web site.

    10. Browse through the WSS 3.0 web site and make sure it has the upgraded
    content.

    Hope the information helps.

    If you need further assistance, please don't hesitate to let me know.

    Best regards,

    Robert Li(MSFT)

    Microsoft CSS Online Newsgroup Support

    Get Secure! - www.microsoft.com/security

    =====================================================

    This newsgroup only focuses on SBS technical issues. If you have issues
    regarding other Microsoft products, you'd better post in the corresponding
    newsgroups so that they can be resolved in an efficient and timely manner.
    You can locate the newsgroup here:
    http://www.microsoft.com/communities/newsgroups/en-us/default.aspx

    When opening a new thread via the web interface, we recommend you check the
    "Notify me of replies" box to receive e-mail notifications when there are
    any updates in your thread. When responding to posts via your newsreader,
    please "Reply to Group" so that others may learn and benefit from your
    issue.

    Microsoft engineers can only focus on one issue per thread. Although we
    provide other information for your reference, we recommend you post
    different incidents in different threads to keep the thread clean. In doing
    so, it will ensure your issues are resolved in a timely manner.

    For urgent issues, you may want to contact Microsoft CSS directly. Please
    check http://support.microsoft.com for regional support phone numbers.

    Any input or comments in this thread are highly appreciated.

    =====================================================

    This posting is provided "AS IS" with no warranties, and confers no rights.

    --------------------
    <Thread-Topic: WSS 2.0 to WSS 3.0
    <thread-index: Acehl/+4giw9QCy3Q+K1JiE/saZFiw==
    <X-WBNR-Posting-Host: 207.46.19.168
    <From: =?Utf-8?B?TWljazM0?= <>
    <References: <>
    <>
    <Subject: Re: WSS 2.0 to WSS 3.0
    <Date: Mon, 28 May 2007 19:21:00 -0700
    <Lines: 49
    <Message-ID: <>
    <MIME-Version: 1.0
    <Content-Type: text/plain;
    < charset="Utf-8"
    <Content-Transfer-Encoding: 7bit
    <X-Newsreader: Microsoft CDO for Windows 2000
    <Content-Class: urn:content-classes:message
    <Importance: normal
    <Priority: normal
    <X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2826
    <Newsgroups: microsoft.public.windows.server.sbs
    <Path: TK2MSFTNGHUB02.phx.gbl
    <Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.windows.server.sbs:39948
    <NNTP-Posting-Host: tk2msftibfm01.phx.gbl 10.40.244.149
    <X-Tomcat-NG: microsoft.public.windows.server.sbs
    <
    <Tahnks for the reply.
    <
    <So are you referring to a fresh install of WSS 3.0? Can I use the same Db
    <(data) as the WSS 2.0 was using?
    <
    <"Costas" wrote:
    <
    <> WSS 3.0 is free and can be installed on any box that runs Windows Server
    <> 2003. The database can exist on a different server, it doesn't have to
    be
    <> on the same server as WSS. During installation you will be asked to
    select
    <> the database server you will be using. One word of caution. When you
    <> install WSS 3.0, make sure you don't select the default option, but
    select
    <> the option that installs on a server farm. If you select the default
    <> option, WSS will install with the default SQL Express database on the
    <> server.
    <>
    <> Costas
    <>
    <>
    <> <> >I posted in the Sharepoint managed newsgroups and they suggested that I
    <> >post
    <> > here.
    <> >
    <> > We recently updated our SBS 2003 R2 to Windows 2003 STD R2. We are
    running
    <> > WSS 2.0, but would like to upgrade to WSS 3.0. I have read that
    upgrading
    <> > WSS 2.0 to WSS 3.0 on an SBS 2003 can be a problem.
    <> > It has to be installed parallel to each other. Something to do with the
    <> > Admin modules that exist in SBS causing issues.
    <> > We figured that after we upgraded to W2K3 STD, we wouldn't have to
    <> > worry about that. But, it does look like there are some of the SBS
    modules
    <> > still hanging around and working.
    <> > We do not want to run it parallel, nor do we want to take the chance
    of
    <> > just
    <> > upgrading to WSS 3.0on the server without taking the steps suggested
    for
    <> > SBS.
    <> > So, we have a nother 2003 STD server which we just added to the domain.
    <> > Can we install the WSS 3.0 on this other server and then stop the WSS
    2.0
    <> > running on the original server. The one issue is that we would have to
    <> > leave
    <> > SQL
    <> > running on the original server for licensing issues.
    <> > Essentially we want to move the WSS 3.0 to a seperate server with the
    SQL
    <> > running on the original. Can we do this? Or does SQL and WSS 3.0
    upgrade
    <> > have to be running on the same server?
    <> >
    <> > Thanks in advance
    <>
    <
     
    Robert Li [MSFT], May 29, 2007
    #4
  5. Mick34

    Costas Guest

    Yes, I'm talking about a fresh install. Robert described how to upgrade the
    the 2.0 databases to 3.0

    Costas
     
    Costas, May 29, 2007
    #5
  6. I wouldn't recommend using the same database you used with WSS 2.0 for the
    3.0 install. I'd rather do a side-by-side installation and check everything
    against your existing one before deciding to take it out for good :)
     
    bass_player [SBS-MVP], May 29, 2007
    #6
    1. Advertisements

Ask a Question

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

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.