Microsoft Office 365 Jump Start

The Microsoft Office 365 Jumpstart series provides an excellent perspective of the overall value Office 365 provides to modern organizations in terms of productivity, access, familiarity, security, control and reliability.

Microsoft Deployment Toolkit (MDT) 2012 Beta 1 Available

Microsoft has just released as a public beta the newest version of Microsoft Deployment Toolkit (MDT) 2012 with a few important updates:

  • Supporting System Center Configuration Manager (SCCM) 2012.
  • Using Lite Touch Installation (LTI), great improvements in the client side look-n-feel.
  • Also for LTI, behind-the-scenes enhancements for partitioning, UEFI (Unified Extensible Firmware Interface), and user state migration.
  • Some minor bugs fixed.

MDT 2012 Requirements

Same as MDT 2010:

  • Windows Automated Installation Kit (WAIK) 2.0. You can download it from here.
    Note: The download page indicates that the WAIK version is “1”; but don’t worry, the actual version is 2.0.
  • MSXML 6.0
  • PowerShell.
  • .Net Framework 3.5 SP1. Available for download here.
    Note: Even though .Net Framework 2.5 SP1 is not a requirement for MDT 2010 installation; one of its features, User-Driven Installation (UDI), does requires the latest Microsoft Framework installed.

MDT 2012 Look-n-Feel

For what I’ve seen so far, the user experience of the Deployment Workbench console is pretty much the same.

mdt2012a01

mdt2012a02

MDT 2012 Beta 1 Download

The beta is available in this link from Microsoft Connect,

Microsoft Office 365 Deployment Readiness Tool

The Office 365 Deployment Readiness Tool provides analysis of your on-premises environment in preparation for an Office 365 enterprise deployment. The readiness tool is integrated with the guidance provided in the web edition of the Microsoft Office 365 Beta Deployment Guide.

Download HERE

I run the tool in my test environment. See below the results

Microsoft Office 365 Deployment Readiness Tool

Beta

Office 365 Deployment Resource Kit build 01.00.00.00
modgClick here for the Microsoft Office 365 Beta Deployment Guide for Enterprises

Domains

modg Deployment Guide: Adding Your Domain(s) to Office 365
All email domains discovered in your environment:
Total: 3

All primary email domains discovered:
Total: 2

Primary email domain suffixes with greater than 50 users:
wardvissers.local
Total: 1


User Identity and Account Provisioning

Active Directory

Statistics

Total number of domains discovered in your forest: 1
Estimated total number of users: 59
Estimated total number of contacts: 0
Estimated total number of groups: 54
Estimated total number of mailboxes: 53
Estimated total number of objects for Directory Synchronization: 113
note
Note: Filters were applied to obtain the above object counts for an Office 365 deployment.

Forest and Domains

The following domains were discovered in your Active Directory forest:
wardvissers.local
Total: 1

Trusts

No forest trusts found
green
You may deploy AD FS 2.0 and Directory Synchronization without multi-forest constraints

Schema and Forest/Domain Functionality Levels

Active Directory forest schema level: Windows Server 2008 R2
Exchange schema level: Exchange Server 2010 SP1
Domain Functionality:Windows Server 2008 R2
Forest Functionality:Windows Server 2008 R2
Domain Controller Functionality:Windows Server 2008 R2
green
It appears that your Active Directory schema is prepared for Exchange Rich Coexistence
modg Deployment Guide: Exchange Rich Coexistence Requirements


Active Directory Cleanup

modg Deployment Guide: Active Directory Cleanup

samaccountname (user name) Attribute

green
Character length test passed
green
Unsupported character test passed

givenname (first name) Attribute

green
Character length test passed
green
Unsupported character test passed

sn (last name) Attribute

green
Character length test passed
green
Unsupported character test passed

displayname Attribute

green
Character length test passed
green
Unsupported character test passed

mail (email address) Attribute

green
Character length test passed
green
Unsupported character test passed
green
No duplicates found

mailnickname Attribute

green
Character length test passed
green
Unsupported character test passed

proxyaddresses (email addresses) Attribute

green
No duplicates found
green
Unsupported character test passed

Directory Synchronization

