Preview Notes on SBS 2011

AID: 4128

Status: Published

4690 points

Bylouisreeves
TypeReview
Posted on2010-11-16 at 20:13:35

The SBS 2011 release date (RTM) is supposed to be around Christmas, 2011. This article is a compilation of my notes -- things I have learned first hand. The items are in a rather random order, but I think this list covers most of what is new and different, and it might be helpful to readers who contemplate upgrading.

A single group mailbox can now have members who all have access to the mail in a single public folder. Think:
info@domain.com

All IIS sites are back inside the default website again.

SharePoint Disaster recovery can be done regardless of whether the Active directory matchers. BUT THE DATABASE IS NOT TIED TO WINDOWS INTERNAL DATABASE ANYMORE either!

10GB database size limit on SQL 2008 R2 (SharePoint). This will be a call generator and SQL RBS may need to be used. Max usage is 1GB of RAM and MAX processor is 1.

SharePoint disaster recovery method unveiled by MICROSOFT trainer in SBS 7 class. It is in the SharePoint DOC I sent everyone.

There is a registry edit you can make on the source server to make migration of an unhealthy server possible (disable health checks). It was the source of 60% of migration failures.

OWA 2010 will allow drag and drop attachments with Silverlight.

Exchange 2010 supports iCAL integration (like Google calendaring)

Reinstalling CAS role is much simpler in SBS 7 than in the past.

A backup can be mounted now
a. Mount a VSS snapshot backup
b. ntdsutil
c. mount snapshot <name>

WBADMIN to start windows backup

Bind an existing certificate to the default web site

appcmd set site /site.name:Default Web Site/-bindings.[protocol='https',bindinginformation='my old ip:443:']

1:

Select all Open in new window

http://forums.iis.net/t/1158284.aspx

SBS 2011 will not allow access to the remote gateway directly. Leverages Remote Desktop Gateway (TCP port 443). It is hidden to prevent misconfiguration.
a. Go to features and install the remote web service (even though it it already installed)
b. dism /online/ enable-feature:gateway-UI
c. dism /online/ enable-DISABLE:gateway-UI

How to create a file of any size you want for testing:

fsutil file creatnew test.txt [size in bytes]

1:

Select all Open in new window

32-Bit hosting is becoming a call generator as may 3rd party apps – install 32 bit directory in IIS – thereby breaking 64 bit browsing completely. Here is the workaround from Microsoft:

Adventure Works needs to migrate their custom website to SBS 2011. This website only runs on 32-bit application pools. To complete this task:
1. Create a new website on port 80, using a host header of “32bit”
2. Create a new app-pool for this website that is 32-bit.
3. Create a “hello world” default.aspx.
4. Make sure you can browse both the normal SBS sites and the new site.

Edit the Global Modules section of C:\Windows\System32\inetsrv\configApplicationHost.Config:
Original:
<add name="kerbauth" image="C:\Program Files\Microsoft\Exchange Server\V14\Bin\kerbauth.dll" />
Modified:
<add name="kerbauth" image="C:\Program Files\Microsoft\Exchange Server\V14\Bin\kerbauth.dll" preCondition="bitness64" />
Admin Command prompt:

Appcmd set module dynamiccompressionmodule /lockItem:false
Appcmd set module staticcompressionmodule /lockItem:false
Appcmd delete module dynamiccompressionmodule /site.name:sitename
Appcmd delete module staticcompressionmodule /site.name:sitename

1:
2:
3:
4:

Select all Open in new window

Requires 120 GB Hard drive

Swing Migration not possible (like in the past). The name cannot be re-used

There is a check box to stop the default downloading of Service packs for WSUS

You can now recreate the OWA virtual Directorys in a simpler way.
a. ResetCasService.ps1 script
b. Exports are saved in Program Files\Microsoft\Exchange Server\V14 as a txt file
<CASFQDN_<VDIR>_log.txt
c. It is a right-click operation in the GUI

Disable loopback checking is defaulted to 1 in SBS 2011. Ever get the browser works everywhere but the server? Here is your answer.
http://support.microsoft.com/kb/896861

