Reference Section > Installation and Deployment > Updating PrimeCut NE on the Client Computers

The client update procedure makes certain assumptions about file locations on your network and how things are named. These should be valid for recent installs, but earlier installations may have had a different naming convention.

How it works:

The start menu item Update Primecut From <your server> is actually just a shortcut to a batch (.bat) file on the server, which copies the contents of \\<your server>\UpdatePrimecut\*.* to the appropriate program files location ion your local machine.

▪If on a 32 bit client the shortcut is to \\<your server>\UpdatePrimecut\setup.bat, which copies the to the local folder c:\Program Files\Primecut4

▪If on a 64 bit client the shortcut is to \\<your server>\UpdatePrimecut\setupx64.bat , which copies the to the local folder c:\Program Files (x86)\Primecut4

Why it might fail:

▪The shortcut on the clients might point to \\<your server>\UpdatePrimecut\setup x64.bat (a space in the name).

Solution: edit the shortcut to point to the correct setupx64.bat, OR rename the file on the server to setup x64.bat. The former is preferred, to be consistent with new installations.

▪You might not have read access to the share on the server, or the share may have been renamed or deleted.

Solution: Contact your system administrator to resolve.

▪You might not have administrative rights on your local client computer (usually you will be asked to enter adminsitrative credentials when you choose run as administrator if this is the case under Windows 7 and up, but under XP where there is no option to it will just fail with ACCESS DENIED messages.

Solution: have an administrator perform the client update for you.