Object count assessment:
Estimated number of objects for Directory Synchronization (entire forest): 113
modg Deployment Guide: Object Count Considerations
Enterprise Admin rights:
green
It appears that you are an enterprise admin
Directory Synchronization admin requirement met!
modg Deployment Guide: Directory Synchronization Required Permissions
Active Directory recycle bin:
warning
Active Directory recycle bin is enabled in your forest this may impact your total object count quota for Directory Synchronization.


Office 365 Single Sign On and Identity

AD FS 2.0 Directory Cleanup Check:

UserPrincipalName (logon ID for Office 365) Attribute

fyi
Update values once you have verified your organization does not have any other application dependencies on the UserPrincipalName attribute.
modg Deployment Guide: Active Directory Cleanup
green
Unsupported characters test passed
green
Spaces in logon value test passed
green
Unicode character test passed
note
Note: All Unicode characters will be converted to underscores (_) in the UserPrincipalName field.
green
No UserPrincipalName duplicates found
warning
Discovered users without a user logon name (blank value) for UserPrincipalName
You will need to provide each user a UserPrincipalName in order for these users to sign into Office 365.
fyi
Below is a list of your UserPrincipalName domain suffixes in use:
wardvissers.local
Total: 1
note
Note: During the Office 365 Beta only one namespace (root and child domains) per AD FS 2.0 farm
Example contoso.com and root.contoso.com would require 1 AD FS 2.0 farm and fabrikam.com would require an additional AD FS 2.0 farm

fyi
Password length per domain:

wardvissers.local = 7

Exchange Online

Discovered Exchange Server(s) on-premises:
Estimated total number of Exchange Servers: 1

Statistics:

Estimated total number of users with default mailbox size (True): 53
Estimated total number of users with larger than default mailbox size (False): 0
Estimated total number of objects with Exchange organization level quota: 6


Lync Online

Lync user assessment:
Estimated total number of users leveraging Office Communications/Lync on-premises: 2
Sip domains:
fyi
The following sip domains were discovered:
wardvissers.local
Total: 1

SharePoint Online

User object count assessment:
green
The number of user objects in your forest is supported.
modg Deployment Guide: Object Count Considerations

Client and End User Experience

modg Deployment Guide: Rich Experience Client Requirements

Summary of client computer readiness (Office 365 single sign-on and rich client checks):

warning
Below is an estimate of computer operating systems NOT ready for Office 365 rich client experience:
Total: 0
green
Below is an estimate of computer operating systems ready for Office 365 rich client experience:
Windows XP Service Pack 3: 3
Windows 7 Service Pack 1: 3
Total: 6

Network


fyi
IP Configuration:

IPv4 Address. . . . . . . . . . . : 192.168.150.60
IPv4 Address. . . . . . . . . . . : 192.168.150.1
Subnet Mask . . . . . . . . . . . : 255.255.255.255
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
Default Gateway . . . . . . . . . : 192.168.150.254

fyi
Trace route to your default gateway:

Tracing route to 192.168.150.254 over a maximum of 30 hops
1 1 ms 2 ms 2 ms 192.168.150.254

fyi
Trace Route test to Exchange Online:

Tracing route to outlook.com [65.55.94.40]
over a maximum of 30 hops:
1 3 ms 2 ms 1 ms 192.168.150.254
2 * 24 ms 25 ms 82.169.11.254
3 25 ms 26 ms 26 ms 195.69.145.20
4 145 ms 146 ms 144 ms 10.14.234.234
5 * * * Request timed out.
6 * * * Request timed out.
7 10.14.234.234 reports: Destination net unreachable.
Trace complete.
fyi

For additional tests utilize the Exchange Remote Connectivity Analyzer

Port Query Tests:

