Print this page

 MESA3

About MESA3

MESA3 is a small but well-known facilities support firm with a marquee list of high tech clients headquartered in San Jose, California.

As frequently happens, we are brought in after other consultants have already failed. Such was the case with this client. We were faced with a disaster that affected the company for an extended period of time. As a Microsoft Partner, we have a safety net in the form of Microsoft technical support services. As our standard ways of recovery were not advancing us forward, we contacted Microsoft and asked for additional assistance. After quite a few hours with Microsoft, we identified an issue in a 3rd-party software package used for backup that prevented us from bringing the company online very rapidly, as we typically do. Unfortunately, this meant that we were dealing with an absolute worst case scenario.

Let’s fast forward a little to the point where the system was back online. We then continued our case with Microsoft and managed to recover the company’s e-mail system fully intact. A little bit of extra magic, and the missing e-mail was also reintegrated and synchronized with the server.

Using Small Business Server 2003 to its maximum potential

  • Microsoft Small Business Server 2003
  • Microsoft Exchange Server 2003 and public folders are used for collaboration and calendaring
  • Custom line of business application was restored and runs flawlessly
  • Microsoft NTFS permissions are set properly to comply with ISO 9001 requirements
  • Remote synchronization with Microsoft Exchange 2003 Server works
  • Remote Web Workplace works as well
  • VPN is in use due to custom line of business application requirements
  • Roaming profiles enable users to use any workstation in the office
  • Backups run and e-mail us the reports

We have yet to implement

  • Network faxing
  • Network scanning to the server - currently enabled to workstations
  • Customized Sharepoint site

The best part

  • We researched some rather obscure questions about Windows Mobile on the Samsung i730 and delivered accurate results very quickly.
  • We were able to configure another never before plugged in i730 that was located over a hundred miles away fully remotely while the user simply watched in disbelief, in about 27 minutes.

We were able to recover the system from a complete state of emergency to a usable server in less than a few days. Discarding initial troubleshooting that led us astray, 12 hours was the actual recovery time.