Honolulu TS2 Seminar

As I posted earlier, Honolulu happened to be graced with a TS2 seminar 2 days ago. It’s about time!

Woody Walton was the presenter for the topics that included Managed Services, System Center Essentials, Exchange 2007/Communicator/etc. and Forefront line of products. He did an excellent job of getting the pertinent information out to the attendees.

Shaky hands, pardon me!

He demo’d System Center Essential 2007 for us, and although I have it in my Action Pack, I haven’t had the chance to install it and play with it yet. The demo got me drooling however, so that may be on the list to do once I finish an office move for one of my clients.

The majority of the Forefront presentation was on the Client Security offering. Since I’ve been using it in the home office, I had a good working knowledge of it already, and managed to net me a SBS 2003 neoprene CD holder for answering the only question presented to us. I r smart. He did let us know that the next line of Forefront products being developed are under the code name "Stirling", for those fascinated by code names.

He also gave us a live demo of the automated voice attendant used to access his e-mail, calendar, voicemail, etc. back in Redmond. I had only read about the feature so seeing it in action was pretty impressive. He did run into some problems with it recognizing his voice input since he was using speaker phone, but I got the gist of the usefulness of the offering. He also ran a video of a "Devil wears Prada" spoof demonstrating the power of the complete offering. Great display of the possible uses of the technology, and funny to boot. The Roundtable hardware looked very cool for those that teleconference with multiple people present in 1 room. Availability is very limited for the Roundtable device though.

Also covered were various VOIP phones, including the Catalina USB Phone and a phone with Communicator embedded, which traverses firewalls. He stated he has a co-worker that’s taken the phone overseas, plugged it into the hotel internet, and was then able to access his information back at the office. Very cool technology.

During our 1 break, I made it down to introduce myself and see if he recognized the Blue Monster, which I use on my business card. He hadn’t, so I explained to him the basics and gave him the info to find more on it. He was very intrigued, to say the least and said he’d definitely get more info on the little guy. I also made him aware that "Centro" had been given a name that morning, which he wasn’t aware of at the time. He probably wished I hadn’t told him, as he referred to it by the full name the rest of the seminar instead of "Centro" (luckily, he had covered what he needed of "Centro" before the break, so it wasn’t much). Sorry!

All in all, a great experience start to finish. Some of the attendees (Microsoft Partners) were making snide remarks and chuckles as he covered some of the material, so I can see now where Vlad gets his "riff-raff" from. A minor annoyance, but nothing that detracted from the entire experience.

On the way out, I talked with one of the guys that sat at the table (didn’t get the name as they were packing it up) and he said TS2 had plans to make it out at least twice a year now. Good news considering they hadn’t been out since I became a Partner over a year ago.

Here’s to seeing more events in Hawaii!

I have another post coming soon covering something I found very interesting in the IT market here in Hawaii. Surprised the hell out of me, for sure.

Tags: System Center Essential

Windows – 1, Linux – 0

 

Remember the SBS 2003 Server I was taking over from another consultant that hadn’t been updated in 2+ years?

Yeah, flawless updating through all 5 SBS 2003 SP1 updates, Server 2003 SP2, Exchange SP2 and WSS SP2, as well as the accompanying 39+ patches after all the SP’s were in. Side effect of all the patching? Server now runs way snappier and I look kingly to the business.

The previous consultants departing gift was an update to their Linux firewall that hadn’t been updated in a year. End result was a firewall that ate itself during the upgrade and a forced reinstall of the entire box. The worst part of the botched upgrade was it happened at the beginning of business hours on Friday so the business was without internet until I could get in and pop a router into place until the other consultant could get onsite and reload the Linux box. The previous consultant is a friend of mine, so of course, I had a field day giving him a hard time.

The SBS 2003 update process took ~13 hours start to finish. 7 hours of that was a full backup of the server before I started the process, so ~6 hours for all the service packs and patches to go in. Part of that time was also dedicated to clearing out the Exchange queues of all the spam that had resided there for over a year after they got hit while using Exchange as their mail server. Once I get the chance to show them the beauty of Direct Push, I believe I can get them to swap back over and get them subbed to ExchangeDefender run by the (in)famous Vlad Mazek.

I did have the foresight of knowing that the Server 2003 SP2 caused issues if the NIC drivers were old, so that was the very first thing updated once the Server was taken down for a good cleaning out and put back online. I’m sure you’d like to hear about having to work around quirks that popped up during the updates, but there were absolutely none. Completely flawless start to finish. The previous consultant, being mostly Linux based, was highly impressed with the speed of the machine after updating. Security isn’t the only reason you should patch.

All in all, a win for the Windows Server product and a black-eye for the Linux product in the eyes of the business. Can’t say I’m unhappy about that.

Tags:

