Notes to O365 migration

内部邮件系统技术方案建议书北京新思软件技术有限公司目录目录 01.项目综述 (4)1.1.项目背景 (4)1.2.建设目标 (4)1.3.设计方法论 (4)1.3.1.面对的挑战 (4)1.4.参考标准 (7)1.4.1.信息安全标准 (7)1.4.2.项目管理标准 (7)1.4.3.邮件标准 (8)1.5.名词解释 (8)2.需求应答 03.架构设计 03.1.网络架构规划与设计 03.2.机房规划 (1)3.3.服务器规划与设计 (1)3.4.存储系统规划与设计 (1)3.5.数据库规划与设计 (1)3.6.运维平台规划与设计 (1)4.功能需求及解决方案 (1)4.1.邮件应用面临的现实挑战 (1)4.2.两个高标准严要求 (3)4.3.反垃圾反病毒安全网关方案 (5)4.3.1.基本概念 (5)4.3.2.垃圾邮件发送手段 (5)4.3.3.垃圾邮件的特征及反垃圾手段 (6)4.3.4.产品特征及技术标准 (9)4.3.5.实际效果 (12)4.4.系统稳定性安全性解决方案 (12)4.4.1.对网络及系统环境要求的说明 (13)4.4.2.对网络障碍情况下系统反应的说明 (13)4.4.3.对DNS障碍情况下系统反应的说明 (14)4.4.4.对软件可能故障系统反应的说明 (15)4.5.邮件海外中继转发解决方案 (16)4.5.1.海外邮件发送问题原因分析 (16)4.5.2.某软件中继转发服务介绍 (17)4.5.3.海外邮件转发服务器示意图 (17)4.5.4.某软件的比较优势 (18)4.6.国内外收发互联互通解决方案 (18)4.6.1.三个环节 (18)4.6.2.四个层次 (19)4.6.3.五个步骤 (19)4.7.邮件审核解决方案 (20)4.7.1.邮件审核概述及必要性分析 (20)4.7.2.某软件邮件审核比较优势 (21)4.8.邮件备份冗灾解决方案 (22)4.8.1.数据备份的技术分析 (22)4.8.2.技术组成 (23)4.8.3.工程配置 (25)4.8.4.实现过程 (25)4.9.邮件平滑迁移解决方案 (27)4.9.1.工作目标 (27)4.9.2.工作顺序 (27)4.9.3.其他说明 (28)4.10.邮件全外包服务解决方案 (29)4.10.1.第一种：租用方式 (29)4.10.2.第二种：自建方式 (29)4.10.3.第三种：系统自建+服务全外包方式 (30)4.10.4.三种方案比较 (30)4.10.5.我方推荐第三种方式的明显优势 (31)5.项目实施方案 (33)5.1.范围管理 (33)5.2.时间管理 (33)5.3.质量管理 (33)5.4.人力资源管理 (33)5.5.沟通管理 (33)5.6.配置管理 (33)5.7.风险管理 (33)6.测试 (33)6.1.连接测试 (33)6.2.兼容性测试 (33)6.3.性能测试 (33)6.4.可用性测试 (33)7.交付 (33)7.1.数据初始化 (33)7.2.数据迁移 (33)7.3.试运行 (33)7.4.培训和知识转移 (34)8.文档 .................................................................................................... 错误!未定义书签。

