Jump to content
[[Template core/front/profile/profileHeader is throwing an error. This theme may be out of date. Run the support tool in the AdminCP to restore the default theme.]]

Community Reputation

0 Neutral

My Information

  • Agent Count
    500+
  1. So, earlier this year 2012 and 2016 servers started having goofy NLA (Network Location Awareness) issues where the NIC would detect the profile as just "Network" and not "domain.local" We know that this is a quick fix with just restarting the NLA service. Also, did the attempt at making the NLA service having an "Automatic - Delayed" start. But we are seeing this happen in servers that are not rebooting. Somehow, during the day or overnight, NLA just loses the domain. How would I go about first, checking to make sure NLA has a domain, and second, creating a monitor that scripts the restart of the NLA service? Or would it be simpler to just make a script that restarts the NLA service every day? Thanks!
×
×
  • Create New...