Scenario

You have followed the installation processes as described in the manual, but only NPM (the most crucial executable zanda.exe) is installed on the workstations. The only trace of NVC on the workstations is a splash screen during boot.

Possible solution

Copy elogger.exe (path \\server\norman\bin) from the server to the workstation and run it for approximately 15 minutes. Meanwhile, open default.ndf in \\server\norman\distrib\nvc\config

Note: Don’t use the configuration editor from the system tray, as this will only edit the server’s own settings.

Go to the LAN/WAN tab, select User defined paths and click Settings. Check that the UNC paths are OK by selecting Start|Run in Windows and type the paths one by one. When you click OK a window should appear, displaying the complete file paths. If you receive the error message The Network Name cannot be found, then the UNC path is invalid, probably because the distribution server name and/or share name (on Novell: volume name and root directory) are misspelled. As of
NVC 5.5 you should no longer type in ‘\\’ in front of the Distribution server name.

If you distribute NVC using SelfXWiz, you should validate the information you have submitted in the Account name field (screen 5 in SelfXWiz) after the following measure: 

  • If your network is a domain, the correct syntax for the account is domain name\user name. 
  • If your network is NOT a domain, the correct syntax is server name\user name. 
  • In a Novell NetWare environment, the correct syntax for an account in default.ndf is the full NDS name for the user, typeless or typeful, including a leading dot.

If you find errors, you should correct them and generate a new SelfXWiz distribution package (nvc5w32.exe). Run your new package on the workstation with problems.

Continue to watch elogger.exe running. After approximately 5 minutes, the messages should change to report copying and extraction of zip files from server to workstation. This is, of course, reliant on correct details in default.ndf in the first place, i.e. UNC paths etc.

If the problem persists only on NT machines, log onto the workstation with an account holding local administrator rights and stop the “server service". If this fails, then the account doesn’t hold sufficient privileges on the workstation. Make sure that the account is a member of “domain admins" and that the “local admins" group on the workstation contains the “global domain admins".

By now you have probably spotted the problem. If you haven’t, copy default.ndf to the local configuration path on the workstation with  poblems (c:\norman\config). In this folder you will find config.ndf which you should rename to config.old.
Then rename this default.ndf to config.ndf.

If all this fails, please call technical support for further advice.