THE OFFICIAL BLOG OF THE SBS "DIVA" : Needed Patches/Tweaks

MPAN member having issues getting re-enrolled?

bradley — Sat, 20 Oct 2007 05:02:00 GMT

If you are a MPAN member having issues with your Action Pack re-enrollment. The best thing for folks to do is call 877-283-1925 and talk to a live person. They will walk them through steps to get MPAN members back on track to order Action Pack.

Submit an online request to obtain a Microsoft hotfix:

bradley — Wed, 04 Apr 2007 19:50:00 GMT

Submit an online request to obtain a Microsoft hotfix:
http://support.microsoft.com/?kbid=935195

Contact Us: Hotfix Request Web Submission Form:
https://support.microsoft.com/common/survey.aspx?scid=sw;en;1399&showpage=1&WS=hotfix

Need a hotfix? Don't want to call in?

Try those links! (and not sure if it's just those OS's mentioned but I'm trying with just entering the KB and seeing what I get!)

Cool!

So what's a nice blog like you ... doing linked off a blog like this?

bradley — Fri, 02 Feb 2007 07:49:00 GMT

That's probably what you are asking about the "HiED West Technology Briefings, News & Training" blog that I just stuck into a new link category on the left hand side called "Blogs to watch". Now while this is a blog about Higher Education West Region...they have some really good posts lately... stick it in your RSS feed and follow along!

http://blogs.technet.com/hied_west_blog/archive/2007/02/01/dst-2007-update-outlook-time-zone-data-update-tool-released-february-1-2007.aspx

That one's a keeper about Daylight savings and the patches needed

Tax Tools program and IE 7

bradley — Sat, 28 Oct 2006 00:41:00 GMT

TO: ALL CFS USERS
FROM: CFS CUSTOMER SERVICE
DATE: OCTOBER 27, 2006
RE: MANDATORY UPDATE

IMPORTANT: ALL CFS USERS MUST INSTALL THIS UPDATE BEFORE INSTALLING THE NEW INTERNET EXPLORER 7

We have posted an update for most CFS programs. It allows CFS software to communicate with Internet Explorer 7 (IE7), which is in the process of being released by Microsoft. Soon, Windows will automatically download and install IE7.

If you do not install this update, you may get an error message when loading our programs, and you will be prohibited from automatically installing future updates.

If you have any of the following programs, you must install this update.

Program	Download Option 1 (Recommended) Automatically Download Update	Download Option 2 Manually Download Update
TaxTools 2006	Click here for instructions	Click here to download file
Payroll System 2006 (941/940, W2/1099, Payroll Corrector)	Click here for instructions	Click here to download file
Small Business Tools 2006	Click here for instructions	Click here to download file
Financial Tools 2006	Click here for instructions	Click here to download file
Tax Corresponder 2006	Click here for instructions	Click here to download file
W4 Calculator 2006	Click here for instructions	Click here to download file
Schedule D Tools 2006	Click here for instructions	Click here to download file
NY Sales Tax Preparer 2006	Click here for instructions	Click here to download file
CA Sales Tax Preparer 2006	Click here for instructions	Click here to download file
CA 571 Preparer 2006	Click here for instructions	Click here to download file
MD Personal Property 2006	Click here for instructions	Click here to download file

There is a third way to download updates if you have a high-speed Internet connection.

Download Option 3: UPDATE AUTOMATICALLY ON STARTUP
If you have a permanent, high-speed Internet connection--such as DSL, ISDN or cable--most CFS programs can be configured

How to build a box.... with Chris Rue's expert fixing

bradley — Tue, 08 Aug 2006 06:00:00 GMT

Okay here's version 2 of the "How to Build a SBS 2003 server" with expert clarification and fixing from Chris Rue....

I think it's much clearer than my version because it's flipped and checking what version you have the other way...

Chris Rue's improved version of "How to Build a SBS 2003 Server patching chart"

How to build a box

bradley — Tue, 08 Aug 2006 04:25:00 GMT

I put together a real rough ..how do you build/patch a box from one version of SBS to another. I'll be fleshing out this more in the coming weeks... but until now... check out

HOW TO BUILD A BOX

With links out to the side for resources or patching links.... someone asked me today if they could MU/WSUS from RTM to SP1 and you can't. Also folks are getting a bit confused thinking that the R2 cdroms are integrated.. remember they are on top when you build the base of SBS 2003 sp1.

So we're not going to be getting on the network with that box...

bradley — Wed, 31 May 2006 19:05:00 GMT

So I'm rebuilding an OEM machine... and feeding it the drivers because the OS does not see the NIC card from the Dell site ... and I realize that not only can't this machine not see the nic cards.. the C: drive isn't a C: drive.

Now THAT is annoying, isn't it? That whenever there's a zip drive it picks that up as a C: drive instead of the read drive.. so now my C.. is my E... arrrrggghhh.. I'll have to fix that.. as the Dell drivers keep trying to install to a C drive that isn't there. Normally I unplug the zip but I forgot to do that this time....

hmmm won't even load up the nic drivers...okay back to the Dell website to see what other drivers are available.

Buffer Overrun error may occur when CRM 3.0 is installed on Microsoft Small Business Server 2003

bradley — Tue, 30 May 2006 19:30:00 GMT

915343 - Buffer Overrun error may occur when CRM 3.0 is installed on Microsoft Small Business Server 2003

Okay so the hotfix I was attempting to call for last night... I got today... and while I'm not running CRM 3.0.. I wanted to see if the patch was available via the "call PSS/CSS, hit the button for hotfixes and get it sent to you for free" and sure 'nuff.... it was.

So if you are a CRM'er running on SBS and you've seen this issue about a "buffer overrun" on your system, know that this is not a 'regression tested patch' and ensure you have a backup and try it in a test network first..but you can call the ITPro support number and get this hotfix...I call US (800) 936-4900 but call whatever number is appropriate for your area. Furthermore due to the "after hours IT Pro" support having a business after hours 24/7 world wide feature now, you "should" be able to get hotfixes 24/7.. I say "Should" because Mariette is supposed to be able but none of us could find the appropriate number for her to call in the Netherlands that would give her the hotfix....

..and we spotted this hotfix by an answer posted to Kathy's question about BufferOverrun in the Managed Partner newsgroups... SEE why we say you need to be a MS Partner if you are selling SBS boxes?

ISA 2004 SP2 public hotfix 916106

bradley — Fri, 28 Apr 2006 07:33:00 GMT

I blogged about this earlier when it was a hotfix and we're seeing it now when it's a "public patch"

http://support.microsoft.com/?kbid=916106

If you have ISA 2004 sp2 and you then get offered that patch.. some machines kick a reboot.. some don't. And when they don't, because the patch is not automagically restarting the services they leave the IIS sites not running and thus your email is not working and companyweb is not functional until you restart the services.

After you get this patch applied.. check the services.... or reboot...

I'm still not sure why some boxes are rebooting and some are not.

Dear Greg (and anyone else)

bradley — Mon, 27 Feb 2006 18:58:00 GMT

Dear Greg:

When I asked you and others to look at the SBS R2 webcast I wanted you to look at it from a "new client" viewpoint. When you say that "how can I sell this to my existing clients?" you are right. This will be a hard sell.

But I think all of the "Gregs" out there are missing the point on this release. Regardless of how we feel about it, listen to the webcast again... hear how the emphasis is on new clients?

Can you answer one more thing for me? Why is it that even to this day there is evidence that we have SBS 2003 boxes that don't have Service pack 1 on them?

I know I'm in the serious minority of how much a PatchAholic wacko I am, but you know what.... I shouldn't be.

That's what R2 is all about. And yeah while some of the more talented in SBSland can roll out WSUS in nothing flat, it's pretty obvious to me that many of you guys and gals out here have not installed it, have not even tried it, and are not using it.

Now granted WSUS can't put SBS 2003 sp1 on that box, but if you haven't begun the process of getting a Patching process in place, then when that new client of yours shows up on that doorstep with a R2 box in tow, and you'll look at that WSUS going.... okay what the heck is this patching thing about anyway....needless to say you'll be starting off on the wrong foot.

Yeah, the first thing you should understand about me is that I will throw on a patch or a hotfix to a server or workstation without blinking an eye, but it will take me longer to roll out a Service Pack. I'll wait, and I'll see, and I'll test on a test box, but I roll it out.

Right now the word on ISA 2004 sp2 is that we're seeing some issues with websites and downloads, and yeah if you must have it installed, the best advice is to delete the cache, install SP2, then disable the compression filter. (Obviously not a biggie for us down here anyway). Due to the time of the year at my office.... I have not installed it. But the best advice I can give on patching in general is ....

Get a test program in place
Learn how to google for issues (hint put the KB article in the Google Groups box and chances are you'll hit someone talking about an issue)
Install it on your machine...and then let it bake before rolling it out to others. Yes, Microsoft tests these...but the cannot test them with every line of business stuff you have.
You don't have to be first. I still remember the day that Windows 2003 sp1 came out and someone downloaded it and installed it during the lunch hour. I mean come on....

Service packs are a big change management.

So yeah Greg... don't look at this as something you'll necessarily need to get for your existing clients unless they are looking to get the SQL 2005. Instead I'd be looking at those clients who could benefit from a member server running Windows 2003 R2 for your existing client base. Or looking to upgrade folks from Standard to Premium (which of course is ONLY one cdrom, you do NOT need to start over and install the entire Premium cdrom set, all you need is the ONE premium disk and you install the SQL...like for example for CRM 3.0)

But don't blow this release completely off. Because for the PatchAholic that I am, this is a milestone for us. Be proud that SBS showcases how far patching has come in Microsoft. Realize how this means a lot of work has gone on under the hood.

Issues with connectivity?

bradley — Thu, 23 Feb 2006 20:20:00 GMT

Installing security update MS05-019 or Windows Server 2003 Service Pack 1 may cause network connectivity between clients and servers to fail
http://support.microsoft.com/default.aspx?scid=kb;en-us;898060

Lately some folks have been complaining about RWW 'dropping' out after someone sitting there and using it and there's two things you might want to check....first I've noticed sometimes with folks on Linksys routers getting that 'drop' issue...and secondly you might try that patch to see if that helps.

Download details: Update for Windows Server 2003 (KB898060):
http://www.microsoft.com/downloads/details.aspx?FamilyId=A0245532-0ACE-4B85-85BF-758E936173DF&displaylang=en

And yes that's a Windows 2003 sp1 patch (which means it's still valid for us under the hood) and I've applied that here at the office and at home with no problems.

P.S. I'm lifting up Alun's comment into the main post as another thing you might want to look at..

I debugged someone through a similar issue with a Linksys router - it was clear that small packets were getting through, but large packets (1500 bytes) were being dropped by something, and we ruled out MS05-019 fairly early on. It did seem to be specifically the router that was at issue.

We 'solved' it by specifically setting the MTU to 1450 bytes.

BCM and SBA service pack 2

bradley — Sat, 21 Jan 2006 02:44:00 GMT

Service pack 2

Service Pack 2 for Business Contact Manager Update and Small Business Accounting provides the latest updates to Microsoft® Office Small Business Accounting 2006 and Microsoft® Office Outlook® 2003 with Business Contact Manager Update. This Service Pack contains significant usability enhancements and stability improvements.

Kerberos errors revisited

bradley — Wed, 28 Dec 2005 06:03:00 GMT

So remember my Kerberos Errors post the other day? J.P. posted back with the final resolution to his last one remaining Kerberos errors that he was getting.....and sure 'nuff... HP printer toolbox software... I'm blogging his resolution here for the next person who ends up with Kerberos errors all over their log files and time sync isn't the resolution....

Well, plugging right along, I eliminated the other three remaining kerberos
errors on login. They were caused by (you guessed it), HP monitoring
"Toolbox" software.

With some trial and error on the client end with MSConfig I was able to
narrow it down to the HP Toolbox printer monitoring software. In researching
the Toolbox software and it's known issues, I came across an article
describing the exact setup. SBS Premium, XP SP2 workstations, kerberos
errors with firewall on, none with it off, HP printer on a workstation and
shared.

The fix was to go to a command prompt, navigate to c:\windows\system32 (or
the default system32 folder for your OS) and then enter the following command
"hpbpro.exe -regserver" (without the quotes) and if you still have the errors
follow the same process except use the command "hpbpro.exe -service"

No to all -- Seven times

bradley — Sat, 05 Nov 2005 01:26:00 GMT

Well I finally did it tonight. Patched the real baby at the office with Exchange 2003 sp2.

I manually shut off the Trend Exchange antivirus

I shut off the server antivirus

I manually shut down the SMTPservice ...just in case....

And I hit the 'No to all” issue. You know..the No issue. When we SBS 2003 sp1 premium folks [that translates to having SQL 2000 sp4 on the box] install Exchange 2003 sp2 on our systems we get prompted along the way to replace existing files with older ones. And...well... given that Exchange 2003 sp2 is 'supposed' to be the new kid on the block for a moment you scratch your head going... huh?

For the record you say “No to all” a total of Seven times.....

For whatever reason the versions of the files that Exchange 2003 sp2 wants to put on are 9.107.8320.4 whereas the ones already ON my box are 9.107.8320.9

..bottom line folks...in the Patching world... Exchange needs to catch up with the other server platforms when it comes to patching. I really have no idea if the difference between a .4 or a .9 is of consequence... I'll keep you posted on that one.

I like my Windows Server patches. They install so much nicer. Time to check the phone for syncing..and it looks like everything is working quite nicely!

P.S. if you replaced them.. merely rerun the SQL 2000 sp4 installation from your SBS 2003 sp1 premium disk 3

Top support issues from the Partner newsgroups

bradley — Fri, 14 Oct 2005 02:32:00 GMT

Why you want...you NEED to be a Microsoft Partner...because you get resources like this...

TOP SUPPORT ISSUES

-----------------------------------------------------------

Issue 1:

********

Memory leak issues

Problem Symptom 1:

==================

Memory leak & Allocated memory alert

Suggestion:

Some of them are caused by the SQL memory processing mechanism:

http://msmvps.com/bradley/archive/2005/03/07/37868.aspx.

Memory leak caused by the Lsass.exe process:

821008 Windows Server 2003-Based Computer Becomes Slow and Unresponsive

After - http://support.microsoft.com/?id=821008

829993 Memory Leak Occurs in the Lsass.exe Process on a Windows Server -

http://support.microsoft.com/?id=829993

Other memory leak issues is most likely related to VSS (while be used with some 3rd party backup program, such as Veritas, Ultrabac.) What you expect to see in this kind of issue may be any of the following:

Poor and gradually declining system performance

Out-of-memory errors

VSS errors

If you do see the symptom listed above, I would suggest the following hotfixes be installed on the server, or you may want to apply SBS 2003 SP1 directly.

826751 Backup Program Causes Gradually Declining Performance -

http://support.microsoft.com/?id=826751

838864 A backup or a restore operation of Exchange 2003 storage groups

fails - http://support.microsoft.com/?id=838864

867667 The Beremote.exe process uses up to 100 percent of CPU resources -

http://support.microsoft.com/?id=867667

870973 A memory leak occurs in an application using the Volume Shadow Copy -

http://support.microsoft.com/?id=870973

831112 You cannot import a transportable shadow volume in Windows Server 2003

http://support.microsoft.com/?id=831112

833167 A Volume Shadow Copy Service (VSS) update package is available for -

http://support.microsoft.com/?id=833167

After the SBS 2003 SP1 installation, you still receive the memory allocation alert to indicate that store.exe is using an abnormal amount of memory.

This is actually the same issue described in the following KB: '867628 Monitoring programs report that the Store.exe process consumes -

http://support.microsoft.com/?kbid=867628

To completely fix this:

You can re-run the Configure Monitoring Wizard and it will also disable the store alert. Note that you need to choose 'Reinstall Monitoring features'

when running MCW (Monitoring Configuration wizard or disable the alert manually from the Health Monitoring page.

Issue 2:

========

Slow Shutdown issues on Exchange 2003 (installed on a Windows 2003 DC)

Problem Symptom

===============

When you shut down a Microsoft Windows Small Business Server 2003-based computer, the shutdown process takes longer than expected to finish.

Cause

=====

The problem of slow shutdowns is not actually a SBS specific one. It exists for every server which is both a domain controller and an Exchange server.

When you shut down the Windows Small Business Server 2003-based computer, the Active Directory directory service shuts down at the same time that the

Microsoft Exchange Server services shut down. Therefore, Active Directory becomes unavailable when the Exchange Server services shut down. For

example, this problem causes Exchange Directory Service Access (DSAccess) searches to time out and to return errors. Additionally, the DSAccess

searches sleep and then restart several times. Therefore, the Exchange Server services that wait for the DSAccess searches to finish are delayed.

Resolution

==========

Apply SBS 2003 SP1, as mentioned in the KB article

http://support.microsoft.com/?kbid=887539

or If you don't want to apply SBS 2003 SP1 currently, please get the Hotfix

887539 from CSS.

or Manually workaround this issue by either modifying the

WaitToKillServiceTimeout value

(http://support.microsoft.com/default.aspx?scid=kb;en-us;555025)

or scripting the Shutdown sequence

(http://www.msexchange.org/tutorials/Accelerating_Exchange_Shut_Down.html).

Issue #3 - Hot Issue

====================

S2S PPTP VPN gets disconnected after SBS 2003 SP1 Premium (ISA 2004)

installation

Problem Symptom

===============

Site to Site (S2S) PPTP VPN connection gets disconnected after the SBS 2003 SP1 (ISA 2004) installation. The scenarios we've seen so far are listed

below:

Linux VPN server <à SBS 2003

Linksys VPN ß> SBS 2003

Netopia VPN ß> SBS 2003

Watchguard ß> SBS 2003

Analysis

========

The key things to zero in on are the GRE Call IDs (that control data flow) and whether the PPTP Echo Reques/Reply process over TCP port 1723 is working

(which keeps the connections connected). We encourage you to get a Netmon trace from the VPN server to try and figure out if there is GRE Call-ID

mapping going on upstream from the ISA server. It will turns out that the remote device is not following the RFC 2647. So we fail because ISA's

pptpfltr.dll is being strict with RFC.

Solution

========

1) Don't use the NAT module in the router. Get a .252 block address from their ISP that allows then to set up routing rather than use NAT. (This

should give you one IP address for the router, one for the ISA server and a network and broadcast address)

2) Contact the router vendor and get an updated firmware that fixes the NAT problem. (That is if one exist) You can always try the latest firmware.

3) Buy another router that does not have this NAT/PPTP compliance issue