SBS 2003 Best Practices Analyzer Tool released

Finally! The long awaited tool for SBS 2003 was released for public consumption today as announced by the Official SBS Blog. I haven’t had a chance to give it a whirl just yet, but soon, very soon.

The Windows SBS Best Practices Analyzer examines the server and collects configuration information from many sources including:

  • Active Directory
  • Windows Management Instrumentation (WMI)
  • Registry 
  • Metabase

After collecting information about server configuration, the Windows SBS Best Practices Analyzer verifies that the information is correct and then presents administrators with a list of issues sorted by severity. The list describes each issue and provides a recommendation or possible solution.

I already know the first victim will be my own box, just to see what effect the various KB fixes I’ve had to apply to fix little issues had on the box. Next in line will be a SBS 2003 box that a previous consultant hasn’t touched in 3 years that I’m getting ready to take over. I don’t expect that one to be too much fun getting it whipped into shape.

So what are you waiting for, head on over and get the goodies and make sure to check out KB 940439 for more information regarding the tool.

Tags:

SBSC – 1, Certified – 0

Yes, I haven’t posted in awhile. Mostly due to the fact that business had picked up right after I swapped themes. All that work on the theme for naught it seemed.

Thanks to the seeming incompetence of a Microsoft Certified Partner, the blog will see it’s first post since the change.

Sad it had to come to this.

I was contacted by my prior employer about his friend’s company that needed some help. No problem, can do. Upon contacting the prospective client, it seemed that the Certified Partner they hired to build/install a new SBS2003 box had left some loose ends on the box. Not little loose ends. Big ones.

No VPN? Check.

No access to Exchange e-mail for certain users? Check.

SSL Certificate errors? Check.

SmartPhones/Blackberries unable to receive mail? Check.

The CP (Certified Partner from here on out) had made numerous trips over the month since installation to try and resolve these issues to no avail. Of course, they charged the client for each failed trip. The client wasn’t happy at all.

I showed up early in the morning after first contact since their business had been pretty much crippled for the past month. First thing I noticed was a SonicWall TZ150 which had VPN capability. Checking the setup, all seemed fine on the firewall side, so I asked the client if their remote users were receiving errors on the SonicWall VPN client. “What’s that?”, she asked. It turns out the CP had failed to instruct the client on the proper usage of the product they recommended to the client. They’re a construction business, not IT support. Unacceptable. I forwarded the VPN port to the SBS server and setup their remote users with remote access since the CP failed to leave information or software for the SonicWall. Remote users login successfully. Cheers begin.

Next on tap, the Exchange users unable to send/receive mail. A quick call to the users revealed they were getting mailbox full errors. It can’t be this easy, can it? Yes, yes it could. A quick change to the 125MB default mailbox size yielded free mail flow once again. Too easy.

The SSL certificate errors, I knew as soon as she told me. Wrong FQDN name on the cert. Quick run of the CEICW and plugging in the correct FQDN resolved the issue.

Roughly 3 hours into the visit and I’ve fixed everything that was crippling their business, that the CP couldn’t fix over the course of a month.

Now for the SmartPhone/Blackberry issues. The CP had arranged for the purchases, so it wasn’t like they didn’t know the client wanted to use the devices for that purpose. I had no prior experience with mobile technologies as none of the other setups I performed needed it, so I explained to them this fact beforehand, but I would delve into the issue and correct it. They had no problems with that all considering I just fixed their main issues.

Fixing it took longer than I had hoped due to the fact I didn’t have a SmartPhone to test with myself. Troubleshooting consisted of making singular changes to the borked configuration and then contacting them to test the changes and report back any errors. This would generally take ~4-6 hours per change since they had a business to run themselves and it wasn’t a vital aspect they needed.

After day 3, during which I had made ~5 changes and gotten the Blackberries to work, the SmartPhones were still experiencing issues related to logging in. It just so happened my fiance had a day off and wanted to go shopping. Since I was waiting on word of the latest change results, I went. It turns out she wanted to go shopping for a new phone. Hmmmm. When all was said and done, she bought me a T-Mobile Dash (Windows Mobile 6 SmartPhone) as a late birthday present after watching me work on this issue for the past few days.

Things will go much faster now.

2 hours after getting the phone home, I had Direct Push working on their server after making several more changes to their Exchange configuration, since I could test immediately. The resulting e-mail I sent from my new phone to theirs arrived late at night on their phone and was responded to with great joy. I love it.

In all fairness to the CP, they were probably sending out newbie technicians to fix seemingly easy problems. My advice, hire better newbie technicians or send out the big guns. Actually, don’t.

Now, the client is ready to jump into Terminal Services. Too easy. Thanks for the new client.

SBSC – 1, CP – 0

Tags:

Clicky Web Analytics