Category Archives: Sbs2011

SBS 2011 monitoring email not sending

From the mailbag tonight comes the question “have you come across a system that has randomly stopped emailing the nightly network reports? Mine has stopped and I can’t work out why, they are still set up correctly and I can manually generate them”

And I’ve seen this before but I always have a hard time finding this old post, so I’m going to reblog it for future bingling.

Bing/Google terms:

sbs diva sbs 2011 monitoring email not sending

For monitoring email cannot be sent issue.
Most of this issue is caused by incorrect configuration on Exchange receive connectors. You can all Exchange Receive connectors and run fix my network wizard to fix SBS specific ones. However, for Default <servername> connector, FNCW cannot create it, you need to manually create by steps in the article below:

Fix My Network wizard (FNCW) Fails to Fix the Exchange SMTP Connectors in SBS 2008

If this doesn’t work, we could investigate this issue by reviewing the following log “C:\Program Files\Windows Small Business Server\Logs\MonitoringServiceLogs” folder, there will be a file called DataServiceComponents.log, this file usually is very huge, this is because it contains almost every detailed error file in it. However, it is incredibly useful, you will be able to find the exact error. Here is an example which shows why reporting email failed to send.

[364] 091128.120849.1072: AdminTME: Status: TaskId = TaskGenerateMonitoringReport, RootTaskId = TaskGenerateAndEmailReport, Success: True, Warning: False, Continue: True, Message:

—<< This line shows the TaskGenerateAndEmailReport, email generating and sending message can be found here, you need to search this key word to locate the root cause.

[364] 091128.120850.4192: Exception:
An exception of type ‘Type: System.Net.Mail.SmtpException, System, Version=, Culture=neutral, PublicKeyToken=b77a5c561934e089’ has occurred.
Timestamp: 11/28/2009 12:08:50
Message: Failure sending mail.
Stack: at System.Net.Mail.SmtpClient.Send(MailMessage message)
at Microsoft.WindowsServerSolutions.SystemHealth.Monitoring.MailUtil.SendMail(String from, String[] to, String subject, Boolean isBodyHTML, String body, String inlineAttachmentPath, String[] attachments)
An exception of type ‘Type: System.Net.WebException, System, Version=, Culture=neutral, PublicKeyToken=b77a5c561934e089’ has occurred.
Timestamp: 11/28/2009 12:08:50
Message: Unable to connect to the remote server
Stack: at System.Net.ServicePoint.GetConnection(PooledStream PooledStream, Object owner, Boolean async, IPAddress& address, Socket& abortSocket, Socket& abortSocket6, Int32 timeout)
at System.Net.PooledStream.Activate(Object owningObject, Boolean async, Int32 timeout, GeneralAsyncDelegate asyncCallback)
at System.Net.PooledStream.Activate(Object owningObject, GeneralAsyncDelegate asyncCallback)
at System.Net.ConnectionPool.GetConnection(Object owningObject, GeneralAsyncDelegate asyncCallback, Int32 creationTimeout)
at System.Net.Mail.SmtpConnection.GetConnection(String host, Int32 port)
at System.Net.Mail.SmtpClient.Send(MailMessage message)
An exception of type ‘Type: System.Net.Sockets.SocketException, System, Version=, Culture=neutral, PublicKeyToken=b77a5c561934e089’ has occurred.
Timestamp: 11/28/2009 12:08:50
Message: No connection could be made because the target machine actively refused it fe80::309c:a749:6920:e429%10:25
Stack: at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Int32 timeout, Exception& exception)

The key aspect of the exception is this:
No connection could be made because the target machine actively refused it fe80::309c:a749:6920:e429%10:25

(In this case, the IP address is an IPv6 address which is not correct, it should be an IPv4 address for SBS 2008, we solved the issue by removing IPv6 address in host files.)

[TIP]: If you have any tough issue about monitoring, go to C:\Program Files\Windows Small Business Server\Logs\MonitoringServiceLogs\DataServiceComponents.log

Bottom line look in that log file, it should give you a hint to what’s going on.

Migrating to Windows Small Business Server 2011 Standard and Essentials

Migrating to Windows Small Business Server 2011 Standard and Essentials

Watch the Teched session on SBS migration

Promise me you won’t try to do this

So your client has Quickbooks 2007 and you are migrating them to SBS 2011.  First off I’m going to say you probably want to sit them down and talk about that Quickbooks 2007 multiuser version and ask them to strongly consider upgrading.  For one the program/version is no longer supported.  Certainly if they had employees they’d have migrated to a newer version before this if they used the payroll module.  But there’s another reason… you strongly do not want to be dealing with an app that wants .NET running on a SBS 2011.

When you install .net 1.1 on your SBS 2011 certain things go boom:


WSUS isn’t WSUSing like it should.

And when I went poking around certain things just are not happy.

If your clients absolutely put their foot down — or more likely than not someone’s gone and done it and you are stuck cleaning up the mess, here’s what I did to get it working —