Appendix 1 - Why Windows XP doesn't have the same issue

You may find that you can make solid PPTP connections through the router by placing the client PC (XP SP2) on the network that is connected to the

EXTERNAL ISA interface and the INTERNAL router interface - effectively the DMZ for this network. It's because the PPTP module in the Windows RAS client

has a different design, it does not check the Call ID in the packet. It just accepts it.

Appendix 2 - RFC 2637

RFC 2637 - http://www.faqs.org/rfcs/rfc2637.html:

Appendix 3 - If it's a ISA 2000 box, not a ISA 2004

Make sure the you have ISA SP2 applied which contains the hotfix 831531. In addition, according to the hotfix 'FIX: Outbound PPTP connections may

disconnect after 60 seconds if the ISA Firewall Service is running - http://support.microsoft.com/?id=831531', the problem should be fixed without changing the binding order.

If remote is not an ISA server, change the local value InactivityIdleSeconds to 30 seconds to ensure that the server's timer always expires first. (See

Q262990 for instructions): '262990 RRAS VPN Dial-On-Demand Failover Mechanism - http://support.microsoft.com/?id=262990 '.

840654 Your VPN connection is disconnected after several minutes in Windows XP - http://support.microsoft.com/?id=840654

UPS attached to a ProLiant ML150 and your CPU at 100%?

