I'm not even sure you would be allowed to install MapGuide Server and the
web extensions on that platform. From
Windows Server 2003 Web Edition, can be used solely to deploy Web pages, Web
sites, Web applications, and Web services. Customers can use Windows Server
2003 Web Edition, to install the following:
. Web server software; for example, IIS.
. Web availability management software; for example, Microsoft
Installations of non-Web serving applications are prohibited. ASP.NET-based
applications that include code written in third-party programming languages
can include that programming language's runtime components. For non-Web
serving applications, you should consider Windows Server 2003 R2 Standard
Client access licenses (CALs) do not apply to Windows Server 2003 Web
Edition. However, Windows Server 2003 Web Edition, can be used as the
scale-out front end for applications such as Windows SharePoint Services and
Windows Rights Management Services. In these scale-out configurations,
Windows Server CALs and/or Exchange CALs may still be required.
In these types of configurations, Windows Server 2003 Web Edition, offers
customers an economical way to deploy scale-out applications, thanks to the
competitively priced licensing model."
But, assuming it would be OK and that all of the components of MapGuide can
be classified as "web serving applications", then I would think the install
steps would be the same as for Windows 2003 since they both share the
underlying IIS 6.0.
This would be a good one for Autodesk to check in with Microsoft
Andy Morsell, P.E.
Spatial Integrators, Inc.
wrote in message news:email@example.com...
I would like to know if i can install MG enterprise site server on a Window
Server 2003 Web edition? In the system requirement, the platform mentionned
is 2000 or 2003 server only.
Andy Morsell wrote:
> But, assuming it would be OK and that all of the components of MapGuide can
> be classified as "web serving applications", then I would think the install
> steps would be the same as for Windows 2003 since they both share the
> underlying IIS 6.0.
I think that if Microsoft is thinking of the services portion of
Sharepoint as being unsuitable for Web edition (in contrast to the web
front end), that MapGuide Server doesn't have much of a chance.
I do think that the Web Extensions portion would qualify though, so
using Web Edition could reduce the costs of a multi-head implementation
Is enterprise licensing based on the server, or do you need an
individual license for each web extensions installation I wonder. This
would make a considerable difference for larger isntallations,
especially once session affinity gets worked out and a single front end
can access multiple servers.