Office 365 System Requirements – Client side
If you ever look at all the migration that we do, we have to completed the biggest challenge; clients has been getting the system requirements ready for Office 365. The best advice is to start updating workstations as quickly and as early in the process as possible. The reason for these updates to be done its becaue of the strategy we choose on the migration platform, whether Cutover or Stagged or Hybrid migration, few components needs to be installed on-permises. Office 365 is a suite of Internet-based services that are designed to help meet your needs for robust security, 24/7 reliability, and user productivity. Click here to get the document from Microsoft.
- Service Connector with .NET 2.0 or higher
- XP SP3 – No identity federation with XP Home or Media Center Editions
- Vista SP2
- Windows 7
- Mac OS X 10.5 (Leopard), 10.6 (Snow Leopard), 10.7 (Lion)
Office Client Requirements:
- Office 2007 SP2 and above
- Office 2008 for Mac & Entourage 2008 Web Services Edition
- Office 2011 for Mac and Outlook 2011 for Mac
- Lync 2010
- Communicator for Mac
- Internet Explorer 7 (IE 8 for Vista or Windows 7)
- Firefox 3.x
- Safari 4.x
Office Professional Plus Requirements:
- Windows XP SP3 (x86)
- Vista SP1(x86 or x64)
- Windows 7 (x86 or x64)
- Server 2003 R2 (x86 or x64)
- Server 2008, R2
- 3.5 GB Free disk space
- Service Connector
- Internet Explorer 7 or higher
- Firefox 3.x
- Safari 4.x
Office Web Apps Requirements:
- Internet Explorer 7 or higher
- Safari 4.x or higher
- Firefox 3.5 or higher
- Chrome 3.x or higher
- Light version supports reduced feature set across virtually any browser
Office Web App Mobile Device Support:
- IE on Windows Mobile 5, 6, 6.1, 6.5, 7.00, 7.5(Mango)
- Apple iOS 5 devices.
- Safari latest version
- Blackberry 4.x and later
- Nokia S60 or later / Nokia windwos smartphone
Software requirement for O365: Click here to know more
Requirements for single sign-on
To use single sign-on, you must:
- Have Active Directory deployed and running in Windows Server 2003 operating system, Windows Server 2008, or Windows Server 2008 R2 with a functional level of mixed or native mode.
- Plan for and deploy AD FS 2.0 on Windows Server 2008 or Windows Server 2008 R2. Also, if the user is connecting from outside your company’s network, you must deploy an AD FS 2.0 proxy.
- Use the Microsoft Online Services Module for Windows PowerShell to establish a trust with Office 365.
- Install the required updates for Office 365 from the Office 365 downloads page to ensure that your users are running the latest updates of either Windows 7, Windows Vista, or Windows XP. To access the Office 365 downloads page, sign in to the Office 365 portal, and, under Resources, click Downloads. The features in Office 365 will not work properly without the appropriate versions of operating systems, browsers, and software.
Requirements for ADFS
Active Directory Federation Services (AD FS) 2.0 deployment can collaborate successfully, you must first make sure that your corporate network infrastructure is configured to support AD FS 2.0 requirements for accounts, name resolution, and certificates.
Minimum requirement: Single-core, 1 gigahertz (GHz), 1GB RAM, 50MB Disk Space.
Recommended requirement: Quad-core, 2 GHz , 4GB RAM, 100 MB Disk Space
Network Service: network services is critical for successful deployment of AD FS 2.0 in your organization. AD FS 2.0 to function, TCP/IP network connectivity must exist between the client; a domain controller; and the computers that host the Federation Service and the Federation Service Proxy.
Attribute Store: AD FS 2.0 requires at least one attribute store to be used for authenticating users and extracting security claims for those users. AD FS 2.0 automatically creates an Active Directory attribute store, by default. AD FS 2.0 to operate successfully, domain controllers in either the account partner organization or the resource partner organization must be running Windows Server 2003 SP1, Windows Server 2003 R2, or Windows Server 2008. When AD FS 2.0 is installed and configured on a domain-joined computer, the Active Directory user account store for that domain is made available as a selectable attribute store. AD FS 2.0 does not require schema changes or functional-level modifications to AD DS. AD FS 2.0 integrates naturally with existing Windows authentication
Requirements for Microsoft Online Services Module
- Operating system: Use Windows 7 or Windows Server 2008 R2.
- Microsoft .NET Framework:You must turn on the Microsoft .NET Framework 3.51 feature in Windows 7 or Windows Server 2008 R2.
- Windows PowerShell 2.0 and AD FS 2.0:In order to run the cmdlets to set up single sign-on, you must turn on the Windows PowerShell 2.0 feature, and you must have administrator privileges on the AD FS 2.0 server.
- All Office 365 software updates: From the Office 365 downloads page, install the required updates. To access the Office 365 downloads page, sign in to the Office 365 portal, and, under Resources, click Downloads. These updates are required because the features in Office 365 will not work properly without the appropriate versions of operating systems, browsers, and software.
Requirements for O365 Directory Synchronization tool
- The default installation of the Directory Synchronization tool (32-bit and 64-bit) includes a version of Microsoft SQL Server 2008 Express.
- Office 365 supports synchronization of up to 20,000 objects. To synchronize more than 20,000 objects, contact Office 365 Support.
- The directory synchronization computer must meet the following requirements:
- It must be running the right version of Windows Server.The Directory Synchronization tool can be run on the 32-bit or 64-bit versions of the following Windows Server operating systems:
- 32-bit: Windows Server 2003 Standard or Windows Server 2008 Standard
- 64-bit: Windows Server 2008 R2 Standard or Windows Server 2008 Standard
- It must be joined to Active Directory. The computer must be joined to the Active Directory forest that you plan to synchronize. The computer also must be able to connect to all the other domain controllers for all the domains in your forest. A forestis one or more Active Directory domains that share the same class and attribute definitions, site and replication information, and forest-wide search capabilities.
- It cannot be a domain controller.The Directory Synchronization tool cannot be installed on Active Directory domain controllers.
- It must run Microsoft .NET Framework 3.x.If you are running Windows Server 2008, the .NET Framework will already be installed; if not, you can download it from the following locations:
- It must run Windows PowerShell:If you are running Windows Server 2003, you need to download Windows PowerShell. If you are running Windows Server 2008, you need to enable Windows PowerShell.
- It must be located in an access-controlled environment.Access to the computer that is running the Directory Synchronization tool should be limited to those users who have access to your Active Directory domain controllers and other sensitive network components. Only users or administrators that have the necessary permissions to make changes to domain controllers in Active Directory should have access to this computer.
- When you activate directory synchronization, you are turning on this feature for your Office 365 subscription. You must activate directory synchronization before you install the Directory Synchronization tool. To activate directory synchronization, run the Microsoft Office 365 Deployment Readiness Tool. This tool inspects your Active Directory environment, and then provides a report that includes a prerequisite check and an attribute assessment that are specific to the directory synchronization tool requirements.If your environment doesn’t meet these requirements, the tool lists the changes you have to make before you can begin directory synchronization.