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 fi...

I was researching how to change the Subnet Mask of a DHCP scope on a Windows 2008 server. It turns out you can’t change the subnet without deleting the scope and recreating it. If there are a lot of customizations to the scope, though, like reservations and scope options, it’s no easy task to delete and recreate the scope. Luckily   I found one page   that explains how to export the scope to a text file, make changes, and then reimport it. The whole process takes only a couple of minutes, and you end up with a deleted and rebuilt scope that has all your customizations intact. Use the below command to export the scope configuration Syntax: C:\>netsh dhcp server \\”Server name” scope “scope subnet” dump>c:\dhcp.txt Example: C:\>netsh dhcp server \\Test01 scope 192.168.1.0 dump>c:\dhcp.txt That creates a text file you can edit to change the Subnet, and whatever else you want changed. Then you have to delete the s...