So here’s what I did to get IIS for Companyweb and WSUS working again without reinstalling the server…

From :
.NET 1.1 may have agressively taken over part of IIS. Try running aspnet_regiis /i from the command prompt for the v2.0 folder. (c:\windows\\framework\v2.0.50727). That will register 2.0 but won’t mess up 1.1. This is the most likely fix.

In my case I launched a command window as an administrator and then went to the folder of c:\windows\\framework\2.0.50727 and typed in aspnet_regiis /i and then did the same from c:\windows\\framework\v4.0.30319 and typed in aspnet_regiis /i

I then did a IISreset.

I also went to the IIS console and ensured that the IIS 1 and 4 isapi filters were allowed to run

Orignally the 1.1 said disallowed.  I also let the 4.0 isapi filters be allowed.

And voila — companyweb and WSUS work.

But do me a huge favor… get them to upgrade from Quickbooks 2007… it’s old, it’s out of date, it’s not supported, it doesn’t like UAC and you really don’t want it running on that aserver.

Additition on 4/8/2012:

Adam writes: “Had a similar issue with something (ASP1.1) messing up WSUS and Companyweb. However, mine was fixed by this link…

HTTP Error 500.0 – Internal Server Error
Calling LoadLibraryEx on ISAPI filter “C:\Windows\Microsoft.NET\Framework\v4.0.30319\\aspnet_filter.dll” failed

Note the double backslashes in the path!!

Unable to Fax From Windows XP with SBS 2011 Standard:

Unable to Fax From Windows XP with SBS 2011 Standard:
SBS 2011 does contain 32 bit Fax drivers that will work with Windows Vista and Windows 7 clients. You could upgrade the client operating system to Windows Vista or Windows 7 and the Shared Fax will work correctly. If upgrading the client operating system is not possible, you can manually replace the 32 Fax drivers with drivers that will work with Windows XP. You can find appropriate drivers on an SBS 2003 SP2 Server. If an SBS 2003 SP2 server is not available, you can obtain the drivers from Windows Server 2003 Service Pack 2.

Step 1: Obtain the Appropriate Driver Files

The appropriate driver files are located on the SBS 2003 SP2 server in the following directory: c:\windows\system32\spool\drivers\w32x86\3
You need to copy the following 6 files to a temporary location:
I think that is written a bit strangely… SBS 2011 does contain 32 bit Fax drivers that will work with Windows Vista and Windows 7 clients. … it should go on an explicity state that it does not include them for XP 32bit workstations.
And I stuck the files up here in case you don’t have access to a SBS 2003 box.

a. SBS 2003 SP2 Server is accessible

What key code can I use to run SBS 2011 standard as a partner?

I’m going to repost the answer to the question of “what key code can I use to run SBS 2011 during this time that there IS no key in the action pack download section.

First off if you visit the action pack download site you will notice that it lists SBS 2008 not SBS 2011 –

You will note that just last week Microsoft made this big deal about how SBS 2011 is now available in all channels.  In the tiny tiny fine invisible print on the page they should have said “except on the Action pack page”. 

Why isn’t it there?  Who knows.  Get Eric Ligman to let his hair down at the WWPC and give you the details (and if you know anything about Eric’s haircut you know that’s going to be a bit difficult). 

So with no Action pack license on the site.. how can you run SBS 2011 in your business to really test it good.  Okay well on that page up on the upper middle there’s another place to click on there.  See that “licensing information” tab?  On THAT page it tells me what I’m licensed for. 

Notice how it says I’m LICENSED for SBS 2011?

Okay so let’s read the recent tweets of Eric Ligman — he says — @dinotech – Your license determines what you are entitled to run, not your product key. Having product key without a license means nothing.

And then he says @dinotech – You need a product key for the product you are licensed for. I.e. An SBS 2011 Std key for an SBS 2011 Std product license.

Then let me repost was was posted to the blog as a comment —

You actually have 75 days left on the install, not 15, since you are able to re-arm the software twice (for up to 90 days of usage). See details here:

As for your statement of, “we are unable to get it properly licensed,” you are fully licensed. Your License Summary at…/Licensing.aspx is specific to your account and your subscriptions/benefits and shows what you are licensed to use through your subscription. A key has nothing to do with your license, so using the current install under your license vs. the key that will be provided on the download site doesn’t change your licensing at all, just the key you’re using to activate it.

As for, “How are we supposed to sell the product if we cannot even get it set up in production?” Why can’t you get it setup in production? I have the steps listed on how and where partners can get and install SBS 2011 right now for internal use at: I would recommend reading that and following those steps to get SBS 2011 running so you are able to use, understand, and sell SBS 2011 today.

Yes, we are fully aware that not having the digital distribution keys on the download site is an inconvenience that we are working on right now; however, let’s not confuse that with not being able to get the SBS 2011 software and the ability to install and use the final bits today (which you absolutely can do through the steps listed in the link above).

