network setup

Not sure if I am in the right place for this...

I work for a university. We have a main site (http://www.test.ca), and below
this we have 140 subwebs. We have 40 Faculty subwebs, and 50 departmental
subwebs, and the other 50 we do nto need to worry about right now. Now I use
Windows 2003 Server, IIS 6, FrontPage Server Extensions to administor all of
this right now.

Now, we want to switch over to use a CMS. The CMS we have selected is
SharePoint 2007 because it can be under our site license, and can provide the
portal technology we want as well.

So all of these subwebs are obviously under the same IP (lets say 1.1.1.1 -
which points to http://www.test.ca). The way our site is designed, is that we
will have:

- 40 faculty (Will not use CMS)
- 50 departmental (Will use CMS)

The 40 faculty who will not be using the CMS, use FrontPage, and I want to
keep it like that. BUT, you cannot install FrontPage Server Extensions on the
same server as SharePoint 2007. So obviously this is going to be an issue. We
want these subwebs to point to the same domain... I am unsure of what to
do... If they can coexist on the same server would be the best solution. If
not and we need to use 2 servers, then that should not be an issue, just as
long as the 2 servers can point to the same domain...

Anyone with any advice on this????

(Here is somethign I thought of, but I am not sure if it will work:

Create 1st Web Server - IP - 1.1.1.1 - install sharepoint on here for the 50
departments to use the CMS
Create 2nd Web Server - IP - 2.2.2.2 - install server extensions on here for
the 40 faculty to use FrontPage

Point 1.1.1.1 to www.test.ca and 2.2.2.2 to www.test.ca as well in the DNS.
Not sure if this cane be done...

Why not use sub domains?
faculty.test.ca
dept.test.ca

you don't have to buy another domain, just notify your DNS admin.
if you own the domain you should be able to add as many subs as you wish.
if you manage your own dns, you just setup extra host records that point to
the correct servers.

You could even setup a default page to ask them where they want to go.
Or even redirect users to the other sub by creating redirects. Example
www.test.ca/faculty


"swwalsh" wrote:

> Not sure if I am in the right place for this...
>
> I work for a university. We have a main site (http://www.test.ca), and below
> this we have 140 subwebs. We have 40 Faculty subwebs, and 50 departmental
> subwebs, and the other 50 we do nto need to worry about right now. Now I use
> Windows 2003 Server, IIS 6, FrontPage Server Extensions to administor all of
> this right now.
>
> Now, we want to switch over to use a CMS. The CMS we have selected is
> SharePoint 2007 because it can be under our site license, and can provide the
> portal technology we want as well.
>
> So all of these subwebs are obviously under the same IP (lets say 1.1.1.1 -
> which points to http://www.test.ca). The way our site is designed, is that we
> will have:
>
> - 40 faculty (Will not use CMS)
> - 50 departmental (Will use CMS)
>
> The 40 faculty who will not be using the CMS, use FrontPage, and I want to
> keep it like that. BUT, you cannot install FrontPage Server Extensions on the
> same server as SharePoint 2007. So obviously this is going to be an issue. We
> want these subwebs to point to the same domain... I am unsure of what to
> do... If they can coexist on the same server would be the best solution. If
> not and we need to use 2 servers, then that should not be an issue, just as
> long as the 2 servers can point to the same domain...
>
> Anyone with any advice on this????
>
> (Here is somethign I thought of, but I am not sure if it will work:
>
> Create 1st Web Server - IP - 1.1.1.1 - install sharepoint on here for the 50
> departments to use the CMS
> Create 2nd Web Server - IP - 2.2.2.2 - install server extensions on here for
> the 40 faculty to use FrontPage
>
> Point 1.1.1.1 to www.test.ca and 2.2.2.2 to www.test.ca as well in the DNS.
> Not sure if this cane be done...

Well its not totally as easy as that... All though I have 50 Departments who
will use the CMS... There are other then that, lets say 5-6 who will not be
using the CMS... Unfortunately I cannot force them to use the CMS, so then
thigns will not look the same. What about these 5-6 not on the CMS, etc.
There are alot of things I have to look at when doing this...

Steve

"Tray" wrote:

> Why not use sub domains?
> faculty.test.ca
> dept.test.ca
>
> you don't have to buy another domain, just notify your DNS admin.
> if you own the domain you should be able to add as many subs as you wish.
> if you manage your own dns, you just setup extra host records that point to
> the correct servers.
>
> You could even setup a default page to ask them where they want to go.
> Or even redirect users to the other sub by creating redirects. Example
> www.test.ca/faculty
>
>
> "swwalsh" wrote:
>
> > Not sure if I am in the right place for this...
> >
> > I work for a university. We have a main site (http://www.test.ca), and below
> > this we have 140 subwebs. We have 40 Faculty subwebs, and 50 departmental
> > subwebs, and the other 50 we do nto need to worry about right now. Now I use
> > Windows 2003 Server, IIS 6, FrontPage Server Extensions to administor all of
> > this right now.
> >
> > Now, we want to switch over to use a CMS. The CMS we have selected is
> > SharePoint 2007 because it can be under our site license, and can provide the
> > portal technology we want as well.
> >
> > So all of these subwebs are obviously under the same IP (lets say 1.1.1.1 -
> > which points to http://www.test.ca). The way our site is designed, is that we
> > will have:
> >
> > - 40 faculty (Will not use CMS)
> > - 50 departmental (Will use CMS)
> >
> > The 40 faculty who will not be using the CMS, use FrontPage, and I want to
> > keep it like that. BUT, you cannot install FrontPage Server Extensions on the
> > same server as SharePoint 2007. So obviously this is going to be an issue. We
> > want these subwebs to point to the same domain... I am unsure of what to
> > do... If they can coexist on the same server would be the best solution. If
> > not and we need to use 2 servers, then that should not be an issue, just as
> > long as the 2 servers can point to the same domain...
> >
> > Anyone with any advice on this????
> >
> > (Here is somethign I thought of, but I am not sure if it will work:
> >
> > Create 1st Web Server - IP - 1.1.1.1 - install sharepoint on here for the 50
> > departments to use the CMS
> > Create 2nd Web Server - IP - 2.2.2.2 - install server extensions on here for
> > the 40 faculty to use FrontPage
> >
> > Point 1.1.1.1 to www.test.ca and 2.2.2.2 to www.test.ca as well in the DNS.
> > Not sure if this cane be done...

You could always setup another site that redirects them to the correct site
based on group memberships.

Or instead of using the different domains use another port.
"swwalsh" wrote:

> Well its not totally as easy as that... All though I have 50 Departments who
> will use the CMS... There are other then that, lets say 5-6 who will not be
> using the CMS... Unfortunately I cannot force them to use the CMS, so then
> thigns will not look the same. What about these 5-6 not on the CMS, etc.
> There are alot of things I have to look at when doing this...
>
> Steve
>
> "Tray" wrote:
>
> > Why not use sub domains?
> > faculty.test.ca
> > dept.test.ca
> >
> > you don't have to buy another domain, just notify your DNS admin.
> > if you own the domain you should be able to add as many subs as you wish.
> > if you manage your own dns, you just setup extra host records that point to
> > the correct servers.
> >
> > You could even setup a default page to ask them where they want to go.
> > Or even redirect users to the other sub by creating redirects. Example
> > www.test.ca/faculty
> >
> >
> > "swwalsh" wrote:
> >
> > > Not sure if I am in the right place for this...
> > >
> > > I work for a university. We have a main site (http://www.test.ca), and below
> > > this we have 140 subwebs. We have 40 Faculty subwebs, and 50 departmental
> > > subwebs, and the other 50 we do nto need to worry about right now. Now I use
> > > Windows 2003 Server, IIS 6, FrontPage Server Extensions to administor all of
> > > this right now.
> > >
> > > Now, we want to switch over to use a CMS. The CMS we have selected is
> > > SharePoint 2007 because it can be under our site license, and can provide the
> > > portal technology we want as well.
> > >
> > > So all of these subwebs are obviously under the same IP (lets say 1.1.1.1 -
> > > which points to http://www.test.ca). The way our site is designed, is that we
> > > will have:
> > >
> > > - 40 faculty (Will not use CMS)
> > > - 50 departmental (Will use CMS)
> > >
> > > The 40 faculty who will not be using the CMS, use FrontPage, and I want to
> > > keep it like that. BUT, you cannot install FrontPage Server Extensions on the
> > > same server as SharePoint 2007. So obviously this is going to be an issue. We
> > > want these subwebs to point to the same domain... I am unsure of what to
> > > do... If they can coexist on the same server would be the best solution. If
> > > not and we need to use 2 servers, then that should not be an issue, just as
> > > long as the 2 servers can point to the same domain...
> > >
> > > Anyone with any advice on this????
> > >
> > > (Here is somethign I thought of, but I am not sure if it will work:
> > >
> > > Create 1st Web Server - IP - 1.1.1.1 - install sharepoint on here for the 50
> > > departments to use the CMS
> > > Create 2nd Web Server - IP - 2.2.2.2 - install server extensions on here for
> > > the 40 faculty to use FrontPage
> > >
> > > Point 1.1.1.1 to www.test.ca and 2.2.2.2 to www.test.ca as well in the DNS.
> > > Not sure if this cane be done...