[There's a reason that Yoda is the unofficial mascot of SBS.  Size indeed matters not.] January 2014 - Posts - THE OFFICIAL BLOG OF THE SBS DIVA

January 2014 - Posts

Essentials 2012 R2 – Client Restore | Title (Required):
http://titlerequired.com/2014/01/30/essentials-2012-r2-client-restore/

We're taking a break of blogging about Exchange - since I honestly want to go back one step and revisit those instructions -  to point out a great post by Rob about making sure you download AHEAD OF TIME, the Windows PE you'll need to fully restore those workstations.

This is a big change from the way prior versions of Essentials worked.  So plan ahead and make sure you disable IE ESC on that server (Enhanced security for IE) in order to be able to download the Windows PE download.

Posted Fri, Jan 31 2014 23:21 by bradley | with no comments
Filed under:

Configure Exchange 2013 external URLs

 

Estimated time to complete: 10 to 15 minutes

There are several settings that you need to configure on the Exchange 2013 virtual directories, which include Outlook Anywhere, Exchange ActiveSync, Exchange Web Services, Offline Address Book (OAB), Outlook Web App, the Exchange admin center, and the availability service.

Learn more at: Virtual Directory Management

  1. Open the EAC by browsing to the URL of your Client Access server. For example, https://Ex2013CAS/ECP.
  2. Enter your user name and password in Domain\user name and Password, and then click Sign in.
  3. Go to Servers > Servers, select the name of the Internet-facing Exchange 2013 Client Access server and then click Edit Edit Icon.


  4. Click Outlook Anywhere.
  5. In the Specify the external hostname field, specify the externally accessible FQDN of the Client Access server. For example, mail.contoso.com.
  6. While you’re here, let’s also set the internally accessible FQDN of the Client Access server. In the Specify the internal hostname field, insert the FQDN you used in the previous step. For example, mail.contoso.com.
  7. Click Save.

 

I think we change that internal domain name to match the external one?

 

 

If this is wrong I'll clarify in a new post and edit this one.

Hit save and you'll get a warning which is okay

  1. Go to Servers > Virtual directories and then click Configure external access domain Configure icon.

 

  1. Under Select the Client Access servers to use with the external URL, click Add Add Icon.

 

  1. Select the Client Access servers you want to configure, and then click Add.

 

 

  1. After you’ve added all the Client Access servers you want to configure, click OK.
  2. In Enter the domain name you will use with your external Client Access servers, type the external domain you want to apply. For example, mail.contoso.com. Click Save.


  3. noteNote:
    Some organizations make the Outlook Web App FQDN unique to protect users against changes to underlying server FQDN changes. Many organizations use owa.contoso.com for their Outlook Web App FQDN instead of mail.contoso.com. If you want to configure a unique Outlook Web App FQDN, do the following after you completed the previous step. This checklist assumes you have configured a unique Outlook Web App FQDN.
    1. In Select server, choose your Exchange 2013 Client Access server.
    2. Select owa (Default Web Site) and click Edit Edit Icon.
    3. In External URL, type https://, then the unique Outlook Web App FQDN you want to use, and then append /owa. For example, https://owa.contoso.com/owa.
    4. Click Save.
    5. Select ecp (Default Web Site) and click Edit Edit Icon.
    6. In External URL, type https://, then the same Outlook Web App FQDN that you specified in the previous step, and then append /ecp. For example, https://owa.contoso.com/ecp.
    7. Click Save.
  4. Click Save.

To verify that you have successfully configured the external URL on the Client Access server virtual directories, do the following:

  1. In the EAC, go to Servers > Virtual directories.
  2. In the Select server field, select the Internet-facing Exchange 2013 Client Access server.
  3. Select a virtual directory and then, in the virtual directory details pane, verify that the External URL field is populated with the correct FQDN and service as shown below:





  4.  
  5. Virtual directory External URL value

    Autodiscover

    No external URL displayed

    ECP

    https://owa.contoso.com/ecp

    EWS

    https://mail.contoso.com/EWS/Exchange.asmx

    Microsoft-Server-ActiveSync

    https://mail.contoso.com/Microsoft-Server-ActiveSync

    OAB

    https://mail.contoso.com/OAB

    OWA

    https://owa.contoso.com/owa

    PowerShell

    http://mail.contoso.com/PowerShell

Blogging my way through a proof of concept migration from SBS 2008 to Essentials 2012 R2 series will be a SMB kitchen project whitepaper.  More about the SMBKitchen project at - http://www.thirdtier.net/enterprise-solutions-for-small-business

Create an Exchange 2013 mailbox

 

To simplify configuration of Exchange 2013 and to help test your new server later on, you need to create an Exchange 2013 mailbox. We'll make this new mailbox a member of the Organization Management role group and you'll use this mailbox when you configure Exchange 2013.

Later on in the checklist you'll need to log into your Exchange 2013 servers. Log in using the Exchange 2013 mailbox you'll create in this step. This will make sure you have the correct permissions to perform each of the steps and that the EAC opens correctly.

How do I do this?

  1. Open the EAC by browsing to the URL of your Client Access server. For example, https://Ex2013CAS/ecp?ExchClientVer=15.
    importantImportant:
    You need to include ?ExchClientVer=15 in the URL when you want to open the EAC with a user that doesn't have an Exchange 2013 mailbox.
  2. Open the EAC by browsing to the URL of your Client Access server. For example, https://Ex2013/ecp?ExchClientVer=15.

In my case https://Exchange/ecp?ExchClientVer=15 which resolves to

 

importantImportant:
You need to include ?ExchClientVer=15 in the URL when you want to open the EAC with a user that doesn't have an Exchange 2013 mailbox.

  1. Enter the user name and password of the account you used to install Exchange 2013 in Domain\user name and Password, and then click Sign in.
  2. I used the domain account so we'll log in with the domain user account.

 

 

 

 

  1. Go to Recipients > Mailboxes. On the Mailboxes page, click Add Add Icon and then select User mailbox.

 

  1. Provide the information required for the new user and then click Save.

Note, I placed this Exchange user in the SBS Organizational unit under SBSUsers 

  1. Go to Permissions > Admin Roles. On the Admin Roles page, select Organization Management and click Edit Edit Icon.
  2. (the edit is the pencil icon

 

  1. Under Members, click Add Add Icon.

 

  1. Select the Exchange 2013 mailbox you just created, click Add, then click OK. Then click Save.
How do I know this worked?

To verify that you've successfully created an Exchange 2013 mailbox and added it as a member of the Organization Management role group, do the following:

  1. In the EAC, go to Permissions > Admin Roles. On the Admin Roles page, select Organization Management.
  2. In the details pane, view the Members list. If the Exchange 2013 mailbox has been successfully added as a member of the Organization Management role group, the mailbox will be listed here.

 

 

 

 

Blogging my way through a proof of concept migration from SBS 2008 to Essentials 2012 R2 series will be a SMB kitchen project whitepaper.  More about the SMBKitchen project at - http://www.thirdtier.net/enterprise-solutions-for-small-business

Posted Thu, Jan 30 2014 22:15 by bradley | with no comments
Filed under:

http://techverse.net/download-windows-7-iso-x86-x64-microsofts-official-servers/
UPDATE : 1/30/2014 : It seems Microsoft has stopped providing Windows 7 ISO images. The Windows 7 links provided below are discontinued

When we have to do a repair install and the person has no media, these are the links I would post.

Now that you've pulled these, you've effectively crippled all operating systems.

The reality of Windows 7 is that it gets component based servicing stack issues that no fixit will fix and ONLY a non destructive repair install will fix.

UPDATE : 1/31/2014 : The links provided for Windows 7 ISO images are not working currently. It seems to be a temporary issue with Digitalriver. According to Microsoft the problem should be resolved in the next couple of days.

http://techverse.net/download-windows-7-iso-x86-x64-microsofts-official-servers/

Thank goodness.

http://technet.microsoft.com/en-US/exdeploy2013/Checklist?state=2284-W-DgBEAgAAQACACAEAAQAAAA%7e%7e

Review the setup log file


You can also learn more about the installation and configuration of Exchange 2013 by reviewing the setup log file created during the setup process.

During installation, Exchange Setup logs events in the Application log of Event Viewer on computers that are running Windows Server 2008 R2 with Service Pack 1 (SP1) and Windows Server 2012. Review the Application log, and make sure there are no warning or error messages related to Exchange setup. These log files contain a history of each action that the system takes during Exchange 2013 setup and any errors that may have occurred. By default, the logging method is set to Verbose. Information is available for each installed server role.

You can find the setup log file at <system drive>\ExchangeSetupLogs\ExchangeSetup.log. The <system drive> variable represents the root directory of the drive where the operating system is installed.

The setup log file tracks the progress of every task that is performed during the Exchange 2013 installation and configuration. The file contains information about the status of the prerequisite and system readiness checks that are performed before installation starts, the application installation progress, and the configuration changes that are made to the system. Check this log file to verify that the server roles were installed as expected.

We recommend that you start your review of the setup log file by searching for any errors. If you find an entry that indicates that an error occurred, read the associated text to figure out the cause of the error.

Early on in my hyperV test I didn't have the second server set to look at the SBS box for it's DNS settings.  When you are in a test situation sometimes your networking isn't a great as it could be. So if you set static nics and have the second server have as it's DNS settings the main server, it will find the main domain controller and be happy.

What you see in my event logs is just that early whoopsie where I didn't have the DNS set and the second server couldn't find the DC

 

Blogging my way through a proof of concept migration from SBS 2008 to Essentials 2012 R2 series will be a SMB kitchen project whitepaper.  More about the SMBKitchen project at - http://www.thirdtier.net/enterprise-solutions-for-small-business

Posted Wed, Jan 29 2014 22:45 by bradley | with no comments
Filed under:

How do I know this worked?


Run Get-ExchangeServer

To verify that Exchange 2013 installed successfully, run the Get-ExchangeServer cmdlet in the Exchange Management Shell. A list is displayed of all Exchange server roles that are installed on the specified server when this cmdlet is run.

For detailed syntax and parameter information, see Get-ExchangeServer

And there's our SBS 2008/Exchange 2007 and our 2013 Exchange server showcasing we have the two chugging along nicely.

and may I just say that hitting the swipe/charm thingy on a Server 2012 over a HyperV manager window is not easy lemme tell ya.

Posted Wed, Jan 29 2014 22:14 by bradley | with no comments
Filed under:

Right about now in this stage of the process I am questioning my sanity.  I honestly have never installed Exchange before.  So while I want to go through the methodical step by step gui process to understand what is going on, to make this feasible from a business deployment standpoint we either need to script it or PowerShell this deployment in the future to make it repeatable.  While the TechNet Essentials instructions have a script for Exchange 2010 (see http://technet.microsoft.com/en-us/library/jj200172.aspx) , they do not have one for 2013.

What you can do when it's your first is to obviously test.  Or hire the folks at www.thirdtier.net to do it for you and then you hang over their shoulder (virtually that is) and pepper them with questions.  And review the current script info posted on Exchange 2013 - http://technet.microsoft.com/en-us/library/aa997281%28v=exchg.150%29.aspx

At this point remember to back up your SBS box because we are making changes to Active Directory.... and here we go....

Now copying files

 

 

We're getting mailboxes installed...

 

Client access role

Next step 10

Next step

 

Right about now you see we need more automation and a script if we're going to be doing this over and over again for clients

 

We're onto step 13

Step 14

And we're done

  1. On the Completion page, click Finish.

  1. noteNote:
If you didn't separate your Active Directory schema preparation from the installation of Exchange 2013, the amount of time this takes is dependent upon your Active Directory site topology. It might take some time for the changes to replicate across your organization.

  1. Restart the computer after Exchange 2013 has completed.
Posted Wed, Jan 29 2014 20:12 by bradley | with no comments
Filed under:

I'm going to use this as an exercise in trying out installing Exchange via the gui (no PowerShell script).  Honestly, the most efficient way is to install this via a script but I'm doing this the slow step by step way to see what happens.

Up next in our install is the prereq check where we see that the system needs to do certain things (IIS setups)

It will actually do these IIS items and at this point need a reboot.

Don't do anything but reboot at this point and then  have the prereq checker check again

When you reboot all these items are installed

We start again

And we check for mailbox and client access role

Again I check for malware

This time there is a much smaller item of things missing, this time it's downloads.

We need the Unified Communications Management 4.0 API and two Office 2010 Filter packs.  To make your life easier you may want to download these ahead of time.

http://www.microsoft.com/en-us/download/details.aspx?id=34992

http://www.microsoft.com/en-us/download/details.aspx?id=17062&fwLinkID=191548

http://www.microsoft.com/en-us/download/details.aspx?id=26604&fwLinkID=262358

 

Posted Mon, Jan 27 2014 22:54 by bradley | with no comments
Filed under:

http://technet.microsoft.com/en-US/exdeploy2013/PrintChecklist?state=2284-W-DQBEAgAAQACACAEAAQAAAA%7e%7e

Next up we start the process of extracting the download and installing Exchange

I always runas admin when I extract the file to ensure that they extract.

Now in hindsight I'd put this file in a subfolder as Exchange spits files all over the place.

When you go to install ensure you either do command line run as administrator, or do a run as administrator

I don't like checking for updates as it adds to the install and introduces possibilities of change.

it goes to copy the files

It starts the install

While I'm installing this I tend to enable network discovery on the server.  Also make sure you move the Exchange server from the computersOU to the ServersOU in the MyBusiness OU up on the SBS box

And now the install is ready to go...well ...sorta

Use the recommended settings

Choose both mailbox and client access role

Don't install it on the C drive, this is only for testing purposes.  Place this on an appropriate drive location.

I don't want to disable malware scanning so I'll enable that

 

 

 

Posted Mon, Jan 27 2014 22:38 by bradley | with no comments
Filed under:

We're in the step of 'watching paint dry' as the full download comes down.

 

 

Posted Sat, Jan 25 2014 19:09 by bradley | with no comments
Filed under:

At this step you want to download the latest version of Exchange 2013 (each CU is a complete build) and use that to download the copy of Exchange to the server.

http://technet.microsoft.com/en-US/Library/jj907309

So whatever the latest one is, is what you want to download.

Our next step also has me hmmmmming.

In the case of SBS 2008 migration to Essentials more than likely we started with one IP and we're going to end with one IP.    So we will have our old Exchange and our new Exchange connecting back in on the same static public IP probably using ARR routing tables at some point in time.

This legacy host name it done up on the DNS provider, so whomever is in control of your server domain name, you'll put this legacy host name setting up there.

For example godaddy's dns.

 You would add it in the A record section up in their DNS manager

So in there you'd click on quick add and you'd add a legacy host name up there in addition to the normal alias you'd use for email.

Create legacy Exchange host name

Estimated time to complete: 5 minutes

You need to create a legacy domain name system (DNS) host name so your legacy Exchange 2007 environment and Exchange 2013 can coexist. For example, if your domain name is currently contoso.com, you're likely using a host name of mail.contoso.com or www.contoso.com for external client access to Exchange. During coexistence, we recommend creating and using, for example, a host name of legacy.contoso.com. You'll associate the legacy host name with your existing Exchange 2007 server and associate your current host name (for example, mail.contoso.com) with your Exchange 2013 Client Access server. Your end users will not see or use the legacy host name. It will be used by Autodiscover and Client Access servers when redirecting legacy users to a legacy server.

All client connections will be redirected, including Exchange ActiveSync, Outlook Web App, POP3, and IMAP4. After the legacy host name has been configured, users will be able to access their mailbox regardless of whether it's on Exchange 2007 or Exchange 2013. If you're upgrading from Exchange 2007 to Exchange 2013, Availability service requests will also be redirected.

You need to create a public DNS record for the legacy.contoso.com host name to point to the external IP address of your Exchange 2007 server. The following is an example of the DNS record that you'd create with your public DNS provider, such as GoDaddy.

importantImportant:
You might need to make changes to your firewall to support this new legacy host name. You might need to add new firewall rules, add an external IP address for your Exchange 2007 server, or make other configuration changes. If your organization has a network management group, a security review process, or change management process, you may need to request permission to perform these changes or have someone else make them for you.

Host name DNS record type Value

Legacy.contoso.com

A

172.16.10.10

172.16.10.10

To verify that you've successfully configured your public DNS records, do the following:

  1. Open a command prompt and run nslookup.exe.
  2. Change to a DNS server that can query your public DNS zone.
  3. In nslookup, look up the record for the legacy.contoso.com host name you created. Verify that the IP address that's returned matches the external IP address of your Exchange 2007 server.

Having problems? Ask for help in the Exchange forums. Visit the forums at: Exchange Server, Exchange Online, or Exchange Online Protection

Our next step according to the Exchange deployment assistance is to.... excuse me?  Disable IPv6? 

If you've been a SBSer for any number of years you'll know is is a step that one shouldn't do on a SBS box  (see http://blogs.technet.com/b/sbs/archive/2008/10/24/issues-after-disabling-ipv6-on-your-nic-on-sbs-2008.aspx )

So, I'm going to first bug this in connect as I don't think this is a valid step and then I'm going to ignore it and go onto the next step

Ignore the following and click next on the instructions

Disable IPv6 on Exchange 2007 servers

Estimated time to complete: 5 minutes

Before you install Exchange 2013, you might need to disable IPv6 on some of your Exchange 2007 servers. Some connections between Exchange 2007 and Exchange 2013 don't work correctly when IPv6 is enabled and an Exchange 2007 server has both the Mailbox and Client Access server roles installed.

If you have Exchange 2007 servers that have both the Mailbox and Client Access server roles installed, complete the following steps on each of those servers to disable IPv6 on them.

Do the following on each Exchange 2007 server in your organization that has both the Mailbox and Client Access server roles installed:

  1. Open the Registry Editor on your Exchange 2007 Client Access server.
  2. Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters\
  3. If the DisabledComponents entry doesn’t exist, do the following to create it:
    1. In the Edit menu, click New, and then click DWORD (32-bit) Value.
    2. Type DisabledComponents and then press enter.
  4. Double-click DisabledComponents.
  5. In the Value data field, enter 0xFFFFFFFF.
  6. Click OK.
  7. Reboot the server.

To verify that you've correctly set the DisabledComponents in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters\, do the following:

  1. Open a Windows command prompt.
  2. Run the following command:

 

  1. Reg Query HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters /v DisabledComponents
    

If the DisabledComponents entry is properly set, you'll see the following:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters
    DisabledComponents    REG_DWORD    0xFFFFFFFF

If you see a value other than 0xFFFFFFFF for the DisabledComponents entry, or if you receive the error ERROR: The system was unable to find the specified registry key or value., the entry isn't set correctly. Verify that you placed the DisabledComponents entry in the correct path and that it's spelled correctly.

Next step is to check the Offline Address book

Configure default offline address book

 

Estimated time to complete: 5 minutes or longer, depending on the number of mailbox databases in your organization

Before you install Exchange 2013, you need to make sure that all of the existing Exchange mailboxes in your organization are assigned a default offline address book (OAB). If you don't do this, any mailbox that isn't assigned a default OAB when Exchange 2013 is installed will automatically download the new OAB generated by Exchange 2013. If you have hundreds or thousands of mailboxes, this could cause significant network traffic and server load.

The steps below show you how to assign a default OAB to Exchange mailbox databases. Assigning a default OAB to a mailbox database has two advantages:

  • Mailboxes stored in a mailbox database will inherit the OAB assigned to a mailbox database if the mailbox itself has no OAB assigned. This allows you to assign an OAB to many mailboxes without having to individually update each mailbox.
  • When the mailbox is moved from an existing Exchange server to Exchange 2013, the mailbox will automatically begin using the new Exchange 2013-generated OAB if the mailbox itself isn't assigned an OAB.

Important   You need to run the commands below on your Exchange 2007 and Exchange 2010 servers separately. The Get-MailboxDatabase and Set-MailboxDatabase cmdlets running on an Exchange 2007 server can't configure mailbox databases running on Exchange 2010 and vice versa.

  1. Open the Exchange Management Shell on your Exchange server.
  2. Run the following command to retrieve a list of OABs.
    Get-OfflineAddressBook
    
  3. Run the following command to view all the mailbox databases (except Exchange 2013 mailbox databases) in your organization and the OABs assigned to them.
    Get-MailboxDatabase | Format-Table Name, Server, OfflineAddressBook -Auto
    
  4. Run the following command to view all the Exchange 2007 or Exchange 2010 mailbox databases in your organization and the OABs assigned to them.
    Get-MailboxDatabase | Format-Table Name, Server, OfflineAddressBook -Auto
    (isn't that the same command we did above?  It looks the same to me?)
  5. For every mailbox database that doesn't have an OAB assigned, assign an OAB from the list you retrieved earlier. You can either set the OAB on each mailbox database individually or set the OAB on all mailbox databases at once. Use the command below that best suits your requirements.
    • To set the OAB on each mailbox database individually, run the following command. The command example uses "Sales Employees" for the mailbox database name on the Ex2007 server, and the "Default Offline Address Book" for the name of the OAB.
      Set-MailboxDatabase "Ex2007\Sales Employees" -OfflineAddressBook "Default Offline Address Book"
      (We're SBS, we probably don't have a problem with this step)
    • To set the same OAB on all mailbox databases at once, run the following command. The command example uses "Default Offline Address Book" for the name of the OAB.
      warningWarning:
      The following command will overwrite the OAB assigned to every mailbox database in your organization. If you want to verify the command has the intended effect, run it with the WhatIf switch parameter first.
      Get-MailboxDatabase | Set-MailboxDatabase -OfflineAddressBook "Default Offline Address Book"
      

To verify that every mailbox database in your organization is assigned a default OAB, run the following command. Every mailbox database should have an OAB listed in the OfflineAddressBook column.

Get-MailboxDatabase | Format-Table Name, Server, OfflineAddressBook -Auto

So far so good... on to the next step

  Blogging my way through a proof of concept migration from SBS 2008 to Essentials 2012 R2 series will be a SMB kitchen project whitepaper.  More about the SMBKitchen project at - http://www.thirdtier.net/enterprise-solutions-for-small-business

Posted Wed, Jan 22 2014 0:07 by bradley | with no comments
Filed under:
  1. Log on to the second server as an administrator.
  2. Open your Internet browser, and then navigate to the Exchange Server Deployment Assistant website  - Susan note:  You'll probably want to disable IE enhanced security otherwise you'll be clicking through a ton of blocked social stuff.

  3. Click On-Premises Only.

  4. Click the new installation option for the version of Exchange Server that you will install.

    noteNote

    If you are migrating from an installation of Windows Small Business Server, you should select the appropriate upgrade option that covers the migration steps.

    You may want to actually do this wizard not from the server itself but from a workstation....

    In my case I'm

    Client Access and Mailbox server installation location

     

    Are you planning to install the Client Access and Mailbox server roles on the same or a different server?

    Exchange 2013 has two server roles: Mailbox and Client Access. During deployment, you can install the server roles on the same server or on different servers. Where you install these roles depends on the number of servers available, their physical capacities, and the layout of your network. For example, you might want to dedicate certain servers to specific functions. For more information, see Exchange 2013 System Requirements.

    Same server

    Different servers

     

    Doing this on the same server.

    I'm not Are you running a disjoint namespace?  Answer no.

    Do you have an existing Edge Transport server? Answer no.

    Also keep in mind:

    Exchange 2013 and Exchange Online support the following minimum versions of Microsoft Outlook and Microsoft Entourage for Mac:

    Outlook 2003 won't cut it.  You need later versions.


    And don't forget

    To prepare the Exchange 2007 servers in your organization for coexistence with for Exchange 2013, you’ll need to install Update Rollup 10 (RU10) for Exchange 2007 Service Pack 3 (SP3) on all the Exchange 2007 servers in your organization before you can install Exchange 2013. The service pack is available in the Microsoft Download Center at Exchange Server 2007 Service Pack 3. The update rollup is available in the Microsoft Download Center at Update Rollup 10 for Exchange Server 2007 Service Pack 3 (KB2788321). (Although this topic isn't an exact match, you can reference it for steps about how to upgrade to Exchange 2007 SP3: How to Upgrade to Exchange 2007 SP1)

    Also, in order for Exchange 2013 to coexist with previous versions of Exchange, all your Exchange 2013 servers must be running Cumulative Update 2 (CU2) for Exchange 2013. To download Exchange 2013 CU2, see Cumulative Updates for Exchange 2013.

     

Posted Tue, Jan 21 2014 23:53 by bradley | with no comments
Filed under:

If you are migrating from a SBS domain this next step should already be done for you...but just in case let's check it out.

Before you install the Exchange Server on the second server, you must first add the current administrator account to the Enterprise Admins group.

  1. Log on to Windows Server Essentials as an administrator.

  2. Run Windows PowerShell as an administrator.

  3. At the Windows PowerShell command prompt, type Add-ADGroupMember ‘Enterprise Admins’ $env:username, and then press Enter

Coming over from a SBS domain

You should see this already in place

 

Now at this point when we're about to start installing Exchange TAKE A BACKUP.  A really really good backup.  And I'm not talking about taking a snapshot (and as an aside, when did they rename snapshots checkpoints in R2?  You don't want to take a snapshot or a checkpoint on a Domain controller - and trust me it can mangle SharePoint when you attempt to roll it back - so don't do it.

But stop right here and ensure you have a way to roll yourself back.

Posted Tue, Jan 21 2014 23:42 by bradley | with no comments
Filed under:

Taking a break of the proof of concept of the migration to reset my twitter RSS feeds

http://www.rssitfor.me/getrss?name=

To follow a RSS feed simply put in the name of the twitter-er after the equals.  

In doing so I also found that my RSS reader that sits inside of Outlook, intravnews doesn't look to healthy even though it still works just fine.

I may need to start looking around for another rss reader

http://blogs.msdn.com/b/mthree/archive/2013/03/15/rss-031513.aspx

 

Posted Mon, Jan 20 2014 22:46 by bradley | with no comments
Filed under:

At this time one can only install Exchange 2013 on Windows Server 2012 as it's not yet supported on R2.  We're waiting for SP1 of Exchange 2013 before it's supported.

So I've installed Windows Server 2012

And then I need to join it to my existing domain

http://technet.microsoft.com/en-us/library/jj200172.aspx

You must install Exchange Server on a second server that is running a version of the Windows Server operating system that officially supports running Exchange Server 2010 or Exchange Server 2013. You must then join the second server to the Windows Server Essentials domain.

For information about how to join a second server to the Windows Server Essentials domain, see Join a second server to the network.

In order to list a TS server in the RWA window you want to follow the connect instructions.  The ONLY exception to this at this time is Multipoint 2012.  At this time you want to manually join MulitPoint due to a bug that's being worked on (see more info http://social.technet.microsoft.com/Forums/windowsserver/en-US/8ba41231-62c1-4d88-a812-422e7c7fa213/can-multipoint-server-2012-join-2012r2-essentials-with-client-connector-and-use-all-functions-?forum=winserveressentials )

In a virtual setting you may need to edit the DNS entries on the test servers to get them to pick up the right dns from the play server.

In my test run because I want to install Exchange first and migrate it over before I tackle the Essentials I don't want to run the connect wizard at this time. 

For now I'll just manually join my member server to the SBS 2008 domain.  I'll go to control panel, then to system and manually change the server name and the domain in here and reboot.

In my case I'm going from Exchange 2007 to Exchange 2013 so I've found some reading material...

Planning and migrating a small organization from Exchange 2007 to 2013 (Part 1) :: Migration & Deployment :: Exchange 2013 Articles :: Articles & Tutorials :: MSExchange.org:
http://www.msexchange.org/articles-tutorials/exchange-server-2013/migration-deployment/planning-and-migrating-small-organization-exchange-2007-2013-part1.html

Enough for tonight... I'll be installing Exchange tomorrow

Blogging my way through a proof of concept migration from SBS 2008 to Essentials 2012 R2 series will be a SMB kitchen project whitepaper.  More about the SMBKitchen project at - http://www.thirdtier.net/enterprise-solutions-for-small-business

 

Posted Sun, Jan 19 2014 23:07 by bradley | with no comments
Filed under:

If you are planning to migrate from an on premises Exchange to hosted email there's a couple of ways to move the email.  Way one is to use a service from www.migrationwiz.com to move the email over.  Price is reasonable.

Way two is to follow the documentation for a cutover exchange as noted in the documentation:

Migrate email to Microsoft Office 365


If you have chosen to use Microsoft Office 365 as the email solution for your domain, follow the guidance in Migrate All Mailboxes to the Cloud with a Cutover Exchange Migration to start the email migration to Office 365. We recommend that you complete the email migration before you install Windows Server 2012 R2 Essentials.

noteNote
The step to remove the on-premises Exchange Server on the Source Server is mandatory if you intend to integrate Windows Server 2012 R2 Essentials with Office 365. For information about how to migrate Exchange Server public folders to Office 365, see the blog post Microsoft Exchange 2013 Public Folders Migration Scripts for Office 365.

 

After you install , you should turn on the Office 365 Integration feature in Windows Server 2012 R2 Essentials by running the Integrate with Microsoft Office 365 task.

 

 

ImportantImportant
To allow the Office 365 migration tool to connect to the Exchange Server that is running on the Source Server, you must enable RPC over HTTP on the Source Server. For information about how to enable RPC over HTTP, see How to Deploy RPC over HTTP for the First Time in Small Business Server 2003 (Standard or Premium). If you cannot successfully run the Office 365 migration tool after you enable RPC over HTTP, view the ValidPorts setting in the registry at HKEY_LOCAL_MACHINE\Software\Microsoft\Rpc\RpcProxy, and make sure that the fully qualified domain name (FQDN) for the Source Server is listed. If the FQDN is not listed, add it manually by using the following example:

 

remote. contoso.com:6001-6002;remote. contoso.com:6004 (replace contoso with the name of your domain).

 

Posted Sun, Jan 19 2014 23:05 by bradley | with no comments
Filed under:

For information about how to migrate email to another on-premises Exchange Server, see Integrate an On-Premises Exchange Server with Windows Server 2012 Essentials <http://technet.microsoft.com/en-us/library/jj200172.aspx>. We recommend that you set up the new on-premises Exchange Server after you install Windows Server 2012 R2 Essentials, and then finish the email migration before demoting the Source Server

http://technet.microsoft.com/en-us/library/dn408634.aspx

So I'm confused.  I would think you'd want to move email FIRST before installing the Essentials server, not the other way around.  You see after you move the fsmo roles on your SBS box you start the 21 day countdown window starting and I would think it would make more sense to move your email first - either to premises server OR to cloud or Kerio or whatever and THEN you migrate the DCs.

Hang loose while I get clarification as to which step is next.

Blogging my way through a proof of concept migration from SBS 2008 to Essentials 2012 R2 series will be a SMB kitchen project whitepaper.  More about the SMBKitchen project at - http://www.thirdtier.net/enterprise-solutions-for-small-business

Posted Sun, Jan 19 2014 0:39 by bradley | with no comments
Filed under:
More Posts Next page »