From: Greg Chapman [greg@mousetrax.com]

Sent: Sunday, November 07, 1999 11:01 AM

To: H. Dwight Paul

Subject: Re: Enabling Discussions per webserver

I think I'll answer this from the bottom up.<g>

Localhost is a carry-over of TCP terminology which refers to the local

machine's IP address. On your NT server, if you examine the contents of

c:\winnt\system32\drivers\etc\hosts (hosts is a file that has no extension

in its name) you should see the following entry:

localhost 127.0.0.1

127.0.0.1 is a reserved IP address that poitns directly to the TCP stacks in

memory, not the network card. If you ping LocalHost from the server's

console, you'll get an echo or reply from 127.0.0.1. Microsoft uses this

value when setting up Web based admin pages for all it's web technology

offered up through IIS. Some of the more common ones are

http://localhost/iisadmin

http://localhost/iishelp

http://localhost/ntadmin

http://localhost/admin

For OSE it's http://localhost/msoffice/msoadmin

Localhost can be replaced by the URL of the machine or its IP address. On

most of the admin stuff (OSE being the exception here), only localhost can

be used because MS sets the admin stuff so that no external IP addresses may

access it. Without modification to the IP security in the MMC, no external

IP address may successfully load the admin pages.

Okay, now, since we're talking about the MMC all of a sudden, you can use

this tool to find out the local drive path that a particular virtual

directory is living under. If, in the MMC (Start, programs, NT Option Pak 4,

Internet Service Manager), you expand Default Web Site, MSOffice and right

click on MSOAdmin and choose properties, A dialog of properties will appear.

On the General tab, there will be a Local Path box that displays almost all

you want to know. By default, the MSOadmin path will be /MSOffice/MSOadmin.

Since there's no more info here, we need to know the local path to MSOffice.

Close this properties sheet and right click on MSOffice and choose

properties. In the Local Path box here, you'll see the default path:

c:\program files\microsoft office\office\scripts1\1033 . If you look up that

path in Windows Explorer, you'll see that there is an MSOAdmin folder in it

which contains the pages displayed by going to

http://localhost/msoffice/msoadmin .

I hope this doesn't sound like I'm talking down. That's not my intent as I

just want to be absolutely clear on the relationship all these systems have

to each other. Virtual paths translated to physical paths can be a real

monster to get a grip on!<g>

Hope that helps!

Greg

How to create a Dynamic Document Directory in Front Page

There is an import files wizard template, that you can pick from the NewWeb dialog box. This will import all the files from a directory into a subfolder on the web. You then can build a page on which you can enter hyperlinks to the files. The unfortunate thing about this wizard is that it doesn't do that for you. Also, unfortunately, you have to enter each hyperlink singly. You can't select all the files and say have it put hyperlinks to all the files in the page you have constructed. Also, unfortunately, this directory then does not show any additional files that you may publish with Word, until you go in and create a hyperlink.

There is a way to set up a Dynamic table of files in the folder, that will show all the files that are deposited in the folder. First you create the folder and put a single file into it using Front Page. Then you open the folder, select the file in the page list control, and click properties. In the properties panel, choose WorkGroup properties, select an existing property, or add a new property that you want to use to designate the files you want to appear on your directory listing, check that for the document, and close the properties panel. Then construct your directory page.

Open the web folder in which you want the directory page, click File|New|Frame and select an appropriate frame--the simplest you want is the header and single pane frame. You might also want one with a footer, and/or side panel for navigation structure. I used the header and single pane and will talk about that. I put this page in a discussion folder, so there is already a page called my_discussion_nav.htm. Choose this one to be 'added' to the header frame. Then choose new page for the second, and you will get a blank page in the panel below the header. (The advantage of this page construction is you do not have to set up another bunch of navigation buttons which could get out of sync at some future time.) Index down into the lower panel to where you want a header to be, and type your header text, and choose the format you want. Then go to the next new line and click the Insert menu, and choose component and then categories. A panel comes up, choose the category that you set up for this directory, choose how you want it sorted and what info you want shown with the title, and click OK. In design mode it will put in a line for every file you have in the folder with that category set that says "File in web", or something like that. Those lines will be changed into hyperlinked file titles in the browser.

You will then be able to save documents to the webfolder, giving them the WorkGroup Category on the fly, and your save documents will appear in the next instance of the directory page. The one fly in this particular ointment, is that the server administrator has to setup WorkGroup property use on the server, for WorkGroup properties to be available in Word2000. I have looked through the Technet Monthly disk and the KB disk, and find only one mention of doing this, which is to look on page 565 of "Using Office with a Web Serve". This sounds to be a book title. I can't believe that it is not documented somewhere on line, but I haven't found it yet. Without having WorkGroup property use set up on the server, you have to go in with Front Page and set the property on each document that you subsequently save. A major bummer.

