Workspace Streaming

Hello,

As mentioned in comment above we were able to import the ADM together with ADML file into AD, have them applied by GPO and here is the result (for testing I was disabling remove all button in ADM file so I could see immediately on Streaming agent interface if GPO was applied
correctly - on our images we have it enabled by default):

1. After logging in to the machine where GPO was applied, Streaming agent interface was showing default configuration from the image (remove all button was not disabled as it was set in ADM).
2. AppstreamCfg file did not change
3. A registry key was created in HKLM\Software\Policies\Symantec\Workspace Streaming\Config which contained all settings from ADM file
4. As soon as I manually restarted AppMgrService changes were applied to AppstreamCfg file and also to the Streaming Agent interface.

This indicates to me that when machine is powered on AppMgrService starts before GPO is actually applied which would explain why I see the changes only after I restart the service after logon.

I would like to know if there is any way how appmgrservice could be started (or restarted) after gpo was applied but before user logs in to the machine or any other way around it. How do you guys use it in your environment? Does it work for you without a need of restarting a service or rebooting a machine? Restarting a service after log on does not seem to me as a good solution and most of our users do not have admin rights anyway and about half of our machines is set to refresh to the base image after log off so reboot would not help.
Or perhaps is there a way how could streaming agent read settings directly from registries mentioned above where every change to registries would take an immediate effect?

If you would have more information or any documentation regarding this topic I would be very happy to go over it.

Thank you!

Best regards,

Peter

Thanks Kedar, we were able to succesfully import admx and adml files into AD. We have a change scheduled for next week to implement this in our testing GPO and then will verify if it actually works since the old adm file which was meant for 6.x streaming agents did not work as expected because GPO was being applied after AppMgrService was running already so when you logged into a machine you could see that changes were applied to AppstreamCfg file by GPO BUT it did not take an affect unless you restarted the service. Symantec advised not to delay a start of appstreammgr service on startup which could possibly address this issue and were were not able to come up with any other solution.

I am really hoping this could move us somewhere further as I see great benefits in ability to change values in AppstreamCfg by GPO.

If you would have any more information or documentation about this topic please feel free to send me a private message I would be happy to go over it.

Thanks,

Peter

Hi Peter,

I have updated the attached files. Do let me know if you still face the issue.

Thanks!

Hello,

anyone was able to successfully import the new ADMX file? We were getting following error when trying to import it to AD:

Looks like file itself is either corrupted or its missing something.

Symantec, can you please provide also ADML file which is supposed to come with ADMX?

Thank you,

Peter

Hi Bob,

The file updates were provided by the Information Development department. I've asked them to provide a comment to Dwight's original post with that information.

Thanks,
Cheryl

Hello,

Dwight Tanner, the author of this post is no longer with Symantec.  His last posts were from 2012 and I have asked our Symantec contacts, who have confirmed this. 

Can someone please update this thread with who at Symantec has posted the updated file "Updated_StreamingPolicy_Aug2015.zip"?  

Our company is a large user of Symantec's SWS software and managing the SWS Agents via GPO is an excellent tool to help the product scale for enterprise deployments.  We are very interested in doing testing of this streaming policy in our environment. 

Thank you,

Bob Saetham