[null, {"document_url": "http://jasonmlee.com/archives/category/church-it/page/3", "unformatted_src": "http://jasonmlee.com/wp-content/themes/focused/img/ico_comments.png", "src": "http://jasonmlee.com/wp-content/themes/focused/img/ico_comments.png", "formatted_filename": "ico comments"}, null, {"document_url": "http://jasonmlee.com/archives/category/church-it/page/3", "unformatted_src": "http://static.flickr.com/4072/4477238796_97b79776db.jpg", "src": "http://static.flickr.com/4072/4477238796_97b79776db.jpg", "formatted_filename": "b db", "alt_text": "IPO-IPRoute"}, null, {"document_url": "http://jasonmlee.com/archives/category/church-it/page/3", "unformatted_src": "http://jasonmlee.com/wp-content/themes/focused/img/ico_comments.png", "src": "http://jasonmlee.com/wp-content/themes/focused/img/ico_comments.png", "formatted_filename": "ico comments"}, null, {"document_url": "http://jasonmlee.com/archives/category/church-it/page/3", "unformatted_src": "http://static.flickr.com/2425/4015180410_af4c9de8e6.jpg", "src": "http://static.flickr.com/2425/4015180410_af4c9de8e6.jpg", "formatted_filename": "af c de e", "alt_text": "Printer"}, null, {"document_url": "http://jasonmlee.com/archives/category/church-it/page/3", "unformatted_src": "http://static.flickr.com/2666/4015199170_2819c09953.jpg", "src": "http://static.flickr.com/2666/4015199170_2819c09953.jpg", "alt_text": "i386"}, null, {"document_url": "http://jasonmlee.com/archives/category/church-it/page/3", "unformatted_src": "http://jasonmlee.com/wp-content/themes/focused/img/ico_comments.png", "src": "http://jasonmlee.com/wp-content/themes/focused/img/ico_comments.png", "formatted_filename": "ico comments"}, null, {"document_url": "http://jasonmlee.com/archives/category/church-it/page/3", "unformatted_src": "http://static.flickr.com/2532/3996071634_55138e69c4.jpg", "src": "http://static.flickr.com/2532/3996071634_55138e69c4.jpg", "formatted_filename": "e c", "alt_text": "RemoteDesktop 2008r2"}, null, {"document_url": "http://jasonmlee.com/archives/category/church-it/page/3", "unformatted_src": "http://static.flickr.com/3418/3996071576_925534cfea.jpg", "src": "http://static.flickr.com/3418/3996071576_925534cfea.jpg", "formatted_filename": "cfea", "alt_text": "RemoteDesktop 2008r2"}, null, {"document_url": "http://jasonmlee.com/archives/category/church-it/page/3", "unformatted_src": "http://static.flickr.com/3461/3995322233_180b4a8cfc.jpg", "src": "http://static.flickr.com/3461/3995322233_180b4a8cfc.jpg", "formatted_filename": "b a cfc", "alt_text": "2008ServerManager"}, null, {"document_url": "http://jasonmlee.com/archives/category/church-it/page/3", "unformatted_src": "http://jasonmlee.com/wp-content/themes/focused/img/ico_comments.png", "src": "http://jasonmlee.com/wp-content/themes/focused/img/ico_comments.png", "formatted_filename": "ico comments"}, null, {"document_url": "http://jasonmlee.com/archives/category/church-it/page/3", "unformatted_src": "http://jasonmlee.com/wp-content/themes/focused/img/ico_comments.png", "src": "http://jasonmlee.com/wp-content/themes/focused/img/ico_comments.png", "formatted_filename": "ico comments"}, null, {"document_url": "http://jasonmlee.com/archives/category/church-it/page/3", "unformatted_src": "http://jasonmlee.com/wp-content/themes/focused/img/ico_comments.png", "src": "http://jasonmlee.com/wp-content/themes/focused/img/ico_comments.png", "formatted_filename": "ico comments"}, null, {"document_url": "http://jasonmlee.com/archives/category/church-it/page/3", "unformatted_src": "http://jasonmlee.com/wp-content/themes/focused/img/ico_comments.png", "src": "http://jasonmlee.com/wp-content/themes/focused/img/ico_comments.png", "formatted_filename": "ico comments"}, null, {"document_url": "http://jasonmlee.com/archives/category/church-it/page/3", "unformatted_src": "http://static.flickr.com/2455/3739936121_62aca3e347.jpg", "src": "http://static.flickr.com/2455/3739936121_62aca3e347.jpg", "formatted_filename": "aca e", "alt_text": "twitteronFB"}, null, {"document_url": "http://jasonmlee.com/archives/category/church-it/page/3", "unformatted_src": "http://static.flickr.com/3525/3740730008_3c43dbca6c.jpg", "src": "http://static.flickr.com/3525/3740730008_3c43dbca6c.jpg", "formatted_filename": "c dbca c", "alt_text": "twitteronFB2"}, null, {"document_url": "http://jasonmlee.com/archives/category/church-it/page/3", "unformatted_src": "http://static.flickr.com/3529/3740746336_77908b7acd.jpg", "src": "http://static.flickr.com/3529/3740746336_77908b7acd.jpg", "formatted_filename": "b acd", "alt_text": "twitteronFBwp"}, null, {"document_url": "http://jasonmlee.com/archives/category/church-it/page/3", "unformatted_src": "http://jasonmlee.com/wp-content/themes/focused/img/ico_comments.png", "src": "http://jasonmlee.com/wp-content/themes/focused/img/ico_comments.png", "formatted_filename": "ico comments"}, null, {"document_url": "http://jasonmlee.com/archives/category/church-it/page/3", "unformatted_src": "http://static.flickr.com/3441/3708349326_e5a6db5fbe.jpg", "src": "http://static.flickr.com/3441/3708349326_e5a6db5fbe.jpg", "formatted_filename": "e a db fbe", "alt_text": "Midwest-Vmware"}, null, null, {"document_url": "http://jasonmlee.com/archives/category/church-it/page/3", "unformatted_src": "http://jasonmlee.com/wp-content/themes/focused/img/ico_comments.png", "src": "http://jasonmlee.com/wp-content/themes/focused/img/ico_comments.png", "formatted_filename": "ico comments"}, null, {"document_url": "http://jasonmlee.com/archives/category/church-it/page/3", "unformatted_src": "http://jasonmlee.com/wp-content/themes/focused/img/ico_comments.png", "src": "http://jasonmlee.com/wp-content/themes/focused/img/ico_comments.png", "formatted_filename": "ico comments"}, null, {"document_url": "http://jasonmlee.com/archives/category/church-it/page/3", "unformatted_src": "http://static.flickr.com/3590/3553406764_551ea68315_m.jpg", "src": "http://static.flickr.com/3590/3553406764_551ea68315_m.jpg", "formatted_filename": "ea m", "alt_text": "Sonicwall Road Show @ Indy Speedway"}, {"document_url": "http://jasonmlee.com/archives/category/church-it/page/3", "unformatted_src": "http://static.flickr.com/2476/3552598893_614496c3d5_m.jpg", "src": "http://static.flickr.com/2476/3552598893_614496c3d5_m.jpg", "formatted_filename": "c d m", "alt_text": "Sonicwall Road Show @ Indy Speedway"}, {"document_url": "http://jasonmlee.com/archives/category/church-it/page/3", "unformatted_src": "http://static.flickr.com/2462/3552601945_c470bf5b81_m.jpg", "src": "http://static.flickr.com/2462/3552601945_c470bf5b81_m.jpg", "formatted_filename": "c bf b m", "alt_text": "Sonicwall Road Show @ Indy Speedway"}, {"document_url": "http://jasonmlee.com/archives/category/church-it/page/3", "unformatted_src": "http://static.flickr.com/3362/3552602575_102bec5375_m.jpg", "src": "http://static.flickr.com/3362/3552602575_102bec5375_m.jpg", "formatted_filename": "bec m", "alt_text": "Sonicwall Road Show @ Indy Speedway"}, {"document_url": "http://jasonmlee.com/archives/category/church-it/page/3", "unformatted_src": "http://static.flickr.com/3306/3553413532_7ac379f9c8_m.jpg", "src": "http://static.flickr.com/3306/3553413532_7ac379f9c8_m.jpg", "formatted_filename": "ac f c m", "alt_text": "Sonicwall Road Show @ Indy Speedway"}, {"document_url": "http://jasonmlee.com/archives/category/church-it/page/3", "unformatted_src": "http://static.flickr.com/3373/3552613313_8daa25dc0a_m.jpg", "src": "http://static.flickr.com/3373/3552613313_8daa25dc0a_m.jpg", "formatted_filename": "daa dc a m", "alt_text": "Sonicwall Road Show @ Indy Speedway"}, {"document_url": "http://jasonmlee.com/archives/category/church-it/page/3", "unformatted_src": "http://static.flickr.com/3310/3552613911_1f39bd50f0_m.jpg", "src": "http://static.flickr.com/3310/3552613911_1f39bd50f0_m.jpg", "formatted_filename": "f bd f m", "alt_text": "Sonicwall Road Show @ Indy Speedway"}, {"document_url": "http://jasonmlee.com/archives/category/church-it/page/3", "unformatted_src": "http://static.flickr.com/3362/3553423232_65448ae843_m.jpg", "src": "http://static.flickr.com/3362/3553423232_65448ae843_m.jpg", "formatted_filename": "ae m", "alt_text": "Sonicwall Road Show @ Indy Speedway"}, {"document_url": "http://jasonmlee.com/archives/category/church-it/page/3", "unformatted_src": "http://static.flickr.com/2482/3553427546_9267375763_m.jpg", "src": "http://static.flickr.com/2482/3553427546_9267375763_m.jpg", "alt_text": "Sonicwall Road Show @ Indy Speedway"}, {"document_url": "http://jasonmlee.com/archives/category/church-it/page/3", "unformatted_src": "http://static.flickr.com/3327/3553430888_f54582c892_m.jpg", "src": "http://static.flickr.com/3327/3553430888_f54582c892_m.jpg", "formatted_filename": "f c m", "alt_text": "Sonicwall Road Show @ Indy Speedway"}, null]
Browsing posts in: Church IT
Mar 30, 2010    | Avaya IP Office 412 & 5610IP & Sonicwall VPN

