Pugazhnetwork

Powershell to get the local computer groups detail: Group Detail: for /F "delims=* tokens=1 skip=4" %i in ('net localgroup') do net localgroup %i >> c:\groups.txt or for /f %i in (MyComputerList.txt) do wmic /Node:%i path win32_groupuser where (groupcomponent="win32_group.name=\"administrators\",domain=\" %i\"") Users detail: $computers = Get-Content -Path C:\computer.txt Get-WmiObject -ComputerName $computers -Class Win32_UserAccount -Filter "LocalAccount='True'" | Select PSComputername, Name, Status, Disabled, AccountType, Lockout, PasswordRequired, PasswordChangeable, SID | Export-csv C:\local_users.csv -NoTypeInformation

Powershell Cmd to fetch local computer users list: $computers = Get-Content -Path C:\computers.txt  Get-WmiObject -ComputerName $computers -Class Win32_UserAccount -Filter "LocalAccount='True'" | Select PSComputername, Name, Status, Disabled, AccountType, Lockout, PasswordRequired, PasswordChangeable, SID | Export-csv C:\local_users.csv -NoTypeInformation

Get-ADObject -IncludeDeletedObjects -Filter {objectClass -eq "c15278" -and IsDeleted -eq $True}

Configuring Network Prioritization on a Failover Cluster Hi Cluster Fans, This blog will describe the Network Prioritization feature and how to configure it.  Network Prioritization is used to designate which type of traffic should be directed through which network in a Failover Cluster running Windows Server 2008 R2.  When designing a highly-available infrastructure, it is important to avoid any single points of failure, so there should be redundancy in all the hardware components, including the servers, storage and the networking.  For this reason we recommend and assume that there are multiple networks in your cluster.  If a network is unavailable Windows Server Failover Clustering will automatically direct traffic through another network to maintain service availability for applications or VMs.  However some networks may be preferred for certain types of traffic based on the network’s speed, security or function, so it can be important to designate which network is used

NETLOGON.LOG Netlogon.log has to offer – trying to track down the source of a user account’s lockouts or find subnets that haven’t been put into an Active Directory site yet. DBFlag is set to  0x2080ffff , just like this TechNet article. That quick looks makes it look like your options are EVERYTHING! or nothing. Data Source: http://support.microsoft.com/kb/109626 All descriptions as-is from Microsoft. Basic Netlogon Flags Flag Name Value Description NL_INIT 0x00000001 Initialization NL_MISC 0x00000002 Misc debug NL_LOGON 0x00000004 Logon processing NL_SYNC 0x00000008 Synchronization and replication NL_MAILSLOT 0x00000010 Mailslot messages NL_SITE 0x00000020 Sites NL_CRITICAL 0x00000100 Only real important errors NL_SESSION_SETUP 0x00000200 Trusted Domain maintenance NL_DOMAIN 0x00000400 Hosted Domain maintenance NL_2 0x00000800 NL_SERVER_SESS 0x00001000 Server session maintenance NL_CHANGELOG 0x00002000 Change Log references NL_DNS 0x00004000 DNS name regist