"Cheating" on an Exchange 2003 Hardware Upgrade

Hello Everyone,

I "cheated" on an Exchange 2003 hardware upgrade I did 2 weekends ago (Fri-Sat), or that's at least how I feel since this was hands down the fastest and easiest upgrade I've ever done (and it was about 80GB of db's on an older server with direct attached storage). At the end of the weekend, I started to think maybe I should carry around one of these "things" for my clients for upgrades. I'll share what this "thing" was later in the posting. I don't want folks to think I'm pushing products. My role in the project was to insure the replacement of the Exchange Server hardware went smoothly. The client was in production 24/7 and literally the office was staffed 6 days a week. So, I was concerned originally how to insure minimal downtime.

Background on existing hardware & performance
We were upgrading from an Exchange 2003 Server that was installed with 3 hard drives in a RAID 5 hard drive configuration (direct attached storage) for the OS, transaction logs, and Exchange databases. Company had about 60 users and 30 BlackBerrys or so. 1 BES user adds a load similar to 2 Outlook users. So, total company usage was about 120 users. Performance was an issue, so some users were configured for cached mode to "improve" performance. Cached mode should not be required for LANs, unless Outlook end users are receiving "retrieving data from server". Always a bad sign to see unless you have poor network connection. Recommended another DAS server that used RAID 1 for the OS, RAID 1 for transaction logs, and RAID 10 for the Exchange databases.

The Migration for a hardware refresh
So, I checked the OS install (another admin handled that), Exchange install (using the /disasterrecovery switch for setup and service pack 2), Exchange config, and insuring the email & public folder migration completed successful. Only catch was during this server replacement, there was to be no downtime and no use of Exchange clustered services. Hmmm, that's a challenge. Or so one would think.

The Cheat
The client I was working for happened to have a 3rd party product (keeping read to find out) for Exchange that in essence allowed the "cheating". And I mean this in a very good way. It saved us a LOT of time. Meaning, we told the 3rd party product to take over all the existing Exchange services (MAPI, SMTP, OWA, IMAP, etc) and all data for the Outlook, OWA, ActiveSync, & BlackBerry was available to all users. This took a few minutes (3 or 4 minutes) on the switch-over. Meaning the appliance takes some time to take control. Once that was done, everyone was operating off the appliance and end users didn't know this besides restarting Outlook and re-authenticating to OWA (ActiveSync & BES users had a slight delay. BES users could be out of service for up to 15 minutes, but that's a limitation of BES). Once the appliance took over, we copied over the Exchange databases (.edb/.stm's) using robocopy to the new Exchange 2003 Server. We considered upgrading to 2007, but the appliance and all the associated Exchange applications would have had to been upgraded, and it wasn't cost effective (TCO reminder). So, after we started robocopy-ing, we went home.

Day 2 of the Migration & Failback
I'm not going to go into the details, but migrating took a few hours including getting the SSL certs for OWA and handling all that. Once the new hardware was setup with Exchange, it was time to bring back all the new email. As I previously said, the reason to copy over the databases to the new server, was the appliance then doesn't need to copy over all data, and just new email/data. So, this is a huge time saver. Once we copied over the databases and transaction logs, we were able to get the Exchange Server fully operational and enable the failback from the appliance. We then failed back from the appliance to the new Exchange Server. This took a lot longer to check that all data was copied from the appliance to the new Exchange Server. This took 10 hours or so and then everyone had to relaunch Outlook and re-authenticate against the new server.

Appliance Details
The "cheat" was an Exchange high availability appliance from Teneros. Even though this appliance runs 2 operating systems, Linux and Windows, the entire configuration is on 2 web pages. Meaning, the Teneros support team is really what runs this product, not the Exchange admin. As per the web interface, to say the amount of information and configuration is sparse, is putting it lightly. Overall the product worked well and we ran into 2 glitches due to permissions and resetting process of the AD name due to poor documentation. And the migration process took longer than expected since the status of synchronization is not very accurate. Not a big deal, since end users are working during the failover and failback. Overall solution is very impressive, but I have some doubts since I'm not a big fan of trusting secret functionality of a black box type solution. I like to know how applications work and I do have concerns over Exchange updates or patches breaking the Teneros functionality. If you are curious, pricing is around $10k, give or take a few thousands. If you wanted to see the demo, Teneros did present at the NY Exchange User Group meeting back in November of December of 2007 or check out their website.

There are many other software solutions on the market that do this, and so I'll blog about when I work with them. My user group has had demo's and presentation on a # of them, but this was the first real world usage of one.

Let me know your thoughts on this.

-Ben

2 Outlook Add-ons / Improving TCO for Exchange 2007

Hello All,

I feel I owe an apology to my blog readers for the long period between blog posts. I've thought about my blog each time I read about a mail related topic. It's time to share my insight into Exchange and life as a ehlo tech. I've committed myself to post shorter if necessary postings, just to insure folks are kept up to date.

So, 3 things that I've wanted to share for a few months (actually a few years for one tool).

1) I personally use and recommend to all clients the best Outlook searching tool I've found for performance, ease of use, stability, and cost for Outlook 2003 (it's been around for years, and is still rock solid). The tool is called Lookout. A bit of background on the tool. The creators of this amazing tool were hired (software company was bought by Microsoft) and now this functionality has been incorporated into MSN Desktop Search. When I reviewed MDS, I still thought Lookout was better based on my 4 criteria above. It might have changed, but Lookout is pretty close to perfect. For clients, the easiest way to explain Lookout, is to refer to Lookout as Google for Outlook. Very fast and easy to use. You can download the latest version 1.30 before they closed shop to work for Microsoft via this URL. If you have any issues, drop me an email or add a comment and I'll post it since I still have a copy of both latest versions (1.30 & 1.28).