Thank you and have a wonderful day,

Eric Ligman

Worldwide Partner Experience Lead

Microsoft Corporation

So what does all that mean?

In the short term use the download from the Technet plus site, key it with that key.  Later on when the Action pack key is finally released, go back, go into the control panel, click change product key and easily rekey it to the action pack key.

Fixing the issue of OWA redirect (courtesy of Daryl Maunder)

Here’s a case where I didn’t think something was broken so it was never bugged.  The situation is the url redirect that forwards your users over to /owa.

OWA is Exchange 2007 and 2010 era.  Exchange is 2003.  If your clients are use to /exchange and they don’t take well to change… well… when you migrate to SBS 2011 it doesn’t work.  The folder structure is there but it doesn’t work.

Now if you have a firm full of people used to logging into RWW or RWA (I’ll probably not get used to that change), and using phones for email access, they probably have never used /exchange and won’t care.  If you have a firm that needs this redirect to work…here’s how to put in back.

I just added it to the as well

 6. Fixing the issue of OWA redirect (courtesy of Daryl Maunder)

Create an Exchange folder in the same folder as the OWA folder.
Make the permissions the same as the /owa folder.
Change the /Exchange virtual folder in IIS to point to this folder instead of the /owa it’s pointing to.
Unticked the http redirect on the /owa folder.
Unticked/reticked the http redirect box on the /exchange folder and it created a web.config file in the exchange folder and the redirect from /exchange to /owa now works.

So how big of a email database can you have on SBS 2011?

So how big of a email database can you have on SBS 2011?

I TB big enough for ya?

Third tier webinar – preparing for migration

Don’t forget to wear green in honor of tomorrow

Meeting time: Mar 17, 2011 12:00 PM (EST)

Add to my Outlook Calendar:

This month the folks at Third Tier are going to review the steps necessary to prepare your existing environment for migration to SBS 2011 Standard. They will use the Microsoft documentation on migration from SBS 2003 as the starting point for their  presentation. In this presentation they will make a some additions/subtractions and reordering of that document. You will leave this session with a blueprint ready to implement for your next migration.

You will find Microsoft’s migration preparation document on TechNet. You should download this document and become familiar with it in preparation for this webinar.


TechNet Webcast: Windows Small Business Server 2011 Standard Launch (Level 200)

• TechNet Webcast: Windows Small Business Server 2011 Standard Launch (Level 200)

Tomorrow at 8 a.m. pacific


• Lucy Ellis, HP
• Michael Leworthy, Microsoft

• 3/15/2011
• 8:00 AM (USA Pacific Time)
(Please log in ½ hour prior to session start time for pre-conference testing)

• Phone: 800-227-8104
• PIN: 5864

System Set-up and Resource Links:

Testing that your systems are compatible with Live Meeting is one of the most important things you need to do to prepare for anytime you use Live Meeting. Below are links to the Live Meeting website that will provide you with the system requirements and plug-ins you need.
• Console Test:
• System Requirements: click here

If you have not used Live Meeting 2007, there are a number of resources available to learn about it on the Live Meeting home page.

Compatibility Fix for Windows 7 / Internet Explorer 8 Users

If you receive a “Server error…contact administrator…” message when trying to log into a Live Meeting room, please click here for instructions on how correct this issue.

Live Meeting Support Contact Info:

Support Request:
Domestic: 866.493.2825 Direct -(toll-free in US)
Europe: 00.800.9522.3000 Direct- (toll-free in Europe)
International: 650.526.6950 Direct- (toll international)

Dual monitors in RWA – yes you can!

Okay so the other day on the SMBTN listserve someone was asking about a compelling reason to migrate from SBS 2008 to SBS 2011.  And honestly it’s a hard sell for that one.  Granted the hardware probably will work just fine, but if they migrated to SBS 2008 from SBS 2003 they probably still have the stretch marks from the migration process and not something that they want to go back through right away… Oh sure there’s lots of little things… like nicer SharePoint… like the face that you can adjust the Remote Web Workplace, like the more features of Exchange 2010, ..

but lots of wow?

Hold on…there’s one hiding in your network. 

One of the key productivity items for a firm is multiple monitors.  Before this multiple monitors over a true rdp session was a big rectangle from the remote session.  Not good.

And up until Server 2008 R2/Windows 7 it wouldn’t handle the multiple monitors across the remote web workplace/access.

Until now.

That’s a remote web access session spread over two monitors.  The desktop I’m remoting into has two montors (it’s Philip Elder’s RWA that he graciously let me test this on) and I’ve got images across the two monitors.

As long as the workstation you are remoting into is a Windows 7 Enterprise or Ultimate (yes, gotta love licensing again) you can offer up multiple monitors across the RWA session.

In Windows 7 Ultimate and Windows 7 Enterprise editions, Remote Desktop Connection supports the use of multiple high-resolution displays in a remote session.