THE OFFICIAL BLOG OF THE SBS DIVA

First off some foundations, unlike SBS Standard you either need to park the url under vanityname.remotewebaccess.com or you need to buy a SSL cert.  But the wizard assumes that you will want to buy your SSL cert from the domain vendor you have your domain name parked under ...and well sometimes you don't do that.

So what's an SBS-E to do? 

How to Install Your Existing Certificate into SBS Essentials - The Official SBS Blog - Site Home - TechNet Blogs:
http://blogs.technet.com/b/sbs/archive/2011/08/04/how-to-install-your-existing-certificate-into-sbs-essentials.aspx

Follow that blog to take ANY third party SSL cert you've purchased and install it on your SBS 2011 Essential Server.

I'll post it up on the www.sbsbuilddoc.com so we won't forget it.

Spotted this in the partner forum....

Got Public Folder replication issues?  Check this post out:

To troubleshoot the issue, I suggest you perform the following steps:

1. On Exchange 2003 server, open Exchange System Manager->expand "Administrative Group"->"Servers"->"ServerName"->"storage group name"->right click the mailbox store and click "Properties"->go to "Diagnostics logging" tab->in the left panel, expand "MSExchangeIS" and click "Public Folder"->in the right panel, select the following items and make sure the logging level is set to "Maximum":

 Replication Incoming message, Replication Outgoing message, Replciation AD Updates, Non-Delivery reports, Replication Backfill, Replication General.

 2. On Exchange 2010 server, open Exchange Management Shell and run the following commands to set the event log level:

 Set-EventLogLevel –Identity "MSExchangeIS\9001 Public\Replication Incoming Messages" -Level Expert

Set-EventLogLevel –Identity "MSExchangeIS\9001 Public\Replication Outgoing Messages" -Level Expert

Set-EventLogLevel –Identity "MSExchangeIS\9001 Public\Replication DS Updates" -Level Expert

Set-EventLogLevel –Identity "MSExchangeIS\9001 Public\Replication Backfill" -Level Expert

Set-EventLogLevel –Identity "MSExchangeIS\9001 Public\Replication NDRs" -Level Expert

Set-EventLogLevel –Identity "MSExchangeIS\9001 Public\Replication Genera" -Level Expert

3. In SBS 2011 Exchange Management Shell, navigate to "C:\Program Files\Microsoft\Exchange Server\V14\Scripts" and run the following two commands: 

.\AddReplicaToPFRecursive.ps1 -TopPublicFolder "\" -ServerToAdd Exchange2010ServerName

.\AddReplicaToPFRecursive.ps1 -TopPublicFolder "\NON_IPM_SUBTREE" -ServerToAdd Exchange2010ServerName 

Please wait and monitor the issue. If the issues persists, please collect application log on both Exchange 2003 and Exchange 2010:

If even Public Folder hierarchy doesn't replicate to SBS 2011, it is probably the mail flow has some problems or the SMTP address of SBS 2011 public folder database is not correct. Please perform the following steps to further troubleshoot the issue: 

1. Log on Exchange 2010 server, click "Start"->click "Run" and type "adsiedit.msc"

2. Expand the "CN=Configuration,DC=[Domain_Name],DC=com"-> " CN=Services"->"CN=Microsoft Exchange"->"CN=<organization name>"->"CN=Administrative Groups"->"CN=Exchange Administrative Group (FYDIBOHF23SPDLT)"->"CN=Databases"

3. Right click the Public Folder database object and click "Properties"->Make sure the following attribute is set correctly:

ProxyAddresses: "SMTP:PFDatabaseName@domain.com"  (For example: the database name is PFDB1, the SMTP address is "SMTP:PFDB1@domain.com")

Mail: "PFDatabaseName@domain.com"

mailNichName: "PFDatabaseName" 

4. Please try to send an e-mail from a user whose mailbox is on SBS 2003 to SBS 2011 user and check whether the recipient is able to receive the e-mail.

 P.S. also ! Remove AV for Exchange on the source. !

Check the following for other known issues:

http://blogs.technet.com/b/sbs/archive/2009/06/21/sbs-migrations-troubleshooting-moving-public-folder-replicas.aspx

When you are banging your head against a wall, don't forget all the resources you have.

1.  www.sbsforum.info - the public SBS forum

2.  www.sbspartnerforum.info - the partner forum where you are guaranteed a response.

3.  www.thirdtier.net - consultants for consultants

So when you are banging your head against a wall remember you have resources...

So I was blonde today.  A client was trying to send an email to the firm and it wasn't coming in.  I was told it was due to content filtering, but I knew that I had Exchange set to quarantine and not to bounce messages... something else was keeping the mail hygiene service from sending the emails inbound...but what?

Turns out the client was sending a really large file (gotta love people who have fat internet speeds while I'm on puny DSL) and one of my connector limits was smaller than what they were trying to send inbound.

http://exchangeshare.wordpress.com/2008/04/24/exchange-2007-where-to-set-message-mail-size-limit/

Set-SendConnector “Connector Name” -MaxMessageSize 40mb

So I kicked the connector up to the maximum (which can be done via PowerShell or via the GUI) and voila.  Big fat hunky email received.

Now if we can just train the clients to not send such large emails.

Is your QuickBooks Enterprise v11 .tlg growing out of control? | Intuit Community:
http://community.intuit.com/posts/is-your-quickbooks-enterprise-v11-tlg-growing-out-of-control

Copied from the Quickbooks forum so I don't forget this for the future --

"One of my brilliant blog readers stumbled on the solution. He posted it to the Performance Issues forum, but I believe all Enterprise v11 users need to know about it.

http://community.intuit.com/posts/tlg-file-grows-very-large-very-fast-enterprise-2011-possible-solution?cid=feed-posts

In a nutshell, the new Search feature can cause some .tlg files to grow out of control. I checked, and mine is just fine. But if you read his story, you'll see that his was growing up to 1.7GB a day!

You can turn it off by going to Edit > Preferences > Search > Company Preferences and un-checking the little check box next to ‘Update Automatically’. If you use the Search feature, you'll need to update manually, which will probably cause your .tlg file to grow so you'll want to follow it up with a manual backup (with full verify).

It's always a good idea to routinely perform manual backups. Not only does it bring your .tlg file size down, but it verifies your data which is essential to your file's health. I have my QuickBooks files automatically backed up automatically by three different services - Intuit Data Services, Gillware and Mozy - and I still do manual backups very week or so. Let's just say I'd be in a heap of trouble if I ever lost any of m client's files!"