ASK

  Having just created a new cluster, I noticed Event ID 1257 being logged in the Cluster Events node within Failover Cluster Manager. Cluster network name resource failed registration of one or more associated DNS name(s) because the access to update the secure DNS zone was denied. cluster Network name: 'Cluster Name' DNS Zone: *dns zone* Ensure that cluster name object (CNO) is granted permissions to Secure DNS Zone.    Here’s a screenshot of the actual events: The reason: Before creating the cluster, I had pre-added (manual) the DNS ‘A’ record for the CNO that I would need using IPAM. The solution: I simply deleted the CNO ‘A’ record in DNS and recreated it, ensuring that when I did so, I ticked, “ Allow any authenticated user to update DNS record with the same owner name ” If you do not manually pre-create the CNO 'A' record in DNS then you will not have this issue.  

Go to powershell and run below mentioned command. Get-Disk -Number 17 | Select UniqueId   Replace numeric digit with actual disk ID (can fetch that from disk management console) output : UniqueId -------- 60002AC0000000000000006A003430FA

We can use the Active Directory powershell cmdlet   Get-ADUser   to query users from AD. We can find and get a list of AD users who never logged in at least one time by checking the AD attribute value   lastlogontimestamp .   The below command lists all users who never logged on. Get-ADUser -Filter {(lastlogontimestamp -notlike "*")} | Select Name,DistinguishedName If you want to list only enabled ad users, you can add one more check in the above filter.   Get-ADUser -Filter {(lastlogontimestamp -notlike "*") -and (enabled -eq $true)} | Select Name,DistinguishedName If you are familiar with LDAP filter you can also find never logged in users by using ldap filter.   Get-ADUser -ldapfilter '(&(!lastlogontimestamp=*)(!useraccountcontrol:1.2.840.113556.1.4.803:=2))' | Select Name,DistinguishedName In most cases, we may want to find AD users who created in last certain days or months and not logged in their system. To achieve this, we need to fil

While installing SQL Server 2008 RC0 it give error message as "Access is denied". Final Solution is - This failure often is caused by a system or domain policy removing the SeDebugPrivelege security privilege from the administrator account running setup. Verify that the account running has this privilege. The AccessChk tool will print all privleges for an account (http://technet.microsoft.com/en-us/sysinternals/bb664922.aspx) by running: accesschk.exe -a \ * Alternatively, we can check this through your group policy editor as mentioned below: Open Group Policy... Start Run Type: gpedit.msc OK Navigate to Computer Configuration\Windows Settings\Security Settings\Local Policies\User Rights Assignment\Debug programs The account through which we are trying to run the setup should be here ( besides the local admin on that machine). I included that here, restarted the server ( this is mandatory, gpupdate /force will not work) and ran the setup and it was successful

I had an odd issue with my Windows Vista. Every time I do right-click on a file or folder, an error message would pop-up saying “Registry Access Denied“, after acknowledging the message, the context menu would appear and function normally. I did numerous searches, examined permissions, removed/added the user from groups, nothing worked. Then it hit me, it was the context menu that was having an issue, perhaps I should take a look at all the items that are listed in the registry to see how they matched the right-click menu after it appeared. Doing yet another search, Online Tech Tips had info on editing the right-click menu. Following the registry path mentioned: HKEY_CLASSES_ROOT\*\shellex\ContextMenuHandlers\ I was able to see that there was an entry for a zip program that wasn’t appearing on the context menu. After backing up the registry, I removed that entry and viola, no more error. Simpler than I thought… zipx was exactly my problem! I uninstalled this and now I don’t g