I have a problem with sites and APIPA addresses when attempting to deploy a new server. The environment is ITMS v7.5 HF6 with 30 site servers for our various geographic locations. Each site server is configured with DHCP to issue addresses to new computers in thier respective locations (there are valid reasons why we don't use IPHelper entries in the firewalls/routers so don't go there). The new servers PXE boot into the WinPE4 automation client without any problems. But this is where my problem starts.
Most of our new computers have multiple NICs with only one configured into an imaging network where it gets a valid DHCP address from the local site server. The rest of the NICs get APIPA addresses when they fail to obtain a DHCP address. This is expected and works as designed. No DHCP for those other NICs again with valid reasons for the configuration. The problem is the PECTAgent registers with the SMP console using one of the APIPA addresses instead of the issued DHCP address. Since the APIPA networks are not assigned to the site of the new server, the PECTAgent picks a site server at random (or by whatever algorithm is used) for its task server. This ends up causing the ghost task to fail because the PECTAgent cannot communicate with the chosen site/task server due to firewall restrictions (again, this cannot be changed). If we assign the APIPA networks of the new computer into the appropriate site, the ghost task runs without incident.
My question is: how do I get the PECTAgent to register consistently with the SMP console using the issued DHCP address and not one of the APIPA addresses? And disabling the extra NICs is not an option.