Recently several new initiatives have caused us to look into extending our Phone system beyond the physical location of our main campus.  We have an Avaya IP Office 412 with 150+ digital extensions.  As part of the IPO you can do VOIP extensions but we haven’t had a large need to deploy those since our building was already wired for a phone and data network separately (Major PROS & CONS to this but not in this post).

We do have however a couple handsets in locations where we can’t get a pair of copper for the digital phones so we have  a couple VOIP extensions on campus.  Those have worked great, plug the phone into the network, configure the IP and the VLan and your making calls.  So it should be that easy over our VPN right?  Wrong.

After several hours of searching to figure out the issue we learned it was both a IPO Issue as well as a configuration issue in the Sonicwall Firewalls.  Since there was little documentation about this specific combo I have documented it here as well as the nuggets of info we learned along the way.

Hardware Used:
- IPOffice 412
- Avaya 5610sw IP-Handset
- Sonicwall TZ100 at remote location and Sonicwall EClass 5500 on main campus.


- Configure a new IP Extension on the IPO, Enter Only the Extension ID and Base Extension
- Configure the User for the Extension and Program Buttons Etc.
- Create an Incoming call route for the DID
- Connect the 5610 to the local network to make sure the phone is working locally.
- Boot From DCHP, Enter IPO IP address (Phone Server) and Enter Voicemail Server IP (FIle Server)
- After the phone talks to the IPO it updates Firmware updates and the the phone is functional