HOSTED PBXApril 2016 Release Notes Copyright NoticeCopyright© 2015 XO Communications, LLC.All rights reserved.Any technical documentation that is made available by XO Communications, LLC.isproprietary and confidential and is considered the copyrighted work of XOCommunications, LLC.This publication is for distribution under XO Communications non-disclosure agreementonly. No part of this publication may be duplicated without the express written permissionof XO Communications, LLC.XO Communications reserves the right to make changes without prior notice. TrademarksAny product names mentioned in this document may be trademarks or registeredtrademarks of XO Communications or their respective companies and are herebyacknowledged.This document is for the United States of America.Table of Contents (3)1Release Overview (4)2Feature / Service Expansion (5)2.1WorkTime UC 2.0 (5)2.2Video Conferencing in My Room (5)2.3WorkTime Guest Client (6)2.4CRM Connect (7)2.5Call Recording Enhancements (7)2.6Feature Access Code (FAC) Updates (Star Codes) (8)3User Experience Improvements (10)3.1Outbound Calling Plan Expansion (10)3.2My Reports Migration to HMTL5 (10)4Expanded Endpoints (11)4.1WorkTime Skype for Business (S4B) & Lync Add-In (11)4.2Desktop and Mobile Client upgrades (11)4.1WorkTime Tablet Client (12)4.2Outlook Add-in Upgrade (12)This release includes a number of new service capabilities in addition to targeted bug fixes to address preexisting issues submitted via the ticketing process. This document outlines the development items included in the production release.This section outlines the changes to features and services available to end usercustomers.2.1 WorkTime UC 2.0The WorkTime user experience is centered around the WorkTime application which canbe deployed on Windows PCs, MAC OS X, IPhone, IPAD as well as Androidsmartphones and tablets. Currently, the Hosted PBX product offers unified messagingapplications such as Instant Messaging & Presence (IM&P) and Desktop Sharing. AMyRoom conference bridge is now integrated as part of the unified messaging offering forusers with the WorkTime Unified Communication bundle.The goal of this effort is to enhance the WorkTime solution by offering:∙An integrated Audio Only MyRoom Conference for users that have a Station Type that includes Unified Communications and have the WorkTime Clientassigned to them.∙An option to add Video creating a Video-enabled MyRoom Conference (Section2.4)∙Support for the Collaborate Guest Client to allow external users to join theconference and participate in the Desktop Share, Video Conference, etc. (Section2.5)∙Support for a discrete WorkTime Collaboration bundle features (Section 2.6) UC 2.0 functionality requires version 21.2.2 or higher of the WorkTime Mobile andWorkTime Desktop clients.Additional details are available in the WorkTime Desktop and WorkTime MobileClient user guides on the Hosted PBX Support Page.2.2 Video Conferencing in My Room2.2.1 OverviewHosted PBX is expanding the MyRoom capabilities to enable the host or leader to createand participants to join a video conference.∙HD Video Collaborationo Supports H.264 AVC constrained baseline profile – up to level 3.1 –supporting up to 720pHD videoo Up to 15 simultaneous MyRoom participantso Resolution Agnostic - able to accept wide variety of resolutions fromCIF to 720pHD∙HD Audio Collaborationo Doubled capacity of MyRoom participants to up to 30 simultaneousparticipantso Supported codecs are G.711 μ-Law, A-Law, G.722 and G.729o Interoperabilityo Supports WorkTime Desktop (Mac, Windows), WorkTime Mobile(iOS, Android), and WorkTime Tablet (iOS, Android)o Interoperates with hardware video phones supporting H.264 AVCconstrained baseline profileFor more information, please refer to the Hosted PBX Support Page.2.2.2 Future ImpactsNone identified at this time.2.2.3 Known IssuesNone identified at this time.2.3 WorkTime Guest Client2.3.1 OverviewThe WorkTime Guest Client is an enhanced feature of the WorkTime UC CollaborationBundle. Delivered from My Room, the host can invite participants to join independent ofthe Hosted PBX WorkTime clients. These guests can receive a link or email containing alink to connect for audio, desktop sharing, and video conferencing from their browser.Desktop and Mobile client user Guides on the Hosted PBX Support Page.Guest Client is an included component in the WorkTime Collaboration Bundle.2.3.2 Provisioning Process ImpactsThe Guest Client is provisioned as an included component of the WorkTime CollaborateBundle.2.3.3 Future ImpactsNone at this time.2.3.4 Known IssuesNone identified at this time.2.4 CRM Connect2.4.1 OverviewCRM Connect is a Hosted PBX Application for Windows Desktop that integrates leadingCRM Applications into Hosted PBX’s service. CRM Connect works in conjunction with aUser’s phone and CRM software to provide a productivity enhancing integrated service.Supported CRM software vendors include: Allstate Insurance Company, ConnectWise,Eniro, Frontrange, Google, IBM, Infobel, Maximizer Software Inc., Microsoft, NetSuite Inc.,SAGE, Inc., Stylite, Sugar CRM, SuperOffice, Swiftpage, TEL.SEARCH,, XING, Zoho Corp. See CRM Connect User Guide on the Support Page forspecific application names and versions.For additional information, please refer to the CRM Connect User Guide.2.4.2 Implementation / User Dashboard ImpactsAdministrators assign CRM Connect licenses in MySite.My Phone is updated with a new “CRM Connect” tab which allows the download of theCRM connect desktop client when assigned to the user. It also provides the userscredentials (same as WorkTime) that must be configured in the client upon first install. 2.4.3 Future ImpactsAn Apple Macintosh version of the client is pending.2.4.4 Known IssuesThere are no known issues at this time.2.5 Call Recording Enhancements2.5.1 OverviewThe Call Recording feature has received several enhancements:∙It now allows enabling/disabling of a pre-alert recording announcement indicating to caller and called party that the call is being recorded.∙ A configurable warning tone intermittently played to alert call participants that a recording is in progress.∙On demand, user-initiated start of the recording (previously the entire call was recorded).∙Pause/Resume control with notification to user.Updates have been made to the Call Recording Quick Reference Guide and the CallRecording Feature Description.2.5.2 Provisioning Process ImpactsNo change to current process.2.5.3 Implementation / User Dashboard ImpactsAdministrators configure new and revised call recording features for users in MySite perstandard procedure.The custom pre-alert announcement is no longer available.2.5.4 Future ImpactsNone anticipated.2.5.5 Known IssuesNone at this time.2.6 Feature Access Code (FAC) Updates (Star Codes)2.6.1 OverviewSeveral Feature Access codes have been added and two have changed. These changesare necessary to support new Hosted PBX functionality and to support future productenhancements.2.6.2 Implementation / User Dashboard ImpactsThese changes only affect the digits dialed by end-users to activate/deactivate certainHosted PBX features.2.6.3 Future ImpactsNo known issues at this time.2.6.4 Known IssuesNo known issues at this time.This section discusses the improvements to the user experience and interfaces.3.1 Outbound Calling Plan Expansion3.1.1 OverviewHosted PBX provides an interface to manage the customer inbound and outbound callingplans for each site and specific user/phone numbers. The Outbound Calling planregulates behavior for calls placed to various destination types. The categories have beenexpanded to support additional calling zones. The Calling Categories are localized basedon country of the Service Provider.For more information, please refer to the Calling Plan QRG3.1.2 Implementation / User Dashboard ImpactsNo Change to Implementation process.User dashboard now includes more selections.3.1.3 Future ImpactsNo impacts anticipated.3.1.4 Known IssuesNo issues have been identified at this point.3.2 My Reports Migration to HMTL53.2.1 OverviewThe My Reports section of My Account is migrating from Flash to HTML5. This changeremoves Flash from the portals, allows reporting to be viewed on tablets.For more information please refer to the My Reports QRG.3.2.2 Implementation / User Dashboard ImpactsUser Dashboard is enhanced per items listed above.No impacts to current Implementation process.3.2.3 Future ImpactsRetirement of Flash environments.3.2.4 Known IssuesNo issues have been identified at this point.This section outlines introduction of new phones, clients, add-ins as well as upgrades toexisting clients. The timing of endpoint changes may take place within the release cycleand are not constrained to the production upgrade dates.4.1 WorkTime Skype for Business (S4B) & Lync Add-In4.1.1 OverviewThe WorkTime Add-in for Microsoft Skype for Business (S4B) is a client-side add-in thatenables calling a phone number using “Call from Phone” or “VoIP from S4B” throughWorkTime Desktop.There is a separate S4B enabled reference client available on the Hosted PBX SupportPage for download as well as a reference client without S4B enabled. The S4B version ofthe reference client has slightly different branding to blend with the S4B experience.Instant messaging, presence, desktop sharing, and S4B-to-S4B calling stay in S4B. Non-S4B calls use Hosted PBX with WorkTime Desktop as the add-in front end.The standard WorkTime Desktop installation is used with the addition of a single registrysetting.The add-in integrates directly with Microsoft S4B and relies on the built-in integrationbetween S4B and other Microsoft products. If S4B displays a calling option in a Microsoftproduct and that call goes through S4B, then the add-in is able to send the call throughWorkTime Desktop.For more information, please refer to the Hosted PBX WorkTime Desktop S4B ProductGuide.4.1.2 Implementation / User Dashboard ImpactsWhen the WorkTime S4B product is added to the site, the version of the WorkTimeDesktop client is downloaded as the S4B client. End Users are assigned the Desktopclient per normal process, but the MyPhone download link will point to the WorkTime S4B.4.1.3 Future ImpactsPotential impacts of changes to the mechanisms and procedures utilized by MicrosoftOperating systems, Skype for Business, and other Microsoft applications.4.1.4 Known IssuesNo issues have been identified at this point.4.2 Desktop and Mobile Client upgrades4.2.1 OverviewThe WorkTime Mobile and WorkTime Desktop clients will upgrade to version 21.2.2 orhigher in order to support new Collaboration functionality. The user guides are or will beavailable on the Hosted PBX Support Page.4.2.2 Implementation / User Dashboard ImpactsNo changes to current process.4.2.3 Future ImpactsClients may upgrade to a later version during 2016 depending on bug fixes or introductionof new feature/functionality.4.2.4 Known IssuesAny known issues are documented in the client Admin, User and Collaborationdocumentation on the Hosted PBX Support Page.4.1 WorkTime Tablet Client4.1.1 OverviewWorkTime Tablet for iPad and Android is Hosted PBX’s newest edition to its WorkTimeclient offering. The new clients share the same look and feel as the other WorkTimeclients.WorkTime Tablet for iOS Tablet provides the following communication features:∙Instant Messaging and Presence (IM&P)∙Voice Calling (VoIP)∙Voice Calling (circuit-switched) – Requires Tablet to have Cellular Service.∙Video Calling∙Hosted PBX Call Settings∙MyRoom - Audio and Video Conferencing∙MyRoom – Guest Client Support∙MyRoom – Desktop Share Viewing4.1.2 Implementation / User Dashboard ImpactsThe WorkTime Tablet client will now be an available option for Sharing assignment in theMySite → User Feature Tab → Sharing Tab.In MyPhone, Users are presented with the link to download the client for Apple AppStoreor Google Play Store.4.1.3 Future ImpactsExpanded functionality based on the Hosted PBX WorkTime Client Roadmap.4.2 Outlook Add-in Upgrade4.2.1 OverviewThe Outlook Add-in for Hosted PBX WorkTime Desktop provides integration betweenWorkTime Desktop and Microsoft Outlook. This add-in enables Microsoft Outlook todisplay WorkTime Desktop contact presence and allows the user to invoke client functionslike Chat, Call from Computer, Call from Phone Added Outlook 2013 support.Updates in the new version, 10.2.0 are as follows:∙The add-in is now supported in Outlook 2013 (32 and 64-bit)∙Added the ability to call a non-WorkTime Desktop contact.∙Right-clicking on an email for a non-WorkTime Desktop contact shows the call options as long as the contact has a valid phone number.∙Added Windows 8.0 support (32 bit and 64 bit).∙Added Windows 8.1 support (32 bit and 64 bit). No, Video Call from within Outlook.The Add-in works with the Microsoft Windows operating system.The updated version of the client is currently available for linking and customerdownload.No changes to current process.4.2.2 Implementation / User Dashboard ImpactsNo changes to current process.Please refer to the Outlook Add-in User Guide for additional details.4.2.3 Future ImpactsNone at this time.4.2.4 Known IssuesNo issues have been identified at this point.。

