Ranger is not running properly when installed upon a non-server edition of Windows (Windows 7, Windows 8).
Examples: Ranger jobs fail with 'can't connect', 'can't find' or 'can't locate' error messages. This error message could be while running a backup, or adding an object or node to the inventory, or while running a restore. This can also cause the GUI interface to crash due to the fact that the Windows machine ran out available connections.
This is due to the fact that the desktop versions of Windows are limited to 20 connections to the OS and thus limiting the capabilities of Ranger to connect to all the resources needed in order to allow Ranger to be deployed and utilized in its desired method. This can be illustrated by going to a command prompt and typing in the command "net config server" which (amongst other things) show you the Maximum Logged on Users which if it is desktop platform is 20. This value represents the conncurrent network connections that are allowed in the OS, which should not be confused with Terminal Services licenses, this is simply concurrent network connections.
Comparitively the Server based platforms of Windows (2K3 & 2K8) are set to 16,777,216 concurrent connections which will service the OS quite will to act as a server.
Move vRanger onto Server based version of Windows.