2) There has been a lot of talk about Xobni for it's built-in searching, stats functionality for Outlook usage, and handy access to recent attachment. I love the idea of stats (reporting how much email sent/received, etc), unfortunately, I don't need searching and can't afford to give up so much real estate in Outlook (it adds a side panel similar to the 3 paneled look) for very cool usage "stats" and UI change for attachments. But, let me know in the comments area any feedback on it. I'm curious. I'll probably need to fire up a virtual machine (VM) to take a look at this.

Joys of Lookout and Xobni by Windows IT Pro. (Site was done when I posted this, so I wanted to confirm no login was required for it. Not sure.)
http://windowsitpro.com/article/articleid/99326/new-add-on-changes-the-way-you-work-with-outlook.html

Xobni's Outlook 2003/2007 Tool for Improving UI, Searching, and Stats. Company's website of their FAQ URL .

3) My background in economics and accounting has always played a major role in insuring technology upgrades and improvements are cost effective. So, having said this, I was a bit surprised when I heard the UI had been changed dramatically in Exchange 2007. One feature that increased TCO was the requirement of using 2 UIs to create new users. The single ADUC (AD Users and Computers) is not adequate anymore. So, a vendor realizing the concern for companies created a single UI for AD and Exchange user creation and modifications. They also plan to add a # of very useful features. I think this is a great idea even though it's 3rd party software, especially considering they'll probably add a lot more functionality than MS would.

Product is called Exchange Tasks 2007 and is from U-BSmart. http://www.u-bsmart.com/WWW/ExchangeTasks/ExchangeTasks.html

Demo of Exchange Tasks 2007 by 3rd party (improving TCO for Exchange 2007)
http://www.msexchange.org/articles_tutorials/exchange-server-2007/management-administration/managing-exchange-2007-recipients-active-directory-users-computers-mmc-snap-in.html

Quote from MS Exchange.org about U-BSmart's Exchange 2007 Tasks

Besides what we covered here, the guys behind the Exchange 2007 Tasks utility have plans on adding features such as Export to PST, Export to Mailbox, a fully integrated Active Directory property page for valid recipient objects, the ability to handle and manage Dynamic Distribution Groups, a Hide Group Members task, the ability to handle and manage Resource Mailboxes, improved management of Unified Messaging and more to future versions of the product.

If you use any of the products above, post some comments and let me know your results.

-Ben

Microsoft's Unified Communication Solution

Hello Everyone,