At this point all was well and we were able to make and receive calls from the IP handset and it was time to take the phone to the remote site.  The remote site is where we started having connectivity issues and the phone wouldn’t boot completely.

-Plug in the phone and choose DHCP and it fails to connect to the server.  Do  a phone reset to clear out all networking gremlins from local network settings: Press Hold then 25327#
-Phone reboots and grabs DHCP address but cannot talk to the TFTP server.
Note: Workstation running the IPO Manager software runs a TFTP server when the application is open but not editing a config file.  If Manager isn’t running IP Phones will not update.

In the troubleshooting we could ping any device on the core network from the VPN except the IPO.  You could ping the Voicemail Server but no response from the IPO.  This was because the IPO requires you to  manually add an IP route for each subnet that is not the subnet of the IPO’s LAN1 Interface.

Some discussion forums noted that you would have to have a license for VPN or Remote IP Handsets but that is not the case.
To Configure the IP Route in the IPO:
- Open the IPO Config Manager and navigate in the tree to: IP Route
- Right Click and Choose New.
- In the new Route Config enter the IP Address of the Remote Router, IP Mask of the Remote Location
- The Gateway IP address should be the LOCAL IP of the Gateway on the Local network
(Don’t enter the Gateway IP that you entered above in the IP Phone)
- Choose the Destination of LAN1
- Save and Merge the Config. (Values shown have been modified and will not work with live config) After this we should have seen the IP Handset boot, talk to the TFTP server and then work…. but that wasn’t the case.  When the phone would boot it would not show up as an extension in the IPO System Status nor would it check in with the TFTP server.  It would however appear to have booted and have a base extension without any call appearances.  Trying to use the phone resulted in a bunch of beeps.