How to create and run two web servers on the SBS server

There is a problem with trying to create a second web server to run on the SBS server. When you do that, using the procedure that you used to create the first one, the new web server is given the same default IPAddress, port, and Header Name. This then causes the new web server to be marked (Stopped) in the OSEAdministrator/IIS console. Any attempt to start it will produce an error message in the wcerr.txt file to the effect that there is a conflict in the web server address triple and you need to reconfigure the server before it can be started.

Solution: Before you attempt to create the second web server, from the SBS server's terminal, open the Network Applet in the Settings panel, click on Protocol|Properties to bring up the TCP/IP properties panel. On the IP Address tab, click Advanced, and then, under the IP Addresses listbox that displays the default IP Address of 10.0.0.2, click Add and input the IP Addresses you want to use. Be sure they do not conflict with any you have already assigned. Then OK all the panels out to the Desktop. It may not be necessary to reboot, at this point, but it is probably a good point.

Now, back in the IIS console, select your computer, and the click Actions|New|Web Site to bring up the New Web Site Wizard. Provide the description, click Next, and in the next panel--where you select the IP Address and the default "[All Unassigned]" is showing--click the listbox dropdown and select the IP Address you choose back in the TCP/IP properties panel. Then proceed as with a new Web server. This will produce a web server which can be configured by the OSEConfiguration Wizard and will be shown as running at the same time as your first web server.

You publish to this second web server by using the IP Address, rather than the name-- http://10.0.0.40, for example.

Wizard to Install Intranet in SQL database

Date: Tue, 29 Jun 1999 09:59:23 PDT

Subject: Re: Intranet setup on SBS 4.5?

From: "Hollis D. Paul" <Hollis@>

Newsgroups: microsoft.public.backoffice.smallbiz

In article <3778547F.4B6759B6@stonypoint-pr.com>, Mark Holoweiko wrote:

> Can anyone advise how to set up a corporate intranet accessible from the

> internet (for remote users) on SBS 4.5? All the Office 2000 hoopla has

> me thoroughly confused. Microsoft websites seem to imply that an upgrade

> to both FrontPage 2000 and Office 2000 are needed on all

> machines--server and client--at a minimum of $250 a pop. Yet SBS comes

> with some sort of intranet feature--I just don't get how to make it

> work for our workgroup of five (three of whom connect remotely via VPN,

> if that matters.)

>

You need to install the Office Server Extensions on the SBS server. I am

not sure if you install it from the server or from the workstation. I

installed from the server, and have not gotten it all to work yet.

Then you play a game of Adventure to find the wizard that will install the

service. The following path got me to the hidden cavern in which the

Wizard was hiding--there was no glowing mushrooms or anything to give a

clue, I just made a lucky guess.

Start|Programs|Office Server Extensions|Server Extensions Administrator

This brings up MS Console Object, version 1.1, which has three folders in

it: Internet Information Server, MS Transaction Server, and MS Server

Extensions. Expand the Internet Information Server Folder and click the

Action button above the panel. This provides a menu, one option of which

is New|{FTP site| Web site }. Then a wizard comes up.

The part that is not working for me is the configuration Wizard, which

adds the collaboration database to the SQL7 server. You might want to

look through the add permissions task in the Server Console and give the

user who is responsible for running the intranet all possible SQL7

permissions. Then perhaps the configuration Wizard will work for you.

After the fact, and much flailing around in dark passageways, I deleted

the directories under c:\InetPub\wwwRoot. Turns out these are the

directories that support the webservice that presents the SBS console. So

I have to recover them before I can add permissions to my user account.

What Account/Name is the OSE Installation Wizard asking for?

The KB article, Q216926, describes the procedure for installing the Office Server Extensions. Basically, it says, start the OSE Installation wizard and provide all necessary information. In steps 11 and 12, the OSE wizard is asking for the Account name and password that OSE will use to setup some user role groups for the collaboration database that been priviously created. What the wizard doesn't say is that it is not looking for the NT account names and associated password. Instead, it wants an SQL Login account name and password, which also has been previously created using the SQL7 Enterprise Manager. When this manager creates a login account, by default, it uses the NT account names and does not ask for a password at that point. The OSE installation will not use any of these NT type Accounts. It will only accept a login account of the SQL type. You have to specifically click the SQL Type radio button, at which point you can enter a name and a password for the account. The OSE Installation wizard will accept one of these Accounts and then create the 4 role groups, which you will later populate using the NT User Manager. It gives you the option of requesting autopopulation, but it does not do that.