Welcome to Musing Sysadmin

We've been using Openfire for departmental instant messaging for some time now, which is described on their site as...

"a cross-platform real-time collaboration server based on the XMPP (Jabber) protocol.".

It's been working quite well for us using their Spark client as well as using the Pidgin client.  My boss saw that there is a video conferencing plugin for Openfire and thought that it could be quite useful for a number of purposes.

The one he was looking at was one that uses WebRTC for the audio/video piece in the browser, though the plug-in is still under development and is only able to utilize Chrome browser.  So I happened upon the Redfire plug-in for Openfire that describes itself as

"Redfire is a plugin for Openfire that embeds the Red5 RTMP server, Cumulus RTMFP server and modified Phono SDK to provide audio/video streaming tools for XMPP application development.".

So the plug-in has a lot going on in the backend to make things happen.  Installation of the plug-in is as simple as unzipping the war file into the Openfire plugins directory of the Openfire server and restarting the service.

After I restarted the Openfire server I was scratching my head for a while over a number of errors that were thrown up in the console, such as "SLF4J: Class path contains multiple SLF4J bindings".

After poking at it for a while I figured out it was actually running even with the errors.

So opening http://our_server:7070/redfire brought up the Redfire testing screen which allowed us to play around a little and confirm things were working as expected.  At the bottom of this page there is a link to download the Spark plug-in to get it to work seamlessly with Spark.  When someone initiates a video conference to a Pidgin client it will display a URL to click on to join the conference, still working on a way to initiate a video conference from Pidgin.

Some of the clients that we rolled this out to had issues with bringing up local audio/video, a quick update of Flash and all was well with the world.

Long story short, Openfire server with the Redfire plug-in makes for a nice little Instant Messaging / Audio / Video Conferencing server.  Oh, did I also mention you can connect it to a VOIP gateway to make external calls.

We have a web based learning management system for our employees and have encountered challenges with the system ever since they applied an update.  Long story short, we needed to script for importing into Active Directory the Manager for employees from a CSV file exported from our HR system.
The export from our HR system is in the following format...

//first_name,surname,job_reference,job_title,department_reference,department,work_phone,work_extension,email_address,employee_number,managerfirstname,managersurname,managerjobtitle,employment_status//

For scripting stuff with AD I definitely recommend using Powershell scripts with the Quest ActiveRoles Management Shell for AD add on(Quest Software has been bought by Dell by the way).  I was originally playing around with reading in the CSV export in our nightly batch, pulling in the users from AD, matching up the manager for each and then outputting the data in a CSV.  This was problematic and took forever.  I decided to break things up and have a separate scheduled task that will run weekly to populate the managers field in AD. After poking around on the web for a bit and borrowing and modifying some scripts, with some trial and error I came up with the following...

clear-host
if ( (Get-PSSnapin -Name Quest.ActiveRoles.ADManagement -ErrorAction SilentlyContinue) -eq $null )
{
    Add-PsSnapin Quest.ActiveRoles.ADManagement
}

$users = import-csv c:\util\LMS_Export_test.txt  

foreach ($user in $users){ 
    $eid = $user.employee_number
    $eid = "$($eid.substring($eid.Length-4,4))"
    $mfid = $user.managerfirstname
    $mfshort = "$($mfid.substring($mfid.Length3,3))"
    $msid = $user.managersurname

    $u = Get-QADUser -LdapFilter "(employeeNumber=$eid)"
    $m = Get-QADUser -LdapFilter "(givenName=$mfshort*)(sn=$msid)"

    If (($u -ne $null) -and ($m -ne $null)){
        set-qaduser -identity $u -office $user.department -title $user.job_title -manager $m.dn
    } 
Elseif ($u -eq $null){Write-Host "User $eid not found"}
Elseif ($m -eq $null){Write-Host "Manager $mid not found"}
}

Worked well, I tested it on a subset of the export list and omited the 'set-qaduser' line and added the following above the If (($u ne $null~ line...

   Write-Host "User $eid"
   Write-Host "manager $msid, $mfid and short $mfshort"

Which allowed me to confirm it was working correctly before writing anything to AD.

Now I just need to modify my AD export script to include the manager field.

Hi there, and welcome to the first post to my blog.  Being that I'm a Systems Administrator I'll be posting on various bits of technology ranging from Active Directory to PHP to Virtualization to SAN with a whole bunch of randomness added to the mix.  I am quite frequently am having to dig up information for one thing or another to get something done and usually have to piece together bits from here and there to come up with a complete solution.  So, when I do I'll try to document all the bits so that hopefully it will be of use to some folks out there.