After we were finally ready with the IPO configuration it now appeared something was blocking traffic over the VPN link from the remote location to the main campus.

A call to Sonicwall reveled that in the latest firmware 5.5.x there are default settings enabled that should not be enabled to allow H.323 packets to travel from remote to local sites over VPN.  These settings should be enabled if you are NATing VOIP traffic via the WAN but not enabled if your VOIP traffic is traversing via VPN.
(Leads me to ask the question, can you not have a combination of VOIP Over VPN and VOIP via NAT, but that question can remain unanswered since it doesn’t impact us).
To disable these settings in the Sonicwall Admin interface go to VOIP and the ALL of the following should all be DISABLED on BOTH routers (Local and Remote).
- Enable Consistent NAT
- Enable SIP Transforms
- Enable H.323
It is important to note these setting changes require a reboot of both routers to take effect.

After a reboot of both routers and a reboot of the handset it registers with IPO as an extension and calls can be made and received.

It is important to note, this VOIP extension is not in the same physical location and it is the PBX operators responsibility to notify your dial tone provider of the physical location of that handset for E911 (PS/ALI Compliance).

Oct 15, 2009    | Installing Printer Drivers on 2008 Server

In the process of migrating our servers from 2003 to 2008 and 2008 R2 we have started migrating our print server.  When you bring online the print server we downloaded the 32bit and 64bit drivers for each printer.  While most of our systems are still 32bit the new print server is a 64bit server, hence needing both drivers.

Installing the 64bit drivers was fairly straight forward but allowing 32bit machines to print via this server you also have to add the 32bit drivers as well.  In the past this has been the reverse but the process is the same.. Add and Share the printer then go back in to the Printer Properties and on the Sharing tab add the driver for the other, in our case adding the 32bit drivers for the guests.

When adding the 32bit drivers we ran into some issues.  Since a lot more printer drivers are shipping with windows in 2008 Server the wizard that adds the printer wants to install the OEM driver.  Which we found would print just fine from the server but give us one of two errors when we tried to add the 32bit driver.

