posted originally in the DLP group - not sure why.
Are you still having trouble? It's been a while since we did our initial deployment but i think most of the configuration for MOVE is done through EPO policies. To set up the Offload Scan Server, if I recall, you install the agent from EPO (go to system tree and then new system), then once its a managed client, deploy VSE, and MOVE from EPO to the new scan server. The rest was pretty much all policy configuration. So you basically modify the MOVE policies to tell your clients where to look for a scan server or the SVA Manager. Hope this helps.
if you use Move Multiplatform environment without SVA manager just install the components. In my example the software is deployed through EPO and the extensions for Move AV Multiplatform Client and Move AV Offload Scan Server are already installed.
I would suggest the Move Multiplatform Extension HF988957 (MOVE-AV_Ext_184.108.40.2062_HF988957.zip)
EPO Master Repository
1) MOVE AV [Multi-Platform] Offload Scan Server: MOVE-AV_Offload_Scan_Server_3500.zip
2) MOVE AV [Multi-Platform] Client: MOVE-AV_Client_3500_WIN.zip
1) Deploay Virusscan Enterprise 8.8 P4
2) Deploy Offload Scanner Plugin
1) Deploy Move Multiplatform Client
Policies for Move AV multiplatform Offload Scanner
MOVE AV [Multi-Platform] Offload Scan Server 3.5:
- Unmark "Register this Offload Scan Server with MOVE SVA Manager".
Policies for Move AV Multiplatform Client:
General Policies: you dont need to add the Offload Scanner IP here if you are using Move Multiplatform 3.5.
Offload Scan Server Assignement: Check "Assign Offload Scan Server manually" and add the Offload Scanner IP here.
Thanks ..followed the same steps.
Installed SVA Manger with two Offload Scan servers in production.
Followed the same steps as mentioned by troja and installed SVA Manger with two Offload Scan servers
are the oss servers communicating with the SVA manager correctly ?