IIS 6 Question: How to Publish from FrontPage 2003

microsoft.public.inetserver.iis.security

21 Aug 2006 3:22 PM

JoeF

Details:
---------
Running Windows Server Enterprise 2003 SP1 w/all Updates
Running IIS 6.0
Enabled Server extensions, ASP and .Net
Did NOT configure FTP service
Joined to Workgroup WORKGROUP
Renamed Default Web Site Description with my own description
Located behind hardware firewalls.

Questions:
-------------
What/how do I configure a user to publish their Frontpage 2003 Web Site to
this fresh new IIS server? Do I need to delete the default web site
directories first?
   - When using FrontPage 2003, do I publish to http://server-name/
        - Will this affect any links when viewing from the public internet
after
          firewall forwards port 80 traffic?
   - Do I just use the administrator account to publish?
   - If I create a new local user, what permissions or groups do I assign
him/her to
     allow publishing and editing web pages?

This will be a public internet web server. My firewall will forward port 80
traffic only to this new server. What other security considerations are
applicable?
   - Can my user publish the web site remotely?

Advanced Questions:
------------------------
I have an exact server configuration from a hardware and software
perspective. How can I create a fault tolerant situation where one server
fails, the other server takes over? Is there such a thing as mirroring the
web site to the other server automatically?

Thanks for any suggestions/assistance you may have. I appreciate it!

Regards,
JoeF

22 Aug 2006 2:13 PM

Funkadyleik Spynwhanker

Show quote

Make a virtual web normally. Right click and choose "FrontPage 2002 Server
Extensions - Extend"

In the resulting managment web page, add or create the user as an
administrator of the web.

You do _NO_ modifications to file permissions in the root folder, and _NO_
configuration in the Users area on the server for this. The FrontPage
(Sharepoint) administration web site does that for you.

>   - When using FrontPage 2003, do I publish to http://server-name/
>        - Will this affect any links when viewing from the public internet
> after
>          firewall forwards port 80 traffic?

No, they'll all be broken. You need to treat DNS separately. I'd suggest
setting up a second hostname www2.whatever.com and publishing to that.
Then, when you are satisfied the site has been moved and is operating
correctly, you switch DNS to send traffic to the new location. That avoids
down time and gives you the luxury of figuring stuff out on your own time
without a webmaster complaining the site is broken.

> - Do I just use the administrator account to publish?

Yes, you can do that, but you probably don't want your webmaster editing
later with it, so you need a site administrator account anyway.

> - If I create a new local user, what permissions or groups do I assign
> him/her to
> allow publishing and editing web pages?

None, you don't. See above.

>
> This will be a public internet web server. My firewall will forward port
> 80
> traffic only to this new server. What other security considerations are
> applicable?

Patch patch patch patch and patch. Other depends on exactly what you are
doing.

> - Can my user publish the web site remotely?

Yes. Once you have the FP site configured completely you can let them do
it. (I would advise that, as they probably have more experience at it.)

>
> Advanced Questions:
> ------------------------
> I have an exact server configuration from a hardware and software
> perspective. How can I create a fault tolerant situation where one server
> fails, the other server takes over? Is there such a thing as mirroring the
> web site to the other server automatically?

Windows does cluster server for that, or there are third party apps to do
it.

22 Aug 2006 2:32 PM

JoeF

Thank you for taking the time to answer my questions. You have been VERY
helpful!
Please clarify one task for me.
   - Make a virtual web normally. Right click and choose "FrontPage 2002
Server
   - Extensions - Extend"

   - In the resulting managment web page, add or create the user as an
   - administrator of the web.

I've already created the site and had the webmaster publish to it since I
joined his user name to the Local Administrators group. Can I still create
avirtual web or change the existing site to a virtual web? FP extensions are
enabled on thecurrent site. - I guess I'm a little confused. Any 'more' help
is appreciated. Thanks again!

-JoeF

Show quote

"Funkadyleik Spynwhanker" wrote:

