• 1 Post
  • 336 Comments
Joined 2 years ago
cake
Cake day: June 18th, 2023

help-circle





  • No, no one should do this.

    First off, definitely don’t mail anything hazardous. You’re mostly putting postal workers at risk.

    Second, the instructions in it were written by an angsty 19-year old, not a chemist or weapons expert or bomb technician. Trying to actually make these things puts you at risk.

    Third, if you’re going to talk about this book then it really is necessary to talk about the historical context that the author wrote it in and how he regretted it after, and what the consequences were:

    […] and the incidents where the book was found among the belongings of the perpetrators, including, but not limited to, the Columbine High School massacre, the Arapahoe High School shooting, and the 2012 Aurora, Colorado shooting, as well as a number of assassination attempts on government officials.












  • The best reason to use PowerShell on Linux is if you are working in a mixed/complex environment, or think that you might pursue a career in enterprise IT and want to learn about working in mixed environments. With PowerShell you can remotely manage Windows systems without having to RDP into them, you can just open a remote PowerShell session and issue commands to the target machine.

    I’ve used this to do things like loop through a list of endpoint hostnames, open a session to each one and get an inventory of installed applications on that system and also flag any hosts that didn’t respond to the remote session and then spit out all the results in a .CSV, fully automatic. Run monthly or as needed.

    You can also interact with the Windows registry via .NET classes, which PowerShell understands natively because it is .NET. You can do this locally and remotely, which looks something like this:
    [Microsoft.Win32.RegistryKey]::OpenRemoteBaseKey([Microsoft.Win32.RegistryHive]::LocalMachine, "<hostname>").OpenSubKey('<registry key path>').GetValue('<key value name>')
    So if you wanted to check if a particular registry key was set on a group of Windows machines, you could write a PowerShell script that could just do that for you with no interaction. It’s also possible to modify registry keys remotely with .SetValue('<key value name>'), so if you need to do that in bulk it’s very convenient.

    Basically PowerShell can take previously arduous and time-consuming Windows sysadmin tasks and make them scriptable. And not just Windows, anything and everything .NET can be easily managed via PowerShell.



  • Beyond your eventual technical solution, keep this in mind: untested backups don’t exist.

    I recommend reading some documentation about industry-leading solutions like Veeam… you won’t be able to reproduce all of the enterprise-level functionality, at least not without spending a lot of money, but you can try to reproduce the basic practices of good backup systems.

    Whatever system you implement, draft a testing plan. A simpler backup solution that you can test and validate will be worth more than something complex and highly detailed.