EEwert

Thanks! The documentation (that I found) wasn't clear (to me) about where (on Windows) and how those files worked in concert. You helped me get past this "mental block" on how Plastic was operating behind the scenes. Not 100% certain why my file search didn't find cryptedservers.conf before. My guess would be the file search not traversing into a hidden directory or maybe not enough coffee. C:\Users\<user>\AppData\Local\plastic4

Only the UI seems to ask for the Encryption password. I looked at the using the "cryptedservers.conf" file but is the contents of the .key file supposed to be the text password? That isn't how the UI stores it. (I actually can't find WHERE the UI stores the password.) How do I make cm.exe happy enough to pull files from an @cloud account that is encrypted?

OK, I am fairly certain it is because of the Encryption key missing. (When I ran the UI the dialog box popped up on a VM that was "fresh".) How do I set the Encryption key for the command line tools? (without a UI!)

I have the 10.0.16.5397 client installed in a docker for windows container. Everything seems to work except that the result of cm update is a workspace with ONLY directories and zero files. The same MSI (10.0.16.5397) on a VM hosting the container works correctly. This also happens within the container if the workspace is located on a mounted volume (i.e. NOT "in" the container). Is there something "extra special" that I am missing to run cm.exe inside a docker container (Windows)? info: PlasticSCM 10.0.16.5397 https://s3.eu-west-2.amazonaws.com/plastic-releases/releases/10.0.16.5397/plasticscm/windows/PlasticSCM-10.0.16.5397-windows-cloud-installer.exe Windows Server 2019 Datacenter 10.0.17763.0 mcr.microsoft.com/windows/servercore:ltsc2019