Spotlight On…Customers are Moving to the CloudNow Available Through EAS!Office 365 Add-ons Simple Licensing for Office 365EasyThe underlying EA does not change. SA benefits are retained, including rights to new versions.Great PricePricing recognizesexisting investment inOffice and CAL Suites.Preserves EAdiscounts foron-premises andvolume discounts foronline services.FlexibleAdd Office 365 at anytime, for any numberof users, to anyworkload.A simple, low-cost way for customers to add Office 365 services at any time, while maintaining currentEA and SA benefitsPermitted Office 365 T ransitions, Add-ons Possible Transitions and Add-ons for Enterprise Product electionsProducts Being Transitionedor “Upgraded” E1E2E3E3 w/oProPlus E4E4 w/oProPlus ProPlusCore CAL Suite ✓/✓✓/✗✓/✗✗/✓✓/✗✗/✓✗/✗Enterprise CAL Suite✗/✗✗/✗✓/✗✗/✓✓/✗✗/✓✗/✗Office Professional Plus✗/✗✓/✗✓/✗✗/✗✓/✗✗/✗✓/✗Office Professional Plus andCore CAL Suite✗/✗✓/✗✓/✓✗/✓✓/✓✗/✓✗/✗Office Professional Plus andEnterprise CAL Suite✗/✗✗/✗✓/✓✗/✓✓/✓✗/✓✗/✗✓✓✓✗Office 365 Add-on versus T ransition in the EA Office Pro Plus SA $7.50ECAL SA $6.50E3 Add-on $3.00E3 USL $15.50$17.00$17.00Add-on (SA + Add-on)Transition (USL + Bridge)EXISTING INVESTMENTCost Benefits Simple: EA does not change•Maintain on-premises licenses and SA, and continue receiving full SA benefits (e.g., new version rights)•Maintain true-up motion for all Qualified Users / DevicesCompetitive pricing : Perceived Add-on discount reflects existing on-premises investments True per user licensing •EA licensing changes to enable per user licensing for Office 365 workloads •True-ups covered for Office 365 workloads on new Qualified DevicesOffice Add-on US Dollar figures reflect pricing for customers with EA Level D pricing rounded to nearest $.50Office 365 Add-on versus Full USL (T ransition)Add-on Full USLMidterm Sales CycleAt EA renewal Low Organizational Device GrowthMultiple Devices Per User Customer desires a hybrid-cloud strategy Customer desires a cloud-centric strategy Customer is at the beginning of their cloud journey and values the ability to move at their own pace with no change to their EA Customer has a defined cloud strategy in place Desires easier per-user licensing and feels comfortable changing EACompany ACompany BScenario 1: Add/Remove Users with Add-ons❝❝❝Scenario 2: Adding new Qualified Devices ❝❝❝❝❝100 Qualified Devices+Scenario 3: Licensing All Users with Add-ons ❝❝❝❝❝Scenario 4: Pro Desktop to Office 365 Enterprise E3Questions?Enterprise plans and Exchange Online Add-on or Full USL Licenses purchased throughEA, MPSA, AOS, Open, or MOSP/Now Extended!Office 365 Add-ons are an integral part of the price listsAdd-on options for every CAL customer and Office 365 workload Deploy quickly using FastT rack and FY14 Office 365 Deployment Offer Learn more on Office FastT rack Recap & Resources /Whether you have Software Assurance or Office 365,you are covered.The coverage that you enjoy with your Software Assurance benefits will continue as cloud-platform coverage with Office 365.IT Pro technical training vouchers Deployment planning services 24x7 Support IT Pro online training courses Office 365 Deployment Offer* 24x7 SupportHome Use Program Office roaming use rights End user e-learning courses Install service on up to 5 devices Office mobile appsEnd user e-learning coursesNew version rights / Extended hotfix Multi-language packSpread paymentsCold backups Software is always up to dateMulti-language packAnnual payment terms99.9% SLA availability hosted offering/wp-content/uploads/2014/03/O365-Support-Overview-Battle-Card-Customer.pdfQuestions…•A customer has an EAS with Office 2010. They want to transition to Office 365 licensing. Will they be required to remove Office 2010 and replace it immediately with O365 ProPlus?Yes, if the customer moved all Office Professional Plus Volume Licence (VL) counts from the EAS to O365 USL, they would require removal and reinstall of Office.1) VL media cannot be used to install Office licensed through the O365 USL2) The latest version (2013) of Office must be installed•Will a customer who transitions from on-premises Office to Office 365 Pro Plus 365 keep the rights to the latest version of on-premises Office if they then transition back?The customer will be entitled to the version that was available when their SA coverage ended for those licenses paid in full. So if they transitioned today, it would be Office Professional Plus 2013.They may also transition back on premises, reattaching and purchasing SA providing:1.Those licences were paid in full2.SA was current on those licences at the time oftransition.•Can a customer run Office in RDS on Azure?Typically, no.You should rent office through SPLA.•A customer has a mix of Office 2003 (via Open) and Office 365 ProPlus as part of E3. However, they are running Windows XP on their machines. What are the implications?They won’t be able to use either version of Office; Office 2003 doesn't work with Office 365 and Office 2013 (Office 365 ProPlus) doesn't run on Windows XP.•A customer buys an Office 365 Add-on and Microsoft doesn’t meet the SLA for a month. Would the customer receive creditfor the add-on or value for the equivalent USL?Only up to the add-on credit./en-us/library/office-365-service-level-agreement.aspx /en-gb/download/details.aspx?id=18128•A customer is deploying 100 seats of the E3 add-on and 80 seats of the E1 add-on through EA/EAS/Open/OV/OVS/MSPA/AOS/MOSP.The minimum qualification for the deployment offer is 150 seats. Would this mixed order of add-ons qualify for the funding?Yes.Office 365 Open timeline H1 FY14March 2013•Launched Office 365 for commercial customers•Launched manual migration offer –Office 365 Open Value offer August 2013•End-to-end experience improvements implemented, which bundled numerous keys into 1 key December 2013•Expanded SKU line up September 2013•Launched Office 365 for public sector customers •Expanded OLS SKU lineup February 2014•Launched programmatic Office 365 Add-ons and retire OOVOH2 FY13H2 FY14OV OVS A simple, low-cost way for customers to add Office 365 services at any time, while maintaining current OV and SA benefits Office 365 Add-on SKUs•The underlying OV and OVS does not change •SA benefits are retained, including rights to new versions Office 365 Add-on SKUs•Pricing recognizes existing investment in Office and CAL Suites •Preserves OV discounts for on-premises and volume discounts for Online Services •Add Office 365 at any time, for any number of users and to any workloadScenarios covered by Office 365 Add-on for OV Commercial Government Education ME1E3E1E1+Archiving E3A3Core CALN/A 1-14%N/A -10%-7%N/A Faculty: -15%Student: -12%E-CAL 1N/A N/A N/A Office Pro Plus-39%2-25%-11%Faculty: -38%Student: -56%Core CAL or E-CAL + Office Pro Plus-66%2-45%-36%Faculty: -51%Student:-56%1CAL Suite to M SKU scenario, as well as E-CAL only customer scenario are no longer part of the supported scenaio effective November 2013.This offer attemps to give price reduction for equvalent O365 functionality already purchased in the VL Program. There is no equivalent offer in O365. 2 Discount % updated effective November 2013 to ensure alignment with equivalent offers and policies provide in other Volume Licensing Channels (such as Enterprise Agreement).Set-up experience for customers •Receive email with login to VLSC •Sign Open agreement and retrieve a single 5x5 code •Instructions provided for redeeming key •VAR purchases from Open/OV/OVS pricelists•Subscription sold for the amount that is orderedFor example customer ordering 87 seats for Office 365 E1 will receive a single key that will activate 87 seats.•Enter single key and basic information on /setup365•Subscription end date set at redemptionSummaryOffice 365 Add-on SKUs arenow an integral part of OV andOVS programs.There are now add-on optionsfor qualified customersFind resources and learn more: Licensing on MPN/en/us/Pages/Licensing/volume-licensing.aspxQuestions?Windows 8.1 EnterpriseOn the pricelist and available without an annuity (SA)OneDriveThere can only be OneHowever, there are two…And Office Web Apps are nowcalled Office Online/one-place-for-all-your-work-files-introducing-onedrive-for-business/Windows Intune Offers Open EA/EAS EESMust license ConfigMgr separatelyPer User Licensing (on up to 5 devices)Must license ConfigMgr separately If the customer also wants Windows…If the customer owns ConfigMgr and SCEP…Notes:•All Prices USD MOSP Direct. Discounts for volume and education.•MDOP & Additional storage for Software Dist available as add-on (same as current offer)•Windows Intune Add-On for ConfigMgr requires ConfigMgr & SCEP to be licensed under the EA/EAS/EES Beginning April 1, 2014Open License, OV, OVSWindows Intune Offer available April 1, 2014System Center 2012 Config Mgr & Endpoint Protection available in all offers Win SA no longer required (For Windows Intune & Windows Intune Add-On)New OfferVLSC User Guide http://bit.ly/1hRe1IROffice 365 Support Battlecard http://aka.ms/YjixedLicensing Office 365 ProPlus in VL http://bit.ly/NB0hYkWindows 8.1 Licensing Brief http://bit.ly/NB0YB1/en-in/licensing/about-licensing/product-licensing.aspx The PUR Explained http://aka.ms/zeabkaCustomer Licensing Education Serviceshttp://aka.ms/cz13p4When What WhereReading24th-25th March Licensing Product & ProgramFundamentalsLondon30th April-1st May Licensing Product & ProgramFundamentals27th-28th May Licensing Product & ProgramReadingFundamentalsNow 2-day events (optional)Y our Call to Action:David Cattanach*********************。

