Still creating accounts by hand? Yeah – we just got out of that boat! If you would like to automate your account creation – here is a sample script you can use!
The faster things become – the faster we want things to become.
For example – PowerShell. On my machine, it takes about 5-6 seconds to be fully functional. Because I link PowerShell scripts into certain MMCs, starting PowerShell quickly is very important to me!
If you need to read through large log files and search for specific keywords, there’s no need to write complex scripts but a simple three liner inside PowerShell can do all the work for you! The sample PowerShell code below, allows you to search through text files such as, log files in Windows 7 systems and outputs every line where a match of the given keyword is found.
Windows Management Instrumentation (WMI) allows you to write scripts and expose information about a Windows 7 resource or service. As we have seen in the previous post – Windows Management Instrumentation (WMI), WMI allows you to access system management information from the command-line interface! WMI can become handy when you need to retrieve specific information which may be not available from the GUI. Mastering the WMI command line utility may turn you into command line freak never wanting to leave the command line.
Windows Management Instrumentation (WMI) allows you to write scripts that configure performance settings and resolve performance issues. System performance is dependant on many factors and settings, and the amount of resources every service or process consumes. With WMI, you can write scripts that manage event logs, file systems, printers, processes, registry settings, scheduled tasks, security, services, shared folders, etc. WMI scripts can monitor and respond to entries in the event log, modifications to the file system or the registry, and other real-time operating system changes.
In part 3 of this AppLocker series, we will go through the rules that AppLocker uses to allow or block specific applications. Firstly, note that explicitly defined Block rules (non generic) override any Allow rules (generic). Secondly, note that if you don’t set a default policy to allow all applications, then any application that has no Allow policy will not be allowed to execute. When creating rules you can take two different approaches, either you allow all applications to run with specific ones set as blocked, or leave the default behavior of AppLocker and then allow specific applications to run (remember to allow administrators full allow permissions and everyone to run system applications). However, it is recommended to start implementing AppLocker rules by performing an audit exercise prior to the actual enforcement of rules.
An answer file gives you the control to perform an unattended installation, that is, the installation process is provided with the answers in a script file instead of having someone attending to it! You can for example, configure passwords, set default Internet Explorer settings, accepting a EULA, etc… The answer file should contain all the settings (answers) required during an installation.
Before proceeding further, I recommend you to Compress and Decompress your most popular archives with WinTar application!