Sometimes you might see error like below while starting “Counter logs” tasks from perfmon and additionally you will see Event ID 2003 with source “Sysmonlog” in Application Event viewer and Event ID 7024 with source “Service Control Manager” in System event viewer.
The test1 log or alert has not started. Refresh the log or alert list to view current status, or see the application event log for any errors. Some logs and alerts might require a few minutes to start, especially if they include many counters or they contain counters to be collected from a remote system that is no longer on the network. For further information see the troubleshooting section in the online help.
If the above mentioned symptoms matches your problem, then it can be fixed by following the below steps.
Open regedit and navigate to “HKLMMACHINESYSTEMCurrentControlSetServicesSysmonLogLog Queries” registry key and go to permissions
Grant full permissions to “Network Service” and propagate them to child objects.
Now try to start your counter log job; it should start now without any issues.
Hope this helps you…
Happy Learning…, Sitaram Pamarthi
Tags: problems with perfmon, unable to start counter logs, Error starting counter logs
When I was with my old organization, we used to deploy operating system with the help of Ghost — an imaging technique. So, after completing the imaging process, we used to run newsid.exe to make the new installation unique in environment.
But surprisingly, the author of newsid has taken a decision to retire that decade old utility. Believe me, it is no more available at any MS websites. MS suggesting it’s customers to user sysprep instead of newsid as sysprep does lot more things which newsid will not.
You can refer to below URL to know reasons behind it’s retirement.
The intent of this post is to give some details on how to set quota notification internal in Exchange 2007. During this interval, a wanning message will be sent to users who are exceeding(or near to) their mailbox limits.
Set Quota notification schedule on a given Mailbox database:
While working on setting up my test Exchange 2007 setup, I got a requirement to create 100 users in my environment. I know how to do it with Vbscript but creating mailbox enabled users increases the complexity of script a bit. Then I explored PowerShell and came up with below piece of code. It might help you too… 🙂
Please note that, the password will be applied for all 100 test accounts we are creating. Above code creates 100 test user accounts with mailbox enabled on MBX1
The above article has good amount of information embedded in it explaining what to do when you delete an exchange cluster resource from a CMS. Exchange clusters are not like any other cluster aware applications which can be restored by simply recreating the resources in cluster group. One example is, SQL. You can do simple recreation of cluster resource if you delete one from SQL instance. But when it comes to Exchange, it is little bit different. Each exchange resource maintains variety of references with each other and with active directory. It also stores it’s unique information about exchange clustered resources in active directory; so recreating the cluster resources manually from cluster admin doesn’t make any sense. You might successfully able to create resources using cluster admin, but exchange will not recognize and use it.
So, follow below steps when you delete any exchange related cluster resource from CMS group. When I say exchange related clustered resource, I mean, Exchange Information Store Instance (CMSNAME), Exchange System Attendant Instance (CMSNAME) and Storage name (CMSNAME).
Note down the values NetBIOS name and IP address of the CMS
Run Stop-ClusteredMailboxServer -Identity “CMSName” -StopReason:”your comment text goes here”
Go to command line and run setup.com /clearLocalCMS /cmsName:”CMSName” to clear the stale entries from cluster; setup.com will be available in your installation media.
Run setup.com /recoverCMS /cmsName:”CMSName” /cmsIPv4Address:”IPAddress” from command prompt. This uses the configuration in active directory and reinstalls the CMS with the old configurations.
Below powershell code helps you to list the files which are greater than given size(2GB in this case) and output the file sizes in MB/GB format. This command searches for files inside c:\mydata folder. You can run this against any folder.
Today, I will take you through some of the PowerShell one-liners which will help you in querying patches installed in your machine. List All installed patches:
You can adopt the above queries and run against remote machine by passing the computer name shown like below.
PS C:> gwmi Win32_QuickFixEngineering -Computer remotecomp | ? {$_.InstalledOn} | where { (Get-date($_.Installedon)) -gt (get-date).adddays(-30) }
It’s a four step process!. You can refer to my previous article if you want to understand about GPPs. In this post, I will take through the practical steps required for implementing Group Policy Preferences in a Windows 2003 Domain based environment. I am not going to talk about configuring any granular settings in GPPs but I will give you idea about introducing GPP infrastructure into your environment.
Step-1 : Install Group Policy Preference client side extensions(CSE) & XMLLite
GPP CSE: You need to deploy the GPP CSE package to all computers which are running with alteast Windows XP SP2/Windows 2003 SP1. This is to make your legacy operating systems understand the new GPP settings. Below are the download locations for GPP CSEs for different OS versions.
Similarly you need to install XMLLite Low lever parser on computers which are running with atleast Windows XP SP2 or Windows 2003 SP1. Download location is available here.
Step-2: Install a Windows Vista/Windows 7 Computer into your domain.
Configuration of GPPs is only possible through GPMC installed on Windows Vista/Windows 7 computer. Install one of these operating system on one computer in your network and add it to your domain.
Step-3: Install Remote Server Administration Tool kit
Based on the OS version(vista/Windows 7) your have installed, download appropriate RSAT and install it. After the installation, you need to enable the GPMC feature.
b)Switch the view to “small icons” and select the “program and features” option from control panel. This opens below windows.
c)Select “Turn Features On or Off” option from above screen and you will ne presented to with a window to select the features.
d)Navigate to “Remote Server Administration Tools” node and select “Group Policy Management Tools” check box like shown below and click on OK.
e)This completes configuring the features
Step-4: Start Configuring GPPs
Now we are done with setup. Go Start-> Run -> type “gpmc.msc” on Windows 7/vista machine to bring up the GPMC management console. Now create a new GPO for desired OU and click on Edit. Now the GPO editor will contain two sections, “Policies” and “Preferences” under User and Computer settings. And need less to say that GPP settings can be configured from “Preferences” section.
My previous article talks about listing domain controllers in a domain in non-powershell world. But with introduction of powershell things changed a lot to give more flexibility to system administrators and developers.
Below piece of powershell code helps to you get it.
While working on some of the MMC related consoles I used to get a error something like below when I try to open the MMC(say dsa.msc or any other).
“MMC cannot open the file . This may be because the file does not exist, is not an MMC console, or was created by a later version of MMC. This may also be because you don’t have sufficient access rights to the file“
.
When I first came across this issue three years back, I spent numerous amount of time to find the solution and using it successfully since then. Also shared this tip with few of my colleagues who faced this problem. I thought of sharing this with my blog audience to make them not to struggle with this kind of error again.
Solution:
Go to start run and enter the command, “%appdata%/Microsoft/MMC” and click on OK
In the opened folder look for file that matches the mmc name troubling you and renamed it to some like backup and try opening your MMC again. It should work!.
TIP : If you have problems in opening “Active Directory Users and Computers”, you need to deal with the file named dsa.
If you are smart enough and you have old backups of this folder, try to compare the file and see what has changed. It’s just falt file with some values structure in XML. Most probably, you want to look at “MMC_ConsoleFile ConsoleVersion” value. This value should be equivalent to your MMC version. Problem may be different in your case, so compare with backup file to list the diffs which helps in reading the problem.
