This Saturday will mark the fourth year that I will be speaking at SQL Saturday Baton Rouge at LSU. Out of all the SQL Saturday events I have participated in since 2014, Baton Rouge is one of the few that I have been to every year since. Houston is another one…and actually, these may be the only ones only because they have had an event every year.
Not only am I speaking on Automation with PowerShell and Deadlocks and Blocking, but I am also participating in a panel discussion on Careers in IT. I’m excited to be invited along with some of the other speakers to be a part of this. Looking back on my own school days, I knew I would have a career in IT, but little did I know I would detour from a path in development to the world of SQL Server, and becoming a DBA.
How do they make this happen? Work. Lots of hard work. After helping with SQL Saturday Dallas 2015, joining the NTSSUG board in 2016, and then having an organizing role in 2016, I found out how much goes into the planning of these events. If you have attended a SQL Saturday or you are going to in the future, be sure to say “THANK YOU!” to all the organizers and sponsors. If you want to get more involved in the SQL Server community, SQL Saturday is a great way to do that – just show up at the event, find an organizer and tell them that the SQL Kitten sent you to be their humble servant volunteer for the day…or you could just say you want to volunteer and leave out the other stuff because it might make it weird.
Posted in Database Administration, DBA, NTSSUG, Performance, Powershell, Professional Development, SQL Saturday, SQL Server, Uncategorized
Tagged automation, database administration, DBA, powershell, sqlsat628, SQLSatBR, SQLSaturday, sqlserver
After whining about not blogging enough, I am going to do something about this. Whether it is PowerShell or SQL, simple or complex, I know that others can benefit from my knowledge and expand their skill sets.
And you are like “That’s great Amy…where’s the PowerShell we are here for?” Ok, Ok….keep your drawers on! 😉
Recently I was tasked with gathering the system information from all of the servers at a client. Another opportunity for some PowerShell dominance.
Author: Amy Herold
Date: 03 May 2017
Purpose: Get the system information from a list of computers/servers, doing one machine at a time and outputting server name
when you can't connect. Output information to a NFO file with the name of the machine.
Notes: Get your list of servers and update the $servers variable below. Make sure they are also formatted the same way as in the sample.
Update the $path variable with where you want to save the NFO files.
<#------------variables you need to change---------------#>
$servers = @('server1','server2');
$path = 'C:\Where_You_Want_The_Files\system_info\';
foreach ($s in $servers)
#------as long as we can connect to the machine, get the system info--------
if((Test-Connection -Cn $s -BufferSize 16 -Count 1 -ea 0 -quiet))
$filepath = $path + $s +'.NFO';
$cmd = "C:\windows\system32\msinfo32.exe";
$args = "/computer $s /nfo $filepath /categories +all";
#if you can connect to the server, gather and save sysinfo
Start-Process $cmd $args -Wait;
"Cannot connect - $s"
With this script you can generate system information files and save them to a specified location. It makes sure a connection can be made to the server first, and then outputs the file. The files are created one at a time, so if you pass in a longer list of servers, you shouldn’t crash your machine. From my testing, this will take some time to run as these files don’t output quickly. Despite that, the output is worth it. This can be modified to pull your list of servers from a file or from a Central Management Server (CMS) instance.
Hope you find this useful. Happy PowerShellin’ 🙂