The zero-install deployment option is not appropriate for all situations.
See below for other automatic start options. The recommended way to launch the pc-client-local-cache.exe on start up is to add a line to your domain login script: cmd /c "start \\servername\PCClient\win\pc-client-local-cache.exe -silent" Administrators should ensure that standard users have write access to the system drive, or manually create the cache directory if required. You can specify an alternate cache with the -cache command-line switch. By default, the cache is created in a directory on the system drive (normally C:\Cache). It does, however, require a globally writable cache directory. Using pc-client-local-cache.exe is recommended on large networks. The cache is self-managing and kept up-to-date ensuring that any new versions of the client are automatically and transparently copied down to the client. The local-cache version has the advantage that any future start ups use the local copy, which minimizes network traffic. The “local-cache” version ( pc-client-local-cache.exe), is a smarter version that first copies itself and associated files to the local drive and launches itself from there. Pc-client.exe launches the client directly off the network share. Two executables provide this launch functionality: You can run the client directly from the PCClient share setup on the server. This avoids the need for a separate installation process on each workstation and ensures the client software is automatically updated in conjunction with server updates. This involves configuring the workstations via group policy or otherwise, to run the client executable directly off the PCClient share - a share set up during installation. The recommended approach with Windows networks is the “zero install” strategy.
This option is available for advanced sites that already leverage MSI packages for staged software deployment and want to continue with this procedure. MSI package-Administrators can also deploy via MSI package, allowing the Client software to be remotely installed via Group Policy. \\\PCClient\win, where MyServer is the name of the server where PaperCut NG/MF is installed. You can access this share by typing the following address into Windows Explorer. Local installation-If you’re after a manual “setup wizard” style installer, run the program client-local-install.exe located in the network share PCClient. This is the recommended strategy for most Windows network environments as it’s 100% self-maintaining. Zero install-Administrators looking for an automated install/deployment option should consider the “zero install” strategy. The deployment options are covered in detail in the \client\README.txt file. You can deploy the PaperCut NG/MF User Client to workstations using a variety of deployment methods. PRODUCTS FEATURED Install the User Client on Windows
0 kommentar(er)
