We are deploying a Bria softphone app, with our new phonesystem, I have the package in SCCM which deploys fine. The app requires a key to run, we have a volume license that we will be using, since SCCM wont let me add the key without reinventing the wheel I figured that I could push it via GPO. So I create the GPO attach it to the test ou but it doesnt work. 

Few notes: 

The app installs its reg files under the HKCU 

Clearly I dont know what I am doing here. 


Any help would be great. 

3 Comments   [ + ] Show Comments


  • Do you have more information about the error ?

    Did the user/comp get the right GPO ? is the user/comp in the right OU ? Is there any error msg when the session is opened ? Have you checked the event log of the comp to trace the application ?
  • We use kix scripting during login to push reg changes instead of gpo's
  • If the original package is an MSI, the simplest route would be to build a user-level feature and make a feature with an advertised entry-point (e.g. an advertised shortcut) a child of that new feature. When the entry-point is used, the package self-heals and your user data gets written.

    If there's no entry-points, you can use Active Setup instead.

    As for what you've done with GP...exactly WHAT have you done? All you've [sort of] described so far is creating a GPO and linking it.
Please log in to comment



You could add the HKCU key to the MSI installer (assumming it is an MSI) then use Active Setup (http://www.sepago.de/d/helge/2010/04/22/active-setup-explained) to ensure it arrives into registry of anyone who logs onto the machine.

More packaging.. less GPO's

Answered 06/13/2013 by: eddieg
White Belt

Please log in to comment
Answer this question or Comment on this question for clarity