Skip to main content

Converting Base Numbers with PowerShell

By
One of the points that I try to get across the IT Pros taking my PowerShell classes is that if it works, then it is correct.  That does not take efficacy into consideration. However, when you are scripting (or writing software) you need to accept that there are multiple paths to success.  We are going to take a look at the Convert class of .Net to make some numeric conversions.

There are 3 numeric bases that are common in the computer science world.  Decimal because we as humans like it.  Binary, because that is how a computer works.  Hexadecimal because it allows us to represent 4 bits with a single character.  Yes there are other reasons but let’s just keep this simple.
The last time I checked, the convert class provide over 290 overloaded static methods to help you perform conversions.  Below I provided the code to convert between our big 3.

#region Convert to Base 16 ----------------------------------------------------
    # From Base 2
    [Convert]::ToString(11001100,16)

    # From Base 10
    [Convert]::ToString(154,16)
    "{0:X4}" -f 154

#endregion Convert to Base 16 -------------------------------------------------

#region Convert to Base 10 ----------------------------------------------------
    # From Base 2
    [Convert]::ToInt32(10110010,2)

    # From Base 16
     [Convert]::ToInt32("FA",16)

#endregion Convert to Base 10 -------------------------------------------------

#region Convert to Base 2 ----------------------------------------------------
    # From Base 10
    [Convert]::ToString(100,2)

    # From Base 16
     [Convert]::ToString([Convert]::ToInt32("FA",16),2)

#endregion Convert to Base 2 -------------------------------------------------

Obviously their can be other ways to achieve some of these conversions.  Take a look at the last one.  We actually had to perform 2 conversions.  One to Base 10 and then to Base 2.  In any case, I often get asked about these conversions from my more advanced students so here they are!
Labels:

Comments

Post a Comment

Popular posts from this blog

How to run GPResult on a remote client with PowerShell

By
In the past, to run the GPResult command, you would need to either physically visit this client, have the user do it, or use and RDP connection.  In all cases, this will disrupt the user.  First, you need PowerShell remoting enabled on the target machine.  You can do this via Group Policy . Open PowerShell and type this command. Invoke-Command –ScriptBlock {GPResult /r} –ComputerName <ComputerName> Replace <ComputerName> with the name of the target.  Remember, the target needs to be online and accessible to you.
Post a Comment
Read more

Set up your Environment to utilize Invoke-GPUpdate

By
I’m sitting in O’Hare enjoying my 3 hour layover as I get ready to teach a Windows 10 class in Fort Wayne.  I’m actually prepping for my class in Fort Wayne in a few weeks, 10982 Supporting and Troubleshooting Windows 10.  This class is very much like the Windows 7 version that I used to teach so I decided to up the detail quite a bit.  In the GPO troubleshootin chapter, I’m including a demonstration on how to use PowerShell’s Invoke-GPUpdate.  I needed to make sure the environment is set up for me to be able to utilize this cmdlet.  If you read the Notes section on Invoke-GPUpdate’s help file, you will see there are three firwall rules that need to be in place:          Remote Scheduled Tasks Management (RPC)          Remote Scheduled Tasks Management (RPC-ERMAP)          Windows Management Instrumentation (WMI-IN) I decided to create a little PowerShell script to crea...
Post a Comment
Read more

Where did a User’s Account Get Locked Out?

By
Updated: May 15, 2015 When this article was originally published, two extra carriage returns were add causing the code to malfunction.  The code below is correct.   My client for this week’s PowerShell class had a really interesting question. They needed to know where an account is being locked out at. OK, interesting. Apparently users hop around clients and forget to log off, leading to eventual lock out of their accounts. The accounts can be unlocked, but are then relocked after Active Directory replication. This problem is solved in two parts. The first one is to modify the event auditing on the network. The second part is resolved with PowerShell. The first part involves creating a group policy that will encompass your Domain Controllers. In this GPO, make these changes. Expand Computer Configuration \ Policies \ Windows Settings \ Security Settings \ Advanced Audit Policy Configuration \ Audit Policies \ Account Management Double click User Account Management C...
18 comments
Read more