bradley — Mon, 10 Oct 2005 02:03:00 GMT

There a fix for ya

When an HP T700 or HP XR5500 Uninterruptible Power Supply (UPS) is connected to a ProLiant ML150 G2 server through the serial port using a serial cable, the CPU utilization will remain constant at 100 percent. As soon as the serial cable is removed, the CPU utilization immediately returns to normal levels.

Any ProLiant ML150 G2 server running System ROM Version 1.10 (or earlier) and is connected to a HP T700 or HP XR5500 Uninterruptible Power Supply (UPS) via a serial cable.

To prevent the processor utilization from immediately increasing to 100 percent when a UPS is connected to the serial port, upgrade the ProLiant ML150 G2 System ROM using the Single Point Solution Systems ROMPaq Firmware Upgrade Diskette for HP ProLiant ML150 G2 Servers, available at the following URL:

ftp://ftp.compaq.com/pub/softpaq/sp31001-31500/SP31081.TXT

ftp://ftp.compaq.com/pub/softpaq/sp31001-31500/SP31081.EXE

Thanks Jaime for the follow up!

SBA on SBS [the unsupported instructions to get the datafile ON the network]

bradley — Mon, 29 Aug 2005 23:56:00 GMT

So you build a Small Business Accounting Program and you call it a multi user version...and then you don't install it on SBS in such a way so that the msde datafile is 'on' the server, but rather on a desktop inside the office.

