We have come across an issue when using the PI Admin Powershell script MoveArchivesToFreeSpace.ps1
There are two PI Server is a Collective and if we run the script on the Primary Server it works as expected.
However, if we run the same script on the Secondary Server using the Secondary server's name and drive paths, it starts to un-register archives on the Primary Server.
We thought that as the PI Collective name has a DNS alias that points to the Primary server, it may have been the issue, so we added a host entry on the Secondary server which pointed to itself.
However that has not fixed the issue.
So has anyone used this scripted on a PI Collective and experienced the same issue?