modg Deployment Guide: Ports and Protocols
green
portal.microsoft.com
Made a TCP 443 connection to portal.microsoftonline.com
green
Outlook.com
Made a TCP 443 connection to outlook.com
green
Outlook.com IMAP
Made a TCP 993 IMAP connection to outlook.com
green
Outlook.com POP
Made a TCP 995 POP connection to outlook.com
green
Outlook.com SMTP
Made a SMTP TCP 587 connection to outlook.com
green
Active Directory Federation Services End Point
Made a TCP 443 connection to nexus.microsoftonline.com
green
Directory Synchronization End Point
Made a TCP 443 connection to adminwebservice.microsoftonline.com
green
Office 365 PowerShell End Point
Made a TCP 443 connection to ps.microsoftonline.com
green
Outlook.com PowerShell End Point
Made a TCP 443 connection to ps.outlook.com
green
Office 365 Community End Point
Made a TCP 80 connection to community.office365.com
green
Lync Online SIP Connection
Made a TCP 443 connection to sipdir.online.lync.com
green
Lync Online Federation
Made a TCP 5061 connection to sipfed.online.lync.com
Domain Name System (DNS) name records checks:
fyi
Found the following MX DNS record(s):
Server: localhost
Address: 127.0.0.1
wardvissers.local
primary name server = ward-dc01.wardvissers.local
responsible mail addr = hostmaster.wardvissers.local
serial = 761
refresh = 900 (15 mins)
retry = 600 (10 mins)
expire = 86400 (1 day)
default TTL = 3600 (1 hour)
Information Gathered On:
WARD-DC01
Date: za 07-05-2011
Start Time: 18:19
End Time: 18:21

GAL Photos in Exchange 2010 and Outlook 2010

With Microsoft Exchange 2010 and Outlook 2010 & Lync & Sharepoint 2010 you can finally get photos into your global address list (GAL) and see just who’s who on your emails. You can do this on 2 way’s

