/build/static/layout/Breadcrumb_cap_w.png

Symantec via Group Policy + MST File

Hello everyone,

This is my first post here and I've searched long and hard for a solution to this.

What I am attempting to do?
I am trying to successfully deploy Symantec AntiVirus 10.1 Corporate Edition via Group Policy including a MST file for the correct SERVERNAME, RUNLIVEUPDATE, NETWORKTYPE variables.

Problem I am having...
I'm using Orca to view Symantec Antivirus.msi and generating a transform file (MST). The problem is I cannot find the place where the SERVERNAME variable is set. I have looked under the Property table and just about every other table. The SERVERNAME does appear in the Registry table but I was under the assumption, per MSDN Tables database that this data should be stored in the Property table.

In any case, I am new to application packaging apart from using the Microsoft Office Resource Kit for Office, Outlook and PRF files.

Thanks for any help or clarity...

Todd

0 Comments   [ + ] Show comments

Answers (3)

Posted by: WayneB 17 years ago
Blue Belt
0
toddistic,

Try using a custom property in the property table SERVERGROUPNAME, our SERVERNAME(also a custom property) is set to an environment variable %APPS_SERVER% which is the local DFS server determined in our login script.

Cheers
WayneB
Posted by: AngelD 17 years ago
Red Belt
0
Use the GRC.DAT file thats included or from your antivirus server and modify it to point to the servername
Posted by: toddistic 17 years ago
Yellow Belt
0
ORIGINAL: WayneB

toddistic,

Try using a custom property in the property table SERVERGROUPNAME, our SERVERNAME(also a custom property) is set to an environment variable %APPS_SERVER% which is the local DFS server determined in our login script.

Cheers
WayneB


so basically i would add another row in the property table called SERVERNAME with a value of <my symantec server>. This is all done using a transform file of course. Thanks for the suggestion!
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