Search results for 'app:weblogs' matching tag 'Tim Bolton'

Weekend Scripter: Finding In-Use Phone Extensions

Anonymous — Sat, 29 Dec 2012 06:00:00 GMT

Summary: Guest blogger Tim Bolton talks about using Windows PowerShell to determine what phone extensions are currently in use.

Microsoft Scripting Guy, Ed Wilson, is here. It is amazing the number of manual tasks that can be safely eliminated by using a little bit of Windows PowerShell. In fact, it is also amazing, in general, how little time it actually takes to create something useful in Windows PowerShell. The funny thing is that even people who “know PowerShell” still fall into the trap of doing something manually—at least I know that I do!

Yes, I admit it … there are still times when I do things manually. Why? Well, I will admit that at times I am lazy. I have been using a mouse a lot longer than I have been using Windows PowerShell. Still, I will say that with Windows 8 and Windows PowerShell 3.0, those manual excursions are becoming less and less frequent. This is because we have so much more built-in cmdlet (and function) coverage that often it really is easier to use Windows PowerShell than to use the mouse. All of our new products incorporate Windows PowerShell to facilitate management. This is great news for people who just want “to get the job done.”

Learn Windows PowerShell—it will save you time and effort.

Today, we have another guest blog post written by Tim Bolton. Tim is learning Windows PowerShell. His article is immediately useful, but it’s also an encouragement to others who want to learn this useful technology.

For more about Tim, see his extremely popular Why Should I Learn Powershell? Real World Example Saves the Day! guest Hey, Scripting Guy! Blog post.

Here's Tim ...

Finding In-Use Phone Extensions

After doing this manually by checking an Excel spreadsheet and dialing each number manually, I was once again reminded of the following rule of POSH: If you have to do something more than twice, script it.

In my current position, one of the common daily tasks is to assign telephone numbers to new users and also reassign numbers depending on where they are working within the company. Once again, with the help and inspiration of my coworkers Brian Peacock and Arturo (Art) Carrera, this script came to life.

Initially the script looked something like this. This was not pretty to look at and my coffee would get cold waiting for it to finish. #FAIL –

