FAQShop.com : How Do I Force My SMSLogon Shares to Update?

How Do I Force My SMSLogon Shares to Update?

I put some new subnets in the boundary of one of my sites this morning. They have not yet replicated to any SMSLOGON share other than the one on the PDC. I have a site set to senior site, and the nt_logon.log says that it's waiting for the next cycle tomorrow morning. I tried stopping and starting the SMS_NT_LOGON_SERVER_MANAGER component on my senior site, but after it starts again, it still says that it will run tomorrow morning.

How do I force it to run an update?
Where do I change that interval (if, in fact, I was inclined to do so).

At your new site, and your senior site, navigate to:

Site Database | Site Hierarchy | site name | Site Settings | Client Installation Methods | Windows NT Logon Client Installation | Logon Settings tab. Change the logon point update schedule to 1 hour, and set it back after the update has processed. You should also check the NT Logon Discovery method if you are using it.

Or if you don't want to change any settings, copy a NT_Logon.not text file (create a text file with a ".not" extension) and copy it to the "SMS\Inboxes\NT_logon.box\Notify" folder on the new site and the Senior site.

This will cause an update to occur within an hour or so. SMS will kick off the update and remove the file. It then waits for the next scheduled update (which puts another NT_Logon.not in that location again temporarily until it starts another update then removes the file).