Our April 8th, NY Exchange User Group meeting featured Stephen Chirico, Sr. Tech. Solutions Professional presenting the details beyond the technical deployment needs of Microsoft Unified Communications (aka UC, which is Microsoft's VoIP, IM, video conferencing, and more solution).

1 word for the meeting, Wow. That's how I would sum up our last meeting and "Star Trek visits NYExUG". Also the concept of a "Communicator Call" is definitely forward thinking, see the highlights below for explanations. This meeting is one for the record books. Great topic, great hardware and software demo-ed, and fun.

It really helped in determining what was required for deployment of Microsoft's UC technology. I've listed some highlights from the slides. Stephen did 2 presentations in one (UC Vision & OCS Architecture). So, you'll see 2 PDFs posted online in addition to the sponsor's (Azaleos) presentation. I would recommend you review both in detail if you're interested in UC.

This Presentation and Past Meeting Presentations

http://meetings.nyexug.com

Highlights

Access Edge Proxy - DMZ based server that proxies all traffic. No AD or authentication done on this box unlike an Exchange Edge Server that uses ADAM or a Windows RODC.
PBX Integration Options - 1) PBX supports mediation server w/o gateway (new PBX), 2) use of an Advanced Media Gateway w/existing PBX, or 3) use of an OCS mediation server w/Basic Media Gateway w/existing PBX. Slide 16 explains this. In essence, the Advanced Media Gateway eliminates the needs for a Windows OCS Mediation Server while the other 2 options require that.
Identity and Presence - available, on call, in meeting, etc. Your status available in Office, SharePoint, Live Communicator, etc.
Communicator Call - call's an identity (not a method/location such as mobile, work, home, IM, email, etc).
MOS = Mean Opinion Scores (what a user thinks of the voice quality).
Star Trek and Microsoft's UC - We saw the Star Trekish Round Table in action. It's a 360 degree audio/video conferencing system that mere mortals can afford as opposed to other 360 degree audio/video solutions out there. See Slide 23 for what attendees saw demo-ed. Speaker is shown on video based on triangulation of voice. Very cool.

URLs to assist users with deploying Unified Communications.

Supported gateways:

http://technet.microsoft.com/en-us/library/bb123948(EXCHG.80).aspx

IP PBX and PBX Support

http://technet.microsoft.com/en-us/library/aa996831(EXCHG.80).aspx

Office Communication Server 2007 Partners:

http://www.microsoft.com/uc/partners_hardware.mspx

Microsoft Unified Communications: Phones and Devices Optimized for Microsoft Office Communicator

http://technet.microsoft.com/en-us/bb970310.aspx

Don't miss our next meeting or the following ones... here are the summaries of the upcoming meetings.

May - Microsoft's Behind the Scenes Look at Exchange Hosting Services by Keith Keeler. (fyi: they don't host Exchange). Don't miss this, I expect this to be like our Dogfood lab backup meeting.

RSVP: http://www.clicktoattend.com/invitation.aspx?code=126627

June - Technical details between 2003 & 2007 & Why Companies Upgrade. Speaker Keith McCall.

July - Presentation/Sponsor of AppAssure's Replay for Exchange. (fyi: this is a interesting solution that offers the ability to backup direct to a virtualized file format [vmdk].)

-Ben

They are back from the dead... Exchange's next version will "re-emphasis" Public Folders

Hello Exchange Folks,

Microsoft reversed course and now Exchange's Public Folders will stay a major component in Exchange Server. This is good news for all. I was a bit worried about the loss of such and the removal of the GUI for Public Folders management in Exchange 2007. Microsoft fixed this in SP1, adding such functionality. Now, Microsoft outlined the following at the URL below... (fyi: this is the Exchange team blog, and has a wealth of great information).

http://msexchangeteam.com/archive/2008/03/31/448537.aspx

Scenario
Use Public Folders Currently?
Document Sharing - SharePoint may be better option.
Calendar Sharing - No need to move
Contact Sharing - No need to move
Discussion Forums - No need to move
Distribution Group Archive - No need to move
Custom Applications - SharePoint may be better option
Organizational Forms - No need to move (or look into use of InfoPath)

From my experience, Public Folders are most frequently used at companies for Calendar Sharing, Contact Sharing, and Distribution Group Archive. So, the need to add SharePoint with it's entire line of support applications (e.g. backup agents [that's plural for SQL and SharePoint], anti-virus, server(s), is a great thing for everyone. Exchange is a great product, so obviously removing and then trying to convince existing users to add more products (e.g. SharePoint) and increase TCO (total cost of ownership) to have the same functionality was a bad idea. Thank you Microsoft for seeing this and making sure Public Folders stayed in Exchange Server.

-Ben

My "Enterprise Class" Home Theater Media Center