Function Get-Extension {

param(

$Extension = (Read-Host "What is the Extension you want to check? ")

)

$CSUser=Get-csuser | where {$_.LineURI -like “*$Extension"}

$GetUser=Get-user | where {$_.Phone -like “*$Extension”"}

$GetUM=Get-UMMailbox -resultsize unlimited | where {$_.PhoneNumber -like "*$Extension"}

$obj = New-Object -TypeName PSObject

$obj | Add-Member -MemberType NoteProperty -Name "CS Display Name" -Value ($CSUser.DisplayName)

$obj | Add-Member -MemberType NoteProperty -Name "Line URI" -Value ($CSUser.LineURI)

$obj | Add-Member -MemberType NoteProperty -Name "AD Phone" -Value($GetUser.Phone)

$obj | Add-Member -MemberType NoteProperty -Name "Exchange SIP" -Value ($GetUM.SIPResourceIdentifier)

$obj | Add-Member -MemberType NoteProperty -Name "Exchange Extension" -Value ($GetUM.Extensions)

Write-Output $obj

}

After I found the few -Filters I could actually use, we got it down to about 2 to 3 minutes. Not too bad but GEEZ! This “is” Windows PowerShell, right? So, this is the second generation, but once again, it felt like well … #FAIL –

Function Get-Extension {

param(

$Extension = (Read-Host "What is the Extension you want to check? ")

)

$CSUser=Get-csuser -Filter "LineURI -like '*$Extension'"

$GetUser=Get-user -Filter "Phone -like '*$Extension'"

$GetUM=Get-UMMailbox -resultsize unlimited | where {$_.PhoneNumber -like "*$Extension"}

$obj = New-Object -TypeName PSObject

$obj | Add-Member -MemberType NoteProperty -Name "CS Display Name" -Value ($CSUser.DisplayName)

$obj | Add-Member -MemberType NoteProperty -Name "Line URI" -Value ($CSUser.LineURI)

$obj | Add-Member -MemberType NoteProperty -Name "AD Phone" -Value($GetUser.Phone)

$obj | Add-Member -MemberType NoteProperty -Name "Exchange SIP" -Value ($GetUM.SIPResourceIdentifier)

$obj | Add-Member -MemberType NoteProperty -Name "Exchange Extension" -Value ($GetUM.Extensions)

Write-Output $obj

}

Then, my coworker Brian mentioned saving it as a string and making it a bit faster instead of waiting for the screen to prompt me for the extension.

This also made it possible (to my surprise) to use –Filter with Get-UMMailbox, which made it much faster—down to 15 seconds! #WINNER! -

Function Get-Extension {

param(

[parameter(Mandatory = $true)]

[String] $Extension)

$CSUser=Get-csuser -Filter "LineURI -like '*$Extension'"

$GetUser=Get-User -Filter "Phone -like '*$Extension'"

$GetOther=Get-User -Filter "OtherFax -Like '*$Extension*'"

$GetUM=Get-UMMailbox -Filter "EmailAddresses -Like '*$Extension*'" # Exchange

$NotFound = "Extension Not Found"

As before, I will answer some of the most common questions I have received about this script to save you some time.

Yes, Yes, Yes, Josh, I know I'm killing puppies with the Write-Host, BUT again, it’s just for visual verification only.
Was there much of a difference in speed gained by using –Filter? YES! We went from waiting anywhere from 4- 6 minutes to 2 -3 minutes to just over 15 seconds. Behold the power of the Shell!
Why use New-Object? Honestly, Claus, Jeffery H, and Jeff W. I just happened to be on chapter 19 of Learn Windows PowerShell in a Month of Lunches (second edition) and, well, it looked like a good idea.
Why are you worried about the OtherFax Number? The reason for that, Brian, is that I have found the techs in the past were using Phone Numbers for Fax Numbers and vice versa. This can cause you to go insane trying to figure out why a particular number will not work correctly searching by Phone Number or Extension alone.
Jeffery, I used the [String] setting, per Brian’s suggestion, to exclude the prompt for an extension making it a bit faster, and I soon realized (to my surprise) that I would now be able to use –Filter with Get-UMMailbox, which otherwise was nearly impossible. Why the limitation on the Filters available, I have no idea. That would be a good question to bring up with the Exchange team.
This is yet another reason to actually “Learn” Windows PowerShell. Do not just copy other people’s work. You are doing yourself a disservice. It did not even occur to me to make it a string, but now I am actually starting to “get it.” The more I “Learn” about Windows PowerShell, the more I want to use it, and I am better off for it.

Link to the repository: http://gallery.technet.microsoft.com/scriptcenter/Get-Extension-a4213c52

~Tim

Thank you, Tim! Great job, and thanks for sharing your script with us today. Join me tomorrow for more cool Windows PowerShell stuff.

I invite you to follow me on Twitter and Facebook. If you have any questions, send email to me at scripter@microsoft.com, or post your questions on the Official Scripting Guys Forum. See you tomorrow. Until then, peace.

Ed Wilson, Microsoft Scripting Guy

Why Should I Learn PowerShell? Real World Example Saves the Day!

Anonymous — Sat, 28 Jan 2012 06:00:00 GMT

Summary: Guest blogger, Tim Bolton, shares a real world story that brings home the need to learn Windows PowerShell.

Microsoft Scripting Guy, Ed Wilson, is here, and it’s time for the Weekend Scripter. Today we have a guest blogger, Tim Bolton.

Tim Bolton has been involved in the IT Pro community for over 18 years. Tim received the Microsoft Certifications MCITP Enterprise Administrator on Windows Server 2008 and MCTS Microsoft Exchange Server 2010, Configuration. Tim is currently working as a Microsoft consultant and systems engineer at Software Solutions. Tim and his family have recently relocated to the Dallas/Fort Worth area.

Blog: Tim Bolton – MCITP – MCTS, Sharing information about IT and things I have broken, fixed, and seen
Twitter: @jsclmedave
LinkedIn: Tim Bolton

Take it away Tim…

Working within a large corporate environment can produce some strange IT issues. Often these issues demand immediate attention and answers, usually with a manager hovering over you.

Recently while I was working in one of those large corporate environments, which had a large network that had just inherited over a thousand servers, a security issue was raised. Each of the production servers are required to have RSA installed and running to ensure secure log ons.

Because this was one of those scenarios where the servers were recently inherited, it proved to be extremely difficult to provide an accurate answer for, “Can you confirm that the RSA service is running on all of the servers within our scope?”

SCCM was not an option at this time and management wanted an answer “now,” so there was not time to open a service ticket for assistance. Logging on to over a thousand servers to verify if the RSA service was running was obviously not an option, and other third-party applications were not at our disposal.

Windows Powershell to the rescue!

With guidance from Windows Powershell MVP, Claus Nielsen, who happened to be online and available, I was able to provide the answer that was needed in a timely manner. I already had a text file (MyServers.txt) with all of the servers in our scope listed, so that part was already accomplished.

The service that the RSA application ran as is OASVC_Local. I simply needed to check for that service on each server in the text file.

Using the appropriate credentials, I pulled the servers from the text file by using Get-Content, and I placed them into a variable that I called $Servers. Here is the command I used.

$Servers = Get-Content "C:\Temp\MyServers.txt"

Now, using the Foreach command, I started checking for the service on the remote servers. The Foreach command will loop through each server in the $Servers variable. Each loop will use the variable $Server which will contain one item from the variable $Servers list of servers. By using the variable $Server (the computer name in this case) and Get-WMIobject to connect to remote servers, the script will query for the service OASVC_Local, and populate the variable $Service with a "Service" object that will contain the properties for each object. Here is the command I arrived at using.

Foreach ($Server in $Servers)

{$Service = Get-WMIobject win32_service -computername $Server -Filter "Name = 'OASVC_Local'"

I also want to determine if the service is running or not. I query if the service is running by using the If statement. If the state equals “running,” then write "RSA is Running for $Server" to a file called RSA.txt, and also write it to the console screen. I wanted to have the results appear on the console screen for quick viewing, in addition to a text file that I could use as a simple search for the key word “NOT” to identify servers that needed attention. (Note: NOT running -BackgroundColor red.) Here is that portion of the script.

If ($Service.state -eq "running")

{

Write-Output "RSA is Running for $Server" | out-file -append C:\Temp\RSA.txt

Write-Host "RSA is Running for $Server”

} else

{

Write-Output "RSA is NOT Running for $Server" | out-file -append C:\Temp\RSA.txt

Write-Host "RSA is NOT Running for $Server" -BackgroundColor red

}

The following image shows the commands that I typed and the output that I received in the Windows PowerShell console.

Here is the script in its entirety. Simple, quick—and it provided me with the information that I needed in seconds. I actually found fewer than 10 servers out of a thousand, that needed to be checked as to why the RSA service was not running. This was a manageable task, which was corrected before the lunch hour.

$Servers = Get-Content "C:\Temp\MyServers.txt"

Foreach ($Server in $Servers)

{$Service = Get-WMIobject win32_service -computername $Server -Filter "Name = 'OASVC_Local'"

If ($Service.state -eq "running")

{

Write-Output "RSA is Running for $Server" | out-file -append C:\Temp\RSA.txt

Write-Host "RSA is Running for $Server"

} else

{

Write-Output "RSA is NOT Running for $Server" | out-file -append C:\Temp\RSA.txt

Write-Host "RSA is NOT Running for $Server" -BackgroundColor red

}

Without guidance and explanation from Windows PowerShell MVP, Claus Nielsen, this would have taken “me” most of the day to configure—time that I did not have. This is yet another “real world” reason that seems to iterate throughout the IT community about learning Windows PowerShell. How many of us can reach out to a Windows PowerShell MVP that “may” be available to assist you with management’s emergencies? I was lucky today, but what will my managers ask tomorrow?

If you are an IT administrator, I would highly suggest that you become familiar with Windows PowerShell. It may save the day and make you out to be the “go to” person when an issue arises. This may also come into play when reviews are due. Harness the power of Windows PowerShell to show your company why you and your skills stand out above the others.

~Tim

Thank you, Tim. This is a great real world example of using Windows PowerShell to save the day! It is also a tribute to the amazing Windows PowerShell community.

Ed Wilson, Microsoft Scripting Guy