Okay ....lemme get this straight... why does EVERYONE see the word 'multi-user' and translate that to “Peer to Peer” except for me? I WANT that datafile ON the Server. I mean that's WHY I have a network you know so that data can be better protected over there. I don't see peer to peer networks as being of value to me. I WANT a server. I WANT the active directory goo. I WANT the control. So what's a gal to do?

She gets advice from her fellow geeks who hack up the way to get it on the server.

So here is the unofficial, unsupported instructions to get SBA on SBS 2003.

“What I have done is install Small Business Accounting on SBS2003. This results in an MSDE instance called MICROSOFTSMLBIZ being installed there. The instance can host the BCM database as well. You would install BCM on your workstation, set it up for sharing and add users. Then shut down Outlook and SQL on your workstation, copy the BCM database and log file to the server and use SQL Enterprise Manager to attach them there. Restart SQL and Outlook on the workstation. You should now be able to redirect Outlook to the copy of the database on the server.

Unfortunately this method is not supported by Microsoft as I mentioned in the meeting. In fact, if you have SBS Premium you can upgrade the MSDE instance to full SQL to remove any database size or number of user limitations.”

Remind me to email Dennis Clark and give him feedback to take back that they DO start supporting SBA on SBS. I mean... it just makes sense, you know?

Messing up that morning email with a few extra printers via a TS session

