I installed SMS SP5 back in February 2003. Our organization migrated to AD in November 2003. In our SMS structure, I am a child site of our parent site. Recently I have been receiving a message in the WNMANUAL.log on clients that says:

Site XXX is at a lower version (2.00.1493.4170) - it will be skipped for assignment

All the other sites in our SMS structure show a version of 2.00.1493.5011. I reinstalled SP5 to make sure all was kosher. This did not work. I did a site reset. This did not work. I manually changed the compver.ini file on the DC's to reflect the component version of 2.00.1493.5011. This too did not work and it gets changed back to 2.00.1493.4170 every night.

Does anyone have insight as to what process is changing my component version number on the compver.ini file on my DC's and how I can get it to stop?

Contributed By: Jeff LeBlanc [MSFT]
When you are sharing Logon Points between sites then each site in the SMS Hierarchy updates the PDC and it is then the Senior Site for Logon Point management that updates all of the other Domain Controllers. So when troubleshooting Logon Points it is usually best to start with looking at the one on the PDC/PDC Emulator to see if it is accurate.

See the following article for a description of Senior Site concepts:

235726 "SMS: How to Specify Senior Site for WinNT Logon Point Management in a Single Domain with Multiple Sites."

If the PDC emulator is incorrect, then you should check to make sure that "Windows Networking Logon Client Installation" is ENABLED, and also that your Domain is entered correctly. If that looks good, then the NT_LOGON.LOG on your Site Server should tell you why the PDC isn't being updated with the correct files. You can force a Logon Point update by creating a 0 byte NT_LOGON.NOT file and copying it into the \SMS\Inboxes\NT_LOGON.BOX\Notify folder on the Site Server. The file should disappear almost immediately and then you can watch the NT_LOGON.LOG for processing. More info on NT_LOGON.NOT in:

257202 "SMS: SP2 Functional Change in Processing Logon Point Updates"

Once the PDC is properly updated, then you can either wait for the Senior Site to update the remaining DC's, or use the NT_LOGON.NOT on the Senior site to force the cycle.