Upgrading from the SCOM 2007 R2 probe to the SCOM 2016 probe

The Probe for Microsoft SCOM 2007 R2 is now EOS, so you should upgrade to the Probe for Microsoft SCOM 2016. If you have the Probe for Microsoft SCOM 2007 R2 installed, when you upgrade to the Probe for Microsoft SCOM 2016 you should be aware that it is not possible to install both the Probe for Microsoft SCOM 2007 R2 and the Probe for Microsoft SCOM 2016 on the same system.

This is because both probes use the same set of SCOM tool scripting files, namely:

tools/README.scom_tool
tools/scom_tool.pl
tools/scom_tool.sql
tools/scom_tool.conf
tools/CreateScomGroup.xml
tools/win32/TelnetScomProbe.VBS
tools/win32/WindowsScomTools.sql
tools/win32/WindowsScomTools.xml
tools/win32/WindowsScomTools.cgi
tools/win32/auto_acknowledge_trigger_windows.sql
tools/win32/update_scom_windows.sql
tools/win32/netcool_tiv_oli_socket/netcool_tivoli_socket.dll
tools/unix/TelnetScomProbe.pl
tools/unix/UnixScomTools.sql
tools/unix/UnixScomTools.xml
tools/unix/UnixScomTools.cgi
tools/unix/auto_acknowledge_trigger_unix.sql
tools/unix/update_scom_unix.sql

To work around this issue, before you upgrade from the Probe for Microsoft SCOM 2007 R2, you need to backup and remove the duplicate files listed above before installing the Probe for Microsoft SCOM 2016.