bradley — Sat, 27 Aug 2005 17:53:00 GMT

Every morning when you view the 6 a.m. view of the network, you get that annoying “error” message that isn't an error message at all... it's just YOU logging into the server via Remote desktop and the system will want to 'add printers”... well so... how do you fix this annoyance?

Event Type: Error
Event Source: TermServDevices
Event Category: None
Event ID: 1111
Date:  8/27/2005
Time:  12:56:08 PM
User:  N/A
Description:
Driver Amyuni PDF Converter 2.07 required for printer Intuit Internal Printer is unknown. Contact the administrator to install the driver before you log in again.

Easy. When you launch the RDP connection, before you enter the password and get to that remote console, click on options on the right side to expand down the view of your options, then into “Local Resources“ tab and untick Printers.

Fixed.

While in there... see the other options you have.

So where's the change IP address wizard?

bradley — Sat, 27 Aug 2005 05:47:00 GMT

There are times I think we need wizards to tell us there are wizards. You know something that would say “You know..before you do that... you do realize we have a wizard for that?”

The change IP address wizard is like that. On server management is buried under the Email and Internet section

Change Server IP Address Enables you to change the IP address of the server's local network adapter and update all network services on the server to use this new address.

But yet this simple wizard makes it easy to change the IP address of the server and not forget a step.

Service pack - revisits

bradley — Fri, 26 Aug 2005 12:25:00 GMT

First off, a REMINDER that if you happen to load up Windows 2003 SP1, and you are a SBSer, you aren't done yet... right in that “Windows 2003 SP1“ page it says:

Important

If you are running Windows Small Business Server 2003, please install using the instructions at, Windows Small Business Server 2003 Service Pack 1 web page.

Taken from this page at the bottom.

Remember we aren't 'just' Windows 2003 sp1. We're a Dagwood sandwich and we have parts.

Next if you are a Dell customer..remember to check the Dell Support site regularly (put in Service Tag then go to downloads and all downloads available for their server will be there). There is a recent Service Pack release which fixes a few problems is what I've heard. I'll have to go check it out myself. As an HP customer I get weekly emails of new fixes and releases [that's really cool, I like that] Dell has the notification email too!