Hi,
I'm using get-content with the parameter -wait as a logfile monitor on remote clients.
It looks like this:
get-content "$drive2\$progpath\log\message.log" -wait -readcount 0 -tail 10
$drive2 is the UNC path to the client.
It worked fine on all clients until we started a rollout in the USA. There I have the problem that the command starts normal but the "-wait" parameter is ignored without any error. Executing the command again returns the same result. We have Win7 clients with powershell 3. I tried to replace the unc path with a mapped drive letter but the result is still the same. The WAN link between Germany and USA is not the fastest but thats not the problem because I had the same problems when I was in the USA with my client. Any idea how to modify the command or how to replace it with a more stable command is welcome.
Regards
Sven