SBS 2010 will not support a 2003 outlook client by default.

MICROSOFT SAYS ISINTEG IS USELESS!!!!! DON’T USE IT!

2007 Database wizard is going away! They are going back to the old isinteg

MailboxRepairRequest is the new way to request mailbox maintenance

New-PublicFolderDatabaseRepairRequest is for public folders.

Public folders are staying and they look to be permanent now.

There is now a PST folder for Exchange 2010 SP1 ! (You don’t need Outlook anymore to backup)
a. New-MailboxExportRequest
b. Set-MailboxExportRequest
c. Remove-MailboxExportRequest
d. Suspend-MailboxExportRequest
e. Resume-MailboxExportRequest
f. Get-MailboxExportRequest
g. Get-MailboxExportRequestStatistics
h. MailboxRestoreRequest or Restore-MailBox

SBS Monitoring database (2008) getting too large has been fixed in SBS 2011
a. The new logs are only kept for 30 days. The link below fixes the 2008 SBS issue.
b. http://blogs.technet.com/b/sbs/archive/2009/07/14/sbs-2008-console-may-take-too-long-to-display-alerts-and-security-statuses-display-not-available-or-crash.aspx

SBS Gadgets are removed from the GPO in SBS 2011.

Gadgets are configurable in RWW C:\Program Files\Windows Small Business Server\Bin\WebApp\RemoteAccess\Customization\Product\custom.xml

You can adjust which computers you can see in RWW by:
HKLM\Software\Microsoft\SmallBusinessServer\BusinessProductivity

SharePoint on SBS 2011 is SharePoint foundation. AND IS SET UP IN FARM MODE

Subject: Autodiscover info
This article has the registry keys to change the Outlook autodiscover behavior.

http://support.microsoft.com/kb/948981

Here are the values (all DWORD values, all defaults are zero):

HKCU\Software\[Policies\]Microsoft\Office\12.0\Outlook\AutoDiscover
ExcludeScpLookup
ExcludeHttpsRootDomain
ExcludeHttpsAutoDiscoverDomain
ExcludeHttpRedirect ExcludeSrvRecord

For example, to exclude autodiscover.domain.com you would set
ExcludeHttpsAutoDiscoverDomain to 1

Asked On: 2010-11-16 at 20:13:35ID4128
Tags: SBS7
,; SBS 2011
,; SBS beta
Topic: SBS Small Business Server
Views: 4038

About The Author

louisreeves

Louis Reeves has 7 years workiing in Support with Exchange, SQL, Windows, Virtualization,. and other related technologies.

More Articles From louisreeves

Comments

Expert Comment

by: demazter on 2010-11-29 at 03:39:25ID: 21633

I am a little confused by this article.

It seems to talk about SBS2010, SBS2011 and SBS 7, the correct name is SBS2011 there is no SBS7 or SBS2011.

A lot of the information seems to be misguided or incorrect.

-> SBS2008 DOES support Outlook 2003, I have clients running it quite happily. And I have not had to make any changes.

-> MICROSOFT SAYS ISINTEG IS USELESS!!!!! DON’T USE IT! - Where have you got this information from? ISINTEG is used to check the integrity of the database after performing a hard repair. it's an essential task.

-> There is no command called MailboxRepairRequest the correct command is: New-MailboxRepairRequest and this is used to correct mailbox and/or database corruption.

-> Public folders are staying and they look to be permanent now - No they are not, Microsoft wants this sort of functionality to be moved to SharePoint. Whilst public folders are there in Exchange 2010 (which is what is included in SBS2011) they are not guaranteeing that it will be supported in the future.

-> There is now a PST folder for Exchange 2010 SP1 - There is? Where? Are you refering to the online archive? This IS NOT a PST file. It is an ordinary database within the Exchange structure that allows for a second mailbox (archive mailbox) to be attached to a user. This is only available using OWA or Outlook 2010 for the time being, there is a Service Pack that is supposed to add functionality to Outlook 2007 but that isn't available yet.

demazter

Author Comment

