Windows Server 2012R2 preview release is now available for download at MSDN. You can download Standard, Datacenter or Essentials edition.
Download it, test it and enjoy!.
All about Windows Servers and much more
Windows Server 2012R2 preview release is now available for download at MSDN. You can download Standard, Datacenter or Essentials edition.
Download it, test it and enjoy!.
Move the FSMO Roles from SBS Server
At this point the SBS Server holds all five FSMO. In order to demote the SBS Server, these roles must first be moved to another domain controller. They can be safely moved to any Domain Controller in the domain.
To transfer the FSMO roles, follow this steps:
Uninstalling the Exchange Server
Now is time to uninstall the Exchange server from the SBS Server. Be careful, if you have installed ForeFront for Exchange Server. In this case you must first uninstall this product:
The second thing that you must do is to create the registry key that enables you to remove the Exchange Server management tools:
It could happen that you will also have to change manually the responsible server for OAB generation, remove public folders and change the source server for send connectors. This are the steps to control (change) this settings:
After this step, it is time to uninstall the Exchange server:
Demote the SBS Server and remove it from the domain
Log on to the Management Server as an administrator and follow this steps to remove the machine from the domain:
After the machine has finished rebooting, remove it from the domain following this steps:
Log on to the DC Server and verify that the DNS A record and computer account for the SBS Server have been successfully removed.
Transferring DHCP role to the new domain controller
The DHCP database and settings can be backed up to allow the replacement server to quickly take over the DHCP server role and service clients again. If DHCP is not running on the SBS server, you may skip this step. To back up the database, follow this steps:
To allow the new server to act as a DHCP server, you must install the DHCP Server role and then configure the server’s settings. This steps assume that you have backed up your SBS Server settings and will restore them to the new server. If you are hosting DHCP on another server, you may skip this step.
Install the DHCP Server Role
You can use this procedure to install and configure the DHCP Server role, using the Add Roles Wizard. Membership in Domain Admins or equivalent is the minimum required to perform this procedure.
To install DHCP
Restore from Backup
Backup Exchange Data
Follow this steps to back up the data in Exchange using Windows Server Backup so it can be restored on the new server running Exchange Server 2007. You are free to use another backup and restore solution, but that will not be covered in this document. If you choose to use Windows Server Backup, you should have Exchange 2007 Service Pack 2 or later installed so that the Exchange backup plugin is registered. You will also need to install Exchange Server 2007 Service Pack 2 or later on the new server in order to have the Exchange backup plugin available for the restore.
Using Windows Server Backup
Using a file copy backup
Note: This step is recommended as a second backup of the Exchange data in the event you plan on migrating the Messaging server to the same hardware in the unlikely event you are unable to restore the Exchange data from your primary backup method after the server is reinstalled.
?
Install the Exchange Server
Using a copy of 64-bit Windows Server 2008R2 Standard Edition, install a new server. The server should be joined to the domain manually as a member server. Once the server is installed, apply all the Windows Service Packs and updates.
There is no requirement that the Messaging Server should be a domain controller. If you have additional DCs, it is not recommended making this server a DC.
Install Exchange and Migrate Data
To install the Windows Server 2008R2 operating system prerequisites, for a computer that will host the Hub Transport, Client Access, and Mailbox server roles, use the Powershell interface:
Install Exchange Server 2010
In this time, you must change the firewall and the DNS setting. Now the new exchange is ready to receive and send mails. This will be possible after you change the forwarding roles on your firewall. You must change forwarding roles for ports 25, 80 and 443 to messaging server IP.
Some changes in DNS are also needed. To do this follow the procedure:
Creating data and migrating users to the new Exchange server
First step to do is creating a new Offline Address Book:
After the database is ready, you can begin moving Mailbox Location with pipeline Get-Mailbox -Server SBS_SERVER | New-MoveRequest -TargetDatabase “NEW_DATABASE” (where SBS_SERVER is the name of the SBS Server and NEW_DATABASE is the name of the Mailbox database on Messaging server). During the move operation, user will be able to send and receive mails, but when the operation is completed, he will be prompted to restart Outlook.
At the end they remain only public folders. You can move them simply with a script from the new Exchange server:
Migrate from SBS 2008 or 2011 (Part 3)
Migrate SharePoint Data (Optional)
This step is an optional. If you are using SBS SharePoint, you might wish to migrate it. SBS deployments that don’t use this component, can skip this step.
You will be able to attach a content database to a destination server only if the version of SBS SharePoint is SP2 or later and the content database is prepared for migration.
To check the version of SharePoint, follow this steps:
Before you begin with migration, it is necessary to verify upgrade readiness on SBS Server. Follow this steps:
On the new server install SharePoint Foundation following this steps:
To transfer content database to the new server, follow this steps:
To transfer content to new server we will use the attach database method. This could be done using this steps: