Skip to main content

How to add criteria in Active Directory Administrative Center


Active Directory Administrative Center is a great tool for System Administrator to manage large Active Directory.

ADAC also provides some criteria when searching.

Add criteria is not shown by default.

So if you are new to ADAC it is just a single click to show the add criteria option.

See screen shot below on how to make it visible:




From the ADAC also you will be able to find Windows Powershell history, which you can modify and use it to automate some process.

To dig further see Technet link below:

https://technet.microsoft.com/en-us/library/dd560661%28v=ws.10%29.aspx


Linux Android App cheat sheet:
https://play.google.com/store/apps/details?id=com.LinuxMobileKit

Comments

Popular posts from this blog

Print error 016-799 - Fuji Film Xerox

016-799 Fuji Xerox or Fuji Film print error code. That shows a description error as “Print instruction Fail detected in decomposer.” The error code and error description are alien languages for users and even system administrators who are not familiar with Fuji Xerox error code. The error code is quite simple and easy to fix, if the job print goes to the printer but print out doesn’t come out. So, basically the print job was received by the printer, but the printer just doesn’t know what type of paper or what size to use or which tray to utilize for the print out. In some instances, this is just a paper mismatch but the error description; if using Windows 10 to print does not exactly points to what is the issue. First thing to check, is the paper size selected by the user to print. Example, if the printer configuration is A3 and A4 sizes only. But then the person printing the file accidentally chooses “A4 Cover” then this error 016-799 will occur. ...

PowerShell Match Drive Letter to Volume ID in AWS

Matching AWS volume ID to its corresponding Windows drive letter is an easy task using PowerShell. Win32_DiskDrive holds the info for the volume-ID. Here’s the script, below enjoy 😊 $get_disks = gwmi -query "SELECT * FROM Win32_DiskDrive" ForEach ( $disk in $get_disks ){         $get_partitions = gwmi -query "ASSOCIATORS OF {Win32_DiskDrive.DeviceID=' $( $disk . DeviceID) '} WHERE AssocClass = Win32_DiskDriveToDiskPartition"     ForEach ( $partition in $get_partitions ){         $get_logicaldisks = gwmi -query "ASSOCIATORS OF {Win32_DiskPartition.DeviceID=' $( $partition . DeviceID) '} WHERE AssocClass = Win32_LogicalDiskToPartition"          ForEach ( $logicaldisk in $get_logicaldisks ){         $insert_the_dash = ( $disk . SerialNumber) . Insert( 3 , "-" ) #insert dash to match AWS v...

Delete Directories with Wildcards using rd or rmdir

  Deleting files in command prompt using wildcards is quite straight forward. Command below will delete all text (".txt") files on the specified path.      Del D:\txtlog\*.txt Command above will delete all files with ".txt" extension in d:\txtlog directory. Easy enough to delete all matching files. Using the same method with rmdir or rd command this will not work. For example, if we have a directory on d drive that is auto-generated by an application and the filename is consistent with a pattern plus incrementing number at the end to differentiate the folder from other folders.    D:\baklogs\log1\    D:\baklogs\log2\    D:\baklogs\log3\    Etc..    D:\baklogs\log100\ The folder name has a consistent pattern that is preceded by the word “log” plus incrementing number. If the command below is executed to remove the directories in one go, an error is shown which h...