What could befall you when building OCS infrastructure?
In the previous parts, I built the OCS infrastructure. The operating system that I used was Windows Server 2008 R2 and the database version was SQL Server 2008 R2. But throughout the article series, I explained the whole installation process as I did it on a Windows Server 2008 operating system. The purpose is to explain in detail what must be done especially for Windows Server 2008 R2, in a separate article (which is this one). Therefore, we can experience the problems which will arise because of the Windows Server 2008 R2 itself. This part of the article series is all about the possible problems and the things that must be completed when installing OCS 2007 R2 on a Windows Server 2008 R2 operating system. Lets start with the listing of problems that I am going to talk about in this article:
Following the rapid progress in networked computing, the conventional file transfer protocols became incapable for fulfilling the particular needs of multiple hosts. The need to access the shared files transparently from multiple hosts over a network conduced to the development of “distributed filesystems (DF)”. DF(s) provide this location transparency to the clients by hiding the underlying distributed structure, naturally in consideration of overhead in transmission and reception in addition to the local disk access times. One of the family member which is called NFS (Network File System) is likewise a file system protocol that allows a client computer (NFS client) to transparently access files on a remote computer (NFS server) over a network as if these files reside on the client computer itself.
