ARM by default records the console output of the script that is being run in its own log file. That should include output from Write-Verbose assuming you pass the -verbose flag or set the $VerbosePreference variable accordingly.
You can find a link to the log file in the "Logbook" section of the ARM fat client in the category "Execute External Script":
the problem is, that since Office 2013 office automation is not working anymore per default in session 0. The reason is that you could write macros and so on. The script engine in ARM is running in session 0 and therefore your script is not working. TO overcome that you need to go to DCOMCNFG.EXE in Admin mode on the machine and check if you can see the Word DCOM Object. Now change to interactive user, that should work now. If you need still further help we can do it together via remote let. Contact me at Mike.Wiedemann@cusatum.de.
Have a nice day.