Please pardon our dust
Okay, so, I've put it on my to-do list to actually post something here for the last...wait, it's been *three weeks* already?!? Time sure does fly...
Here I will detail upcoming changes to the site, as well as a status update on the error handling series.
Read MoreGet-RoundHole | Add-SquarePeg -Force -ErrorAction Ignore
Don’t say I never post anything…just almost never…
Read MoreYou get a favicon, and you get a favicon...
Okay, my art skills aren't amazing by any stretch of the imagination, but I've been tired of seeing the default icon on my website. So, I've drawn a very simple 16x16 icon for it using favicon.cc.
That's all; nothing much exciting for today.
This is not what it should look like...
While checking on some things, I decided to load my site in Edge and was in for a bit of a shock: my site was rendered with what appears to be Times New Roman. After validating that I did in fact have fonts configured properly, I did a bit of research on how to fix it, and the short answer is, I can't (at least, not easily). It's a bug in Edge that's been going on for a while now.
Here's a post from almost two years ago about the problem. The best response is towards the end (next to last reply at the time of writing, on October 13th of 2016) and breaks down what is happening and what individuals can do to correct it.
I want to be clear here that I think Edge is overall an excellent browser with a lot of potential, but these sorts of bugs are really problematic and I hope that Microsoft is taking them seriously.
In my last post, I wrote about how setting the Execution Policy is not a viable security countermeasure, and is very easy to bypass by malicious actors. The examples provided work when the Execution Policy is set by running "Set-ExecutionPolicy"; however, it does not bypass an Execution Policy set by Group Policy.
This post will demonstrate a way to get around that as well.
Read MoreWhile there are some benefits to signing your PowerShell code, security really isn't one of them. If something is run on your system that attempts to execute a malicious PowerShell script, it does not matter what your Execution Policy is set to.
Read on for a brief explanation of what Execution Policy actually affects, and a demonstration of how easy it is to bypass.
Read MoreAs I mentioned in a previous post, I now have a GitHub account; all of my small code samples will be hosted there as gists, bigger functions will be added to my "poshsite" repository, and bigger projects will get their own repositories. I've removed all of the directly embedded code from this site and converted them to gists; this will give me a better place to store and share my code, and it provides much better syntax highlighting than what I was previously using.
That's not even getting in to the fact that it tracks changes for me automatically.
Anyway, you can find me at https://github.com/poshcodebear, and my gists at https://gist.github.com/poshcodebear.
It's been a while since my last post, so I thought I'd say a few things about what I've been up to the last few months. While I may not have posted here, I have been quite busy, and working on a lot of other things.
A lot of what I've been doing is just using PowerShell for what it does best: administering systems. Through that, I've learned a lot and have grown my tool belt plenty, but the project I'm working on right now is probably the biggest thing I've done with PowerShell yet: I'm creating a full user management application for provisioning and disabling user accounts in both Active Directory and Office 365 to make a complex process simple for low level techs. The most exciting part of it for me is that I'm building it as a fully functional GUI application using WPF. I'm not using any expensive toolkit like PowerShell Studio to build it, either, so I'm building the GUI in Visual Studio (by the way, VS 2015 Community is out, and it's great!), loading it in to my script with a couple of functions I adapted from things I found online, then adding actions to the button clicks to make them execute my PowerShell code.
Through this, I've been learning a lot about WPF, how to lay out a GUI with XAML, and the .NET framework.
I'm hoping to share the things I'm learning from this, along with many other things, very soon.
Okay, not a PowerShell thing (directly, anyway), just finding that my method of storing my code is becoming unmanageable. Basically, what I've been doing is throwing everything in my Google Drive, which is overall very convenient, but over time is showing to be unwieldy. Especially since, though I write a change log with my more important scripts, I have no way to go back to an old version of my code.
I already had a GitHub account, I've just not been using it. So, depending on how things work, I'll probably start sharing more of my code from there rather than embedding it directly here, and just provide a link to it instead.
In my limited interaction with GitHub in the past, it was fantastic and fairly easy to use. If you're looking for a way to store your code, and even collaborate, it's a great system for it. If you're on GitHub already, I'm on there as poshcodebear. You can find me here: https://github.com/poshcodebear.
There's not much there yet, but I'm going to start migrating my code to there soon so you'll see things start to pop up.
