Re: FPSE2002 migration to WSS2.0
From: Lawrence Garvin (onsitechsolutions_at_news.postalias)
Date: 07/08/04
- Next message: Greg McAllister: "Re: Running WSS & Sharepoint Portal Server on the same Server"
- Previous message: Jared: "Re: Importing large amounts of data into existing lists"
- In reply to: Lawrence Garvin: "Re: FPSE2002 migration to WSS2.0"
- Next in thread: Fred Chateau: "Re: FPSE2002 migration to WSS2.0"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 8 Jul 2004 13:03:34 -0500
A follow-up....
...while reading articles in another newsgroup, I discovered this KB
article: 823378, which talks about removing FPSE 2002 from the VIRTUAL
SERVER, in order to extend with WSS 2.0, but makes no mention, suggestion,
or insinuation, that FPSE 2002 must be removed from the WINDOWS SERVER.
In fact, it insinuates that both products /can/ coexist on the same Windows
Server, albeit not on the same IIS Virtual Server.
Can we get some consistency as to the configuration and coexistence
requirements and limitations of FPSE 2002 and WSS 2.0?
"Lawrence Garvin" <onsitechsolutions@news.postalias> wrote in message
news:ueeqfARZEHA.2500@TK2MSFTNGP09.phx.gbl...
>
> ""Arnold Gao [MSFT]"" <v-agao@online.microsoft.com> wrote in message
> news:cKJ8MNMZEHA.2752@cpmsftngxa06.phx.gbl...
> > Hi Lawrence,
> >
> > I would like to share some experience with you.
> >
> > 1. FPSE 2002 and WSS can coexist together, for example, SBS 2003.
However,
> > this kind of coexistence may result in some potential issues in certain
> > scenario. That's why it is not recommended to do so.
>
> Fair enough. Thank you for the clarification. Knowing what I know about
the
> various "custom integrations" done within SBS2003, I suspected this was
the
> case, and it's no great surprise. However, the fact that Microsoft
> specifically made it happen on SBS2003 means that it CAN happen, and
> instructions for such environments ought to be published for the benefit
of
> the Microsoft Community.
>
> Or.. one could simply do as I did... install MSDE and WSS on an existing
> Server 2003/IIS6.0/ASP.NET server with an empty Default Web Site.
>
> > 2. The scenario that installing WSS on Windows server 2003 web edition
> with
> > MSDE together is not a supported one. We have to install a separate SQL
> > server on another server and then let WSS connect to the remote server.
>
> Yes, Yes, Yes.. I know this as historical fact -- but fortunately
Microsoft
> has certified MSDE for installation on Windows Server 2003, Web Edition.
> Furthermore, Windows Sharepoint Services /is/ (and always has been)
> supported if the full version of SQL Server 2000 is installed on the Web
> Edition server -- so your contention that a remote database server must be
> used is fundamentally false. Whether or not the MSDE 2000 Release A
product
> (supported on Web Edition) can now be used in place of SQL Server 2000 on
> the Web Edition server is the question at hand.
>
> Short of Microsoft failing to update some older documentation, there
doesn't
> seem to be anything newer than the MSDE Rel A release date that continues
to
> support this incompatibility.
>
> Allow me to quote from various sources:
>
> First, from the System Requirements for MSDE 2000
> http://www.microsoft.com/sql/msde/productinfo/sysreqs.asp
> which clearly states that MSDE 2000 is now supported on Windows Server
2003,
> Web Edition. The document is dated June, 2003 -- ironically long before
the
> release date of MSDE Rel A. (Did somebody forget to post an 'updated on'
> date on the document?)
>
> It is my understanding that prior to Rel A, MSDE 2000 was not supported on
> Windows Server 2003, Web Edition, but now it is. In fact, as a possible
hint
> to that situation, the MSDE Rel A release notes fail to mention Web
Edition
> as a supported platform, even though other sources contradict this fact,
> supporting the idea that it was not supported at one time.
>
> Second, from the System Requirements for Windows Sharepoint Services
>
http://www.microsoft.com/windowsserver2003/techinfo/sharepoint/sysreqs.mspx
> which states that Sharepoint is supported on Web Edition, albeit only with
> the full version of SQL Server 2000.
>
> The document is dated July, 2003, but was updated in June, 2004.
> Clarification as to whether this statement was relevant before, or after,
> MSDE began being supported on Web Edition would be useful. It would also
be
> useful if published documents on the Microsoft site that contain
'updates',
> would reference that which has been updated. Ergo, a "change summary"
posted
> on the document would be most useful.
>
> Also, admittedly the Administrator Guide does claim, also, that the full
> version of SQL Server 2000 is required on the Web Edition -- though some
> confusion as to the actual date of this document still exists, since it
> carries a copyright date of 2003, but wasn't actually published until
March,
> 2004. Perhaps this document also predates MSDE Release A?
>
> However, I submit and suggest that these limitations were imposed, not
> because of Sharepoint Services, but because of limitations in the support
> for MSDE on the Web Edition.
>
> If that is not the case, then it would be nice to know /exactly/ why this
is
> the case, as there are several inconsistencies in these scenarios.
>
> First, we're told that MSDE can do /anything/ that SQL Server can do --
only
> in a smaller environment.
>
> Second, an APPLICATION should be functional on any 'version' of the
> Operating System, as long as the core system requirements are present.
Since
> we're told that the IIS6 on Web Edition is identical to the II6 on
Standard
> and Enterprise, and I know for a fact that the MSDE comes from the same
> archive -- I'm extremely challenged to understand why an implementation on
> Web Edition would be any different from one on Standard Edition -- except
> that MSDE 2000 (which was released prior to Windows Server 2003) had not
> been previously certified, thus the restrictions to using a full SQL
Server
> 2000 (which had been certified).
>
> Now, having said all of that -- do I understand that if I were to
replicate
> this exact same problem on a Standard Edition server, rather than a Web
> Edition server, you'd be willing to get past the B.S. that it's "not
> supported" and address the real issues that the documentation has
> deficiencies and the instructions are faulty -- even for a Standard
Edition?
>
> If so... I'll be happy to "replicate" the problem on Standard Edition so
> that we can continue with addressing the fundamental failure in the
> migration process -- unless, of course, you can describe /exactly/ why
such
> a procedure would fail on Web Edition, but not on Standard Edition; or at
> least define /exactly/ why the implementation is still "unsupported",
since
> all of the individual components /are/ supported.
>
> > Hope it helps.
>
> No, it doesn't, because it ignores the qualifying fact that I /did/
> successfully install, and make operational, a Sharepoint web site
(currently
> in development) on a Web Edition server. If you'd care to take a look at
the
> results, I'd be happy to put the site in my DNS to allow you access.
>
> The issue is with the migration/conversion of existing FPSE2003 sites (not
> STS 1.0 sites), and with the deficiencies in the Sharepoint Administrator
> Guide relevant to these procedures.
>
> > Sincerely,
> >
> > Arnold Gao
> >
> > Microsoft Partner Online Support
>
> > ====================================================
> > When responding to posts, please "Reply to Group" via
> > your newsreader so
> > that others may learn and benefit from your issue.
> > ====================================================
> > This posting is provided "AS IS" with no warranties, and
> > confers no rights.
>
>
- Next message: Greg McAllister: "Re: Running WSS & Sharepoint Portal Server on the same Server"
- Previous message: Jared: "Re: Importing large amounts of data into existing lists"
- In reply to: Lawrence Garvin: "Re: FPSE2002 migration to WSS2.0"
- Next in thread: Fred Chateau: "Re: FPSE2002 migration to WSS2.0"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