The first 32bit driver error: This error is a result from attempting to install a 32bit driver that doesn’t match the 64bit driver that the printer is currently using.  This is most likely caused by installing the printer with the OEM driver for that printer that came from windows update or shipped with Windows Server.  This is an issue because the Printer name in the OEM.inf and the .inf file provided by the vendor for the 32bit driver is somehow formatted differently … ie: ‘PCL_6’ might be ‘PCL6’ or some other slight variation in the printer name in the .inf file.

The two solutions are to:

1. Find the oemsetup.inf file and edit the printer name or change the 64bit driver that the printer is using.
2. The easier of the solutions is to change the 64bit driver from the OEM driver to a downloaded 64bit driver supplied from the vendor.  Once you change the driver or add the manufacture’s driver the install of the x86 driver will not be an issue.

The second 32bit Driver Error: This occurs when the driver doesn’t match the formatting in the 64bit driver as above, but the issue isn’t resolved when using a vendor supplied 64bit driver.  You can attempt to find the differences between the two vendor supplied drivers as mentioned in issue 1 or take the following steps to install the 32bit driver.

1. Login as an Admin on any  client machine running 32-bit OS (it can be W2k3, XP, Vista doesn’t matter)
2. Access the print server PrintserverName and choose Printers and Faxes
3. Select the printer you would like to add the 32-bit driver
4. Go to properties
5. Sharing Tab
6. Additional drivers
7.Check the box for x86 for windows 2000,windows xp and windows 2003
8.click ok
9. The driver will be installed from the included drivers on the 32bit OS or it will prompt you for the location of the driver.
8.Once the driver is installed you can check the server and the X86 box will be enabled.

2008r2 Print Server
Oct 9, 2009    | Installing ACS Facility Scheduler on Remote Desktop Server 2008r2 

Happy Facility Scheduling…

ACS TechnologiesFacility Scheduler
Oct 8, 2009    | Windows 2008R2 Remote Desktop Server Licensing – No more auto discovery

One of our recent projects has been preparing for and testing of the migration of our ACS Server.  We are are working to migrate our ACS Terminal Server from a 2003 Terminal server to a 2008r2 Remote Desktop Server and one of the problems that has caused frustration is the Remote Desktop Server CALs (Client Access Licenses).

We have software assurance so having those CALs wasn’t the issue, SA migrated our 2003 TS CALs to 2008r2 Remote Desktop CALs… The problems started when we brought the new server online and added the Remote Desktop Role it wouldn’t sync up with the license server.

Previously we had setup one of our ‘backup’ domain controllers to be the terminal server license server so all Terminal servers would auto discover our Terminal Server licenses… but not with this new 2008r2 box.  Well alas I found out why… as noted here in the RD Licensing Tech net article:

“Prior to Windows Server 2008 R2, the license server was automatically discovered on the network. This discovery is no longer supported for an RD Session Host server that is running Windows Server 2008 R2.

In Remote Desktop Session Host Configuration in Windows Server 2008 R2, you must specify a license server for the RD Session Host server to use. You can either choose from a list of known license servers or manually enter the name.”

But nowhere in the document does it say how do setup said configuration… Other than you can do so by going to the Remote Desktop Session Host Configuration window.  In the RDSHC window (my abbreviation not Microsoft’s) you can see what license issues you have, and in our case we didn’t have an active license server but we couldn’t figure out how to fix that.

Finally today I came across this article [here] which links to this article [here] that actually gives the step by step instructions.  The gotcha is in the RDSHC window you need to not right click on any of the tree headings but select the top level and then go into the window and right click on the RD license server text for the properties menu to display.

Incase the links go dark here are the step-by-step copied from the TechNet page.

To specify a license server for the RD Session Host server to use

