While this may not kill every application, it will most certainly cause problems for the more complex ones, such as OpenOffice, or Firefox Portable. The problem is that if more than one user uses the same installed copy of a Portable App at the same time, then they are sharing the data and configuration files. Whether you use a network drive, or terminal server, or other method to share the apps. In an other scenario, what will be changed when portable apps is installed on a terminal-server 2003? I read that is not possible, as the file ex firefox, will be used by only one user and for the second user it came out that the application is just in use. Now i thought, to not update all the applications on different sticks/hard disk from each user, to install the portable apps in the network file-server so that the users can start it from there and no data will lost when sticks or external hard disks will borken/lost Untill this problems all worked perfekt, updates too. the problem was that i had a problem with the disk, where i saved the portable apps and so i lost my files as the disk was broken. The idea behind is that the application will not be loaded on the usb-stick or lockal external hard disk, but on the file server for more users. Lastly, NetDrive lets you use Windows Explorer to easily view and browse your files.įor 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."įor more information on iFolder, see the Novell iFolder Documentation.Has everybody some experience with using protable apps on a file server in a network, where more than one user can use the applications of portable apps on the same time? Furthermore, with iFolder, at the end of your session, you must delete the files you worked on from the local workstation. If you access your iFolder files through a browser, you must manually upload and download your files. So, why map a drive to get to your files when you can just open up a browser? The advantage to using NetDrive over a browser in this situation is that once a drive is mapped to your iFolder server, you can modify your files without manually downloading and uploading them from your local workstation to the iFolder server-with NetDrive, the downloading and uploading activites are transparent to the user. If you are familiar with iFolder, you know that it has a Java* applet that lets users access their files from a browser. Using NetDrive to Access Your iFolder Files (For a visual representation of how this works, see Step 9.) Once 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. NetDrive 4.1 supports mapping drives via ZENworks OnDemand Servies to both iFolder 1.0 and 2.0 servers. IMPORTANT: NetDrive 4.0 supports mapping drives via Novell OnDemand Services to only iFolder 1.0 servers. NetDrive supports Windows NT servers running any of the following thin-client applications: However, because of the Novell ® iFolder TM automatic syncronization features, you can't install iFolder on the thin-client server (this would cause all of the user data to sync down to the thin-client server's hard drive). This allows mobile users to access their applications from a virtual desktop or thin-client session. In a thin-client environment, most applications, like NetDrive, are installed on the server. Using NetDrive and iFolder in a Thin-Client Environment
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |