7.25.2006

Life Needs a 'Best Practices Analyzer'

Wouldn’t it be nice if you could sit down at your computer, answer a few simple questions, and then be given a set of instructions for fixing/improving your life?  Heck, the only thing better than that would be an ‘undo’ button for those little mistakes we all make.  But alas, we’ll have to wait a few more years for the geniuses at Google to come out with those services (in perpetual beta, I’m sure).

All joking aside, Microsoft has some excellent tools to offer in its growing suite of Best Practices Analyzers (BPAs).  As of today there are 4 separate BPAs:

  • Exchange Server BPA: This is by far the most robust of all Microsoft BPAs.  In fact, other Microsoft product groups are so enamored with the Exchange BPA that they are writing their own rule-sets to tie into the Exchange BPA engine.
  • SQL Server BPA: Unless I’m mistaken (and believe me, you all will let me know if I am) the SQL Server BPA was the first BPA released by Microsoft.  While not as polished or current as the Exchange BPA, the SQL BPA has still come in handy on customer engagements to find config/security issues w/ SQL Server 2000.
  • ISA Server BPA: Microsoft released a new ISA Server BPA build today, which is what prompted me to write this post.  If you’ve ever run the Exchange BPA – this one will look very familiar.  Remember what I said about other product groups using the Exchange BPA engine?  The ISA Server BPA is a perfect example.  Like the SQL and Exchange BPAs, I’ve found this one very helpful in identifying issues, as well as documenting the current state of a customer’s environment before making changes.
  • BizTalk Server 2006 BPA: I’m not a BizTalk guy, so I’ve never needed to use the BizTalk BPA .  However, no post about BPAs would be complete without it… so there you go.

One last thing – if you’re a Microsoft Operations Manager guru, you want to check out the Exchange BPA Management Pack (MP) for MOM 2005.  This MP essentially deploys the Exchange BPA to your Exchange servers and then executes a BPA scan on a pre-defined schedule.  It’s even smart enough to fire MOM alerts if something looks out of the ordinary.

If you have any BPA feedback (good/bad/ugly), please post a comment for the benefit of the community.  And keep your eyes peeled for more BPAs in the near future.

7.24.2006

Exchange '07 In Production - Don't Even Think About It

Exchange 2007 Beta 2 drops today, and I know some of you are very excited. However, please save yourself a lot of time/money and don’t introduce Beta 2 into your production environment. This means no in-place upgrades and no new server installs that join your existing organization.

The only way to test Beta 2 in a ‘live’ environment is to deploy a separate AD Forest and create the necessary trusts and connectors. See the Exchange Server 2003 Release Notes for more information on deploying Exchange 2007 Beta 2 in a separate forest (specifically the section Cross-Forest Connectors: Exchange 2007 to Exchange 2003).

I’ll post more on this topic as soon as I get the code implemented in my test lab. Stay tuned…

7.18.2006

Hmmm... Should I Patch My ATM Machines?

I subscribe to quite a few RSS feeds and mailing lists… but the following thread on Shavlik’s Patch Management list really takes the cake.  Be afraid – be very afraid:

Post Subject: Patch Management for Automated Teller Machines (ATM)

Hi All,

The company that I work with will be rolling out ATM's with WinXP Operating system. These ATM's will be connected to our Backend system thru TCP/IP. I am just wondering how members of this list from the Banking Industry deploy patches to these ATM's.

Do you employ automated patch deployment using WSUS, BigFix, Shavlik, Patchlink etc...? Or do you do manual deployment of patches? Or do you apply patch at all?

Is hardening the OS and limiting the ports open will suffice not to install patches?

I ask this because during deployment of patches there will be downtime which may affect the business. On the other hand if the ATM is infected with a virus due to absence of a patch this will also affect the business.

I hope that you can help me on this. Thanks in advance for your replies.

** Name withheld to protect this guy (and his employer)

…And an Interesting Reply

I'm in the banking field. We have 11 new ATMs that run XP... Our first concern was patching. We were told by the service provider that we were responsible for patching, but that if we "broke" something in the process that they wouldn't fix the ATM. So if a patch causes an incompatibility with the ATM software we would have to fix it ourselves.

What's our approach? We don't have one yet.

** Name withheld

…Finally, a Voice of Reason

For Diebold Automated Teller Machines we test all announced MS patches and post advisories on our Diebold Customer Internet Support (DCIS) site.

Diebold Customer Internet Support (DCIS) is a system designed by Diebold to keep you current on software updates for Microsoft Windows(r) operating systems deployed on your Diebold ATMs.

This valuable system provides:

Custom user profile to view Windows software updates specifically for your deployed Diebold ATMs
Microsoft bulletin link for each Windows software update
Direct link to the Windows software download sites
Downloads Windows software update tracking
Secure customer administrator access and option to add 4 additional customer users to access DCIS