1. Using Powershell Smile

    A minor schema change

    First stop, the AD Schema. A minor schema modification is required to flip the thumbnailPhoto attribute to make it replicate to the Global Catalog.

    1. If you haven’t registered the Schema MMC snap-in on the server you want to make this change on, go ahead and do so using the following command:

      Regsvr32 schmmgmt.dll

    2. Fire up a MMC console (Start -> Run -> MMC) and add the Schema snap-in

    3. In the Active Directory Schema snap-in, expand the Attributes node, and then locate the thumbnailPhoto attribute. (The Schema snap-in lists attributes by its ldapDisplayName).

    4. In the Properties page, select Replicate this attribute to the Global Catalog, and click OK.

      Figure 1: Modifying the thumbnailPhoto attribute to replicate it to Global Catalog

      Loading pictures into Active Directory

      Now you can start uploading pictures to Active Directory using the Import-RecipientDataProperty cmdlet, as shown in this example:

      Import-RecipientDataProperty -Identity "Ward VIssers" -Picture -FileData ([Byte[]]$(Get-Content -Path "C:\pictures\wardvissers.jpg" -Encoding Byte -ReadCount 0))

      To perform a bulk operation you can use the Get-Mailbox cmdlet with your choice of filter (or use the Get-DistributionGroupMember cmdlet if you want to do this for members of a distribution group), and pipe the mailboxes to a foreach loop. You can also retrieve the user name and path to the thumbnail picture from a CSV/TXT file.

      2. Using a Free tool like Outlook Photos from Exclaimer

      Download the Tool HERE

      The tool is easy to use Smile.

      Prerequisites

      User Preferences

        Domain user – The logged in user’ account is required to be an Active Directory account.

        Domain computer – The computer the user is logged into needs to be joined to an Active
        Directory domain.

        Active Directory permissions – The logged in user must have permission to upload photos to the required Active Directory accounts. (Alternate credentials can be supplied or control of the thumbnailPhoto field can be delegated to the logged in user.)

      Operating System

      • Windows Server 2003 x86 (including all service pack levels).
      • Windows Server 2003 R2 x86 and x64 (including all service pack levels).
      • Windows Server 2008 x86 and x64 (including all service pack levels).
      • Windows Server 2008 R2 x86 and x64 (including all service pack levels).
      • Windows Small Business Server 2003 (including all service pack levels).
      • Windows Small Business Server 2008.
      • Windows Small Business Server 2011.
      • Windows XP x86 and x64 (including all service pack levels).
      • Windows Vista x86 and x64 (including all service pack levels).
      • Windows 7 x86 and x64 (including all service pack levels).

      Other Software

      Microsoft Outlook 2010 x86 and x64

      Microsoft .NET Framework 3.5 SP1

      Microsoft Exchange 2010 RTM and above

      Active Directory

      You must be logged into an Active Directory domain to run the application.

      Active Directory Forest
      Domain and Forest functional level of Windows Server 2008 and above.
      For Domain or Forest functional level of Windows Server 2003, the Windows Server 2008 Forest preparation must first be complete.

      Screenshots

        image image

      Microsoft Virtualization for VMware Professionals Jump Start

      The “Microsoft Virtualization for VMware Professionals” Jump Start is specially tailored for VMware and Microsoft virtualization technology pros. This cutting-edge course features expert instruction and real-world demonstrations of Hyper-V, many components of the System Center Suite, including VMM 2012, and a myriad of VDI solutions. This course is designed for Data Center Managers, IT Professionals, IT Decision Makers, Network Administrators, Storage/Infrastructure Administrators & Architects. Expert IT infrastructure consultant, Corey Hynes, and Microsoft Technical Evangelist, Symon Perriman, leveraged an engaging "team teaching" approach which makes the class as entertaining as it is educational Smile

      Virtualization Jump Start (01): Virtualization Overview
      Virtualization Jump Start (02): Differentiating Microsoft & VMware
      Virtualization Jump Start (03a): Hyper-V Deployment Options & Architecture | Part 1
      Virtualization Jump Start (03b): Hyper-V Deployment Options & Architecture | Part 2
      Virtualization Jump Start (04): High-Availability & Clustering
      Virtualization Jump Start (05): System Center Suite Overview with focus on DPM
      Virtualization Jump Start (06): Automation with Opalis, Service Manager & PowerShell
      Virtualization Jump Start (07): System Center Virtual Machine Manager 2012
      Virtualization Jump Start (08): Private Cloud Solutions, Architecture & VMM Self-Service Portal 2.0
      Virtualization Jump Start (09): Virtual Desktop Infrastructure (VDI) Architecture | Part 1
      Virtualization Jump Start (10): Virtual Desktop Infrastructure (VDI) Architecture | Part 2
      Virtualization Jump Start (11): v-Alliance Solution Overview
      Virtualization Jump Start (12): Application Delivery for VDI

      Download all the Video’s:
      Video: WMV | WMV (ZIP) | PSP
      Audio: WMA | MP3

      Now only finding some spare time to watch’s these video’s Winking smile

      DPM 2010 Enabling/Disabling co-location of data on Tape

      With this feature, you can achieve better tape utilization by co-locating data from multiple protection groups with similar retention range. This feature is disabled by default. You can use following PowerShell commands to enable and disable tape co-location.

      Enable Tape co-location:

      Set-DPMGlobalProperty -DpmServer <DPM Server Name> -OptimizeTapeUsage $true

      After data co-location has been enabled, DPM will check for the following conditions before allocating a tape:

      1. The expiry date of the current dataset should fall in between the following dates:
        Upper bound: furthest expiry date among all the datasets on the tape – (furthest expiry date among all the datasets on the tape – current date) * TapeExpiryTolerance
        Lower Bound: furthest expiry date among all the datasets on the tape + (furthest expiry date among all the datasets on the tape – current date) * TapeExpiryTolerance.
      2. Current time should be less than first backup time of the dataset on the media + TapeWritePeriodRatio * RetentionRangeOfFirstDataset.

      A dataset will be collocated only if both the above conditions are true.

      When you add the value to the registry, set the DWORD to be the actual percentage in decimal. The Default is 17 percent if that value is not present. Most likely you need to increase that value to a higher percentage and in some cases you need to set it to 100 in order for tape co-location to work as desired.

      TapeWritePeriodRatio – Indicates the number of days for which data can be written on to a tape as a fraction between 0 and 1. The default value is 0.15 – meaning by default, we will write to the same tape for 15% of the retension range period specified for each PG.

      TapeWritePeriodRatio is not a registry. It is a global property for the DPM which needs to be set using DPM CLI command. Here is the command to set it:

      Set-DPMGlobalProperty –DPMServerName <dpm server name> -TapeWritePeriodRatio <fraction>

      EXAMPLE, to set the write period ratio to 50%, use the following command.

      Set-DPMGlobalProperty –DPMServerName MY-DPMSEREVR -TapeWritePeriodRatio .50

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

      System Center Virtual Machine Manager 2012 Beta Evaluation

      System Center Virtual Machine Manager 2012 delivers industry leading fabric managment, virtual machine management and services deployment in private cloud environments. Virtual Machine Manager 2012 offers key new features that include hypervisor creation and management, network management, storage management, private cloud creation, self-service usage and service creation. It features deep investments in server application virtualization, service design and service modeling all of which can be used to efficiently offer an on-premises private cloud.

      Feature Summary

      • Fabric Management
        • Hyper-V and Cluster Lifecycle Management – Deploy Hyper-V to bare metal server, create Hyper-V clusters, orchestrate patching of a Hyper-V Cluster
        • Third Party Virtualization Platforms – Add and Manage Citrix XenServer and VMware ESX Hosts and Clusters
        • Network Management – Manage IP Address Pools, MAC Address Pools and Load Balancers
        • Storage Management – Classify storage, Manage Storage Pools and LUNs
      • Resource Optimization
        • Dynamic Optimization – proactively balance the load of VMs across a cluster
        • Power Optimization – schedule power savings to use the right number of hosts to run your workloads – power the rest off until they are needed
        • PRO – integrate with System Center Operations Manager to respond to application-level performance monitors
      • Cloud Management
        • Abstract server, network and storage resources into private clouds
        • Delegate access to private clouds with control of capacity, capabilities and user quotas
        • Enable self-service usage for application administrator to author, deploy, manage and decommission applications in the private cloud
      • Service Lifecycle Management
        • Define service templates to create sets of connected virtual machines, os images and applica tion packages
        • Compose operating system images and applications during service deployment
        • Scale out the number of virtual machines in a service
        • Service performance and health monitoring integrated with System Center Operations Manager
        • Decouple OS image and application updates through image-based servicing
        • Leverage powerful application virtualization technologies such as Server App-V

      System Requirements

      • Supported Operating Systems:Windows 7 Enterprise;Windows 7 Professional;Windows 7 Ultimate;Windows Server 2008 R2;Windows Server 2008 R2 Datacenter;Windows Server 2008 R2 Enterprise
        • Windows Server 2008 R2 (full installation) Standard, Enterprise, Datacenter x64
        • Windows 7 Professional, Enterprise, Ultimate x32, x64
        • Windows Remote Management (WinRM) 2.0
        • Windows PowerShell 2.0
        • Microsoft .NET Framework 3.5 Service Pack 1 (SP1)
        • Windows Automated Installation Kit (AIK) for Windows 7
        • SQL Server 2008 or SQL Server 2008 R2 Standard, Enterprise, and Datacenter
        • Windows Deployment Services (WDS) – (Version on Windows Server 2008 R2)
        • Windows Software Update Services (WSUS) 3.0 SP2 64bit

      Download System Center Virtual Machine Manager 2012 Beta Evaluation HERE

      Rollup 3 for Exchange Server 2010 Service Pack 1

      exchange 2010

       

      Microsoft releasd Update Rollup 3 for Exchange Server 2010 SP1 that  resolves the following issues that are described in the following Microsoft Knowledge Base (KB) articles:

      2506998 A call is disconnected when transferring the call from the main auto attendant to an auto attendant that has a different language configured in an Exchange Server 2010 environmen

      2497682 The store.exe process crashes when you try to unmount an active copy of a mailbox database that is hosted by a mailbox server in an Exchange Server 2010 SP1 environmen

      2497669 A meeting request cannot be opened after you disable the "Display sender’s name on messages" option in the EMC on an Exchange Server 2010 server

      2494798 Certain email messages cannot be downloaded when you log on to an Exchange Server 2010 mailbox by using an IMAP4 client applicatio’n

      2494389 Unnecessary events are logged in the Application log when you run the "Test-EcpConnectivity" cmdlet in an Exchange Server 2010 environment

      2489822 "The Mailbox you are trying to access isn’t currently available" error when you use OWA Premium to try to delete an item that is in a shared mailbox

      2489713 Exchange Server 2010 SP1 supports the remote archive feature after an update changes Outlook cookies name

      2489602 The "Get-FederationInformation" cmdlet cannot query federation information from an external Exchange organization in an Exchange Server 2010 environment

      2487852 "You do not have sufficient permissions. This operation can only be performed by a manager of the group." error message when you try to change the "ManagedBy" attribute in an Exchange Server 2010 SP1 environment

      2487501 The body of an email message is empty when you try to use an IMAP client application to read it in an Exchange Server 2010 environment

      2484862 You cannot read an email message by using an IMAP client in an Exchange Server 2010 environment’

      2482471 A content search fails in an IMAP client application that connects to an Exchange Server 2010 mailbox

      2482103 It takes a long time to expand a distribution list by using EWS in an Exchange Server 2010 environment

      2482100 You cannot create or update an inbox rule that specifies the "NoResponseNecessary" value by using EWS in an Exchange Server 2010 environment

      2481283 Various issues occur after you use Outlook to sign and then forward an email message in an Exchange Server 2010 environment

      2479875 The Microsoft Exchange Mailbox Replication Service service crashes when you run the "New-MailboxImportRequest" cmdlet to import a .pst file into a mailbox in an Exchange Server 2010 environment

      2479227 Forwarding rule does not function and the EdgeTransport.exe process crashes on an Exchange Server 2010 server

      2476973 Event ID 2168 is logged when you try to back up Exchange data from a DAG in an Exchange Server 2010 SP1 environment

      2469341 Various issues occur after you forward a signed email message by using Outlook in online mode in an Exchange Server 2010 environment

      2468514 OWA 2010 removes Calendar links that you add into multiple calendar groups by using Outlook 2010 calendar

      2467565 You cannot install an update rollup for Exchange Server 2010 with a deployed GPO that defines a PowerShell execution policy for the server to be updated

      2464564 You cannot change your password if the user name that you type in OWA is in UPN format when you enable Exchange Server 2010 SP1 Password Reset Tool

      2463858 A request to join a distribution group does not contain the distribution group name in an Exchange Server 2010 SP1 environment

      2463798 Users may experience a decrease in performance in Outlook or in OWA when you use IMAP4 to access the calendar folder in an Exchange Server 2010 SP1 environment

      2458543 A memory leak occurs in the Exchange RPC Client Access service on Exchange Server 2010 servers

      2458522 Entries disappear from a junk email blocked list or a junk email safe list after you install Exchange Server 2010 SP1

      2457868 "HTTP Error 400 Bad Request" error message when you use OWA in Exchange Server 2010 SP1 to receive instant messages by using Internet Explorer 9

      2457688 Error message when you try to add an external email address to the safe sender list in OWA in an Exchange Server 2010 SP1 environment

      2457304 You receive a synchronization failed email message when you synchronize your mobile device by using ActiveSync on an Exchange Server 2010 mailbox

      2451101 7BIT is not in quotation marks when you use the "FETCH (BODYSTRUCTURE)" command to request for a specific message in an Exchange Server 2010 environment

      2447629 vent ID 4999 is logged when the Exchange Mail Submission Service crashes intermittently on an Exchange Server 2010 Mailbox server

      2445121 memory leak occurs in the Microsoft.Exchange.Monitoring.exe process when you run the "Test-OwaConnectivity" cmdlet or the "Test-ActiveSyncConnectivity" cmdlet in the EMS on an Exchange Server 2010 server

      2443688 Event ID 10003 and Event ID 4999 are logged when the EdgeTransport.exe process on an Exchange Server 2010 server crashes

      2432494 You cannot view the mailbox database copies that are hosted on certain Mailbox servers by using the Exchange Management Console after you install Exchange Server 2010 SP1

      2426952 You cannot remove a mailbox database copy from a database on an Exchange Server 2010 server

      2424801 The Microsoft Exchange Service Host service on an Exchange Server 2010 server crashes

      2423754 The recipient response status is incorrect after you add another user to an occurrence of a meeting request in an Exchange Server 2010 environment

      2417084 A public folder disappears from the Public Folder Favorites list of an Exchange Server 2010 mailbox

      2410571 A RBAC role assignee can unexpectedly change permissions of mailboxes that are outside the role assignment scope in an Exchange Server 2010 environment

      2398431 Using Pipelining in SMTP to check email addresses does not work correctly when you disable tarpitting functionality on a Receive connector in an Exchange Server 2010 environment

      2277649 You receive misleading information when you run the "New-TestCasConnectivityUser.ps1" script on an Exchange Server 2010 server

      2009942 Folders take a long time to update when an Exchange Server 2010 user uses Outlook 2003 in online mode

      You can download the update HERE

      How to demote a Exchange 2007 CCR Cluster with Load balanced CAS/HUB Servers

      I used the following steps to do this.

      1. All public folders and system folders that are housed on the Exchange 2007 CCR Cluster computer must be replicated to another Exchange 2007/2010 computer that is in the site.

      2. Verify the contents of the public folder store with the following Powershell commands
      Get-PublicFolderStatistics -server <Exchange 2007_Server_Name> | fl | out-file d:\PFstat.txt

      Get-PublicFolder -server < Exchange 2007_Server_Name > \ -recurse | fl | out-file d:\PFIPMSub.txt

      Get-PublicFolder -server < Exchange 2007_Server_Name > \non_ipm_subtree -recurse | fl | out-file d:\PFNonIPMSub.txt.

      3. Remove the replicas from the public folder store

      MoveAllReplicas.ps1 -Server ccrclustername –NewServer newservername

      4. Remove the public folder store

      Remove–PublicFolderDatabase –Identity "Public_Folder_Store_Name"

      5. Change the server that is responsible for generating the Offline Address Lists

      Move-OfflineAddressBook –Identity OfflineAddressBookIdParameter -Server ServerIdParameter

      6. Move the Routing Group Connectors by using the following command:

      Get-RoutingGroupConnector | where {$_.SourceTransportServers -like "<First Exchange 2007 server>"} | Set-RoutingGroupConnector -SourceTransportServers "<Second Exchange 2007 server>"
      Get-RoutingGroupConnector | where {$_.TargetTransportServers -like "<First Exchange 2007 server>"} | Set-RoutingGroupConnector -TargetTransportServers <Second Exchange 2007 server>

      7. To modify any Send connectors that have the first Exchange 2007 server as the source transport server, run the following commands:

      Get-SendConnector | where {$_.SourceTransportServers -like "<First Exchange 2007 server>"} | Set-SendConnector -SourceTransportServers "<Second Exchange 2007 server>"

      8.Important:
      How to use the Exchange Server SP1 2007 Setup wizard to remove Exchange 2007

      1. Log on to the server from which you want to remove Exchange 2007.

      2. Open Control Panel, and then double-click Programs and Features.

      3. In Programs and Features, select Microsoft Exchange Server 2007, and then click Uninstall.

        If you click Change instead of Uninstall, you can add server roles, but you cannot remove server roles.

      4. In the Exchange Server 2007 SP1 Setup wizard, on the Exchange Maintenance Mode page, click Next.

      5. On the Server Role Selection page, clear all the server role check boxes, clear the Management Tools check box, and then click Next.

        By default, all server roles are selected. This indicates that no server roles will be removed. To remove a server role, you must clear the appropriate check box.

      6. On the Readiness Checks page, after the check completes, click Uninstall.

      7. On the Completion page, click Finish.

      8. (Optional) If you are removing Exchange from a Mailbox server, remove the Exchange database files (*.edb) and storage group log files (*.log).

        If you reinstall the Mailbox server role on this server, you must first remove the database and log files from the server.

      9. (Optional) Remove the setup log files that are located at %systemdrive%\ExchangeSetupLogs.

      10. (Optional) Remove the following virtual servers that are created for Exchange 2007 under the Default Web Site in IIS:

        • Microsoft-Server-ActiveSync
        • OAB
        • Owa

        When you remove Exchange 2007, neither IIS nor these virtual servers are removed

      9.  First Remove the Passive Mailbox Node

      10. Second the Primary Mailbox Role

      11. Remove the CAS/HUB’s Role on the nodes
      Important: NOT AT THE SAME TIME

      12. Demote the Cluster

      13. Demote the NLB Cluster

      14. Remove the Servers from the domain

      15. Shutdown the Servers

      16. Take a cold bier when you are don with testing and everything works Winking smile

      Exchange 2010 Free space within a Mailbox Database

      In previous versions of Exchange Server there was a process called "online maintenance". This process ran at night and one of the tasks was to an online defragmentation to do within the database. The task was that the empty spaces are grouped together resulting in more efficient use of the Mailbox Database.

      In Exchange 2010 has changed and there is a 24×7 online process. There is also the option of online, direct to see how much space is available within the databases with the Powershell command:

      Get-MailboxDatabase –Status | fl Name,AvailableNewMailboxSpace

      Output:

      image

      If we were to do an offline defragmentation on the Mailbox Database the mailbox database would be approximately a 90MB smaller.

      This is on my test Exchange 2010 server with only a few mailboxes. In normal production enjoinment this will  be a lot more.

      In Exchange 2010 you can you a online mailbox move. There fore you can
      better create a new mailbox database en move all the mailboxes to the new mailbox database.
      Then you have the same result with no down time.

      Translate »