Hi Tony...not related to PItoPI APS but the same principle. You could: On the little PI System have the Powershell Tools for the PI System, which connects to the AF Server of the big PI System. The Powershell script would connect to an AF Database, e.g. "Configuration", search for the tag prefix based on an AF Element being named as the little PI System VM name (and inheriting from a specific Element Template), then have the Powershell script modify the PItoPI APS config (to be determined). Finally, set a flag in the AF Database to say that the prefix has been applied.
If you have Windows 2k8 R2 as the little PI System host OS then you can use the Windows local policy to set your Powershell script on startup...it would check the flag and only run if it has not already been applied. Or you could even has the Powershell script remove itself from the local policy once it has done it's business.
Is that along the lines of what you meant?
Thank you for your reply.
The key thing (and I'm guilty of not digging into this further myself yet) is figuring out if the PItoPI APS Connector has a config file where I could modify the prefix text before starting up the connector If so then I can try what you suggest as each little PC has to some how be 'registered' with the big PI anyway and I will have to create an AF structure for each one on registration. As you can appreciate I'm trying to use as much out of the box stuff as possible.