>
>
> "JoeF" <J***@discussions.microsoft.com> wrote in message
> news:671EF149-FF41-4FAC-A828-BB8EBA350AE1@microsoft.com...
> > Details:
> > ---------
> > Running Windows Server Enterprise 2003 SP1 w/all Updates
> > Running IIS 6.0
> > Enabled Server extensions, ASP and .Net
> > Did NOT configure FTP service
> > Joined to Workgroup WORKGROUP
> > Renamed Default Web Site Description with my own description
> > Located behind hardware firewalls.
> >
> > Questions:
> > -------------
> > What/how do I configure a user to publish their Frontpage 2003 Web Site to
> > this fresh new IIS server? Do I need to delete the default web site
> > directories first?
>
> Make a virtual web normally. Right click and choose "FrontPage 2002 Server
> Extensions - Extend"
>
> In the resulting managment web page, add or create the user as an
> administrator of the web.
>
> You do _NO_ modifications to file permissions in the root folder, and _NO_
> configuration in the Users area on the server for this. The FrontPage
> (Sharepoint) administration web site does that for you.
>
>
> >   - When using FrontPage 2003, do I publish to http://server-name/
> >        - Will this affect any links when viewing from the public internet
> > after
> >          firewall forwards port 80 traffic?
>
> No, they'll all be broken. You need to treat DNS separately. I'd suggest
> setting up a second hostname www2.whatever.com and publishing to that.
> Then, when you are satisfied the site has been moved and is operating
> correctly, you switch DNS to send traffic to the new location. That avoids
> down time and gives you the luxury of figuring stuff out on your own time
> without a webmaster complaining the site is broken.
>
> >   - Do I just use the administrator account to publish?
>
> Yes, you can do that, but you probably don't want your webmaster editing
> later with it, so you need a site administrator account anyway.
>
> >   - If I create a new local user, what permissions or groups do I assign
> > him/her to
> >     allow publishing and editing web pages?
>
> None, you don't. See above.
>
> >
> > This will be a public internet web server. My firewall will forward port
> > 80
> > traffic only to this new server. What other security considerations are
> > applicable?
>
> Patch patch patch patch and patch. Other depends on exactly what you are
> doing.
>
> >   - Can my user publish the web site remotely?
>
> Yes. Once you have the FP site configured completely you can let them do
> it. (I would advise that, as they probably have more experience at it.)
>
> >
> > Advanced Questions:
> > ------------------------
> > I have an exact server configuration from a hardware and software
> > perspective. How can I create a fault tolerant situation where one server
> > fails, the other server takes over? Is there such a thing as mirroring the
> > web site to the other server automatically?
>
> Windows does cluster server for that, or there are third party apps to do
> it.
>
>
>

22 Aug 2006 9:04 PM

Funkadyleik Spynwhanker

Virtual web = Thingie on the server you can see in IIS, as opposed to a
folder with web site files in it "a web". It's a collection of settings on
the server that tell the server to respond to certain traffic using the
hostname, what folder the files are in, if it requires a user/pass, etc.

If you already published, you have one set up already.

Same with the server extensions. They are administered via a set of web
pages and scripts that get installed with IIS. You access them via a
browser program while sitting in front of the server, or in the case of
specific web settings you can use a link across the internet. You open all
this up by right clicking on the virtual web in the MMC, or by using a
shortcut that exists in your "Administrative Options" in "Control Panel".
(Again, while sitting in front of the server or otherwise accessing the
screen.)

You were set up to make it a comlicated process involveing messing around
with users, permissions, folder trees, etc. when it isn't that complicated
(and would be prone to error if it was done manually.) Basically, you make
a web site, "extend" it with FP. Thats it. The "extending" process
includes creating a user to edit the site which is NOT an administrator on
anything but the web site. (They wouldn't be able to log into your server
and format the hard drive, for example.)

But it sounds like you got to where you need.

Show quote

