In a thin-client environment, most applications, like Novell® NetDrive 4.1, are installed on the server. This allows mobile users to access their applications from a virtual desktop or thin-client session. However, because of the Novell iFolder® automatic synchronization features, you can't install iFolder on the thin-client server. It would cause all of the user data to sync down to the thin-client server's hard drive.
NetDrive supports Windows NT 4 and 2000 servers running any of the following thin-client applications:
IMPORTANT:Novell NetDrive 4.0 supports mapping drives via ZENworks OnDemand Services only to iFolder 1.0 servers. Novell NetDrive 4.1 supports mapping drives via ZENworks OnDemand Services to both iFolder 1.0 and 2.x servers.
After NetDrive is installed on your thin-client server, a mobile user can use NetDrive to map a drive to the iFolder server, thereby making the iFolder server's copy of his iFolder data accessible via Windows Explorer. (For a visual representation of how this looks, see Step 9.)
Figure 4-1 Using NetDrive to Access Your iFolder Files
If you are familiar with iFolder, you know that it has a Java* applet that lets users access their files from a browser. So, why map a drive to get to your files when you can just open up a browser? The advantages of using NetDrive over a browser in this situation are as follows:
For instructions on how to use NetDrive on your thin-clint server to access your iFolder files, continue with the next section, “Installing NetDrive on a Terminal Server.”
For more information on iFolder, see the Novell iFolder documentation.