Is there any reason to keep logging for a very high volume site? What valuable data is there to be had in the raw logs.
We do keep the logs today for "just in case" could someone provide an answer for "Just in case What?"
Is there away in IIS 6 to programmaticly turn on/off logging in a web farm. we have 10 servers and I don't want to when needed log on to each and flip logging on, and then when we are done login and turn it off.
I know about remote management tools..but would like to use a powershell script or the like.
Using Microsoft System Center I continually have the following errors.
Alert: Network or Active Directory Required Resources Not Available
Source: DC-SMS01.hq.gratisinc.com
Path:
Last modified by: System
Last modified time: 5/13/2009 12:10:24 PM
Alert description: Windows cannot obtain the domain controller name for your computer network. (An unexpected network error occurred. ). Group Policy processing aborted.
We have Domain Controllers all over the place, they are happy and in sync. FSMO roles are spread out, and the network links are all fast and not saturated.
Anyone have this issue? If so how did you solve it?
Specific Error: Agent proxying needs to be enabled for a health service to submit discovery data about other computers.
Microsoft.SystemCenter.DiscoveryWriteActionModule.AgentProxyingNotEnabled.Alert
We use Microsoft System Center 2007. The management server throws this error. I have enabled proxying per the instructions but alas the error re-occurs. Has anyone else had this and fixed it? or do I just disable the monitor?