Convert WMV encoded with G2M4 Codec

I ran into some issues using a video created with GoToMeeting. Turns out that GoToMeeting uses its own codec (G2M4) when encoding the videos, so it won't play in all media players. My specific issues was that it wouldn't automatically stream & play in a webpage when uploaded to our Intranet.

I used these instructions from the folks at AVC to convert the video to a more friendly WMV3 codec:

http://www.any-video-converter.com/convert-g2m3-g2m4-codec-video-to-wmv-avi-mp4-flv.php

Step One:
Please click here to download and install the gotomeeting codec.

Step Two:
Please go to C:\Program Files\Citrix\GoToMeeting\723 (a folder with numbers, which is the version of GTM you have installed). There will be a file called "g2mtranscoder.exe". This is the utility that GoToMeeting uses to convert the file to a generic WMV file after recording.

Step Three:
Now follow the instructions below to use command line to convert the WMV G2M3/G2M4 Codec Video file:
1. Copy g2mtranscoder.exe AND g2m.dll files and paste them onto the ROOT C: drive (ie not in a folder).
2. Place the GoToMeeting recorded WMV G2M3/G2M4 Codec Video file on the ROOT C: drive as well.
3. Launch the command prompt (start -> run -> cmd).
4. If the command prompt launches and shows a file/folder path (ie C:\Documents and Setting\etc) then type "cd.." (without the quotes) until you are seeing just the root C: in the command prompt line (will look like C:\>).
5. Now, type the following at the prompt: "c:\g2mtranscoder.exe source=c:\videofilenamehere.wmv". (Of course put the name of your video file instead of those words and don't forget the .wmv).

6. This should have kicked off the conversion, but there is no visual indication of this. You can make sure it's working though - open Task Manager and click on Processes then sort by CPU usage, you should see the g2mtranscoder hogging all your CPU cycles. It's working!

Please note it would take about 20-30 minutes for g2mtranscoder.exe to convert a one-hour long file to a generic WMV file.
7. When the g2mtranscoder.exe process stops, you would get the WMV WMV3 codec video in ROOT C: drive, which has replaced the source WMV G2M3/G2M4 codec video.

Migrating Scalix to Google Apps: Mail

We are investigating Google Apps as a replacement for Scalix 11.4.6. I am doing a test migration right now that will move all my mail folders using (the older free version of) imapsync. Here is the script that I am using:

imapsync --host1 my.host1.com --user1 username --password1 **** --authmech1 PLAIN \
--host2 imap.gmail.com --user2 username --password2 **** --authmech2 LOGIN --port2 993 --ssl2 \
--exclude "Calendar|Contacts|Deleted Items|Journal|Junk E-mail|Notes|Other Users|Public Folders|Tasks" \
--prefix2 "SX/" --regexflag 's/\\X-*//g' --allowsizemismatch --useheader 'Message-ID' --skipsize

Let's go through the script:

These are the basic lines required for imapsync, specifying our hosts and login credentials.
imapsync --host1 my.host1.com --user1 username --password1 **** --authmech1 PLAIN \
--host2 imap.gmail.com --user2 username --password2 **** --authmech2 LOGIN --port2 993 --ssl2 \

This line excludes non-mail folders that will be moved manually, most likely via Outlook connectors & PST files. (ugh)
--exclude "Calendar|Contacts|Deleted Items|Journal|Junk E-mail|Notes|Other Users|Public Folders|Tasks"

This line will prefix each folder name is Google Apps with "SX". I want to keep migrated data separate from the default folders in Gmail.
--prefix2 "SX/"

This is required to fix an error with headers added by Scalix (BAD parse error: non-storable system tag "\X-Has-Attach"). See this post on the Zimbra forums.
--regexflag 's/\\X-*//g'

Since we are modifying the message (--regexflag, above) we need to tell imapsync to ignore message sizes, since they will no longer match. Instead, we need imapsync to use the "Message-ID" header to compare messages. These options allow us to run imapsync again after the intial sync and only sync changes.
--useheader 'Message-ID' --allowsizemismatch --skipsize

Big thanks to Mark for this post!

Latitude e6220 "Unknown Device"

I was just re-installing Windows 7 x64 on a Dell Latitude e6220. After installing drivers, there was one "Unknown Device" in device manager. In Properties -> Details, the Hardware Id is listed as:

ACPI\SMO8800
SMO8800

Turns out this is a driver for the hard drive's free fall sensor. Go to dell support, select computer type and your operating system. Select the "Application" category and you will see:

ST Microelectronics-Driver
Applies to: Free Fall Sensor

Direct Link (Win7 x64): http://www.dell.com/support/drivers/us/en/19/DriverDetails/DriverFileFormats?DriverId=F91KT&FileId=2731102934