I am working on a Domain DFS Namespace plan and was wondering how some
of you all organize your information in it.
Specifically I was wonder do you publish Home Directories, Profile
Directories and Department File shares in it.
Out goal is to develop a Unified Data Access Service for PC, but to
provide accommodations for UNIX, Mac, and FTP / Web access. I don't
necessarily want to make it so Macs and Unix have to bind to our AD to
get access to these services.
I am also wondering if any of you provide access to no Microsoft clients
via the Domain DFS or do you stand up a stand alone DFS and install NFS
services on it?
Is it feasible to mix Domain DFS links with standalone DFS.
Here something as an example.
Logical
company.lan
-Domain-DFS
Users
Org
Software
Pub
- Standalone DFS - (Clustered) Mapped to Users (Needs High
Availability)
- Profiles
- Home (Needs MSFT, Mac, Unix access) Possibly URL as well.
- Standalone DFS - (Clustered) Mapped to Org
- Each Department (MSFT, Mac, Unix, maybe URL)
- Standalone DFS - (Clustered) Mapped to Software
- Each Application Type (Might go away with Softricity
- Public (MSFT, Mac, UNIX, FTP and URL)
- Standalone DFS - (Clustered) Mapped to Pub
- Outgoing (MSFT, Mac, UNIX, FTP and URL)
- Incoming (Accessable via FTP and URL)
Physical
AD Domain
Stand-Alone DFS Server Clusters.
Main Site DR Site
Servers Servers
-FS1 -DRFS1
-FS2 -DRFS2
-FS3 -DRFS3
-FS4 -DRFS4
Probably use some type of SAN storage and Mirroring to host actual data.
List info : http://www.activedir.org/List.aspx
List FAQ : http://www.activedir.org/ListFAQ.aspx
List archive: http://www.mail-archive.com/[email protected]/