At the last NY Exchange User Group meeting (March 2008 - StealthBITS Exchange auditing software), the topic of DVRs came up before the meeting. Not sure how, but it did. So, I figured I would share how I built the ultimate DVR for me. And this ain't your run of the mill DVR (e.g. cable company, TiVo, Replay, etc). This IS art to me. See the in construction HTPC photos.

The home theater media center (aka home theater pc, htpc) journey started about one and a half years ago, back in August 2006. A buddy of mine dropped me an email and literally told me he was building a "media center PC" due to a Maximum PC article and wanted to know if I was interested. Little did I know when I responded and told him "Cool. Until they can record HD off cable, I'm not building. I'd love to see yours." Well, I've learned quite a lot since then, and that the holy grail is not HD, but commercial skip and portability (think iPod/streaming/burning).

The journey, and it was one since it took over a year from start to finish involved determining what media center software to run, what hardware, and managing the whole process. So, we quickly determined that the media center software was going to be SnapStream's BeyondTV which is probably the most feature complete (e.g. multiple tuners, commercial skip, multi-format support on record [MPEG2, DIVX, WMV, H.264], no monthly fees [sorry TiVo], burn shows/films to DVDs, download them) and stable solution (runs on Windows and works - sorry MythTV) on the market.

The bigger and more complicated process was selecting what hardware to run this on. We quickly determined this could not be a standard PC (e.g. Dell, HP, laptop, etc) due to noise levels, looks, and functionality. We wanted more than those could provide. So, we quickly realized we must build a custom PC. This was something, I gave up in 2000 due to time constraints and deciding that once multi-processor computers were widely available, I'd be willing to accept an OEM one (fyi: main stream desktop OEMs started providing SMP support back in 2000). But, not on this. This HTPC was going to be in my living room so it was going to be very visible and so it needed to be unique and eye-catching. This was going to be our art work center piece.

So, before we could select the exterior case, we had to figure out which "heart" was going to run this. This was the most critical piece of the entire project, since a motherboard which is not stable or has not been sufficiently tested with hardware for compatibility, can easily derail a stable environment (e.g. lockups, hangs, reboots, etc). So, we spent months reading, discussing, and evaluating which motherboard to go with. In the end we decided on a Asus P5B Deluxe w/o WiFi motherboard. This was going to be the heart of our future HTPC.

Realizing that "just" selecting the motherboard was very difficult and time consuming, I realized we were going to need some help maintaining and managing this entire project. So, we quickly embraced and started using Google Docs (Spreadsheets). It's a great free web based collaboration tool. This made keeping track of parts #'s, comments, URLs, notes, etc a whole lot easier than the original back and forth email and phone calls.

Once we had selected the motherboard, we spent a few months repeating this process for the case (roomy for all the components and works with the motherboard), hard drives (they had to be quiet, fast, and reliable), the video card (had to be passive, no fans on this one), and the CPU heat sink (quiet and efficient). The rest of the components were figured out in a matter of mere weeks. I know, sometimes one of my flaws is I'm too thorough and detail oriented. My buddy didn't help me on that since there were times he was performing calculations on sizing of the CPU heat sink and case.

In the end, I purchased the following hardware components:
1 x Asus P5B Deluxe w/o WiFi, Intel LGA775
1 x Zalman HD160XT HTPC Enclosure with 7" LCD Touchscreen LCD
1 x XFX GeForce 7600GS 256MB DDR2 PCI-E GPU (PV-T73P-UMH4) RoHS, HDTV ready, HDCP Ready, SLI ready, Vista ready
2 x Samsung HD080HJ, 80GB, SATA, 8MB - 8.9ms, 2.5/2.9bel
2 x SAMSUNG SpinPoint T Series HD501LJ 500GB 7200 RPM 16MB SATA 3.0Gb/s Hard Drive
1 x Pioneer DVR-112D IDE, 18x DVD+R, 10x DVD+DL
1 x Processor, Core 2 Duo E6550 2.33GHz, 4MB L2 Cache, 1333MHz FSB
1 x Artic Cooling Freezer 7 Pro for All Pentium D
1 x OCZ OCZ2G8002GK 2GB Kit DDR2-800 PC2-6400 Gold Gamer eXtreme XTC Edition Dual Channel Memory
1 x Antec NeoHE 500W Power Supply
1 x SnapStream Beyond TV PCI Bundle (Digital)
1 x 3ware 8006-2LP SATA RAID Card
1 x Hauppauge PVR-500 for 2 tuner support (Ben only). Card supports 2 inputs. My buddy purchased the PVR-150.
1 x Adesso WKB-4000US, wireless SlimTouch Mini 2.4GHz USB Touchpad Keyboard (Ben only)
1 x APC 1500VA UPS (Ben only)

