Deployment - Direct Access explained
Posted by Panagiotis Mantzouranis on 13 March 2019 09:40 AM
Deployment profiles in Gizmo have a very important option named "Direct Access"
Direct Access affects the way Gizmo will deploy the files to the clients. It is directly connected to the source folder of the deployment profile
"Source" is the path where the files you want to copy to the client are located. "Direct access" option dictates if that path is accessible by Gizmo server or Gizmo client.
if source is a local server folder, e.g. "D:\Games\Fortnite", the path is accessible only by the Server.
That means that direct access should be disabled
if source is a mapped network drive on the client, e.g. "Z:\Games\Fortnite", the path is accessible only by the client.
That means that direct access should be enabled
if source is a network (UNC) path, e.g. "\\fileserver\Games\Fortnite", accessible by both server and clients, direct access can be either enabled or disabled
Direct access option has an effect on deployment speed. If direct access is enabled, deployment mechanism uses standard windows transfer protocol. When direct access is disabled, Gizmo uses its own proprietary transfer protocol to push the files from the server to the client.
That slows down deployment speed roughly 20%-30%. We suggest you use "direct access" whenever possible, since it provides the best performance.
On the other hand, not using "direct access" means that you do not have to make files directly accessible to the clients. You do not have to create network shares or mess with sharing permissions. It is quicker and safer to use this option.