Hi Tom,

It'd be worth revisiting your desire not to install SharePoint in the
extranet - by which I presume you mean a "zone" partitioned by means of a
firewall.
Your concerns about doing this may now have been addressed (e.g. SharePoint
2007 does not require AD accounts for users). Overall the attack surface of
2007 is vastly reduced if properly configured.

If you have today MCMS in your extranet, you are really only looking at
replacing this with MOSS 2007. If you configure the MOSS box appropriately
you are not exposing yourself to anymore risk than you are today with MCMS.

Bottom line is if you want to move to the new WCM features in MOSS, you need
a MOSS box!!

But there is another solution. Install MOSS in your "intranet" and use an
ISA server (or other reverse proxy) in the "Extranet" to 'web publish' the
application. The security merits of this are arguable, but it avoids the
need to install the app server in the DMZ/whatever.

I'd also check out the architecture/planning guide over on technet which
details the changes from the preferred MCMS separate authoring and browse
environments and the extreme flexibility (wrt deployment) now available with
MOSS.

hth
Spence
www.mcmsfaq.com



"Tom" <Tom@discussions.microsoft.com> wrote in message
news:6C31A53D-5A06-464A-BBDE-C643A7316597@microsoft.com...[vbcol=seagreen]
> Stefan:
>
> So what are customers like me who are using CMS 2002 SP2 to do.  I am
> using
> it in an Extranet environment and really don't want to have to install
> Sharepoint in my extranet environment.
>
> Is there a migration path for those who wish to upgrade to MOSS '07 in an
> extranet world?
>
> Tom
>
>
> "Stefan GoƟner [MSFT]" wrote:
> 

[ Post a follow-up to this message ]