There are issues when using GPOs to push out Prism version 7.0.x Subscription Files, but it may still be possible depending on your environment. Here is some clarification about why KB Q10054 was changed to exclude version 7.

There are issues related to running a Subscription File in GPO's when there is already a client on the target computer. Examples include if an older client is already installed and running and the Subscription is meant to upgrade the files, or if the Subscription file runs on a computer that already has the newest client installed. We are working to resolve these issues in our next maintenance release.

If you are planning to use GPOs to install the client to a computer that does not have the Prism client installed, this is doable today. Just use a batch file to check if a client already exists and only run the Subscription file if not. The batch file would look similar to the following:

@ECHO OFF

IF EXIST "c:\program filesew boundary\client\ptclient.exe" GOTO END

subscription.exe /clientinstall /system

:END

Run the batch file as a Machine Startup Script. Copy the batch file and Subscription file to the GPO path on the server.  Be sure to run several tests prior to doing a mass rollout.

If you are looking to upgrade the client on existing computers that are already polling a Channel, perhaps you can push out the Subscription file as a Command Task. This is our recommended method for upgrading a client. This also works if you want to subscribe a computer to a different Channel. Push out the Subscription file using the Channel that the computer is already subscribed to. Details on how to do this are documented in this technote:  http://www.nbtnet.newboundary.com/supportkb/article.aspx?id=10222&cNode=8F6U8O