ipvoscesc
IPv6 support for OfficeScan starts in this version. Earlier OfficeScan versions do not support IPv6 addressing. IPv6 support is automatically enabled after installing or upgrading the OfficeScan server and clients that satisfy the IPv6 requirements.
The IPv6 requirements for the OfficeScan server are as follows:
The server must be installed on Windows Server 2008. It cannot be installed on Windows Server 2003 because this operating system only supports IPv6 addressing partially.
The server must use an IIS web server. Apache web server does not support IPv6 addressing.
If the server will manage IPv4 and IPv6 clients, it must have both IPv4 and IPv6 addresses and must be identified by its host name. If a server is identified by its IPv4 address, IPv6 clients cannot connect to the server. The same issue occurs if pure IPv4 clients connect to a server identified by its IPv6 address.
If the server will manage only IPv6 clients, the minimum requirement is an IPv6 address. The server can be identified by its host name or IPv6 address. When the server is identified by its host name, it is preferable to use its Fully Qualified Domain Name (FQDN). This is because in a pure IPv6 environment, a WINS server cannot translate a host name to its corresponding IPv6 address.
The FQDN can only be specified when performing a local installation of the server. It is not supported on remote installations.
The client must be installed on:
Windows 7
Windows Server 2008
Windows Vista
It cannot be installed on Windows Server 2003 and Windows XP because these operating systems only support IPv6 addressing partially.
It is preferable for a client to have both IPv4 and IPv6 addresses as some of the entities to which it connects only support IPv4 addressing.
The following table lists the limitations when the OfficeScan server only has an IPv6 address.
|
Pure IPv6 Server Limitations |
|
Item |
Limitation |
|
Client management |
A pure IPv6 server cannot:
|
|
Updates and centralized management |
A pure IPv6 server cannot update from pure IPv4 update sources, such as:
|
|
Product registration, activation, and renewal |
A pure IPv6 server cannot connect to the Trend Micro Online Registration Server to register the product, obtain the license, and activate/renew the license. |
|
Proxy connection |
A pure IPv6 server cannot connect through a pure IPv4 proxy server. |
|
Plug-in solutions |
A pure IPv6 server will have Plug-in Manager but will not be able to deploy any of the plug-in solutions to:
|
Most of these limitations can be overcome by setting up a dual-stack proxy server that can convert between IPv4 and IPv6 addresses (such as DeleGate). Position the proxy server between the OfficeScan server and the entities to which it connects or the entities that it serves.
The following table lists the limitations when the client only has an IPv6 address.
|
Pure IPv6 Client Limitations |
|
Item |
Limitation |
|
Parent OfficeScan server |
Pure IPv6 clients cannot be managed by a pure IPv4 OfficeScan server. |
|
Updates |
A pure IPv6 client cannot update from pure IPv4 update sources, such as:
|
|
Scan queries, web reputation queries, and Smart Feedback |
A pure IPv6 client cannot send queries to smart protection sources, such as:
|
|
Software safety |
Pure IPv6 clients cannot connect to the Trend Micro-hosted Certified Safe Software Service. |
|
Plug-in solutions |
Pure IPv6 clients cannot install plug-in solutions because none of the plug-in solutions support IPv6. |
|
Programs |
Pure IPv6 clients cannot install the following programs because they do not support IPv6:
|
|
Proxy connection |
A pure IPv6 client cannot connect through a pure IPv4 proxy server. |
Most of these limitations can be overcome by setting up a dual-stack proxy server that can convert between IPv4 and IPv6 addresses (such as DeleGate). Position the proxy server between the OfficeScan clients and the entities to which they connect.