On in his comments there is a built in tool for migrating account from cPanel to Plesk. Your Plesk version is 10.4.4 or higher with the latest updates installed.
-->The management tools in Exchange Server 2016 and Exchange Server 2019 include the Exchange Management Shell and the Exchange Toolbox. You can install the management tools on other client computers or servers in the Active Directory domain to help you manage your Exchange organization. The management tools have similar operating system, .NET Framework, and Windows Management Framework (Windows PowerShell) requirements as an Exchange server. The notable exception is: you can install the management tools on client versions of Windows. For more information, see Exchange Server system requirements and Exchange Server prerequisites.
Note
The management tools don't include the Exchange admin center (EAC). The EAC is a web-based console that's hosted on Exchange 2016 Mailbox servers, and like any web site, you can access the EAC from other computers. For more information about the EAC, see Exchange admin center in Exchange Server.
For more information about the Exchange Management Shell and the Exchange Toolbox, see Exchange Server PowerShell (Exchange Management Shell) and Exchange Toolbox.
What do you need to know before you begin?
- Estimated time to complete: 20 minutes
- The computer where you want to install the Exchange management tools requires access to Setup.exe in the Exchange installation files. To download the latest version of Exchange, see Updates for Exchange Server.
- For information about keyboard shortcuts that may apply to the procedures in this topic, see Keyboard shortcuts in the Exchange admin center.
Tip
Having problems? Ask for help in the Exchange forums. Visit the forums at: Exchange Server, Exchange Online, or Exchange Online Protection.
Use the Exchange 2016 Setup wizard to install the Exchange management tools
- In File Explorer on the computer where you want to install the management tools, right-click on the Exchange ISO image file that you downloaded, and then select Mount. In the resulting virtual DVD drive that appears, start Exchange Setup by double-clicking
Setup.exe
. - The Exchange Server Setup wizard opens. On the Check for Updates? page, choose one of the following options, and then click Next to continue:Connect to the Internet and check for updates: We recommend this option, which searches for updates to the version of Exchange that you're currently installing (it doesn't detect newer Cumulative Updates). This option takes you to the Downloading Updates page that searches for updates. Click Next to continue.
- Don't check for updates right now
- The Copying Files page shows the progress of copying files to the local hard drive. Typically, the files are copied to
%WinDir%TempExchangeSetup
, but you can confirm the location in the Exchange Setup log atC:ExchangeSetupLogsExchangeSetup.log
. - On the Introduction page, click Next to continue.
- On the License Agreement page, review the software license terms, select I accept the terms in the license agreement, and then click Next to continue.
- On the Recommended Settings page, choose one of the following settings:
- Use recommended settings: Exchange automatically sends error reports and information about your computer hardware and how you use Exchange to Microsoft. For information about what's sent to Microsoft and how it's used, click ? or the help links on the page.
- Don't use recommended settings: These settings are disabled, but you can enable them at any time after Setup completes.
Click Next to continue. - On the Server Role Selection page, configure the following settings:
- Select Management tools.
- Automatically install Windows Server roles and features that are required to install Exchange: Select this option to have the Setup wizard install the required Windows prerequisites. You might need to reboot the computer to complete the installation of some Windows features. If you don't select this option, you need to install the Windows features manually.Note: Selecting this option installs only the Windows features that are required by Exchange. You need to install other prerequisites manually. For more information, see Exchange Server prerequisites.
Click Next to continue. - On the Installation Space and Location page, either accept the default installation location (
C:Program FilesMicrosoftExchange ServerV15
), or click Browse to choose a new location. Make sure that you have enough disk space available in the location where you want to install the management tools. Click Next to continue. - If this is the first installation of Exchange in your organization (Exchange server or the management tools), you arrive on the Exchange Organization page. On this page, configure the following settings:
- Specify the name for this Exchange organization: The default value is First Organization, but you typically use the company name for this value. The organization name is used internally by Exchange, isn't typically seen by users, doesn't affect the functionality of Exchange, and doesn't determine what you can use for email addresses.
- The organization name can't contain more than 64 characters, and can't be blank.
- Valid characters are A to Z, a to z, 0 to 9, hyphen or dash (-), and space, but leading or trailing spaces aren't allowed.
- You can't change the organization name after it's set.
- Apply Active Directory split permission security model to the Exchange organization: Most organizations don't need to select this option. If you need to separate management of Active Directory security principals and the Exchange configuration, split permissions might work for you. For more information, click ?.
Click Next to continue. - On the Readiness Checks page, verify that the organization and server role prerequisite checks completed successfully. If they haven't, the only option on the page is Retry, so you need to resolve the errors before you can continue.After you resolve the errors, click Retry to run the prerequisite checks again. You can fix some errors without exiting Setup, while the fix for other errors requires you to restart the computer. If you restart the computer, you need to start over at Step 2.When no more errors are detected on the Readiness Checks page, the Retry button changes to Install so you can continue. Be sure to review any warnings, and then click Install to install the management tools.
- On the Setup Completed page, click Finish, and then restart the computer.
Use Exchange unattended Setup mode to install the Exchange management tools
- In File Explorer on the computer where you want to install the Exchange management tools, right-click on the Exchange ISO image file that you downloaded, and then select Mount.
- To install the Exchange management tools from the command line, use the following syntax in elevated command prompt (a Command Prompt window you opened by selecting Run as administrator):This example uses the Exchange Setup files on drive E: to install the management tools on the local server
For more information, see Install Exchange using unattended mode.
Integrating the latest version of the UM board now directly in Exchange 2013 with Cisco telephony system is a hot topic in our projects.
In terms of architecture, the approach with Microsoft Exchange Server 2013 is completely different from the Exchange Server predecessors 2007 and Exchange Server 2010. In previous versions , UM was a role that could be deployed if the need was there. In Exchange 2013 , these roles are combined into two types of servers. components or services can be collocated on the same server or separate two name servers CAS and MBX.
Unified Messaging Exchange 2013 requires the use of multiple TCP and UDP ports for communication between servers Exchange 2013 and other devices. Features and services offered by UM depend on various static TCP / UDP ports and dynamic . Proper functioning is ensured by the CAS server running the service call routing and MAILBOX server running the Unified Messaging service.
Services are:
- SESworker (GFW )(TCP -In )
- UMCallRouter (GFW )(TCP -In )
- UMCallRouter (TCP -In )
- UMService (GFW ) (TCP -In )
- UMService (TCP -In )
- UMWorkerProcess - RPC (TCP -In )
- UMWorkerProcess (GFW ) (TCP -In )
- UMWorkerProcess (TCP -In )Regarding signage, like the previous versions , Microsoft Exchange 2013 UM only supports the SIP protocol.Service call UM CAS server routing uses the SIP protocol transported TCP (Transmission Control Protocol) or TLS (Transport Layer Security) to communicate with MBC running the Unified Messaging service servers.By default, a CAS server listens for SIP requests on TCP port 5060 in unsafe mode and TCP port 5061 Safe mode.By default, a MBX server listens for SIP requests on TCP port 5062 in unsafe mode and TCP port 5063 in Safe mode.Ports:The purpose of this introduction is to highlight the fact that significant changes in the mode of operation of Microsoft Exchange 2013 UM needed review the traditional integration with Cisco environment.The context of this step by step:
- 1 Microsoft Exchange Server 2013
- 1 Server Cisco Call Manager 9.1.2 publisher and one subscriber
Integration TCP
The test environment:
Step 1: Configuring the Cisco Call Manager:
- Creation of SIP profile: Device-> Device Settings-> SIP Profile
- Creating a security profile SIP : System -> Security - > SIP Trunk Security Profile
- Creation of pilot issue of our voicemail system : Advanced features -> ; Voice Mail - > Voice Mail Pilot
- Creating a profile for our voicemail system : Advanced features -> Voice Mail - > Voice Mail Profile
- Creating a profile for our voicemail system : Advanced features -> Voice Mail - > Voice Mail Profile
- Creating a SIP trunk pointing to the Exchange 2013 server: Device - > Trunk
- In our example, a single Exchange 2013 server is present , where CAS and MBX servers are separated, the Trunk 1 must be directed to 5060 CAS server, other ports to the MBX server.
Creating a routing domain , the goal is that when the CAS server responds fqdn with the Mailbox server , the Cisco phone system can know which answer Trunk
This was necessary to repeat this step for each Mailbox server environmentCall Routing - . > SIP Route Pattern - Creating a route pattern to send the desired numbers to Exchange UM
Call Routing -> Route / Hunt -> Route patternIn this example, 6991 is automated reception , in 6999 voicemail. - Configuring a phone test:
Tests will be carried out with the ' Christopher ' user with the extension number ' 1103 .'
Step 2: Configuration Microsoft Exchange 2013 UM
- In the EAC management interface , we will create a specific numbering plan Cisco .
Unified Messaging -> UM plans , create a dial plan. - Specify the name, type numbering plan ( telephone ) and the number of digits of your dial plan current business , in our example , TCP is the selected mode, the security is ' Unsecured .'
- By clicking on the ' Configure' option , you can customize the behavior of your UM system your needs.
- You can set in the ' Outlook Voice Access ' tab the number assigned to this feature, in our example, ' 6999 ' will be the pilot number of the voice mail for the Exchange UM dial plan 'Cisco' . Different customization parameters of receptions or information messages are also possible.
- You can create a dialing 'all' removing all restrictions within your tests and assign the different uses of your dial plan.
- From the homepage of your dial plan interface, you can customize your strategic , gy default assigned automatically upon creation.
- As part of your integration tests, you can also evaluate features offered in the Microsoft Exchange UM 2013.
- Creating automated reception, in our example, the number assigned is ' 6991 '.
- In the EAC management interface , we create gateways representatives both servers Cisco .
Phone Unified Messaging - > UM IP gateways - Creating the gateway representing the CUCM Publisher with the IP address 10.0.100.51
- Creating the gateway representing the CUCM Publisher with the IP address 10.0.100.52
- The time has come to make your tests. In the EAC management interface , we enable users to benefit from unified messaging features .Recipients -> Mailbox , select the desired user.
- Enable unified Messaging, choose the default policy assigned the dial plan .