Since the Get-PIPoint cmdlet is not recognized on your system, it sounds like you need to start at ground 0 and load the OSIsoft's Powershell cmdlets. These have been available with PI SMT since PI Data Archive 2015 R2 was released.

Let me also sway you away from a very bad direction. You are under the belief that you may need to use the "SDK" and the GetPoints2 method. NO, NO, NO. The GetPoints2 method is from the PI SDK, which is slated for deprecation, and for several years we urge all new development to be done in AF SDK. Headaches of Component Object Model will not go away with Powershell, yet PS is very agreeable with .NET calls. So if you must use an SDK in PS, then use AF SDK and only then if the OSIsoft cmdlet's do not provide the functionality that you need.

Since the Get-PIPoint cmdlet is not recognized on your system, it sounds like you need to start at ground 0 and load the OSIsoft's Powershell cmdlets. These have been available with PI SMT since PI Data Archive 2015 R2 was released.

Let me also sway you away from a very bad direction. You are under the belief that you may need to use the "SDK" and the GetPoints2 method. NO, NO, NO. The GetPoints2 method is from the PI SDK, which is slated for deprecation, and for several years we urge all new development to be done in AF SDK. Headaches of Component Object Model will not go away with Powershell, yet PS is very agreeable with .NET calls. So if you must use an SDK in PS, then use AF SDK and only then if the OSIsoft cmdlet's do not provide the functionality that you need.

Thank you for this. You're entirely correct. I'm attempting to run this on our dedicated interface server and I didn't realise the PS tools could run on another server that isn't the Data Archive. Oh how I was wrong.

This is the much simpler solution and I've got it doing what I require. Just need to work out how to remove the character length limit on the results...