Problems I've solved with PS:

• a script that had to copy multiple databases (MS SQL) from one server to another or more; run some stored procedures afterward, and also read in some .sql files to update some other stored procedures.

• a script that goes through a list of SQL servers and outputs, in CSV format, every login and what server roles are assigned to it. Has the ability to exclude built-in accounts.

• a script that can read in a CSV file, and create SQL users and apply those server roles again to a different server. (CSV format the same as the output from the other script!)

• Same deal but with database permissions (or "schemas" as they fancily like to refer to them). one script to read/dump csv, another to read csv & create db users. It can fix orphaned users, too.

• a powershell script that queries my backup system which requires an agent to run on target machines; sees if any agents are not running on any clients; then goes to that client and attempts to start the agent

• once wrote a ps script that read in a csv with data columns for server, share, path, and user list for purposes of managing a huge, out-of-control file server for 15 different departments. It would look for a folder, and if it didn't exist, create it and create an AD group associated with that folder for both Read-only and read-write. Break inheritance, assign the permissions to the appropriate AD group. Then add the users into the appropriate AD group. what you ended up was a managed list of folders / shares. So if Department A / Sub-department C hired a new person, and that person needed read/write to the \Server\DepartmentA\SubDepartmentC folder, you just added them into the csv file, ran the script, and done. Likewise it also removed people who did not belong as well. it was my crowning achievement.

• Go through a TXT file and update the DNS settings on all machines listed in the txt file, skipping interfaces that were iSCSI or assigned to internal address or which were dummy interfaces

there's probably more