Category: Windows SBS Server

Migrate from SBS 2008 or 2011 (Part 1)

Published on in Exchange Server, Virtualization, Windows SBS Server, Windows Server by Elvis

Migrate from Windows Small Business Server 2008 to Standard Edition Products

This guide outlines how to migrate an existing Windows Small Business Server 2008 or 2011 domain to a standard version Windows 2008 domain. Migration of some component settings and data are also covered. This guide tells you how to remove your existing servers from the Windows Server 2008 network as you proceed through the migration. It assumes that you have obtained licensed copies of the following products:
• Windows Server 2008R2 Standard Edition (2 Copies, 3 Copies optional),
• Microsoft Exchange Server 2010 Standard Edition,
• Windows Sharepoint Foundation (Optional Download).

The following product may also be a part of the SBS 2008 product, but will not be discussed in this migration document:
• Forefront Security for Exchange 2007 (FSE).
 

Windows Small Business Server Migration Overview

There are several basic upgrade scenarios for the SBS 2008 customers. Most installations will fall into one of these broad categories:

•  The SBS 2008 installations will be migrated to Windows Server 2008 R2 Standard, Exchange Server 2010 Standard and SharePoint Foundation. This scenario is covered in this document.
•  Hybrid migrations. In some cases, it may be preferable to selectively migrate only some components (for example, if an installation chooses to continue using Exchange Server) or to consolidate or distribute roles. This paper will address the main steps of these processes, but will not attempt to cover all the possible variations.
•  Any additional domain controllers and services running on servers, other than the Windows Small Business Servers in the environment, do not need to be migrated. For instance, if DHCP is not running on the SBS server, it does not need to be migrated. If Sharepoint Services is hosted on a non SBS server, it does not need to be migrated.
 

Backup the Existing Environment

It is strongly recommended that SBS server is completely backed up before beginning the steps in this document. This includes full server backup, as well as System State backup of the SBS Server (in case that data needs to be restored or the migration rolled back).

In addition, configuration and data of component applications should be backed up separately, before beginning the migration. The output of the various backup tools will be used later in the migration.

 
Obtain Installation Media

It is important not to start the migration until all media are physically on site. The original SBS media cannot be used to install stand-alone versions of the products.
Consider downloading any component Service Packs that are currently installed in the environment, such as:
• Windows Server 2008R2 Service Pack 1 or later,
• Exchange Server 2010 Service Pack 2 or later.
 

Components Not Upgraded

SBS-specific components cannot be moved or copied to other installations. These components will cease to work and are not supported after SBS is migrated. This list includes:
• Remote Web Workplace (RWW),
• SBS 2008 Administration Console,
• SBS wizards,
• SBS licensing.
 

Premium Edition Upgrades

SBS 2008 Premium Edition includes a separate copy of Windows Server 2008 Standard (32 and 64 bit) and a copy of Microsoft SQL Server. This server does not need to be upgraded or migrated as a part of this process. No action is needed for the server to continue to work and will be licensed once the SBS domain is migrated. It is highly recommended to back up this server separately, because of other changes in the environment that may affect it.

In some cases the SQL instance from this SKU may have been installed on SBS server. In this case, the databases will need to be backed up and restored to a new server installation.

If you used your Premium Edition server to act as a Hyper-V host machine, you can safely leave this server running without additional changes. There is no need to reinstall the Premium Server.

 

Migrate from SBS 2008 or 2011 (Part 2) .

SharePoint Error in SBS 2011 Console

Published on in Windows SBS Server by Elvis

In some cases, I receive a critical error in SBS Console from SharePoint services. When I look into Event viewer, I find an error with this text:

The SharePoint Health Analyzer detected an error.  Web.config file has incorrect settings for the requestFiltering element.
The requestFiltering element in web.config must have the allowDoubleEncoding attribute set to true in order to support file names with the + character in them.
Also, it must have a child requestLimits element with the maxAllowedContentLength attribute set to 2147483647 to avoid interfering with file uploads.
Ensure the requestFiltering element exists in web.config, that its allowDoubleEncoding attribute is set to true, that it has a child requestLimits element,
 and that its maxAllowedContentLength is set to 2147483647.
For more information about this rule, see “http://go.microsoft.com/fwlink/?LinkID=163442“.

This is strange, because the element allowDubleEncoding does not exist, so I investigated how to solve it. The only think that was different in my web.config file and in the error was the value of the parameter maxAllowedContentLength. Therefore, there is the solution of the problem. Everything will be all OK, after you change this value.
You can change this value directly in web.config or true Internet Information Services. To change it true IIS, you must first download an IIS Administration Pack from here.
1. Open the IIS, navigate to SBS SharePoint site, and click on Configuration Editor.

There you have to navigate to System.webserver > Security > requestFiltering.


Expand requestedLimits and change the maxAllowedContentLength value to 2147483647.

Apply the changes, close IIS and restart IIS from command prompt with IISReset /restart.

After this, the critical alert in the console will disappear..

Useful links for Windows Server Essentials 2012

Published on in Office 365, Windows SBS Server, Windows Server by Elvis

In the last days, I found three good links for Windows Server 2012 Essentials administrators.
First is a detailed step-by-step instruction how to implement the direct access with the Server 2012 Essentials. I suggest everyone who wants to implement this functionality to look at this post.
The second link is a Windows app “My Server”, which makes locally available many server management functionalities. A good app, but it is working only with the Essentials server.
The last one is a page with great tools for managing Office 365. There are third party tools, but they can be also useful for administrating Office 365..

Connecting Windows 8 to SBS 2008 (2011) RWW

Published on in Windows SBS Server by Elvis

Some of us have problems with connecting Windows 8 to SBS 2008 or SBS2011 Remote Web Workplace. In RWW, after the connection is established, it is possible to view E-Mails in OWA and open the companyweb site, but it is impossible to connect to internal computers.
This issue is (or will be) solved with Update Rollup package or you can solve it manually, directly in Internet explorer with few clicks:
– add your RWW site to Trusted sites,
– open the RWW site in compatibility mode.
After this, you will be able to connect to all computers..

Windows Server 2012 Essentials is now RTM

Published on in Windows SBS Server, Windows Server by Elvis

Today Microsoft published the RTM version of Windows Server 2012 Essentials. Download is available on MSDN for Microsoft partners. The new version is similar to the old one, with some new features (like the connector for on premise Exchange, Cloud backup …). This version is also a replacement for Home server, which means that now are available Media functions (similar as that in Home server).
Good, now you have enough reasons to download it. Test and enjoy it!.