Archive for June 4th, 2014

Update AD EmployeeNumber Attribute From CSV File

Wednesday, June 4th, 2014

2014-06-04 Initial Post

The other month I needed to update the EmployeeNumber attribute of all Active Directory user accounts based on a CSV file generated from Oracle HRMS. You may modify this script to update a different attribute, such as EmployeeID.

#Script updated 2014-03-31, created 2014-03-06, by
#PURPOSE: Takes a CSV input file that contains "E-mailAddress,EmployeeNumber" on each line (DO NOT include header in CSV file).
# Searches AD for user account that has the e-mail address as its primary address.
# If found, update that respective AD account with the corresponding EmployeeNumber.
#There is some limited error checking and a status file is generated after script completion.
#I was not able to get the Import-Csv command to work correctly so I used Get-Content to grab data from the input file.
#Tested against Windows Server 2008 R2 SP1 AD.
$strFilePathInput = "X:\TempPowerShell\setAD-EmployeeNumberINPUT.csv"
$strFilePathOutput = "X:\TempPowerShell\setAD-EmployeeNumberOUTPUT.csv"
Get-Content $strFilePathInput | ForEach-Object{
$strUserInfoLineFromFile = $_
$strUserEmailAddress = $strUserInfoLineFromFile.Split(",")[0]
$strUserEmployeeNumber = $strUserInfoLineFromFile.Split(",")[1]
If($objADuser = Get-ADUser -Filter {mail -eq $strUserEmailAddress }) #The mail attribute is the primary/reply e-mail address.
Set-ADUser $objADuser -EmployeeNumber $strUserEmployeeNumber
If($?) #If True, which means previous command (set EmployeeNumber) was successful. Invalid e-mail address or insufficient AD permissions will make this False.
"OK - Updated," + $strUserInfoLineFromFile | Out-File -Append $strFilePathOutput
"ERROR - Could not update," + $strUserInfoLineFromFile | Out-File -Append $strFilePathOutput
"E-mail address has no primary match," + $strUserInfoLineFromFile | Out-File -Append $strFilePathOutput

Whirlpool WFW9250WR Front-Loading Washer F9 E1 Error, Clogged Drain Filter

Wednesday, June 4th, 2014

2014-06-04 Initial Post

Back on 2012-11-12, my washer beeped and displayed the F9 E1 error about midway through a cycle. I looked up that error code in the Use & Care Guide and here’s what it stated:

“F9E1” on display (Drain Problem)

Press POWER to cancel the cycle. Unplug washer or disconnect power.

Plug in washer or reconnect power. Re-select cycle and press

START/PAUSE. If the problem remains, call for service.

I did all that several times to no avail. I was pretty much set on calling an appliance repair place and then I found the answer here: It stated to “remove the lower front panel and unscrew the filter from the pump and clean it out.” I figured out how to do that and here’s my summary:

  1. Unplug power from the washer.
  2. Prop the two front legs of the washer on a piece of 2 x 4 or something similar.
  3. Unscrew the three screws on the bottom of the front panel (I used my Metrinch ¼ inch/6mm socket). These screws are hard to grip, so you’ll need to put some pressure on them.
  4. The drain components are on the right side. Put something under the big white drain plug to catch water as you turn it slowly counter clockwise. There might be a lot of water in there, so take your time and close the plug when you need to, to dump the water; Do this as many times as necessary to remove all the water.
  5. Inside the white drain tube, on the right side is the filter area. I found a piece of my wife’s bra in there, so after removing that and checking with a mirror to verify that nothing else was caught in there, I put everything back and put the washer on the RINSE/DRAIN & SPIN cycle and it has worked fine since.

It wasn’t my idea of how to spend a Monday evening, but I saved $50 some dollars and most importantly, time. I was dreading the idea of having to take a day off from work to meet with the appliance repairman.

Whirlpool-Washer-Drain01 Whirlpool-Washer-Drain05Whirlpool-Washer-Drain02Whirlpool-Washer-Drain03Whirlpool-Washer-Drain04

In IT, What Is the Difference Between Systems Engineer and Systems Administrator?

Wednesday, June 4th, 2014

2014-06-04 Initial Post

Both terms can mean the same thing if used at different organizations, e.g., a Systems Administrator at Company A might do the same thing as a Systems Engineer at Company B. But when the same company has both titles, there is a difference. The engineer plans and sets up the systems and the admin maintains them.

So usually, the engineer is more knowledgeable and experienced. Novell used to have the Certified Novell Administrator (CNA) and Certified Novell Engineer (CNE) certifications. The CNA, IIRC, required only one exam while the CNE required the CNA and something like three or four additional exams. Microsoft had the same concept with the Microsoft Certified Systems Administrator (MCSA) and Microsoft Certified Systems Engineer (MCSE). The point was that the CNE/MCSE had additional training/knowledge beyond the CNA/MCSA.

Even when I was a Sr. Systems Engineer, I would just tell people that I was a Systems Administrator. The reason was that I didn’t feel qualified to call myself an “engineer” because I didn’t have a degree in an engineering discipline. This is why the blog that you're reading is named Sys Admin Extraordinaire. I know people who’ve gone to school for engineering and I know that it requires a tremendous amount of math and sciences skills, and not everyone is cut out for it. But the funny thing is that I have met degreed engineers who think that what I do is so difficult. Back when I was in computer school for my CNE, my friend’s uncle, who went to school for electrical engineering, thought that being a CNE was a big thing.

I also feel that the term “systems engineer” is overused and needs to be more specific such as IT Server Systems Engineer or Telephony Systems Engineer. There is actually a college major for “systems engineering” which basically consists of learning about all the major engineering disciplines with the goal of being able to understand how to utilize that knowledge to design a complex system.