Hi Alex,
another question regarding the Windows client and its portable mode:
Is everything in the C:\Program Files\x2goclient directory "self-contained" and not relying on absolute path names by default, or does a truly portable install require additional pre- or post-install tweaks? In other words, can I copy/move the entire folder to another drive/medium (Network share, USB memory stick, CD-ROM,...) and it should still work?
I don't care about the entries in the start menu, these can easily be (re)created with a script if needed. The reason why I'm asking is that this would allow for a central update location in a LAN when a new client version gets released: Either run the client directly from the network share, or have a script copy the contents onto the client machines.
I'm aware the installer has the /S option for a silent install, but having a single copy on a network share (or simply copying updated files over to the clients using robocopy or xcopy) seems easier than a scripted update on $BIGNUM client machines. (where $BIGNUM in my case is currently roughly 30 LANs with 5-15 client machines each, with more to come each month).
-Stefan