Hello All,

Hope someone can shed me the light on these?



1. In WSS 2.0, I only need to type in "Companyweb", however, to open
WSS 3.0 web site, I have to type in "http://server:8082". Is there
any way to make "server:8082" work without typing in "http"?

2. The company has 4 main departments that each currently has a
respective shared folder at huge size on server. For example,
"Construction" - 80GB, "Office Admin" - 50GB, "Environment" - 70GB,
"VP" - 30GB. There are many photos in each folder, that's why they are
huge.
Not everything in the shared folders will be moved to WSS 3.0, but I
expect the database will grow huge eventually.
- Will the new WSS 3.0 site be able to support such amount of data?
- Should I leave all departments in the main portal "http://server:
8082" or should I make a few more portals, such as "http://server:
8083", "http://server:8084", etc for each department?
- I think the real question for this is "Should I leave each
department for its own content database? and How to do it?"

Thanks a lot
jack

Inline:

-Cliff


"Jack" <dontaskwhoiam2001@newsgroup> wrote in message
news:db69598e-67b5-4c46-bae0-ae3849a168ad@newsgroup

> Hello All,
>
> Hope someone can shed me the light on these?
>
> 1. In WSS 2.0, I only need to type in "Companyweb", however, to open
> WSS 3.0 web site, I have to type in "http://server:8082". Is there
> any way to make "server:8082" work without typing in "http"?

Not that I'm aware of. IE makes "guesses" on the http protocol and port,
but when specifying a non-standard port, that negates most browsers'
(including IEs) intelligent guessing, so the protocol must also be
specified. You *could* set up the sharepoint site to operate on port 80
with a host header and that could potentially resolve your issue, however.

> 2. The company has 4 main departments that each currently has a
> respective shared folder at huge size on server. For example,
> "Construction" - 80GB, "Office Admin" - 50GB, "Environment" - 70GB,
> "VP" - 30GB. There are many photos in each folder, that's why they are
> huge.
> Not everything in the shared folders will be moved to WSS 3.0, but I
> expect the database will grow huge eventually.
> - Will the new WSS 3.0 site be able to support such amount of data?

Not on SQL Server Express/MSDE. The database has a hard limit. If you are
running a full SQL Server then sure.

> - Should I leave all departments in the main portal "http://server:
> 8082" or should I make a few more portals, such as "http://server:
> 8083", "http://server:8084", etc for each department?
> - I think the real question for this is "Should I leave each
> department for its own content database? and How to do it?"

Based on the sizes you gave, wouldn't matter much. You either can handle
all of them (a full blown SQL Server install) or you can't. Beyond that, it
is more of an organizational choice. I prefer using site collections for
large organizational barriers and sites within the collection for
departments, but each sharepoint setup is unique in that regard and very
company specific.

>
> Thanks a lot
> jack
>