Re: front page 2003 running on small business server 2003 r2 issue

Ron Symonds (one "m") and Ronx are the same person. :)

FrontPage extensions are found by:
Control Panel->Add/Remove Programs
Click Add/Remove Windows Components
Click Application Server
Click Details button
Click Internet Information Service (IIS)
Click Details
Tick FrontPage 2002 Server Extensions
Click OK, Click OK, Click Next

You will need disc one for the Operating System.

Next step is to create a new website or two. This will require that the server is bound to multiple IP addresses - one extra IP address for each new website. To set this up you need
Control Panel->Network Connections-Local NetWork->Properties
Internet Protocol (TCP/IP)
Properties
Advanced
Add
Fill in the form
Click OKs to clear the dialogues and restart the computer.

Create folders for the websites.

Use IIS MMC to create the websites.

Extend the websites using
Control Panel->Administrative Tools->SharePoint Administration Manager
Some advice for this is at http://www.rxs-enterprises.org/fp/b/smtp - this is not the complete handbook, but may get you going.

Do not confuse the above with SharePoint Central Administration, which is for SharePoint sites.
--
Ron Symonds - Microsoft MVP (FrontPage)
Reply only to group - emails will be deleted unread.

http://www.rxs-enterprises.org/fp

FrontPage Support: http://www.frontpagemvps.com/




"sangsara enterprises ltd." <sangsaraenterprisesltd@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:15CB3670-F734-4F9C-9A7D-199858FCADE8@xxxxxxxxxxxxx:

It took some time to assemble an accurate overview of our exchanges so as to
attempt a feasible action plan. Double teaming two Ron(s) added an extra bit
of muddle, as did the information interchange timings, but was able to
achieve a satisfactorily informative outcome using the old wasteful hard copy
paper/cut and paste methodology.

What I get is: Ron Symmonds advises first installing Server Extensions to be
found on my Windows OS CD. Then there is the creation of new IIS Websites
preliminary to publishing Front Page content websites to these receptacles.
To clarify what is on this box: Small Business Server 2003 Standard R2 OS -
to which I have an effectively upgraded to Premium Edition as already in
possession of Front Page 2003 and SQL Server 2005 [with SP2]. Where exactly
are these extensions? Disk One gives me the option to install the OS but no
partial option is apparent; and the Technologies CD also provides no such
option. BTW thank you for your efforts to clarify other technical
relationships between the IIS server function and Front Page interface as
well as the real relevance of using template web sites.

Question: How and where do I go to install the Extensions from where among
my OS CDs?

RonX [also referred to as Thomas? by Ron Symmonds] have tried to go through
Control PanelàAdd/Remove ProgramsàWindows Components. There is no 'option'
choice presented under IIS here, IIS itself is not displayed as a separate
component among the 15 shown. Does it form part of another component, and if
so which one and what's the protocol involved to get the job done?

Guys, appreciate your help to get the foundations in place properly before
attempting the next step of setting up the IIS Server enabled web site
together. This is stage one. Only after these developmental aspects are
under control can my attention advance to shift on to Sharepoint Services.
It is imperative these technical aspects get in place so my actual
operational projects can finally get started.

--
peter fischer


"Ronx" wrote:

> You are mistaken.
>
> FrontPage will create sub webs in an existing web site that has FP
> extensions installed. It will create disc based webs on a hard disc,
> where there is NO web server. It cannot create a brand new, server
> based web site. A new web site requires a new IP address or Host
> Header, DNS, a folder on the disc drive ... FrontPage might be able to
> produce the folder, but cannot update DNS or supply Host-Headers or IP
> addresses.
>
> As Thomas said, the FP extensions for Windows 2003 are on the Windows
> CD.
>
> Template sites are just templates - design guides. They contain some of
> the files necessary to go IN a web site, they are not complete web
> sites.
> Apart from the database wizards, they do NOT include form handlers -
> these depend on the server, FP extensions is an example of a form
> handler. The database wizards do not require FrontPage extensions on
> the server.
>
> The last version of FrontPage that included the extensions was FP 2000.
> This included FP2000 extensions, which if installed would break Windows
> 2003 (probably requiring reformat and re-install to repair).
>
> --
> Ron Symonds - Microsoft MVP (FrontPage)
> Reply only to group - emails will be deleted unread.
>
> http://www.rxs-enterprises.org/fp
>
> FrontPage Support: http://www.frontpagemvps.com/
>
>
>
>
> "sangsara enterprises ltd."
> <sangsaraenterprisesltd@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:056E2DB5-815C-46EC-B7BA-E519CA72D889@xxxxxxxxxxxxx:
>
> > Ronx, now you have me somewhat confused. it is my understanding front page
> > 2003, when used to create a web site, does the whole job. meaning - when one
> > publishes the site from the hard drive where it is originally saved [for
> > control purposes] to a web server the site is created on the web server by
> > front page itself. the only difference in my circumstance is the fact iis
> > 6.0 is my web server and resident on the same computer as the one used to
> > create the site. in fact to avoid chances of comitting 'operator error' the
> > test sites used by me are ms template sites, so should be complete with all
> > the necessary service files. furthermore, it is also my [perhaps misguided]
> > belief when installing front page as a full install with aoo the options the
> > server extensions are included by default. are you suggesting running the
> > windows business server program to reinstall server extensions? just do not
> > want to get more muddle in the mix than need be.
> >
> > peter fischer
> >
> >
> > "Ronx" wrote:
> >
> > > I have only a passing acquaintance with SBS, but IIS does not need much
> > > configuring, except for individual web sites.
> > > The company web site and other web sites can be dealt with in parallel.
> > > The Company Web Site uses SharePoint Services, not the FrontPage
> > > extensions; it is unlikely (though possible) that other sites will use
> > > WSS, but may use FrontPage extensions instead.
> > >
> > > Install FrontPage extensions from the Windows 2003 CD.
> > > Create your websites from IIS MMC and extend them if you need
> > > extensions.
> > > --
> > > Ron Symonds - Microsoft MVP (FrontPage)
> > > Reply only to group - emails will be deleted unread.
> > >
> > > http://www.rxs-enterprises.org/fp
> > >
> > > FrontPage Support: http://www.frontpagemvps.com/
> > >
> > >
> > >
> > >
> > > "sangsara enterprises ltd."
> > > <sangsaraenterprisesltd@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> > > news:9F4DBC03-C71B-4EF1-89FF-D7A13C036FCE@xxxxxxxxxxxxx:
> > >
> > > > thanks for your reply Ronx. from your questions it would seem i've gone
> > > > about this whole exercise incorrectly. is it possible you could work with
> > > > me, provide me step-wise directions so i can achieve each plateau in an
> > > > orderly fashion. this may allow me to achieve the outcome, if the interim
> > > > steps are implemented properly- obviously something all wrong in my
> > > > blundering so far.
> > > > is it on target to assume you have familiarity with the the small business
> > > > server operating system as well? am doing other work debugging iis in
> > > > parallel efforts on my part. seems appropriate. am doing so within another
> > > > thread.
> > > > it would seem first i must correctly configure iis within sbs, discouver
> > > > what's going on right now. next:add server extensions and then go about
> > > > actually implementing the 'company web' itself before trying to add the other
> > > > web sites.
> > > > otherwise there'd be too many loose variables on the table. or is my take
> > > > incorrect?
> > > > --
> > > > peter fischer
> > > >
> > > >
> > > > "Ronx" wrote:
> > > >
> > > > > Have you created a website in IIS for the new sites? Did you wish to
> > > > > overwrite the Company Web site, which it sounds like you are doing?
> > > > > Are the new websites sharepoint sites, or FrontPage extended sites? If
> > > > > extended, you will need a new website and install the FrontPage
> > > > > extensions on the server, then configure the new website with the
> > > > > extensions.
> > > > > --
> > > > > Ron Symonds - Microsoft MVP (FrontPage)
> > > > > Reply only to group - emails will be deleted unread.
> > > > >
> > > > > http://www.rxs-enterprises.org/fp
> > > > >
> > > > > FrontPage Support: http://www.frontpagemvps.com/
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > "sangsara enterprises ltd."
> > > > > <sangsaraenterprisesltd@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> > > > > news:EE60EFFC-0789-43C6-8AC8-365F45614C2E@xxxxxxxxxxxxx:
> > > > >
> > > > > > bear with me, am a newby with all kinds of system issues. this one concerns
> > > > > > attempts to publish two web sites [both templates so they're clean] to
> > > > > > localhost. 'myfirstattempt' local log showed success, but using explorer
> > > > > > only turned up default 'companyweb' with the option to install it. have
> > > > > > never been able to get this to work in either sharepoint 2.0 or 3.0, so for
> > > > > > all intents it remains unistalled.
> > > > > >
> > > > > > but it is the only thing which comes up on 'localhost'. then tried to
> > > > > > publish 'publishtowebserver' another template. log files reveal conflict for
> > > > > > index.htm both in local and remote site logs. hit 'publish' button @ lower
> > > > > > right next. got dropdown box with list of 'conflicts', chose to 'ignore and
> > > > > > continue', got another dropbox:FP3 has detected that changes you have made to
> > > > > > the navigation structure conflicts with changes another author has made to
> > > > > > website you are publishing to. what do you want to do-->let FP merge the
> > > > > > changes. comment: interesting as am the only user; outcome: both local
> > > > > > +remote web site confolict @ index.htm.
> > > > > >
> > > > > > in explorer localhost brought up a sbs2003 page: options: if you chose 'my
> > > > > > company intranet web site" you get mycompany homepage; choose network
> > > > > > configruation wizard you get 'page cannot be found, and error 404; choose
> > > > > > remote workplace' it asks for username/password access; 'information and
> > > > > > answers' choice provides options to learn all about SBS2K3
> > > > > >
> > > > > > am trying to solve this issue from sbs2k3r2 side troubleshooting a number of
> > > > > > aspects. how this interfaces with fp3 may provide a common solution.
> > > > > > uninstalling and reinstalling iis6.0 inadvisable; have reinstalled sharepoint
> > > > > > 2.0 and the 3.0 upgrade to no avail.
> > > > > >
> > > > > > my problem solving skills limited by lack of experience and confidence.
> > > > > > really need step by step direction to conquer these challenges. thanks in
> > > > > > advance, it will probably be a long and tedious process.
> > > > > >
> > > > > >
> > > > > > --
> > > > > > peter fischer
> > > > >
> > > > >
> > >
> > >
>
>

.