You can also specify a license server for the RD Session Host server to use by applying the Use the specified Remote Desktop license servers Group Policy setting. This Group Policy setting is located in Computer ConfigurationPoliciesAdministrative TemplatesWindows ComponentsRemote Desktop ServicesRemote Desktop Session HostLicensing and can be configured by using either the Local Group Policy Editor or the Group Policy Management Console (GPMC). Note that the Group Policy setting will take precedence over the license servers configured in Remote Desktop Session Host Configuration.

Now.. I have to say I am not complaining that the new navigation is bad.. just the new way things are being displayed in 2008 and 2008r2 one has to get accustomed to… BUT i am complaining that its a little frustrating when you search the net for ‘how to configure type articles’ and you have go to three or four layers deep to find the instructions.

So… i hope this helps you in you quest to configure the Remote Desktop license server… as well as provides me a place to look when I forget next time I bring online a new server.

Remote Desktop Server LicensingTerminal Server 2008r2
Sep 29, 2009    | Clean-up of a Orphaned Active Directory Server 2003R2 Namespace

In my previous post [here] I documented how to enable Access Based Enumeration on a 2003R2 DFS AD Namespace.  Since then several times in testing and now once in production or NameSpace has become orphaned from its NameSpace Server Host and I have had search how to clean-up an orphaned DFS Namspace.

Incase it every happens again… and so that I don’t have to search the web and try to figure out which random terms I used in the Google search I am documenting the process to fix an Orphaned Namespace here… for your use as well as mine.

Since historically just pasting the links ends up burning me… I have included the step by step procedure, that was of course copied from several websites (Note: I am not claiming, any responsibility for, or noting the existence of, original content).

Your Mileage may very and no implied guarantees that the following steps will solve your issue… But the following did fix my issue with an Orphaned Namespace.

These steps have worked to delete the orphaned namespace because of server failure or loss of DFSRoots directory
(or migrating from one SAN to another and thinking that DFS replication will replicate your DFSRoots to a new volume on the new SAN… which by the way DFS replication doesn’t replicate DFSRoots)

The domain-based DFS configuration is stored in the AD database as well as some settings on the DFS Namespace Host server, so every time you launch the DFS management console, it will try to retrieve the DFS information from AD.

There are two nodes in AD which store the information of the DFS Namespace:

Node1. Store the DFS Namespace information which shows under the Namespaces node in DFS management console. CN=DFS-Configuration, CN=System, DC=Domainname, DC=domainsuffix

Node2. Store the DFS Replication group information which shows under the Replication node in DFS management console. CN=DFSR-GlobalSettings, CN= System, DC=Domainname, DC=domainsuffix

ON a DC use ADSIedit.msc to delete the orphaned namespace information domain.tldDFS_Namespace under the node CN=DFS-Configuration.

1. Launch ADSIedit.msc

2. Connect to "Default naming context" (the domain partition)

3. Expand and locate to the following node:
CN=Dfs-Configuration, CN=System, DC=ourdomain, DC=tld

4. Check if the orphaned namespace CN=DFS_Test is under it, if so, you may delete this node CN=DFS_Test

5. Afterwards, please run "repadmin /syncall" if there are multiple domain controllers in the environment

6. Then run "dfsrdiag pollad" on all the DFS member servers to manually make them sync the information from AD database.

Then, you may launch the DFS management console and then right-click on the orphaned namespace, and then select Remove Namespace from Display… if needed.

After these steps you can proceed to re-create your DFS Namespace. When creating the Namespace you may receive the error: “ The Server you specified already hosts a namespace with this name. Please Select Another Namespace or another server to host the namespace.”

If that occurs:

1. Stop the DFS service by tying net stop dfs at a command prompt.

2. Delete the following three registry keys/values:

3. Reboot the server and restart DFS Service.

4. If it still appears, delete the Namespace from the Display.

5. Proceed to recreate a Namespace.

DFS NameSpace
Sep 24, 2009    | ACS (ChMS) and PCO integration … Dead for now

Hey Jason,



