We have seven location that we would like to setup, and connect. The
location are spread out over a 60 mile radius.
I am meeting with the local bell company today to discuss what option are
availible to us for high speed communication.
If anyone could look the following information, and give me an opinion that
I can take to my boss, I would appreciate it.
If you need more information, please let me know.
Proposal for OGLE NET:
The corporate office will run Microsoft Back Office Server, using MS-SQL,
MS-Exchange, MS-Proxy Server, MS-System Management Server and MS-WinNT
Each remote location will run Microsoft Back Office Server, MS-Exchange,
MS-Proxy Server, MS-System Management Server and MS-WinNT Server.
The clients for all location will run Windows 95 or 98. Services will be
installed for Exchange, SQL, Proxy, SMS and Microsoft Networks.
All location will be connected via the Proxy Servers (no caching, no dial
on demand) using a yet to be decided high-speed connection (T1, ISDN). The
possibility of Internet VPN is still being discussed.
All units must have a unique name. Name conventions are as follow.
First two digits indicate machine location (00=CORP, 02=Arlington Salon,
Digits three through six indication OS on unit (NTS40 = NT Server 4.0,
WIN95 = Windows 95, DOS60 = Dos Version 6, etc.)
Digits seven through nine indicate the role of the computer (PFS= Primary
File Server, WKS=General Work Station, APT=Appointment Book, etc)
The last two digits indicate the unit number for that role.
The example above indicates that the machine is in the corporate office,
running NT Server 4.0, acting as a file server and is the first file server
in the group.
02WIN95APT02 would indicate that the machine is in the Arlington salon,
running Windows 95, acting as an Appointment Book and is the second
appointment book in the group at that location.
MS- System Management Server.
All soft installation will occur via the SMS. It will handle inventory of
all machines, at an administrators defined interval (default to seven
days). The inventory includes OS, BIOS, HD (size/free), memory, installed
software, last config change, resource settings (IRQ and environmental
The SMS administrator can query this inventory to find machines that can
run a specific software package, have had config changes or may need
upgrading. The SMS administrator can create packages to be sent to clients
for upgrading software or new installations. The clients SMS service will
check for new packages, and depending on the package setting, perform the
upgrade with or without user intervention. Packages can be installed at
users choice or mandatory.
This mail host will handle all email and meeting requests. Each location
will have a domain name, so email will be routed to the correct Exchange
Server. All email is stored on the Exchange Server and auto archived after
three weeks. Users can access their Exchange account from any workstation.
The user profile will use the network security cache to log the user into
their mailbox. This also allows the users to "Roam", so the contents of
the users inbox will not remain on the workstation.
Exchange Mailboxes are automatically setup when the user is added to the NT
The SQL Server will handle all database transactions for the SALON.DB. It
offers us the ability to unload data while the system is running, so we can
have the database redundant at a disaster recovery point. That recovery
database will be updated a least every hour, more often if the network is
not experiencing loads over 50%.
Each location will connect to the data source via a Proxy Sever. This will
allow use to use Intranet or Internet planning. It will also provide us
with a higher level of security. Client requests are sent to Proxy Server,
then routed to the data source.
The Protocol used will be TCP/IP. DHCP will lease the IP address for up to
three days. If an IP address expires, the client will receive a new lease
upon sign on. This will eliminate the need to manual assign IP addresses.
When the users signs on the SMS will update the clients Inventory to
reflect the change in IP address.
I have a model network up and running with everything described above,
expect the Proxy Server (I didn't have phone lines in the work area).
Everything is running fine. I started to run disaster testing today.