by: louisreeves on 2010-12-08 at 13:50:20ID: 21953

Public folders do n

SBS 2011 doesn’t support outlook 2003. That was a typo -I appreciated your comments. The notes are directly from my SBS 2011 Class notes. The official release name has been changed several times. I don’t have a lot of time so thank for editing. The writing is based on what I already know. However if you need links to know where some of this is coming from:

1, Isinteg- http://msdn.itags.org/exchange-server/194430/
2. Public folders-and idea SharePoint is replacing them http://www.outlookwise.com/outlookwise/article_the_future_of_exchange_server_public_folders.htm

So guess what? Some of this stuff is undocumented and guess what you won’t be able to Google it for a while.

1.      Public Folders are staying in the future of exchange.
2.      ISINTEG is abused by people who don’t know what it’s for, or when to use it.
3.      There is a new exchange public folder (for backup) you can export the mailbox from Exchange into a public folder. Then you can copy that data off so you don’t need to make an outlook PST folder.

I had a chance to see some of this stuff in action. My apologies for some of the cryptic writing. I was lab-ing and typing at the same time. I hope this might be useful to someone. I would make an article out of it but I am juggling multiple responsibilities. This one is not the top one.
ot look to be going away now. these are notes not a copy paste fix it doc.

Expert Comment

by: demazter on 2010-12-08 at 14:02:03ID: 21954

SBS 2011 doesn’t support outlook 2003
yes it does, Exchange 2010 does so why wouldn't SBS201??

There is a new exchange public folder (for backup) you can export the mailbox from Exchange into a public folder. Then you can copy that data off so you don’t need to make an outlook PST folder.

No there isn't. There is a new on-line archive, this is not a public folder and it's not a PST file. It's an additional mailbox.

Most of your article has been contradicted by your own follow up post.

Not sure where you have got a lot of this information from but it seems misguided at best.

demazter

Expert Comment

by: mudgie on 2010-12-16 at 06:39:51ID: 22117