ACS TechnologiesPlanning Center Online
Jul 20, 2009    | WordPress to Tweets to a Facebook Fan Page

Recently our Communications and Technology initiative has been working to navigate how we as an organization are using / will use some of the social media tools… we are calling this our social media experiment (an experiment because we don’t know the outcome nor really the steps we’ll use to get to stated outcome).

As part of experiment we were wanted to reuse the content that was already being created by several of our blogs on our wordpress.mu server we host.  These blogs can push to our @NwoodsChurch twitter account and since that is already happening we wanted to consume the twitter content on Facebook as well.

The are are several Facebook applications that claim to work for consuming a twitter feed and posting it on Facebook, but we quickly learned that what works on a normal Facebook profile doesn’t always work for a Facebook Page for an organization.

So after a bit of time of trial and error and ignoring the step by step instructions for each application that just didn’t work, we found a solution (which i am documenting here for your use as well as my recollection should I ever need to recreate the process).

There were two main apps we tried: the “official” Twitter Application and Selective Twitter Status.  Both claim they can push updates into a Fan Page Wall but we found only Selective Twitter to work.

The one major drawback to Selective Twitter is the requirement of using #fb (hash tag) in each tweet.  Since our twitter account is a branded account for our organization and not someone’s personal account all tweets are applicable to go to Facebook… but this application requires the hash tag.

When installing either application if you are already using one of these apps to post to your profile’s wall your not going to have great success trying to push those updates or another twitter accounts updates to your Fan Page’s wall.

Solution, create a company alias (profile) account and make that new account an admin for the page in addition to your profile (or other Admins for your fan page).

1. With the company account login to Facebook and navigate to the editor for your Fan Page.
2. Choose Browse More in the More Applications tool.
3. Search for Twitter and choose Selective Twitter Status
4. Choose the option Add to my Page. 5. In the “Add Selective Twitter Status to your Page” window Select the your Fan Page you are configuring.
– Don’t choose “Application” unless you would like to also install the App for your profile as well.
6. The next time you browse your applications on the Edit page for your Fan Page you will see Selective Twitter.  Choose Edit to configure the Application.
7. On the Edit page you will see 4 tabs select the tab “Your Fan Pages” 8. Select the page you would like to have the tweets display (if you manage only one page you won’t need to choose a selection)
9. Enter your Twitter Username
10. Check has permission and then Save.

Now all tweets for the username entered above will appear as updates to the wall of your Fan Page when they are tagged with #fb.

When using WordPress Plugin “WordTwit” you can add #fb to the message field in the general options so all tweets from the blog are pushed into twitter then consumed by Selective Twitter Status to display on your Fan Page Wall.  Below we configured the faith stimulus stories blog to push all posts to twitter with the hash tag #fb. Jul 10, 2009    | vmware Midwest Users Group 


07:00 – 08:00am – Registration

08:00 – 08:30am – Keynote / Opening Remarks

08:45 – 11:45am – Demonstrations & Presentations

12:00 – 01:00pm – Lunch and Expo

01:00 – 04:00pm – Demonstrations & Presentations

We’ll also be featuring:

The VMUG Team May 26, 2009    | 
ACS Pre-Convention Day (Roundtable & Checkpoint 201)

ACS TechnologiesCheckPointCITRT
May 21, 2009    | Indy Motor Speedway

After a great morning session (see Session 1 and Session 2 for Notes for the details of the info presented in the Road Show Presentation) at the the Sonicwall Road show presentations we headed over to the Indy Motor Speedway for the lunch and afternoon festivities.

Sonicwall provided lunch in one of suites above the track near the start/finish line.  There was an awesome spread of food and great conversation.

After lunch we headed to the Garages and Pit Road during the Firestone Indy Lights Qualifying.  We had a great time checking out the cars of the Indy Cup drivers as well as the Indy Lights.

Here are some photos from the afternoon… go here for all the photos.