"JoeF" <J***@discussions.microsoft.com> wrote in message
news:4076C579-EF18-4A83-BC00-C548DC41D4EC@microsoft.com...
> Thank you for taking the time to answer my questions. You have been VERY
> helpful!
> Please clarify one task for me.
>   - Make a virtual web normally. Right click and choose "FrontPage 2002
> Server
>   - Extensions - Extend"
>
>   - In the resulting managment web page, add or create the user as an
>   - administrator of the web.
>
> I've already created the site and had the webmaster publish to it since I
> joined his user name to the Local Administrators group. Can I still create
> avirtual web or change the existing site to a virtual web? FP extensions
> are
> enabled on thecurrent site. - I guess I'm a little confused. Any 'more'
> help
> is appreciated. Thanks again!
>
> -JoeF
>
> "Funkadyleik Spynwhanker" wrote:
>
>>
>>
>> "JoeF" <J***@discussions.microsoft.com> wrote in message
>> news:671EF149-FF41-4FAC-A828-BB8EBA350AE1@microsoft.com...
>> > Details:
>> > ---------
>> > Running Windows Server Enterprise 2003 SP1 w/all Updates
>> > Running IIS 6.0
>> > Enabled Server extensions, ASP and .Net
>> > Did NOT configure FTP service
>> > Joined to Workgroup WORKGROUP
>> > Renamed Default Web Site Description with my own description
>> > Located behind hardware firewalls.
>> >
>> > Questions:
>> > -------------
>> > What/how do I configure a user to publish their Frontpage 2003 Web Site
>> > to
>> > this fresh new IIS server? Do I need to delete the default web site
>> > directories first?
>>
>> Make a virtual web normally. Right click and choose "FrontPage 2002
>> Server
>> Extensions - Extend"
>>
>> In the resulting managment web page, add or create the user as an
>> administrator of the web.
>>
>> You do _NO_ modifications to file permissions in the root folder, and
>> _NO_
>> configuration in the Users area on the server for this. The FrontPage
>> (Sharepoint) administration web site does that for you.
>>
>>
>> >   - When using FrontPage 2003, do I publish to http://server-name/
>> >        - Will this affect any links when viewing from the public
>> > internet
>> > after
>> >          firewall forwards port 80 traffic?
>>
>> No, they'll all be broken. You need to treat DNS separately. I'd
>> suggest
>> setting up a second hostname www2.whatever.com and publishing to that.
>> Then, when you are satisfied the site has been moved and is operating
>> correctly, you switch DNS to send traffic to the new location. That
>> avoids
>> down time and gives you the luxury of figuring stuff out on your own time
>> without a webmaster complaining the site is broken.
>>
>> >   - Do I just use the administrator account to publish?
>>
>> Yes, you can do that, but you probably don't want your webmaster editing
>> later with it, so you need a site administrator account anyway.
>>
>> >   - If I create a new local user, what permissions or groups do I
>> > assign
>> > him/her to
>> >     allow publishing and editing web pages?
>>
>> None, you don't. See above.
>>
>> >
>> > This will be a public internet web server. My firewall will forward
>> > port
>> > 80
>> > traffic only to this new server. What other security considerations are
>> > applicable?
>>
>> Patch patch patch patch and patch. Other depends on exactly what you are
>> doing.
>>
>> >   - Can my user publish the web site remotely?
>>
>> Yes. Once you have the FP site configured completely you can let them do
>> it. (I would advise that, as they probably have more experience at it.)
>>
>> >
>> > Advanced Questions:
>> > ------------------------
>> > I have an exact server configuration from a hardware and software
>> > perspective. How can I create a fault tolerant situation where one
>> > server
>> > fails, the other server takes over? Is there such a thing as mirroring
>> > the
>> > web site to the other server automatically?
>>
>> Windows does cluster server for that, or there are third party apps to do
>> it.
>>
>>
>>

24 Aug 2006 3:38 AM

Roger Abell [MVP]

Hi Joe,

I am going to differ a little on this.
I never give out FrontPage level "administrator" to web content owners,
instead at most giving "advanced author" role. The "administrator" role
does enable them to do some things, like "server health", and defining
new machine local user accounts for use with their web/website.

All that you need to do, at a minimum, is to
a) define a new website, or a new web vdir in an existing site
b) extend that with the FP server extensions
c) define a normal, limited account for use by the owner
d) use the Sharepoint Admin pages, or via the Administer link
    on the page you are left on after extending, to grant Advanced
    Author to the account defined for use with the web or site root web