This service is available to all Diebold customers with a current service contract free of charge. You can register at the following site https://patchaccess.diebold.com/DCIS/DCISLogon.asp

Donn Bohn
Diebold Global Software and Services

Jeff’s Thoughts

  • ATM machines shouldn’t run XP (sorry, Microsoft).  Seriously, when XP launched it was all about the ‘eXPerience’.  What kind of ‘eXPerience’ do you need on an ATM?  I get frustrated enough when people decide to use the ATM for all their banking (deposits, stamps, etc.) while I’m just wanting a quick cash fix.  I can’t even imagine waiting in line behind some customer watching streaming video, or synchronizing their iPod. :P
  • Regardless of what OS is being used on said ATMs – your IT security policy must include patch management.  Yes, that includes you too Mr. Linux Zealot.
  • If your vendor isn’t supportive of security best practices, spend your money elsewhere.  Otherwise, your customers will!

 

6.21.2006

Be Careful with WSUS SP1

While most users have been unaffected by the upgrade to WSUS SP1, there are a number of scenarios where problems may occur.  Microsoft just released an updated WSUS SP1 Readme file that details all current known issues.  I’ve seen a couple of these first hand, and helped others with them via the WSUS public newsgroup.  I even had a guy approach me at Tech-Ed with a failed upgrade (he renamed his server after installing WSUS, but before upgrading to SP1).

Even though WSUS SP1 is a ‘true’ service pack (meaning no new features) it’s still wise to look before you leap.  If you find any additional issues with WSUS SP1, please post them to the public newsgroup ‘microsoft.public.windows.server.update_services’ and the product team and MVPs will do our best to help.

6.15.2006

Finally... Cisco VPN Client for Vista Beta 2

After months/years of waiting, Cisco has finally published a Vista-compatible VPN client. The version number is 4.8.01.0410, and the download is approximately 11MB. I haven’t had a chance to install and test this yet since I’m on my way to another Tech-Ed 2006 session. However, I wanted to get the info out to the community as soon as possible. I’ll post some screen shots and a brief review as soon as possible.

Note: You need a valid Cisco CCO login to access the VPN client software. However, there are no specific requirements to be on Cisco’s beta program or anything. The Vista VPN client appears at the top of the list of Windows VPN client downloads.

Update: The new VPN client works like a champ under Vista Beta 2. Check my photo gallery for screen shots of the install and runtime experience.

Update 2: I've had several requests, but unfortunately I can't share this software via e-mail or any other mechanism. Thanks for understanding.

6.13.2006

Ready or not - Here's the June IE Security Update

In a previous blog post I discussed the April IE security update and its ramifications for Siebel and other 3rd party applications.  Well, the 60–day reprieve patch originally offered to mitigate these issues is no longer valid once you install MS06–021 (released today).  I’ve heard rumors that some large Microsoft customers have access to a custom hotfix that extends the 60–day reprieve.  Unfortunately I can’t verify this information – so please contact your PSS TAM or Microsoft Account Rep regarding this patch if you haven’t already.

For what it’s worth, my own company recently updated our Siebel servers to be compatible with the IE ActiveX changes (Siebel update number 7.7.2.6 MR).  There are many other versions of Siebel out there (7.0, 7.5, 7.8, etc.) so your mileage may vary.

Note: While you’re patching MS06–021, be sure to install MS06–023 as well.  It’s important to apply both updates, otherwise IE is still vulnerable.

Happy Patching!

6.12.2006

SMS 2003 R2 Released to Manufacturing

It appears that Systems Management Server 2003 R2 has released to manufacturing.  Continuing the ‘R2’ strategy, SMS 2003 R2 adds functionality on top of an existing product in an evolutionary way (unlike revolutionary upgrades, such as the eventual upgrade from SMS 2003 to System Center Configuration Manager 2007).

Here’s a brief overview of the new features in this release:

  • Inventory Tool for Custom Updates – Allows you to scan for and deploy 3rd party software updates.
  • Scan Tool for Vulnerability Assessment – Uses the MBSA 2.0 engine to scan for common misconfiguration scenarios, such as a blank administrator password.

Find out more about the SMS 2003 R2 update, and register for the free download here.

Badges... We Don't Need No Stinkin Badges

Trying to make sense of ‘who’s who’ at Tech-Ed? Here’s a tip – check their badge color:

  • Blue – Staff (Both Microsoft and External Vendors)
  • Black – Crew (sort of an ‘Uber-Staff’ badge – don’t mess with these people)
  • Green – Attendee
  • Grey – Trade Show Only
  • Orange – Exhibitor
  • Purple – Tech-Ed Sponsor and Exhibitor Booth Staff
  • Red – Media/Analyst
  • Yellow – Speaker