SYSOCMGR removes NNTP dll's

[DanSin]

Hi, Using sysocmgr.exe to script the addition/removal of Server 2003 optional components (ex. DHCP, DNS, Unix print services) we see it always removes nntpapi.dll and nntpadm.dll. It doesn't matter if we are adding or removing a component, and the component in question seems to have no known relationship with NNTP.

The spin off, is that some of the Administration Tools Pack tools, namely WINS Manager and Terminal Service Manager must be reinstalled (advertised) when they are used the next time.

Can anyone explain the relationship between SYSOCMGR and the two NNTP DLLs?

 

[DanSin]

I've drilled into the behaviour a bit more and have a theory. SYSOCMGR queries the values at HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\Oc Manager\Subcomponents and enforces the present state of all the Windows components. This behaviour occurs in addition to the settings passed to sysocmgr via the inf file.

In my case, we have no IIS components installed and since the two DLL's named in my original post belong to IIS, these DLL's are removed by virtue of running sysocmgr. Now I must figure out a way to keep IIS off my server and at the same time keep nntpadm.dll and nntpapi.dll installed for the benefit of the AdminPak. Sounds like it's time to open a Premier Support ticket.