As of September 2015, I have released version 2 of my PowerShell Logging solution, and is now known as PSLogging.
There has been a number of significant improvements with the most notable being that the PowerShell Logging function library has now been converted into a fully fledged PowerShell module. All of the details about the new version, the improvements and how to use and integrate the new version into your new and existing scripts can be found here – PSLogging PowerShell module.
Note: This version of the logging solution is no longer supported or maintained, so please upgrade to the new version today!
Today I thought I would share some thing that I have developed over the last year or so as I have been working more and more with PowerShell…. some standard functions that can simply be dot sourced and called at any time so that all my scripts have some awesome logs to go along with the awesome script.
Recently I found a number of VMs with old network adapters (i.e. Flexible or E1000). To improve performance and reliability, I decide to upgrade these NICs to VMXNET3.
The really annoying thing about iOS devices is that they revert your button formatting back to their crappy default look. For me, that is REALLY annoying! I went through all of the effort to make my buttons look awesome, and then on mobile device (or even possible some other browsers) they look nothing like what I want.
Last week at work I was having such a great time until my Windows machine got a Blue Screen of Death (BSOD). I was trying to figure out what caused it, until one of my colleagues told me about BlueScreenView – an awesome little app that loads the minidump file created by Windows and will pin point exactly what the problem was. It is so awesome, that it can actually re-create the blue screen of death and give you a preview of what it looked like.
It has been ages since my last post, but it doesn’t mean I haven’t been busy working away on different things. One of the things I have been spending a lot of my time on is Responsive Web Design….
And below is my Responsive Web Design: CSS Grid Template I created for all of you all to use, learn and enjoy:
Recently I have had to restrict access to an IIS site to users who are in a specific AD group – in my case Domain Admins (but it can be any group you want). This is how you do it….
Last week I had a user report that his account kept locking a number of time throughout the day. Usually this is because they haven’t logged out of a machine and then have changed their network password, so when that remote machine tries to authenticate… bang account lockout.
More often than not, the user has no idea what he is still logged into, so the only way is to solve this is to go through the Security event logs on each domain controller and find the account lockout event for that user. This will then tell you from what machine the account lockout took place. You can then get the user to log out and problem fixed.
Although this works, to be honest it’s manual process which really like most manual processes…it’s boring. So then I thought, why not create a PowerShell script that can easily do this for me.
Just thought I would let you know what I found a few days ago when using SMS Trace (
Trace32.exe). I have been using this tool to view SCCM logs for the last few years and I can’t believe I didn’t come across this until now… would have saved me heaps of grief!