Guide B: Microsoft Office 365 Setup ContentsThings to take note before you begin (1)Microsoft Office 365 Features (2)Step 1: Installing Microsoft Office (3)Step 2: Configuring Outlook Desktop App (7)Step 3: Installing Microsoft Teams (9)Step 4: Configuring OneDrive App (11)What do the OneDrive icons mean? (15)Things to take note before you begin✓You have completed Guide A: Laptop Configuration.✓Ensure you have stable Internet access.✓The whole process will take approximately 30 to 60 minutes, depending on your laptop’s specification.Office 365 is a service portal provided by Microsoft to you and is subjected to their terms of usage. By using the Office 365, do note that you have agreed to Microsoft’s terms of usage.Before you begin to use Office 365, please kindly read the terms of usage via https:///en-sg/servicesagreementStep 1: Installing Microsoft Office1.1 Go to https:// and login using your RP credentials.1.2 Click “Install apps” > “Microsoft 365 apps”.1.3 You will receive a prompt to download the file.Click “Open file”.1.4 After the installer in downloaded, you will get an UAC prompt as shown below.Click “Yes” to allow the installation to begin.1.51.6 Once the installation is completed, click “Close”.1.7 Go to Start Menu and search for Word.Click on the application to launch it.1.8 Once launched, a prompt will pop up to accept the license agreement to use Office 365.Click “Accept ”.1.9To ensure that your Office 365 is activated, go to “File ” > “Account ” and verify that product is activated as per below screenshot.On completion of Step 1, you have successfully installed Microsoft Office.On completion of Step 1, you have successfully installed Microsoft Office 365.Step 2: Configuring Outlook Desktop App2.1 Go to Start Menu and search for Outlook.Click on the application to launch it.2.2 Outlook will automatically detect your RP email address and enter your credentials if it prompts tologin. Click “Connect” and it will start to connect to the server to retrieve your email configuration details.2.3 After successfully connected to your RP email, the below screen will show.Uncheck “Set up Outlook Mobile on my phone, too” and click “Done”.2.4 Outlook will then load your mailbox and your emails will begin synchronization.Please note that it will take a while for Outlook to communicate with the server to retrieve your details.Step 3: Installing Microsoft Teams3.1 Download Microsoft Teams (for work or school) from this link.3.2 Click “Download for desktop”.3.3 Click “Download Teams” and it will download an TeamsSetup_c_w_.exe installer to your Downloadsfolder.3.4 Double-click on the TeamsSetup_c_w_.exe installer from your Downloads folder and let MicrosoftTeams install.3.5 Upon successful installation, locate the Microsoft Teams icon on your taskbar and click to open.3.6 To confirm that you are signed in, click on the profile icon found on the top-right corner > your nameand RP email address should appear.Step 4: Configuring OneDrive App4.1 Go to Start Menu and search for OneDrive.Click on the application to launch it.4.2 Enter you RP email address and click “Sign in”.4.34.4 Choose which folders (Desktop, Documents and Pictures only) you want to backup automatically toOneDrive.*Note: It is highly encouraged to backup all folders to OneDrive as it will be saved to the cloud so in case any Hardware related issue happens to your laptop and/or you are unable to backup your files, at least you would have a copy of it in OneDrive.4.5Click “Next ” all the way.4.6Click “Later”.4.7 Click “Open my OneDrive folder”.4.8 It will redirect you to the OneDrive folder in File Explorer.Default path: C:\Users\<Student ID>\OneDrive – Republic PolytechnicRed circle with white crossPress OneDrive icon with sync pending arrows。

