The issue was that PowerShell writes the file in ASCII instead of UTF-8, by default. I changed that to write UTF8 BOM and it is now working *however* new issue, with multiple
commands, one after another, it was only executing the first sync command. I searched for documentation but couldn't find whether or not multiple
commands should be supported, followed by a single
, so I'm not sure if I was just mis-scripting or if it is not supported. Can you confirm?
Assuming it is not supported and attempting to forge ahead, since I was using the
for the scripts, I couldn't run them all sequentially (each one starts before the prior completes) so I was faced with 2 choices:
- Rewrite using the
.com and create individual script files before running (possibly overwriting before running to not clog things up)
- Rewrite using the PowerShell wrapper
I chose option #2 and it is working, but there is one major drawback: logging
The wrapper logs an incredible amount of data. It seems like much more than the
. I have been running this initial sync for about a day now and my log file is over 50 GB. I may run out of hard disk space before the initial sync completes. Haven't decided how I will handle, but I already re-coded the script to allow me to pick a spot to resume instead of re-running all sub-folders, in case I do need to change something.
Would love your thoughts on this. Quite a journey I've been on here.
All said, it would be *awesome* if the synchronize logic could handle a Regular Expression (separately for both the local and remote would be even better). This entire exercise could have been avoided if it did. Obviously, great software, but if I had a feature request in mind, that would be it.