> I'd like to hear from those who have had to manage IT resources for
> offices that are located on opposite sides of oceans.
>
> Our primary challenge right now is this: Our original offices, and
> our CIFS file servers, are located in Wisconsin, USA. We also have an
> office in the Netherlands. The folks in the Netherlands interact
> heavily with files on the CIFS file servers in Wisconsin - as does the
> entire company.
Depending on what type of CIFS server you're using ... If it's at least
Windows Server 2003 R2 ... I'd recommend DFS. All the participating AD
servers/CIFS servers synchorinize to each other across the WAN at whatever
rate they can, while each one has a copy of the CIFS share. Wherever a user
sits, they use the same UNC path, and the fileserver they actually interact
with is whatever one is closest. So the Netherlands people get LAN speeds,
and Wisconsin users get LAN speeds ... and the servers just sync to each
other as best they can across the WAN.
Here is some of the procedure I follow for myself:
1) Go to Add/Remove Programs / Windows Components
2) Add: Distributed File System
3) After it's done, go to Administrative Tools / DFS Management (not to
be confused with Distributed File System)
4) Right-click on Namespace, and Add New Namespace
a. Server: yourservername
b. Name: yoursharename
c. Edit Settings
i. You'll notice by default it uses C: Change to D:
ii. Custom Permissions. Everyone Full Control.
iii. Click Next, Ok, Whatever. Until you select
NameSpace Type.
d. NameSpace Type: Domain-based \\example.dom\yoursharename
e. Next, Create, Close. Whatever
Apparently I didn't write down the steps to sync between more than one
server. But I've done it before, so I know it can be done, and I know it
works reasonably well.
_______________________________________________
Discuss mailing list
Discuss@lopsa.org
http://lopsa.org/cgi-bin/mailman/listinfo/discuss
This list provided by the League of Professional System Administrators
http://lopsa.org/