Copyright © 2020 Moxa Inc. Released on February 24, 2020About MoxaMoxa is a leading provider of edge connectivity, industrial computing, and networkinfrastructure solutions for enabling connectivity for the Industrial Internet of Things (IIoT). With over 30 years of industry experience, Moxa has connected more than 57 million devices worldwide and has a distribution and service network that reaches customers in more than 70 countries. Moxa delivers lasting business value byempowering industries with reliable networks and sincere service. Information about Moxa’s solutions is available at . How to Contact Moxa Tel: +886-2-8919-1230 Migrating from the Moxa ART platform to the Moxa New Generation RISC PlatformMoxa Technical Support Team****************Contents1 Introduction ....................................................................................2 2 Steps for Migrating to the Cortex-A8 Platform ................................ 63 Using the Migration Checking Tool .................................................. 64 Reporting Migration Problems ........................................................ 7 5Revision History (7)1IntroductionMoxa provides a wide portfolio of RISC-based Linux embedded computers for industrialapplications, and has developed a new generation of computing platforms (using the Cortex A8 processor), the UC-2100/3100/5100/8100 series, which are designed to replace the UC-7100/IA-240/IA-260 series computers. Moxa will phase out the old products, listed below in T able 1, in 2020. Users can refer to T able 1 to choose the proper successor products. The specifications of most of the successor products include the specifications of the old products.For more details, please visit Moxa’s official website.Table 1. Successor Product ModelsOld product Model name (MOXA ART platform) Successor(Cortex A8 platform)UC-7101-LX UC2101-LXUC-7112-LX/UC-7112-LX Plus UC-2111-LX/UC-2112-LXIA240-LX/ IA260 UC-5100 seriesIn the following paragraphs, we give users some pointers on how to migrate programs originally used on old computers to the newer computers.Before migration, users must have a good understanding of the differences between the two software environments, device node definitions (i.e., peripherals), and API definitions.Table 2. Differences Between Software Development EnvironmentsFrom ToPlatform MOXA ART platform Cortex A8 platformOS μClinux 2.6.19Standard Linux 2.6.9 Debian ARM 8 or 9Tool Chain arm-elf-toolchain-1.6.sh(built for 32-bitenvironment) arm-linux_1.3.sh(built for 32-bitenvironment)arm-linux-gnueabihf_6.3_Build_amd64_20171114.sh(built for 64-bit environment)Native Compiler N/A N/A YesGCC version 2.95.3 3.3.2 4.9.2Glibc version 0.9.26 2.2.5 2.19$PATH /usr/local/bin /usr/local/arm-linux/bin /usr/local/arm-linux-gnueabihf-6.3/usr/bin/ Console portbaudrate19200 115200 115200Auto start program when boot up /etc/rc /etc/rc.localor /etc/init.dsystemdFrom ToReset Button At least 5 seconds required to load factory defaults Press and hold the reset button for 7 to 9seconds to reset the computer to the factorydefault settings.As above, the differences in the software environment are the tool-chain, versions of the kernel and Gcc, $PATH (environment variable), etc. The differences in the peripherals lie in the SD, RTC, Buzzer, and USB definitions. Refer to T able 3 for detailed relevant differences of the Device Node Definitions (Peripherals).Table 3. Differences Between Device Node Definitions (Peripherals)Model UC7101UC-7112-LXUC-7112-LX Plus IA240-LXIA260-LXIA262-LXCortex A8 platformSerial Port /dev/ttyM0~1/dev/ttyM0~4/dev/ttyM0~1USB N/A/mnt/usbstorage/media/usb0SD /mnt/sd/media/sd-mmcblk1pRTC /dev/rtc/dev/rtc0Buzzer /dev/console N/A(encapsulate in API)The Cortex-A8 platform adopts new API calls. If you have used the MoxaART platform’s APIs, refer to the following section, modify the original source code, and then recompile the code for use with the new platform.UART Mode APIOperation MoxaART platformw/ uC linux MoxaART platformw/ standard linuxCortex-A8 platformInitialize Moxa UARTcontrol libraryN/A N/A int mx_uart_init(void);Set mode of target UART port int ioctl(fd,MOXA_SET_OP_MODE,&mode)int ioctl(fd,MOXA_SET_OP_MODE, &mode)int mx_uart_set_mode(intport, int mode);Get mode of target UART port int ioctl(fd,MOXA_GET_OP_MODE,&mode)int ioctl(fd,MOXA_GET_OP_MODE, &mode)int mx_uart_get_mode(intport, int *mode);For more details, refer tomoxa-arm-based-computer-linux-user-manual-for-debian-9-manualWatchdog APIOperationMoxaART platform w/ uC linuxMoxaART platform w/ standard linux Cortex-A8 platformOpen watchdog deviceint swtd_open(void) int swtd_open(void)intopen(“/dev/watchdog”,O_RDW R)Keep alive int swtd_ack(int fd) int swtd_ack(int fd) int ioctl(fd,WDIOC_KEEPALIVE, 0)Set timeout int swtd_enable(int fd, unsigned long time)int swtd_enable(int fd, unsigned long time) ioctl(fd, WDIOC_SETTIMEOUT, &timeout)Get timeout int swtd_get(int fd, int *mode, unsigned long *time)int swtd_get(int fd, int*mode, unsigned long *time) ioctl(fd, WDIOC_GETTIMEOUT,&timeout)Disable ack int swtd_disable(int fd) int swtd_disable(int fd) int options =WDIOS_DISABLECARD;ioctl(fd, WDIOC_SETOPTIONS, &options);Close watchdog file handle int swtd_close(int fd) int swtd_close(int fd)For more details, refer to moxa-arm-based-computer-linux-user-manual-for-debian-9-manualBuzzer APIOperationMoxaART platform w/ uC linuxMoxaART platform w/ standard linux Cortex-A8 platformInit buzzer control N/AN/Aint mx_buzzer_init(void) Play buzzerioctl(fd, KDMKTONE, unsigned int arg);ioctl(fd, KDMKTONE, unsigned int arg);int mx_buzzer_play_sound(unsign ed long duration)Stop buzzerN/AN/Aintmx_buzzer_stop_sound(void)For more details, refer to moxa-arm-based-computer-linux-user-manual-for-debian-9-manualDIO APIplatform MoxaART platform w/ uC linux MoxaART platform w/ standard linux Cortex-A8 platformInit DIO control N/A N/A int mx_dio_init(void)Set DO state N/A int set_dout_state(int doport, int state) int mx_dout_set_state(int doport, intstate)Get DO state N/A int get_dout_state(int doport, int *state) int mx_dout_get_state(int doport, int*state)Get DI state N/A int get_din_state(int diport, int *state) int mx_din_get_state(int diport, int *state)Set DI event N/A int set_din_event(int diport, void(*func)(int diport), int mode, unsignedlong duration) int mx_din_set_event(int diport, void (*func)(int diport), int mode, unsigned long duration)Get DI event N/A int get_din_event(int diport, int *mode,unsigned long *duration) int mx_din_get_event(int diport, int*mode, unsigned long *duration)For more details, refer to moxa-arm-based-computer-linux-user-manual-for-debian-9-manualOther operationsplatform MoxaART platformw/ uC linux MoxaART platformw/ standard linuxCortex-A8 platformDefault user root root moxaupramdisk/downramdiskYes Yes No.System commands busybox busybox Standard Debian commands init system SysV SysV systemdShell sh sh dash/bashnetworkinterface configuration/etc/motd /etc/network/interfaces /etc/network/interfaces2Steps for Migrating to the Cortex-A8 PlatformIn this section, we give the steps you should follow to migrate a program from the MoxaART platform to the Cortex-A8 platform.Step1: Set up the Cortex-A8 platform’s development environment, including installing the Cortex-A8 platform’s native compiler or tool chain. For more details, refer to moxa-arm-based-computer-linux-user-manual-for-debian-9-manual.Step2: Develop or move the old code to the new development environment.Step3: Check the information provided in the above tables to modify the code and then compile it.Step4: If you receive any error messages during compilation, return to Step 3.Step5: Download the program to the Cortex-A8 platform via SSH.Step6: If needed, set up the systemd script for your program.Step7: Test the program.→If bugs are found, return to Step 3.→If no bugs are found, continue with Step 8.Step 8: Distribute the program to additional Cortex-A8 platform units if needed.3Using the Migration Checking ToolTo help users migrate old programs to new platforms more efficiently, Moxa provides amigration tool for listing the file names and line numbers of source code using old definitions.Users can refer to the resulting information to modify only those portions of the source code that require modification.You may download the tool from Moxa’s product website.Usage:1.Upload your MoxaART platform’s source code to the new Moxa Cortex-A8 platform.2.Put the migrate_check.sh in the same directory as your source code.3.Execute migrate_check.sh. If the tool finds old definitions in your source code, it will showfile names and line numbers of that source code. Please modify the code using the newdefinitions. For new definitions, refer to moxa-arm-based-computer-linux-user-manual-for-debian-9-manual.4.Note that you may need to modify the logic of the program after using the new API.4Reporting Migration ProblemsBefore reporting migration problems to the Moxa Technical support team, please prepare the following items:1.Old product model name, firmware version (kversion)2.New product model name, firmware version (kversion)3.Error message.4.How to reproduce the error.5Revision HistoryVersion Release Notes Release Date v1.0 --- 2020-03-03。