So, after waiting 2-3 weeks and getting all the equipment, we started the process to unpack and build one HTPC. The reasoning behind building one at a time, was to see what issues we might run into, and to limit the confusion of having duplicate items out. Our first issue was getting the CPU (w/ brand new 1333 FSB support) working on the motherboard (Asus P5B Deluxe). The motherboard had a sticker claiming support of 1333 FSB, but this took a few hours of upgrading the BIOS firmware 2 or 3 versions later and doing this only via a USB memory stick (we didn't have a floppy drive of course - make sure all servers you buy have a floppy drive). The next issue was getting the BIOS configured in the correct RAID configuration. The RAID configuration we wanted to run was two RAID 1 configuration. One RAID 1 for the operating system and one RAID 1 for the media files. Who wants to lose their TV shows/movies or all that configuration? This is a mission critical application like Exchange, hence the need for redundancy. ;-) More on that later. So, we ran into a problem that the motherboard only supported 1 array (this took hours to figure it out since you needed to plug the SATA HDs into different ports on the motherboard to get the RAID array working versus standard SATA ports, the technical writers for the documentation first language is probably not English, and none of the folks we read using this motherboard on the internet were running/writing about 2 arrays difficulties). So, you could not configure 2 separate arrays of RAID 1, but a single RAID 1 array. This would have meant combining our OS and media drives, which was unacceptable. So, we ended up purchasing the 3ware SATA RAID card above. This obviously delayed the HTPC build by another week. Once we had this, we configured all 4 HDs off the RAID card to two separate RAID 1 arrays.

After this, we connected the motherboard up and connected all the cables for the Zalman case. This turned out to be an issue, since when we installed Windows XP Pro w/SP2 (pre-applied), the SD/CF/Memory Stick and those ports took drive letter C and forced XP to install the boot onto drive letter D. So, back to powering off and disconnected those ports and then another re-install. Once this was done we shutdown all the extra services and tweaked it for speed. This HTPC will not get Windows Updates, anti-virus, or any firewall above the XP one. Speed and stability are too important for this. Hence the importance of running a locked down XP for the HTPC.

One would think we are done, but we still had a full day of work ahead of us. I had bought special heat resistant tubing (www.wirecare.com, F6 - self wrapping braided sleeving) for the best cabling job one could do. Cabling is very important when designing an ultra quiet PC. So, we spent about 7 hours dedicated to just cabling the inside of one of the HTPC's. A bit excessive, but it's a master piece in increasing airflow which reduces fan noise. Keep in mind, this is for the living room, so you don't want to hear it at all.

Current Configuration
HTPC is connected via HDMI (audio + video on this single cable) to a Sony Bravia 40" LCD.
Switched from RF Firefly remote for BeyondTV control to an IR Firefly remote (Firefly is the BeyondTV remote). Using an IR remote for the Sony TV.
7" touchscreen LCD on Zalman is used for performance monitoring and photo showing.

Planned Upgrade
Convert both IR remotes (TV & BeyondTV) to a single unified Logitech Harmony One Universal Remote
Connect second cable box connect to second TV tuner card already installed.

Redundancy and Data Protection on the HTPC
One would think two RAID 1 arrays for the operating system and media files would be sufficient, but not in Ben's book. So, I run Symantec Ghost 12 (image the entire OS volume) before any major configuration changes (e.g. software changes, version updates, hardware additions, etc). I run a Ghost Server on my home network which makes it easy for backups and have prepared the boot CD in case of the need for a bare metal restore. And I have already prepared (slip streamed) the Ghost boot CD for the RAID and motherboard drivers for the HTPC.

So, in the end, we spent about 1 1/2 years from brain storming in the beginning to completed product. During this time, about 3 or 4 full days (7-12 hrs) over a period of about a month building the base configuration of the hardware and getting Windows installed. It was weeks longer to get all the software (e.g. BeyondTV, video card, remote software, etc) and hardware configured correctly. As of Fall of 2007, the HTPC has been fully operational, and it's a pleasure to look at it and use it (even my wife uses it, it's that easy). Will I get my money's worth out of subscription fees, no, but sometimes in life folks work on something because they love it. This is what I love.... computers, technology, and increased productivity.