This can also take the form
a) define new website in IIS if this is new entire site, not just new
    web in existing site.
b) browse to the Sharepoint administration website
c) if this in new site, select to extend the site
else
c) if this is a new web in existing site, select to administer that site,
    and on the site's admin page click to add new web
d) access the Sharepoint admin page for the new site or web and
    set grant of Advanced Author role to Windows limited account
    that will be owner/publisher

Much depends on what you mean by a public internet webserver
If you are looking at hosting webs for diverse owners, be aware that
a standard install of FP server extensions will NOT help you to keep
one web/website owner from reading source of another, even if you
use different app pools configured to use different accounts. Further,
if you go to the work of making sure there is such segmentation, which
is not easy to do, then a FP extended web owner with the FP role of
Administrator can destroy that separation by simply triggering some of
the server health functions.

Roger

Show quote

"JoeF" <J***@discussions.microsoft.com> wrote in message
news:671EF149-FF41-4FAC-A828-BB8EBA350AE1@microsoft.com...
> Details:
> ---------
> Running Windows Server Enterprise 2003 SP1 w/all Updates
> Running IIS 6.0
> Enabled Server extensions, ASP and .Net
> Did NOT configure FTP service
> Joined to Workgroup WORKGROUP
> Renamed Default Web Site Description with my own description
> Located behind hardware firewalls.
>
> Questions:
> -------------
> What/how do I configure a user to publish their Frontpage 2003 Web Site to
> this fresh new IIS server? Do I need to delete the default web site
> directories first?
>   - When using FrontPage 2003, do I publish to http://server-name/
>        - Will this affect any links when viewing from the public internet
> after
>          firewall forwards port 80 traffic?
>   - Do I just use the administrator account to publish?
>   - If I create a new local user, what permissions or groups do I assign
> him/her to
>     allow publishing and editing web pages?
>
> This will be a public internet web server. My firewall will forward port
> 80
> traffic only to this new server. What other security considerations are
> applicable?
>   - Can my user publish the web site remotely?
>
> Advanced Questions:
> ------------------------
> I have an exact server configuration from a hardware and software
> perspective. How can I create a fault tolerant situation where one server
> fails, the other server takes over? Is there such a thing as mirroring the
> web site to the other server automatically?
>
> Thanks for any suggestions/assistance you may have. I appreciate it!
>
> Regards,
> JoeF

24 Aug 2006 3:50 PM

JAMOS

Hi,

You can use MS Application Center 2000 for load balancing and other admin
functions such as application pool admin and monitoring. I can supply more
info if needed.

--
CHEERS,
JAMOS

Show quote

"JoeF" wrote:

> Details:
> ---------
> Running Windows Server Enterprise 2003 SP1 w/all Updates
> Running IIS 6.0
> Enabled Server extensions, ASP and .Net
> Did NOT configure FTP service
> Joined to Workgroup WORKGROUP
> Renamed Default Web Site Description with my own description
> Located behind hardware firewalls.
>
> Questions:
> -------------
> What/how do I configure a user to publish their Frontpage 2003 Web Site to
> this fresh new IIS server? Do I need to delete the default web site
> directories first?
>    - When using FrontPage 2003, do I publish to http://server-name/
>         - Will this affect any links when viewing from the public internet
> after
>           firewall forwards port 80 traffic?
>    - Do I just use the administrator account to publish?
>    - If I create a new local user, what permissions or groups do I assign
> him/her to
>      allow publishing and editing web pages?
>
> This will be a public internet web server. My firewall will forward port 80
> traffic only to this new server. What other security considerations are
> applicable?
>    - Can my user publish the web site remotely?
>
> Advanced Questions:
> ------------------------
> I have an exact server configuration from a hardware and software
> perspective. How can I create a fault tolerant situation where one server
> fails, the other server takes over? Is there such a thing as mirroring the
> web site to the other server automatically?
>
> Thanks for any suggestions/assistance you may have. I appreciate it!
>
> Regards,
> JoeF