Change install location or add logic to support beta powershell versions

[bobfrankly]

Regarding Line 24 of:
https://github.com/Unitrends/unitrends-pstoolkit/blob/master/Unitrends/Install.ps1

I'm suggesting changing the install path to C:\Program Files\Powershell\Modules
OR making decision logic for the install location, based on the $env:psmodulepath variable.

The reasoning for this is that beta versions of powershell (the one's I've observed so far anyway) do not have the "C:\Windows\System32\WindowsPowerShell\v1.0\Modules\Unitrends" path within the $env:psmodulepath variable, so beta versions of powershell are incapable of using/testing the unitrends module as it stands.

This reasoning may also apply to the open-source standalone version of powershell in it's entirety, but I have not tested that far out.

[MartynKeigher]

Hey @bobfrankly

Not been on here for quite some time... Job changes, relocation, new roles/responsibilities, etc... but, I'm interested in getting this going. Still a thing you need or did you get this taken care of already??

Let me know & if its still a thing you need... I'll work on it.

://mk

[bobfrankly]

I don't need it at this time, but it was a detail that I encountered testing out PSCore. Seeing as PSCore is the direction that they're taking for future PS development, I made this issue as a heads up.