Any questions, drop me an email.

-Ben

My Research into dimmable compact fluorescent lights

Hello All,

I figured I would share this with everyone. I spent a few hours over a few weeks researching compact fluorescent lights (CFLs) that are dimmable (versus standard on/off CFLs). And in the end, I've decided not to purchase or recommend dimmable CFLs yet. The best dimmable solution I found was from TCP though.

There are 2 major issues with the current dimmable CFL technology. First is only mechanical dimmers (e.g. sliders with a switch, or slider which clicks when power is off) are supported. Meaning, electronic (e.g. touchpad's, LEDs, etc) will cause pre-mature* failure since most electronic dimmers always have a small amount of electricity flowing to the bulb. This causes the ballast (analogy is the engine of a car) to cycle on and off rapidly constantly which is very bad for the longevity of ballast. And the mechanical dimmers are fine if you can configure them to cut-off all electricity to the CFL at 20% power. Power of 0-20% is bad for a ballast similar to the way a electronic dimmer is. It causes it to experience that on-off problem as well. So, if you ever see any flickering on a CFL, that's a bad sign. The second issue is some dimmable CFLs need to be used in non-enclosed fixtures due to heat generation. In other words, open lamps, sconces, etc. And the CFLs that can be used in closed fixtures tend to be significantly longer (up to 2" for a 23 watt CF dimmable) than dimmable CFLs & even traditional incandescent light bulbs. Due to these issues, I've decided to re-visit this towards the end of the year. Planned fixes within about a year according to the tech at TCP was addressing the 0-20% issue for mechanical dimmers, low voltage for electronic dimmers even in off position, and reduced size.

* I spoke with a technician (customer service rep was not helpful since I knew more about the products then she did) at one of the major lighting manufacturers (TCP) and he amused me with the term "pre-mature" failure. He explained that dimmers w/o 20% cut-off would cause the ballast to go into that on/off mode when within 0-20% and result in a failure sooner than normal. The ballast would just fail (versus a lamp failure). Which would be a problem especially since the TCP 161 Series is probably going to be discontinued since it has not sold well (it's 25% more costly than the 101 series). So, there will be a point in the future you will not be able to buy either the ballast or the lamp.

Good website for dimmable CF bulbs (they also talk about 3 way, and more)

http://www.edf.org/page.cfm?tagID=633&fixture=0&shape=0&feature1=1&brightness=0&color=0

Considered the following before deciding not to proceed with the replacements.

TCP, 161 Series - enclosed fixtures

2 piece dimmable SpringLamp

Item # 16120L - 20 watt, 6.1"

Replacement Lamp - 36020

$19.30 http://www.lightbulbemporium.com/proddetail.asp?prod=TCP16120L

TCP 101, SpringLamp CF - open fixtures

# 10120 - 20 watt, 5.28"

# 10123 - 23 watt, 5.4"

20-100%

$14.90 - http://www.lightbulbemporium.com/proddetail.asp?prod=TCP10120

-Ben

Attended the NYC Launch Event for Windows Server 2008

Hello All,

I attended the NYC Launch Event for Windows Server 2008 and while it was interesting (RemoteApp & beta look of Hyper-V), the venue really brought down the entire experience due to organization and layout. Some examples were finding different things (e.g. user group areas, hands on demo, etc) and making my way through the vendor areas. Microsoft should realize this is not the venue to use in the future. Also, the NFR software provided was a let-down. The only real piece of software provided that was non-crippled was Vista Ultimate w/SP1 & Visual Studio 2008 (I'm not a dev, so this isn't very useful to me). Nice, but we all received Vista a year ago or so at the Vista Launch. Oops. :-) So, a copy of Windows 2008 Server was expected. I'll be donating the NFR software to the user group at our upcoming meeting. On that note....

Our upcoming meeting for Tue, March 11 is a vendor presented Exchange auditing solution by StealthBITS. Keep track of Exchange Server changes via this solution. They are also sponsoring the meeting. Another major announcement for the meeting is my company donated an Xbox 360 Arcade System (includes 5 games) to be raffle off. So, you don't want to miss this meeting. Visit www.nyexug.com to RSVP to the meeting.

-Ben