US20190199710A1 - Directory driven mailbox migrations - Google Patents
Directory driven mailbox migrations Download PDFInfo
- Publication number
- US20190199710A1 US20190199710A1 US16/286,453 US201916286453A US2019199710A1 US 20190199710 A1 US20190199710 A1 US 20190199710A1 US 201916286453 A US201916286453 A US 201916286453A US 2019199710 A1 US2019199710 A1 US 2019199710A1
- Authority
- US
- United States
- Prior art keywords
- migration
- server
- computing device
- source system
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
- H04L63/0823—Network architectures or network communication protocols for network security for authentication of entities using certificates
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/10—Office automation; Time management
- G06Q10/107—Computer-aided management of electronic mailing [e-mailing]
-
- H04L51/22—
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
- H04L51/42—Mailbox-related aspects, e.g. synchronisation of mailboxes
Definitions
- a method for migrating data from a source server to a target system includes: obtaining, using a computing device, a set of credentials to access the source server; accessing the source server using the set of credentials; requesting, automatically by the computing device, a directory structure associated with communication data from the source server; populating, by the computing device, the target system using the directory structure; requesting the communication data from the source server; and populating the target system with the communication data.
- a computing device includes: a processing unit; and a system memory connected to the processing unit, the system memory including instructions that, when executed by the processing unit, cause the processing unit to: access a source server; request a directory structure associated with communication data from the source server; populate a target server using the directory structure; request the communication data from the source server; and populate the target server with the communication data.
- a computer readable storage medium has computer-executable instructions that, when executed by a computing device, cause the computing device to perform steps comprising: obtaining, using the computing device, an email address and a password of a user of a source server; using autodiscover based on the email address to identify addressing information associated with the source server; accessing the source server using the addressing information and the password; requesting, automatically by the computing device, an offline address book from the source server over a Name Service Provider Interface (NSPI) protocol; populating, by the computing device, a target server using the offline address book, including creating one or more mailboxes for one or more users identified in the offline address book, and the target server being a hosted server; requesting communication data, including email items and calendar items, from the source server; populating the mailboxes on the target server with communication data; and reporting a status of a migration of the communication data to the user.
- NPI Name Service Provider Interface
- FIG. 1 shows an example networked computing environment.
- FIG. 2 shows details of a source server from the networked computing environment of FIG. 1 and an example migration system.
- FIG. 3 shows an example server computing device of the migration system of FIG. 2 .
- FIG. 4 shows an example method for a user to initiate migration of communication data.
- FIG. 5 shows an example method for migration of communication data.
- FIG. 6 shows an example user interface for a migration system.
- the present disclosure is directed to the migration of communication data, such as email items, calendar items, task items, etc., from a source server to a target server.
- the systems and methods described herein allow for the automated migration of communication data from a source server, which is located on-premise, to a target server, which is typically one or more hosted servers.
- a complete migration process is provided by: (i) re-creating the on-premise directory structure at the target server, and (ii) thereupon migrating the communication data from source server to the target server.
- a company decides to move its communication data, including all email items, calendar items, task items, etc., from an on-premise installation to a hosted solution. To do so, the company selects a cloud service that hosts an email solution off-premise for the company.
- an administrator for the on-premise installation provides credentials to a migration system to initiate the migration. These credentials provide the migration system with administrative access to the on-premise communication server.
- the migration system accesses the on-premise communication server and obtains a copy of the directory structure associated with the communication server.
- the migration system uses the directory structure to populate the directory structure at the target communication server in the cloud.
- the directory structure is used to populate mailboxes and distribution groups on the target communication server.
- the migration system accesses the communication data on the on-premise server initiates a migration of the communication data from the on-premise communication server to the newly-populated mailboxes on the target communication server in the cloud.
- the migration process is automated.
- the administrator provides his or her credentials.
- the migration system thereupon downloads the directory structure, populates the target space, and migrates the data.
- the migration system reports the status and any errors associated with the migration to the administrator during the migration process.
- the environment includes a source server 110 , a network 120 , and target servers 130 , 140 , 150 .
- the source server 110 is typically one or more computing devices hosting one or more business applications.
- the source server 110 can include an Exchange Server from Microsoft Corporation of Redmond, Wash.
- the Exchange Server is an example of a business server that implements messaging and collaborative business processes.
- the source server 110 is part of a corporate network, such as a local area network or wide area network, that is positioned behind a firewall.
- a corporate network such as a local area network or wide area network
- the source server 110 is a network of computing devices maintained by a business.
- One or more Exchange Servers are part of the source server 110 and provide communication and collaborative services, such as email, calendar, tasks, journals, etc.
- the network 120 is a bi-directional data communication path for data transfer between one or more devices.
- the network 120 establishes a communication path for data transfer between the source server 110 and the target servers 130 , 140 , 150 .
- the network 120 can be of any of a number of wireless or hardwired WAN, LAN, Internet, or other packet-based communication networks such that data can be transferred among the elements of the networked computing environment 100 .
- Other embodiments of the network 120 are possible as well.
- the target servers 130 , 140 , 150 are one or more servers that are accessible through the network 120 .
- the target servers 130 , 140 , 150 each host cloud services, including communication services such as email, calendar, task, etc.
- the target server 130 can host an Exchange Server that is accessible through the network 120 .
- the target server 130 thereby provides a hosted solution for communication data to one or more individuals or businesses.
- the source server 110 includes a communication server 111 with a source directory structure 112 and source mailboxes 114 .
- the source directory structure 112 includes a directory structure, such as the directory of addresses associated with the communication server 111 of the source server 110 .
- This can include the offline address book used by the Exchange Server to store email addresses, distribution lists, etc., associated with the communication server 111 .
- the source mailboxes 114 are the one or more message stores that include all of the messaging data for the source server 110 , such as email items, calendar items, task items, journal items, etc.
- the message stores are included as part of the Exchange System.
- the source server 110 also includes a computing device 116 .
- the computing device 116 can be located within or outside the corporate network.
- the computing device 116 includes a local application or web browser that is used by an administrator or other individual that has access to the communication server 111 .
- the computing device 116 can be used by the administrator to initiate the migration process.
- FIG. 2 also shows a migration system 210 that is configured to automate the migration of the information included in the communication server 111 to a target system, such as a hosted solution like the target servers 130 , 140 , 150 .
- a target system such as a hosted solution like the target servers 130 , 140 , 150 .
- the migration system 210 includes a user interface module 220 , a populating module 230 , and a data migration module 240 .
- the user interface module 220 provides a user with information about the migration process. This information can include both information to initiate the process, as well as status information as the migration process progresses and is completed. See, e.g., FIG. 6 .
- the populating module 230 obtains information to allow the populating module 230 to populate the target system in preparation for transfer of the communication data to the target server.
- the populating module 230 obtains directory structure from the source directory structure 112 . This directory structure is used to build the structure necessary to support the communication data that will be migrated from the communication server 111 to the target server, like target servers 130 , 140 , 150 .
- the migration system 210 is incorporated as part of the target servers 130 , 140 , 150 .
- the migration system 210 can be provided as a service on the target server 130 .
- the migration system 210 is a separate system that facilitates the transfer from the communication server 111 in the source server 110 to one of the target servers 130 , 140 , 150 .
- the migration system 210 includes one or more computing devices, such as a computing device 301 .
- the computing device 301 includes at least one processing unit 305 and a system memory 310 .
- the system memory 310 can store an operating system 315 for controlling operation of the migration system 210 or another computing device.
- One example operating system 315 is WINDOWS® operating system from Microsoft Corporation.
- the system memory 310 may also include one or more software applications 320 and may include program data.
- Software applications 320 may include many different types of single and multiple-functionality programs, such as an electronic mail program, a calendaring program, an Internet browsing program, a spreadsheet program, a program to track and report information, a word processing program, and many others. Examples of such software are the Exchange Server and Office suite of applications from Microsoft Corporation.
- the system memory 310 can include physical computer readable storage media such as, for example, magnetic disks, optical disks, or tape. Such additional storage is illustrated in FIG. 3 by removable storage 325 and non-removable storage 330 .
- Computer readable storage media can include physical volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information, such as computer readable or computer-executable instructions, data structures, program modules, or other data.
- Computer readable storage media can also include, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed by the migration system 210 . Any such computer storage media may be part of or external to the migration system 210 .
- Communication media is distinguished from computer readable storage media.
- Communication media may typically be embodied by computer readable instructions, data structures, program modules, or other data in a modulated data signal, such as a carrier wave or other transport mechanism, and includes any information delivery media.
- modulated data signal means a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal.
- communication media includes wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared and other wireless media.
- the migration system 210 can also have any number and type of an input device 335 and output device 340 .
- An example input device 335 includes a keyboard, mouse, pen, voice input device, touch input device, and others.
- An example output device 340 includes a display, speakers, printer, and others.
- the migration system 210 can also contain a communication connection 345 configured to enable communications with other computing devices over a network (e.g., network 120 of FIG. 1 ) in a distributed computing system environment.
- the various other servers and systems described herein can include one or more computing devices 301 configured in a manner similar to that shown in FIG. 3 .
- FIG. 4 an example method 400 for a user to migrate data from a source server to a target server is shown.
- the method 400 is presented to the user as a wizard that assists the user through the migration process.
- a wizard is provided that collects the necessary information to allow the migration to start. Additionally, the user can monitor the status of the migration and review any errors that may occur.
- the user initiates the migration process. In one example, this can occur by having the user use the computing device 116 to contact the migration system 210 to request the migration of communication data from the communication server 111 to a remote server, such as the target server 130 .
- the user provides the user's credentials to the migration system 210 .
- this includes having the user provide the user's e-mail address and password for the communication server 111 in the source server 110 .
- the user has permission to access all of the mailboxes on the communication server 111 for which migration is desired.
- the user can also select a maximum number of connections that are established with the source server 110 . This allows the user to control possible overloading of the source server 110 as communication data is migrated.
- Example numbers of connections can be between 1 and 10.
- the migration system 210 uses the credentials to identify the information necessary to initiate communication with the communication server 111 and accomplish the migration.
- the user confirms the details of the migration before the migration process is initiated. For example, as described below, the user is presented with validation information such as the number of mailboxes and groups that are going to be migrated. The user can confirm this information to allow the migration system 210 to proceed with the migration.
- the user is able to monitor the status of the migration as the migration occurs. This includes presenting migration information, such as the progress of the migration to the user. See FIG. 6 .
- the migration process is completed. This can occur after all of the data has been migrated to the target server. This can also occur if the user decides to prematurely abort the migration process.
- an e-mail report is sent to the user when migration is complete. Errors during populating and/or migration of data are sent with the e-mail report. There are two typical types of errors that can be reported: populating errors and data migration errors.
- Possible populating failures can be during reading the remote directory structure on the source server, creating the associated object (mailbox, distribution list, etc.) on the target server, and setting the properties of the object.
- Data migration errors can include possible authentication errors, remote system connection errors, bad items encountered, and other errors.
- MX record is a record in the Domain Name System that specifies a mail server responsible for accepting email messages on behalf of the source server.
- MX record is a record in the Domain Name System that specifies a mail server responsible for accepting email messages on behalf of the source server.
- “TargetAddress stamping” is used to modify delivery of emails.
- the NSPI protocol is used to add a TargetAddress property on the records for migrated users.
- an “alternative” email address corresponding to the user in the target server is added. This alternative email address allows messages that are sent to the user on the source server to be automatically routed to the mailbox on the target server when migration is completed.
- FIG. 5 an example method 500 for migrating data from a source server to a target server is shown.
- this involves the migration of communication data from a source server, such as the communication server 111 of the source server 110 , to a target server, such as the target server 130 .
- a request for migration is received from a user.
- the migration process can be initiated by a user of the source server 110 .
- the credentials of the user are requested.
- these credentials can include the user's email address and password for the communication server 111 in the source server 110 .
- the remaining steps of the method 500 can be done automatically with little or no input from the user.
- the credentials are used in an attempt to discover the relevant parameters associated with the source server 110 .
- an Autodiscover Service from Microsoft Corporation is used to identify addressing information associated with the source server 110 .
- the Autodiscover Service provides an automated mechanism for locating servers based on a user's email address.
- the Autodiscover service is used to identify the RPC/HTTP endpoint, Authentication Type support, whether SSL is supported by the source server, and the mail server name associated with the communication server 111 . If the Autodiscover Service is successful, the source system is accessed using the user's credentials to verify access.
- the user can also prompted to manually enter the source server settings, such as RPC/HTTP endpoint, Authentication type, etc.
- control is instead passed to operation 518 .
- a directory at the source server is queried to determine the number of objects (e.g., mailboxes, distribution lists, etc.) that are to be populated and migrated using the method 500 . These numbers are provided to the user to confirm before migration begins.
- this is accomplished by having the migration system query the source server over the Name Service Provider Interface (NSPI) protocol.
- NSPI Name Service Provider Interface
- the NSPI protocol provides messaging clients access to addressing data stored by a server, such as an Exchange Server.
- a server such as an Exchange Server.
- the NSPI protocol is the protocol that the OUTLOOK® messaging and collaboration client from Microsoft Corporation uses to access address book data remotely.
- the NSPI protocol is used by the migration system to get the number of recipient data stores that will be populated.
- the result is categorized into type of recipient (e.g., mailboxes, contacts, distribution groups). This information is then presented to the user.
- the directory structure at the source server is requested.
- control is instead passed to operation 522 .
- the directory structure for the communication store is built on the target server. Generally, this is done by traversing the directory structure from the source server and populating mailboxes accordingly.
- a mailbox is created for each user and distribution list in the directory structure. Initially, a check is made to determine if a mailbox has already been created for a particular user (using aliases as well, as described below) or distribution list. If not, the mailbox is created on the target server. In one example, a random password is also assigned to each mailbox.
- a mailbox has already been created for a user, an error is generated.
- a check is made to determine if the address is a legacy address that was used to address the user on the source server. If so, the legacy address is assigned as an X500 proxy address associated with the user. In this manner, legacy addresses can continue to be used to address the user without creating undeliverable messages.
- the populating in operation 522 can be modified if the entry in the directory structure has special properties. For example, if the entry in the directory structure is a resource, a mailbox is created on the target server with the appropriate property type, such as room or equipment, and the capacity property is set.
- a mailbox is created for the distribution group.
- a distribution group is created in a similar manner, except the group membership for the distribution group is maintained.
- a mapping is persisted between the group memberships defined on the source server and the new groups created on the target server. This mapping is used to rebuild the hierarchy associated within the groups, as described below.
- the identity of the group owner is noted and mapped to the corresponding user on the target server.
- the group membership of each created distribution list is rebuilt. Because the group membership of each list is stored in the mapping of the source groups and target groups, a single pass over each populated list is done to add the appropriate group members.
- control is passed to operation 526 .
- the mailbox data is requested from the source server.
- the mailbox data is requested in batches or per user mailbox. The data is populated based on the mailboxes that have been populated on the target server.
- the completion of the migration is reported to the user.
- any errors associated with the migration process are also provided.
- the user interface 600 includes a status window 610 displaying the status of the migration to the user.
- the status window 610 includes source information 612 .
- the source information includes the location of the source data (e.g., “source.com”) and the number of mailboxes processed (e.g., “16 of 100 mailboxes”).
- the status window 610 also includes initiation information 614 that provides the individual that started the migration (e.g., [email protected]) and the time at which the migration was initiated (e.g., Tuesday, Jan. 6, 2009 at 8:24 AM). Finally, the status window 610 includes error information 616 that reports any errors associated with the migration to the user. In this example, two mailboxes could not be created on the target server. The user can select “View Error Report” to access a report detailing the errors.
- the example embodiments described herein can be implemented as logical operations in a computing device in a networked computing system environment.
- the logical operations can be implemented as: (i) a sequence of computer implemented instructions, steps, or program modules running on a computing device; and (ii) interconnected logic or hardware modules running within a computing device.
- the logical operations can be implemented as algorithms in software, firmware, analog/digital circuitry, and/or any combination thereof, without deviating from the scope of the present disclosure.
- the software, firmware, or similar sequence of computer instructions can be encoded and stored upon a computer readable storage medium and can also be encoded within a carrier-wave signal for transmission between computing devices.
Landscapes
- Engineering & Computer Science (AREA)
- Business, Economics & Management (AREA)
- Human Resources & Organizations (AREA)
- Computer Hardware Design (AREA)
- Strategic Management (AREA)
- Entrepreneurship & Innovation (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Marketing (AREA)
- Quality & Reliability (AREA)
- Computing Systems (AREA)
- Computer Security & Cryptography (AREA)
- Economics (AREA)
- General Engineering & Computer Science (AREA)
- Operations Research (AREA)
- Data Mining & Analysis (AREA)
- Tourism & Hospitality (AREA)
- Physics & Mathematics (AREA)
- General Business, Economics & Management (AREA)
- General Physics & Mathematics (AREA)
- Theoretical Computer Science (AREA)
- Information Transfer Between Computers (AREA)
Abstract
Description
- This application is a continuation of application Ser. No. 15/707,853, filed Sep. 18, 2017, which is a continuation of application Ser. No. 13/007,095, filed Jan. 14, 2011, and assigned U.S. Pat. No. 9,769,150, which documents are both incorporated herein by reference in their entirety for all that they teach and for all purposes.
- Many institutions are moving email services from on-premise installations to hosted solutions. The process of moving an established email system to a hosted environment can be significant. It is usually necessary for the directory structure to be replicated in the hosted environment before the data associated with each user's mailbox can be sent. The replication of this directory structure can be difficult and require additional software and/or hardware to be installed locally to allow for the replication. This complexity can lead to inefficient processes and errors during the migration process.
- In one aspect, a method for migrating data from a source server to a target system includes: obtaining, using a computing device, a set of credentials to access the source server; accessing the source server using the set of credentials; requesting, automatically by the computing device, a directory structure associated with communication data from the source server; populating, by the computing device, the target system using the directory structure; requesting the communication data from the source server; and populating the target system with the communication data.
- In another aspect, a computing device includes: a processing unit; and a system memory connected to the processing unit, the system memory including instructions that, when executed by the processing unit, cause the processing unit to: access a source server; request a directory structure associated with communication data from the source server; populate a target server using the directory structure; request the communication data from the source server; and populate the target server with the communication data.
- In yet another aspect, a computer readable storage medium has computer-executable instructions that, when executed by a computing device, cause the computing device to perform steps comprising: obtaining, using the computing device, an email address and a password of a user of a source server; using autodiscover based on the email address to identify addressing information associated with the source server; accessing the source server using the addressing information and the password; requesting, automatically by the computing device, an offline address book from the source server over a Name Service Provider Interface (NSPI) protocol; populating, by the computing device, a target server using the offline address book, including creating one or more mailboxes for one or more users identified in the offline address book, and the target server being a hosted server; requesting communication data, including email items and calendar items, from the source server; populating the mailboxes on the target server with communication data; and reporting a status of a migration of the communication data to the user.
- This Summary is provided to introduce a selection of concepts, in a simplified form, that are further described below in the Detailed Description. This Summary is not intended to identify key or essential features of the claimed subject matter, nor is it intended to be used in any way to limit the scope of the claimed subject matter.
- Aspects of the present disclosure may be more completely understood in consideration of the following detailed description of various embodiments in connection with the accompanying drawings.
-
FIG. 1 shows an example networked computing environment. -
FIG. 2 shows details of a source server from the networked computing environment ofFIG. 1 and an example migration system. -
FIG. 3 shows an example server computing device of the migration system ofFIG. 2 . -
FIG. 4 shows an example method for a user to initiate migration of communication data. -
FIG. 5 shows an example method for migration of communication data. -
FIG. 6 shows an example user interface for a migration system. - The present disclosure is directed to the migration of communication data, such as email items, calendar items, task items, etc., from a source server to a target server.
- In some examples, the systems and methods described herein allow for the automated migration of communication data from a source server, which is located on-premise, to a target server, which is typically one or more hosted servers. A complete migration process is provided by: (i) re-creating the on-premise directory structure at the target server, and (ii) thereupon migrating the communication data from source server to the target server.
- For example, in one embodiment, a company decides to move its communication data, including all email items, calendar items, task items, etc., from an on-premise installation to a hosted solution. To do so, the company selects a cloud service that hosts an email solution off-premise for the company.
- Once the cloud service is selected, an administrator for the on-premise installation provides credentials to a migration system to initiate the migration. These credentials provide the migration system with administrative access to the on-premise communication server. The migration system accesses the on-premise communication server and obtains a copy of the directory structure associated with the communication server.
- The migration system uses the directory structure to populate the directory structure at the target communication server in the cloud. For example, the directory structure is used to populate mailboxes and distribution groups on the target communication server. Once populated, the migration system accesses the communication data on the on-premise server initiates a migration of the communication data from the on-premise communication server to the newly-populated mailboxes on the target communication server in the cloud.
- In this example, the migration process is automated. The administrator provides his or her credentials. The migration system thereupon downloads the directory structure, populates the target space, and migrates the data. The migration system reports the status and any errors associated with the migration to the administrator during the migration process.
- Referring now to
FIG. 1 , an example networkedcomputing environment 100 is shown. The environment includes asource server 110, anetwork 120, andtarget servers - The
source server 110 is typically one or more computing devices hosting one or more business applications. For example, thesource server 110 can include an Exchange Server from Microsoft Corporation of Redmond, Wash. The Exchange Server is an example of a business server that implements messaging and collaborative business processes. - Typically, the
source server 110 is part of a corporate network, such as a local area network or wide area network, that is positioned behind a firewall. For example, in a corporate environment, thesource server 110 is a network of computing devices maintained by a business. One or more Exchange Servers are part of thesource server 110 and provide communication and collaborative services, such as email, calendar, tasks, journals, etc. - The
network 120 is a bi-directional data communication path for data transfer between one or more devices. In the example shown, thenetwork 120 establishes a communication path for data transfer between thesource server 110 and thetarget servers network 120 can be of any of a number of wireless or hardwired WAN, LAN, Internet, or other packet-based communication networks such that data can be transferred among the elements of thenetworked computing environment 100. Other embodiments of thenetwork 120 are possible as well. - The
target servers network 120. In this example, thetarget servers - For example, the
target server 130 can host an Exchange Server that is accessible through thenetwork 120. Thetarget server 130 thereby provides a hosted solution for communication data to one or more individuals or businesses. - Referring now to
FIG. 2 , thesource server 110 is shown in more detail. Thesource server 110 includes acommunication server 111 with asource directory structure 112 andsource mailboxes 114. - In one example, the
source directory structure 112 includes a directory structure, such as the directory of addresses associated with thecommunication server 111 of thesource server 110. This can include the offline address book used by the Exchange Server to store email addresses, distribution lists, etc., associated with thecommunication server 111. - The
source mailboxes 114 are the one or more message stores that include all of the messaging data for thesource server 110, such as email items, calendar items, task items, journal items, etc. The message stores are included as part of the Exchange System. - The
source server 110 also includes acomputing device 116. Thecomputing device 116 can be located within or outside the corporate network. In one example, thecomputing device 116 includes a local application or web browser that is used by an administrator or other individual that has access to thecommunication server 111. As described further below, thecomputing device 116 can be used by the administrator to initiate the migration process. -
FIG. 2 also shows amigration system 210 that is configured to automate the migration of the information included in thecommunication server 111 to a target system, such as a hosted solution like thetarget servers - In this example, the
migration system 210 includes a user interface module 220, apopulating module 230, and adata migration module 240. - The user interface module 220 provides a user with information about the migration process. This information can include both information to initiate the process, as well as status information as the migration process progresses and is completed. See, e.g.,
FIG. 6 . - The
populating module 230 obtains information to allow thepopulating module 230 to populate the target system in preparation for transfer of the communication data to the target server. In this example, the populatingmodule 230 obtains directory structure from thesource directory structure 112. This directory structure is used to build the structure necessary to support the communication data that will be migrated from thecommunication server 111 to the target server, liketarget servers - In example embodiments, the
migration system 210 is incorporated as part of thetarget servers migration system 210 can be provided as a service on thetarget server 130. In another example, themigration system 210 is a separate system that facilitates the transfer from thecommunication server 111 in thesource server 110 to one of thetarget servers - Referring now to
FIG. 3 , in example embodiments, themigration system 210 includes one or more computing devices, such as acomputing device 301. Thecomputing device 301 includes at least oneprocessing unit 305 and asystem memory 310. Thesystem memory 310 can store anoperating system 315 for controlling operation of themigration system 210 or another computing device. Oneexample operating system 315 is WINDOWS® operating system from Microsoft Corporation. - The
system memory 310 may also include one ormore software applications 320 and may include program data.Software applications 320 may include many different types of single and multiple-functionality programs, such as an electronic mail program, a calendaring program, an Internet browsing program, a spreadsheet program, a program to track and report information, a word processing program, and many others. Examples of such software are the Exchange Server and Office suite of applications from Microsoft Corporation. - The
system memory 310 can include physical computer readable storage media such as, for example, magnetic disks, optical disks, or tape. Such additional storage is illustrated inFIG. 3 byremovable storage 325 andnon-removable storage 330. Computer readable storage media can include physical volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information, such as computer readable or computer-executable instructions, data structures, program modules, or other data. - Computer readable storage media can also include, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed by the
migration system 210. Any such computer storage media may be part of or external to themigration system 210. - Communication media is distinguished from computer readable storage media. Communication media may typically be embodied by computer readable instructions, data structures, program modules, or other data in a modulated data signal, such as a carrier wave or other transport mechanism, and includes any information delivery media. The term “modulated data signal” means a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal. By way of example, communication media includes wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared and other wireless media.
- The
migration system 210 can also have any number and type of aninput device 335 andoutput device 340. Anexample input device 335 includes a keyboard, mouse, pen, voice input device, touch input device, and others. Anexample output device 340 includes a display, speakers, printer, and others. Themigration system 210 can also contain acommunication connection 345 configured to enable communications with other computing devices over a network (e.g.,network 120 ofFIG. 1 ) in a distributed computing system environment. - In example embodiments, the various other servers and systems described herein can include one or
more computing devices 301 configured in a manner similar to that shown inFIG. 3 . - Referring now to
FIG. 4 , anexample method 400 for a user to migrate data from a source server to a target server is shown. - In one example, the
method 400 is presented to the user as a wizard that assists the user through the migration process. For example, a wizard is provided that collects the necessary information to allow the migration to start. Additionally, the user can monitor the status of the migration and review any errors that may occur. - Initially, at
operation 410, the user initiates the migration process. In one example, this can occur by having the user use thecomputing device 116 to contact themigration system 210 to request the migration of communication data from thecommunication server 111 to a remote server, such as thetarget server 130. - Next, at
operation 420, the user provides the user's credentials to themigration system 210. In one example, this includes having the user provide the user's e-mail address and password for thecommunication server 111 in thesource server 110. In this example, the user has permission to access all of the mailboxes on thecommunication server 111 for which migration is desired. - In addition to providing the user's credentials, the user can also select a maximum number of connections that are established with the
source server 110. This allows the user to control possible overloading of thesource server 110 as communication data is migrated. Example numbers of connections can be between 1 and 10. - As described further below, the
migration system 210 uses the credentials to identify the information necessary to initiate communication with thecommunication server 111 and accomplish the migration. - Next, at
operation 430, the user confirms the details of the migration before the migration process is initiated. For example, as described below, the user is presented with validation information such as the number of mailboxes and groups that are going to be migrated. The user can confirm this information to allow themigration system 210 to proceed with the migration. - Next, at
operation 440, the user is able to monitor the status of the migration as the migration occurs. This includes presenting migration information, such as the progress of the migration to the user. SeeFIG. 6 . - Finally, at
operation 450, the migration process is completed. This can occur after all of the data has been migrated to the target server. This can also occur if the user decides to prematurely abort the migration process. - In one example, an e-mail report is sent to the user when migration is complete. Errors during populating and/or migration of data are sent with the e-mail report. There are two typical types of errors that can be reported: populating errors and data migration errors.
- Possible populating failures can be during reading the remote directory structure on the source server, creating the associated object (mailbox, distribution list, etc.) on the target server, and setting the properties of the object. Data migration errors can include possible authentication errors, remote system connection errors, bad items encountered, and other errors.
- Upon migration completion, the user is reminded to modify the delivery of email so that new email is delivered to the target server rather than the
communication server 111. In one example, this involves having the user update the mail exchanger record (MX record), which is a record in the Domain Name System that specifies a mail server responsible for accepting email messages on behalf of the source server. In another example, “TargetAddress stamping” is used to modify delivery of emails. In this example, the NSPI protocol is used to add a TargetAddress property on the records for migrated users. Specifically, an “alternative” email address corresponding to the user in the target server is added. This alternative email address allows messages that are sent to the user on the source server to be automatically routed to the mailbox on the target server when migration is completed. - Referring now to
FIG. 5 , anexample method 500 for migrating data from a source server to a target server is shown. In one disclosed example, this involves the migration of communication data from a source server, such as thecommunication server 111 of thesource server 110, to a target server, such as thetarget server 130. - Initially, at
operation 510, a request for migration is received from a user. As previously noted, the migration process can be initiated by a user of thesource server 110. - Next, at
operation 512, the credentials of the user are requested. Typically, these credentials can include the user's email address and password for thecommunication server 111 in thesource server 110. - Generally, once the user provides the user's credentials, the remaining steps of the
method 500 can be done automatically with little or no input from the user. - Next, at
operation 514, the credentials are used in an attempt to discover the relevant parameters associated with thesource server 110. In this example, an Autodiscover Service from Microsoft Corporation is used to identify addressing information associated with thesource server 110. The Autodiscover Service provides an automated mechanism for locating servers based on a user's email address. In this context, the Autodiscover service is used to identify the RPC/HTTP endpoint, Authentication Type support, whether SSL is supported by the source server, and the mail server name associated with thecommunication server 111. If the Autodiscover Service is successful, the source system is accessed using the user's credentials to verify access. - Next, at
operation 516, a determination is made regarding whether or not the source server has been successfully accessed. If the source server has not been accessed successfully due to a failure in the Autodiscover Service or a failure in the credentials to provide access, control is passed back tooperation 512. When prompting the user to re-input credentials, the user can also prompted to manually enter the source server settings, such as RPC/HTTP endpoint, Authentication type, etc. - If the server is successfully accessed at
operation 516, control is instead passed tooperation 518. Atoperation 518, a directory at the source server is queried to determine the number of objects (e.g., mailboxes, distribution lists, etc.) that are to be populated and migrated using themethod 500. These numbers are provided to the user to confirm before migration begins. - In one example, this is accomplished by having the migration system query the source server over the Name Service Provider Interface (NSPI) protocol. The NSPI protocol provides messaging clients access to addressing data stored by a server, such as an Exchange Server. For example, the NSPI protocol is the protocol that the OUTLOOK® messaging and collaboration client from Microsoft Corporation uses to access address book data remotely.
- The NSPI protocol is used by the migration system to get the number of recipient data stores that will be populated. In this example, the result is categorized into type of recipient (e.g., mailboxes, contacts, distribution groups). This information is then presented to the user.
- Next, at
operation 519, the directory structure at the source server is requested. In the example shown, this involves themigration system 210 requesting the directory structure from thecommunication server 111 using the NSPI protocol, as described above. - Next, at
operation 520, a determination is made regarding whether or not the directory structure has been obtained from the source server. If not, control is passed tooperation 530, and an error is indicated for the user. - Instead, if the directory structure is successfully obtained from the source server, control is instead passed to
operation 522. Atoperation 522, the directory structure for the communication store is built on the target server. Generally, this is done by traversing the directory structure from the source server and populating mailboxes accordingly. - Specifically, a mailbox is created for each user and distribution list in the directory structure. Initially, a check is made to determine if a mailbox has already been created for a particular user (using aliases as well, as described below) or distribution list. If not, the mailbox is created on the target server. In one example, a random password is also assigned to each mailbox.
- If a mailbox has already been created for a user, an error is generated. In addition, a check is made to determine if the address is a legacy address that was used to address the user on the source server. If so, the legacy address is assigned as an X500 proxy address associated with the user. In this manner, legacy addresses can continue to be used to address the user without creating undeliverable messages.
- The populating in
operation 522 can be modified if the entry in the directory structure has special properties. For example, if the entry in the directory structure is a resource, a mailbox is created on the target server with the appropriate property type, such as room or equipment, and the capacity property is set. - If the entry is a distribution group, a mailbox is created for the distribution group. A distribution group is created in a similar manner, except the group membership for the distribution group is maintained. A mapping is persisted between the group memberships defined on the source server and the new groups created on the target server. This mapping is used to rebuild the hierarchy associated within the groups, as described below. In addition, the identity of the group owner is noted and mapped to the corresponding user on the target server.
- Once all objects have been populated on the target server, the group membership of each created distribution list is rebuilt. Because the group membership of each list is stored in the mapping of the source groups and target groups, a single pass over each populated list is done to add the appropriate group members.
- Once the directory structure is built, control is passed to
operation 526. Atoperation 526, the mailbox data is requested from the source server. In some examples, the mailbox data is requested in batches or per user mailbox. The data is populated based on the mailboxes that have been populated on the target server. - Finally, at
operation 528, a determination is made regarding whether nor not mailbox data migration is complete. If not, control is passed back tooperation 526. If so, control is instead passed tooperation 530. - At
operation 530, the completion of the migration is reported to the user. In some example, any errors associated with the migration process are also provided. - For example, referring now to
FIG. 6 , anexample user interface 600 is shown. Theuser interface 600 includes astatus window 610 displaying the status of the migration to the user. In this example, thestatus window 610 includessource information 612. The source information includes the location of the source data (e.g., “source.com”) and the number of mailboxes processed (e.g., “16 of 100 mailboxes”). - The
status window 610 also includesinitiation information 614 that provides the individual that started the migration (e.g., [email protected]) and the time at which the migration was initiated (e.g., Tuesday, Jan. 6, 2009 at 8:24 AM). Finally, thestatus window 610 includeserror information 616 that reports any errors associated with the migration to the user. In this example, two mailboxes could not be created on the target server. The user can select “View Error Report” to access a report detailing the errors. - The example embodiments described herein can be implemented as logical operations in a computing device in a networked computing system environment. The logical operations can be implemented as: (i) a sequence of computer implemented instructions, steps, or program modules running on a computing device; and (ii) interconnected logic or hardware modules running within a computing device.
- For example, the logical operations can be implemented as algorithms in software, firmware, analog/digital circuitry, and/or any combination thereof, without deviating from the scope of the present disclosure. The software, firmware, or similar sequence of computer instructions can be encoded and stored upon a computer readable storage medium and can also be encoded within a carrier-wave signal for transmission between computing devices.
- Although the subject matter has been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.
Claims (20)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US16/286,453 US20190199710A1 (en) | 2011-01-14 | 2019-02-26 | Directory driven mailbox migrations |
Applications Claiming Priority (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US13/007,095 US9769150B2 (en) | 2011-01-14 | 2011-01-14 | Directory driven mailbox migrations |
US15/707,853 US10263977B2 (en) | 2011-01-14 | 2017-09-18 | Directory driven mailbox migrations |
US16/286,453 US20190199710A1 (en) | 2011-01-14 | 2019-02-26 | Directory driven mailbox migrations |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US15/707,853 Continuation US10263977B2 (en) | 2011-01-14 | 2017-09-18 | Directory driven mailbox migrations |
Publications (1)
Publication Number | Publication Date |
---|---|
US20190199710A1 true US20190199710A1 (en) | 2019-06-27 |
Family
ID=46491767
Family Applications (3)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/007,095 Active 2031-08-09 US9769150B2 (en) | 2011-01-14 | 2011-01-14 | Directory driven mailbox migrations |
US15/707,853 Active US10263977B2 (en) | 2011-01-14 | 2017-09-18 | Directory driven mailbox migrations |
US16/286,453 Abandoned US20190199710A1 (en) | 2011-01-14 | 2019-02-26 | Directory driven mailbox migrations |
Family Applications Before (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/007,095 Active 2031-08-09 US9769150B2 (en) | 2011-01-14 | 2011-01-14 | Directory driven mailbox migrations |
US15/707,853 Active US10263977B2 (en) | 2011-01-14 | 2017-09-18 | Directory driven mailbox migrations |
Country Status (1)
Country | Link |
---|---|
US (3) | US9769150B2 (en) |
Families Citing this family (18)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9769150B2 (en) | 2011-01-14 | 2017-09-19 | Microsoft Technology Licensing, Llc | Directory driven mailbox migrations |
US8606878B2 (en) * | 2011-02-28 | 2013-12-10 | Red Hat, Inc. | Systems and methods for de-populating cloud data store |
US10965742B2 (en) | 2012-02-13 | 2021-03-30 | SkyKick, Inc. | Migration project automation, e.g., automated selling, planning, migration and configuration of email systems |
US9971787B2 (en) | 2012-07-23 | 2018-05-15 | Red Hat, Inc. | Unified file and object data storage |
CN103731336A (en) * | 2012-10-12 | 2014-04-16 | 腾讯科技(深圳)有限公司 | Mailbox data migration method and device |
US8983908B2 (en) * | 2013-02-15 | 2015-03-17 | Red Hat, Inc. | File link migration for decommisioning a storage server |
CN103490983B (en) * | 2013-09-17 | 2017-03-01 | 新浪网技术(中国)有限公司 | Corporate mail system and its method carrying out mail migration |
US11016941B2 (en) | 2014-02-28 | 2021-05-25 | Red Hat, Inc. | Delayed asynchronous file replication in a distributed file system |
US10025808B2 (en) | 2014-03-19 | 2018-07-17 | Red Hat, Inc. | Compacting change logs using file content location identifiers |
US9965505B2 (en) | 2014-03-19 | 2018-05-08 | Red Hat, Inc. | Identifying files in change logs using file content location identifiers |
US9986029B2 (en) | 2014-03-19 | 2018-05-29 | Red Hat, Inc. | File replication using file content location identifiers |
US10027738B2 (en) * | 2014-10-01 | 2018-07-17 | SkyKick, Inc. | Optimizing data migration processes |
US10771452B2 (en) * | 2015-03-04 | 2020-09-08 | SkyKick, Inc. | Autonomous configuration of email clients during email server migration |
US10592483B2 (en) | 2015-04-05 | 2020-03-17 | SkyKick, Inc. | State record system for data migration |
US10649671B2 (en) * | 2015-05-21 | 2020-05-12 | Quest Software Inc. | Processing unknown or unexpected properties encountered during migration or archiving operations |
US10402381B2 (en) * | 2015-06-04 | 2019-09-03 | Quest Software Inc. | Determine confidence of mail archive ownership from senders in “sent items” folder |
CN109936611B (en) * | 2017-12-19 | 2021-08-24 | 中标软件有限公司 | Data migration method of mail |
CN109802884B (en) * | 2018-12-29 | 2021-09-07 | 论客科技(广州)有限公司 | Campus mail migration method and device |
Citations (23)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5915004A (en) * | 1996-07-11 | 1999-06-22 | Microsoft Corporation | Moving a messaging system mailbox |
US6208717B1 (en) * | 1997-03-03 | 2001-03-27 | Unisys Corporation | Method for migrating or altering a messaging system |
US20030073494A1 (en) * | 2001-10-15 | 2003-04-17 | Kalpakian Jacob H. | Gaming methods, apparatus, media and signals |
US20040267890A1 (en) * | 2003-04-18 | 2004-12-30 | Serge Soulet | Method and apparatus for causing one messaging service to migrate towards another |
US20060015584A1 (en) * | 2004-07-13 | 2006-01-19 | Teneros, Inc. | Autonomous service appliance |
US20060015645A1 (en) * | 2004-07-13 | 2006-01-19 | Teneros, Inc. | Network traffic routing |
US20060015641A1 (en) * | 2004-07-13 | 2006-01-19 | Teneros, Inc. | Autonomous service backup and migration |
US20060015764A1 (en) * | 2004-07-13 | 2006-01-19 | Teneros, Inc. | Transparent service provider |
US20070106733A1 (en) * | 2005-11-10 | 2007-05-10 | Microsoft Corporation | Cross-forest sharing |
US20070143420A1 (en) * | 2005-12-19 | 2007-06-21 | William Daniell | Methods, systems, and computer program products for sorting electronic-mail messages |
US20070244996A1 (en) * | 2006-04-14 | 2007-10-18 | Sonasoft Corp., A California Corporation | Web enabled exchange server standby solution using mailbox level replication |
US20080109448A1 (en) * | 2006-11-06 | 2008-05-08 | Messageone, Inc. | System and Method for Managing Data Across Multiple Environments |
US20080235238A1 (en) * | 2007-03-23 | 2008-09-25 | Microsoft Corporation | E-Mail Tool Management Shell Command Set |
US20080288559A1 (en) * | 2007-05-18 | 2008-11-20 | Sonasoft Corp. | Exchange server standby solution using mailbox level replication with crossed replication between two active exchange servers |
US20090144743A1 (en) * | 2007-11-29 | 2009-06-04 | Microsoft Corporation | Mailbox Configuration Mechanism |
US7552358B1 (en) * | 2005-04-22 | 2009-06-23 | Symantec Operating Corporation | Efficient backup and restore using metadata mapping |
US20110145565A1 (en) * | 2009-12-14 | 2011-06-16 | Microsoft Corporation | Federated authentication for mailbox replication |
US20110264748A1 (en) * | 2010-04-26 | 2011-10-27 | BitTitan Inc. | On-demand mailbox synchronization and migration system |
US20130061291A1 (en) * | 2009-09-30 | 2013-03-07 | Amazon Technologies, Inc. | Modular Device Authentication Framework |
US8447826B1 (en) * | 2009-09-14 | 2013-05-21 | Symantec Corporation | Method and apparatus for providing highly available storage groups |
US9213697B1 (en) * | 2009-05-20 | 2015-12-15 | Acronis International Gmbh | System and method for restoration of MS exchange server mail |
US9235641B1 (en) * | 2007-01-31 | 2016-01-12 | Emc Corporation | Method and apparatus for archive processing of electronic messages |
US10467187B1 (en) * | 2009-05-20 | 2019-11-05 | Acronis International GbmH | System and method for restoration of MICROSOFT exchange server mail |
Family Cites Families (13)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7801913B2 (en) * | 1998-12-07 | 2010-09-21 | Oracle International Corporation | System and method for querying data for implicit hierarchies |
US6829333B1 (en) * | 2000-01-31 | 2004-12-07 | Frazier Spaeth Llc | Automated system for messaging based on chains of relationships |
US6938039B1 (en) * | 2000-06-30 | 2005-08-30 | Emc Corporation | Concurrent file across at a target file server during migration of file systems between file servers using a network file system access protocol |
US7587455B2 (en) | 2004-05-14 | 2009-09-08 | Mirapoint Software, Inc. | Method for mailbox migration |
GB0426509D0 (en) * | 2004-12-03 | 2005-01-05 | Ibm | An email transaction system |
US8799206B2 (en) * | 2005-02-07 | 2014-08-05 | Mimosa Systems, Inc. | Dynamic bulk-to-brick transformation of data |
EP1788770B1 (en) * | 2005-11-16 | 2009-04-22 | Totemo AG | A method for establishing a secure e-mail communication channel between a sender and a recipient |
US7617243B2 (en) * | 2006-05-24 | 2009-11-10 | Microsoft Corporation | Integrated address book based on departmental hierarchy |
US8346874B2 (en) | 2008-01-22 | 2013-01-01 | Microsoft Corporation | Mail object migration |
US8856376B1 (en) * | 2008-12-18 | 2014-10-07 | Bank Of America Corporation | Stabilization tool for a high-capacity network infrastructure |
US8224924B2 (en) * | 2009-03-27 | 2012-07-17 | Bank Of America Corporation | Active email collector |
US9769150B2 (en) | 2011-01-14 | 2017-09-19 | Microsoft Technology Licensing, Llc | Directory driven mailbox migrations |
US9571435B2 (en) * | 2014-09-04 | 2017-02-14 | International Business Machines Corporation | Automated spam filter updating by tracking user navigation |
-
2011
- 2011-01-14 US US13/007,095 patent/US9769150B2/en active Active
-
2017
- 2017-09-18 US US15/707,853 patent/US10263977B2/en active Active
-
2019
- 2019-02-26 US US16/286,453 patent/US20190199710A1/en not_active Abandoned
Patent Citations (23)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5915004A (en) * | 1996-07-11 | 1999-06-22 | Microsoft Corporation | Moving a messaging system mailbox |
US6208717B1 (en) * | 1997-03-03 | 2001-03-27 | Unisys Corporation | Method for migrating or altering a messaging system |
US20030073494A1 (en) * | 2001-10-15 | 2003-04-17 | Kalpakian Jacob H. | Gaming methods, apparatus, media and signals |
US20040267890A1 (en) * | 2003-04-18 | 2004-12-30 | Serge Soulet | Method and apparatus for causing one messaging service to migrate towards another |
US20060015584A1 (en) * | 2004-07-13 | 2006-01-19 | Teneros, Inc. | Autonomous service appliance |
US20060015645A1 (en) * | 2004-07-13 | 2006-01-19 | Teneros, Inc. | Network traffic routing |
US20060015641A1 (en) * | 2004-07-13 | 2006-01-19 | Teneros, Inc. | Autonomous service backup and migration |
US20060015764A1 (en) * | 2004-07-13 | 2006-01-19 | Teneros, Inc. | Transparent service provider |
US7552358B1 (en) * | 2005-04-22 | 2009-06-23 | Symantec Operating Corporation | Efficient backup and restore using metadata mapping |
US20070106733A1 (en) * | 2005-11-10 | 2007-05-10 | Microsoft Corporation | Cross-forest sharing |
US20070143420A1 (en) * | 2005-12-19 | 2007-06-21 | William Daniell | Methods, systems, and computer program products for sorting electronic-mail messages |
US20070244996A1 (en) * | 2006-04-14 | 2007-10-18 | Sonasoft Corp., A California Corporation | Web enabled exchange server standby solution using mailbox level replication |
US20080109448A1 (en) * | 2006-11-06 | 2008-05-08 | Messageone, Inc. | System and Method for Managing Data Across Multiple Environments |
US9235641B1 (en) * | 2007-01-31 | 2016-01-12 | Emc Corporation | Method and apparatus for archive processing of electronic messages |
US20080235238A1 (en) * | 2007-03-23 | 2008-09-25 | Microsoft Corporation | E-Mail Tool Management Shell Command Set |
US20080288559A1 (en) * | 2007-05-18 | 2008-11-20 | Sonasoft Corp. | Exchange server standby solution using mailbox level replication with crossed replication between two active exchange servers |
US20090144743A1 (en) * | 2007-11-29 | 2009-06-04 | Microsoft Corporation | Mailbox Configuration Mechanism |
US9213697B1 (en) * | 2009-05-20 | 2015-12-15 | Acronis International Gmbh | System and method for restoration of MS exchange server mail |
US10467187B1 (en) * | 2009-05-20 | 2019-11-05 | Acronis International GbmH | System and method for restoration of MICROSOFT exchange server mail |
US8447826B1 (en) * | 2009-09-14 | 2013-05-21 | Symantec Corporation | Method and apparatus for providing highly available storage groups |
US20130061291A1 (en) * | 2009-09-30 | 2013-03-07 | Amazon Technologies, Inc. | Modular Device Authentication Framework |
US20110145565A1 (en) * | 2009-12-14 | 2011-06-16 | Microsoft Corporation | Federated authentication for mailbox replication |
US20110264748A1 (en) * | 2010-04-26 | 2011-10-27 | BitTitan Inc. | On-demand mailbox synchronization and migration system |
Also Published As
Publication number | Publication date |
---|---|
US20120185926A1 (en) | 2012-07-19 |
US10263977B2 (en) | 2019-04-16 |
US9769150B2 (en) | 2017-09-19 |
US20180007036A1 (en) | 2018-01-04 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US10263977B2 (en) | Directory driven mailbox migrations | |
US11265376B2 (en) | Migration project automation, e.g., automated selling, planning, migration and configuration of email systems | |
AU2018206697B2 (en) | Authentication of service requests initiated from a social networking site | |
US8140506B2 (en) | File sharing based on social network | |
US8416935B2 (en) | Methods and systems for calling conference participants to establish a conference call | |
JP6924906B2 (en) | Systems and methods for initiating external actions via a group-based communication system | |
US10778669B2 (en) | Autonomous configuration of email clients during email server migration | |
US10645087B2 (en) | Centralized authenticating abstraction layer with adaptive assembly line pathways | |
US20100010998A1 (en) | Document storage access on a time-based approval basis | |
JP2013536497A (en) | Method and apparatus for automated workflow management | |
US20100094652A1 (en) | System, method, and a computer program product for networking healthcare professionals | |
US20160028591A1 (en) | Managing cross-premises resources through integrated view | |
US20080133726A1 (en) | Network administration with guest access | |
US9769099B2 (en) | Systems and methods of handling email communication | |
US11153377B1 (en) | Shared channel invitation paths | |
US20220035770A1 (en) | Asynchronous method for provisioning a service using file distribution technology | |
US20180109490A1 (en) | Active and passive method to perform ip to name resolution in organizational environments | |
US20240015040A1 (en) | Domain and invite management in a group-based communication system | |
US20100179997A1 (en) | Message tracking between organizations | |
US11695727B1 (en) | Techniques for bidirectional cross-platform communications | |
Wesselius et al. | Exchange Infrastructure | |
Stanek | Microsoft Exchange Server 2007 administrator's pocket consultant | |
Goodman | IPhone with Microsoft Exchange Server 2010: Business Integration and Deployment | |
Wesselius et al. | Coexistence and Migration | |
Wesselius et al. | Troubleshooting Exchange 2013 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: MICROSOFT TECHNOLOGY LICENSING, LLC, WASHINGTON Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:MICROSOFT CORPORATION;REEL/FRAME:048447/0650 Effective date: 20141014 Owner name: MICROSOFT CORPORATION, WASHINGTON Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:TOPATAN, KUTLAY;IVANOV, MAXIM;BOCTOR, VICTOR;AND OTHERS;SIGNING DATES FROM 20110105 TO 20110113;REEL/FRAME:048447/0617 |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: DOCKETED NEW CASE - READY FOR EXAMINATION |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: NON FINAL ACTION MAILED |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: RESPONSE TO NON-FINAL OFFICE ACTION ENTERED AND FORWARDED TO EXAMINER |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: FINAL REJECTION MAILED |
|
STCV | Information on status: appeal procedure |
Free format text: NOTICE OF APPEAL FILED |
|
STCV | Information on status: appeal procedure |
Free format text: APPEAL READY FOR REVIEW |
|
STCV | Information on status: appeal procedure |
Free format text: ON APPEAL -- AWAITING DECISION BY THE BOARD OF APPEALS |
|
STCV | Information on status: appeal procedure |
Free format text: BOARD OF APPEALS DECISION RENDERED |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- AFTER EXAMINER'S ANSWER OR BOARD OF APPEALS DECISION |