Citrix Provisioning

Hi,

I'm currently preparing to migrate NOD32 V2.7 on Citrix Presentation Server 4 to NOD32 V3 on Citrix XenApp 5.

For NOD32 V3 I've just completed installing Remote Administrator on MS SQL and I'm now creating policies and templates.

The Citrix XenApp 5 configuation is as followed:
- HP ProLiant server
- VMware ESXi
- multiple XenApp 5 servers streamed using provisioning services
- baseline applications and streamed applications inside XenApp 5 server

As an AV can't be streamed because of it's drivers it needs to be placed inside the baseline. The baseline is contained inside an image (vdisk) which is streamed to the server using network boot.

I can install NOD32 V3 in the baseline image (vdisk) using direct install, GPO or push install. Once installed this vdisk is streamed to multiple XenApp 5 servers. The server maintains it's own hostname based on MAC address.

Which installation and configuration method should I use to install NOD32 in a baseline image and how can I easily configure each unique XenApp 5 server so that it is (automatically?) recognized in Remote Administrator?

 

Found this article on Citrix forums while researching XenApp exclusions:
Provisioning Services Anti Virus Best Practices

The Citrix forum thread Antivirus definition files update - Vdisk has some guidelines for Trend Micro, McAfee and Sophos on how to update a provisioned image in standard mode.

It seems like rules for a desktop image also apply to provisioning. So I can rephrase my question: does NOD32 V3 have a mechanism for imaged system so that it uses the new hostname (and possibly a new identifier) to report to Remote Administrator?

 

Found too many issues configuring V3 from ERA. Trying V4.