Category: General

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
Click here for the Microsoft Office 365 Beta Deployment Guide for Enterprises

Domains

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: 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

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

It appears that your Active Directory schema is prepared for Exchange Rich Coexistence
Deployment Guide: Exchange Rich Coexistence Requirements

Active Directory Cleanup

Deployment Guide: Active Directory Cleanup

samaccountname (user name) Attribute

Character length test passed

Unsupported character test passed

givenname (first name) Attribute

Character length test passed

Unsupported character test passed

sn (last name) Attribute

Character length test passed

Unsupported character test passed

displayname Attribute

Character length test passed

Unsupported character test passed

mail (email address) Attribute

Character length test passed

Unsupported character test passed

No duplicates found

mailnickname Attribute

Character length test passed

Unsupported character test passed

proxyaddresses (email addresses) Attribute

No duplicates found

Unsupported character test passed

Directory Synchronization

Object count assessment:
Estimated number of objects for Directory Synchronization (entire forest): 113
Deployment Guide: Object Count Considerations
Enterprise Admin rights:

It appears that you are an enterprise admin
Directory Synchronization admin requirement met!
Deployment Guide: Directory Synchronization Required Permissions
Active Directory recycle bin:

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

Update values once you have verified your organization does not have any other application dependencies on the UserPrincipalName attribute.
Deployment Guide: Active Directory Cleanup

Unsupported characters test passed

Spaces in logon value test passed

Unicode character test passed

Note: All Unicode characters will be converted to underscores (_) in the UserPrincipalName field.

No UserPrincipalName duplicates found

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.

Below is a list of your UserPrincipalName domain suffixes in use:
wardvissers.local
Total: 1

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


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:

The following sip domains were discovered:
wardvissers.local
Total: 1

SharePoint Online

User object count assessment:

The number of user objects in your forest is supported.
Deployment Guide: Object Count Considerations

Client and End User Experience

Deployment Guide: Rich Experience Client Requirements

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

Below is an estimate of computer operating systems NOT ready for Office 365 rich client experience:
Total: 0

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

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


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


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.

For additional tests utilize the Exchange Remote Connectivity Analyzer

Deployment Guide: Ports and Protocols

portal.microsoft.com
Made a TCP 443 connection to portal.microsoftonline.com

Outlook.com
Made a TCP 443 connection to outlook.com

Outlook.com IMAP
Made a TCP 993 IMAP connection to outlook.com

Outlook.com POP
Made a TCP 995 POP connection to outlook.com

Outlook.com SMTP
Made a SMTP TCP 587 connection to outlook.com

Active Directory Federation Services End Point
Made a TCP 443 connection to nexus.microsoftonline.com

Directory Synchronization End Point
Made a TCP 443 connection to adminwebservice.microsoftonline.com

Office 365 PowerShell End Point
Made a TCP 443 connection to ps.microsoftonline.com

Outlook.com PowerShell End Point
Made a TCP 443 connection to ps.outlook.com

Office 365 Community End Point
Made a TCP 80 connection to community.office365.com

Lync Online SIP Connection
Made a TCP 443 connection to sipdir.online.lync.com

Lync Online Federation
Made a TCP 5061 connection to sipfed.online.lync.com
Domain Name System (DNS) name records checks:

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