I understand that Exchange 2010 formerly required encrypted communications and that Outlook 2003 did not support RPC. I believe this was resolved in Exchange 2010 SP1, which is part of SBS 2011 (http://support.microsoft.com/kb/2006508). Nevertheless there are other unresolved issues that would militate towards upgrading the clients to 2007 or later. I would like to know for sure since I'm already quoting server projects based on SBS 2011 (one of which has been approved). This gives me one more thing to consider when planning the project!

Expert Comment

by: demazter on 2010-12-16 at 06:56:50ID: 22119

Outlook 2003 does work with Exchange 2010 without SP1.
The reason it doesn't is because RPC Encryption is not enabled in Outlook 2003 and by default is turned on with Exchange 2010.

This can simply be resolved by disabling the need for RPC Encryption which since you wouldn't have been using it anyway isn't a huge problem.

Ten once you have completed the upgrade of the clients turn it back on.

Expert Comment

by: mudgie on 2011-01-18 at 12:15:33ID: 22941

I deployed SBS2011 for a client that has several copies of Outlook 2003. They're all working in-house. None of them are external users so I can't chime in on Outlook Anywhere.

Expert Comment

by: HBPROCK on 2011-01-24 at 10:43:26ID: 23105

I noticed you say you cant do a swing migration as you cant use the same name. Is this True? as Im planning a swing migration shortly. If Im using a temp Server in the swing process I cant see why I wouldn't be able to call the new SBS 2011 server the same as the 2003 one.

Expert Comment

by: demazter on 2011-01-24 at 10:58:19ID: 23106

A swing migrations means you stage the migration with an intermediate server, once you have the intermediate server up and running you demote the SBS2003 server then you can add an SBS2011 server as an additional server to the domain with the same name as the now non-existent SBS2003 server.

There is no reason why this wouldn't work, however, I would suggest you visit why a swing migration is required at all. Why do you need to keep the same server name?

If you do insist on a swing migration some articles that I have written may be of some use to you:

Migrate Small Business Server 2003 to Windows 2008 R2 and Exchange 2010: http://www.experts-exchange.com/Software/Server_Software/Email_Servers/Exchange/A_2881-Migrate-Small-Business-Server-2003-to-Exchange-2010-and-Windows-2008-R2.html

Migrate Windows 2003 server to SBS2008:http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Server/SBS_Small_Business_Server/A_2465-Migrate-Windows-2003-with-Exchange-to-Small-Business-Server-2008.html the process is exactly the same if it was from Windows 2008 R2 with Exchange to SBS2011.

Expert Comment

by: HBPROCK on 2011-01-24 at 12:03:25ID: 23110

Hi thanks for your post I have done swing migrations before with the swingkits from sbsmigration.com. As regards to why the name thing. It seems just to limit the mount of downtime the customer has to face and any data connections that are written to unc paths like manufacturing Software and machines dnt need to be repainted back to the data on the new server . If you think this is no longer the recommended solution then I would appreciate other peoples ideas and comments.

Expert Comment

by: demazter on 2011-01-24 at 12:05:43ID: 23111

an SBS2003 to SBS2011 migration can be performed with zero downtime as with SBS2003 to SBS2008.

The name thing can be resolved by using CNAME records in the internal DNS once the migration has completed to assist in legacy application maintenance.

The only time would be during the copy of data from one server to the other when there may be some disruption but if you do a swing migration you will need to do this twice.

I would definately not recommend a swing migration over and above a traditional migration.

Expert Comment

by: HBPROCK on 2011-01-24 at 12:19:00ID: 23114

Thanks again for your comments this may be a daft question but those 2 guides are going from SBS to server or server to SBS. How do you get the mailboxes across etc if both servers are SBS?

Expert Comment

by: demazter on 2011-01-24 at 12:25:18ID: 23115

Ahh, that's the easy bit :) You follow my migration guide here: http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Server/SBS_Small_Business_Server/A_4234-Migrate-Small-Business-Server-2003-to-Small-Business-Server-2011.html

Expert Comment

by: HBPROCK on 2011-01-24 at 13:01:21ID: 23116

Thanks for your input Just read through the Article. Great work will defiantly following this I think as it seems allot easier than the Swing Kit which seems to take days even to read as there is allot of work involved and the Server name thing I suppose isn't 100 % critical, all though the C Name change in DNS may be a good option.

One thing slightly off Topic Im trying to convince some of our customers who have just been quoted with SBS 2008 to change to 2011 as the price is pretty much the same. Speaking to Microsoft and looking what's in the product I get the impression that its just an improved version of 2008 which incorporates 2008 R2 which seems to me to be a more stable less buggy and certainly faster OS and I have done a couple of Exchange 2010 Installs and have had no issues at all. I have always found SBS 2008 to be quite slow and alot of silly little issues. I almost look at this as a bit like Microsoft quickly changing Vista to Windows 7 which of course was a Massive improvement. What are your thoughts on the Matter. Do you think SBS 2008 is going to continue to be improved and supported or is it Like with Vista / Windows 7 that there will now concentrate on 2011. Wish do you class as the better product?

Sorry for all the questions just really interested to hear your opinion.

Many thanks

HBP

Expert Comment

by: demazter on 2011-01-24 at 13:05:14ID: 23117

the CNAME record will resolve your names resolution problem.

As for the versions, SBS 2011 includes Exchange 2010 and the better performance received from this against Exchange 2007, Windows 2008 R2, Sharepoint Foundation etc. I wrote this back in the preview days so the title says SBS 7 but the detail is still correct: http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Server/SBS_Small_Business_Server/A_3834-SBS-7-A-first-look.html

SBS2011 is by far the better product and if you have not already installed SBS2008 I would be trying to convince my customers to move to 2011 instead if there was a planned upgrade.

Expert Comment

by: HBPROCK on 2011-01-24 at 13:13:20ID: 23118

Thanks again for you help I think SBS2011 is the way we need to be going just awaiting the OEM Media to arrive in the UK as its still stuck In Germany somewhere apparently.

Expert Comment

by: demazter on 2011-01-24 at 13:13:52ID: 23119

Ahh...yes....I know that feeling very well :)