Software Deployment

Have figured out that i can do a unmanaged client installation and copying in the correct GRC.dat after the installation is finished and restarting the SAV service.

But after i install the client i get a message saying the virus def log is old. Do anyone know how to hide this message? (Do not want the clients to see this message)

If you read the documentation (PDF) that comes with the installation media it describes which properties to change for your needs.
You do not have to restart the service for it to take the new GRC.DAT, it will do so in a few minutes by itself.

Thx for help AngelD. HAven't read the installation documentian thorough i guess.

I still have one problem though?
After the installation a message pops ut saying my virus def is old. How do i hide this message?

I still have one problem though?
After the installation a message pops ut saying my virus def is old. How do i hide this message?
I think Kim made it clear in his response, i.e.:
If you read the documentation (PDF) that comes with the installation media it describes which properties to change for your needs.

Bankeralle,

If I recall correct the document should give you that answer too.

K guys.. I am trying to write a transform to drop a version of the GRC.DAT file on the target computer based on a public property. I'm trying to figure out the cleanest way to do this.. The PDF you guys have referred to in this thread was not included in the source I was given and I can't find it on Symantec's site.

To illustrate, this is what I'm trying to accomplish:

I have GRCA.DAT, GRCB.DAT, GRCC.DAT.. depending on the public property, I want to copy one of these files and obviously rename it as GRC.DAT.

Add them to separate components and then use a property as condition for each component.

I can't recall if the dat file is removed after it has been handled but in that case use a custom action to copy the file instead.
Store them at the source (same folder as the MSI) and then use the SOURCEDIR property to grab the source folder and then just copy the one you want depending on the public property you want to use.

Thanks AngelD - that's what I ended up doing but wasn't sure if it was the cleanest way.

ORIGINAL: AngelD

Add them to separate components and then use a property as condition for each component.

I can't recall if the dat file is removed after it has been handled but in that case use a custom action to copy the file instead.
Store them at the source (same folder as the MSI) and then use the SOURCEDIR property to grab the source folder and then just copy the one you want depending on the public property you want to use.


Hi AngelD - What did you mean by the dat file being removed after it's been handled? Do you mean that the installer deletes it after it has read the settings from it? If that's the case, that seems to be what's happening. Is there a way to make it persistent without use of Custom Actions?

If I recall, if a grc.dat is found present it will be read and the info is then written to registry. When this is done the grc.dat is removed.
If you add such file to a component and set as keypath then you may well create a repair-loop so that is why I suggested a custom action instead. If you remove the GUID for the component (blank ComponentId column value) then there should be no problem as the component will not be stated as installed.
I would use a custom action instead.

ORIGINAL: AngelD

If I recall, if a grc.dat is found present it will be read and the info is then written to registry. When this is done the grc.dat is removed.
If you add such file to a component and set as keypath then you may well create a repair-loop so that is why I suggested a custom action instead. If you remove the GUID for the component (blank ComponentId column value) then there should be no problem as the component will not be stated as installed.
I would use a custom action instead.

Thanks dude

ORIGINAL: jayteeo

ORIGINAL: AngelD

If I recall, if a grc.dat is found present it will be read and the info is then written to registry. When this is done the grc.dat is removed.
If you add such file to a component and set as keypath then you may well create a repair-loop so that is why I suggested a custom action instead. If you remove the GUID for the component (blank ComponentId column value) then there should be no problem as the component will not be stated as installed.
I would use a custom action instead.

Thanks dude


Hey AngelD - one more question.. do you know if there's even a good reason that GRC.DAT should remain on the computer even after the install has run?

Don't think so as it's already "been taken care of", are you seeing that it is?