Windows administrator rights is required for Network Client Machines
|Date:||25 February 2005|
|Abstract:||You need Windows administrator rights to access the Network Server from a Network Client machine|
|Submitted By:||LANSA Technical Support|
|Last Review:||December 2010|
In the LANSA Online Documentation - "Installing LANSA on Windows":
There is a section called "Visual LANSA Client Only Checklist" which states the following:
Visual LANSA Client Only Checklist
- Do you have Windows administrator rights?
A clearer explanation of this is that the user accessing the Network Server machine from the Network Client MUST has Windows administrator rights for the Network Server PC. If not, you will experience problems when trying to access the Network Server from a Network Client machine (e.g. you only see the hourglass when trying to logon to the server from the LANSA development environment).
To ensure the Network Client user has access to the Network Server machine, just add the user to the Windows administrator group on the Network Server PC and reboot the server before attempting to install or use a Network Client PC. This can avoid any Windows security issues to access the Network Server PC.
In summary, the user must be part of the Windows administrator group to:
- Install/Upgrade Visual LANSA
- Use the Visual LANSA development from Network Client to Network Server
- Execute any Visual LANSA applications using a Network Client to a Network Server machine
Note: After adding users to the Windows administrator group on the Network Server PC and rebooting, you may encounter a situation where a successfully installed Network Client cannot connect to Visual LANSA on a windows 200 Server or windows 2003 Server. This may be be caused by the shared LANSA directory on the windows server being created with only "Read Only" permission by default. Refer to 'Read Only' shared drives on Windows Servers stops Visual LANSA Network Clients connecting to server