Interacciones hormonales de la oleoil estrona

1. Verify System Requirements

Make sure that all hardware and software components are installed and conform to the NME System Requirements cited in the corresponding NME Release Notes.

Local AD Server: In the end your organization will be served by the remote BPOS-S Exchange and Active Directory servers, but during the migration transition you will temporarily need a local "staging" AD server with Exchange schema to facilitate directory updates. The local AD server must conform to the System Requirements for the AD server (as specified in the current NME Release Notes), and must be configured with the Exchange schema. No live local Exchange server is required.

2. Prepare BPOS-S Components and Install Software

When you first order BPOS-S services, Microsoft gives you a specified domain called a MODRD (Microsoft Online Direct Routing Domain) that will later be used as your forwarding address.

Microsoft’s Directory Sync tool may reside on the admin's NME migration workstation if it is a Server 2003 box running SP2. If the migration machine is run on an XP platform then it must reside on a separate workstation.

Install the necessary BPOS-S tools, such as the Single Sign-On application, and the Microsoft Dir Sync tool, on the appropriate machines.

3. Create Admin Accounts

Create these necessary admin accounts:

• An administrative account in BPOS-S that is enabled with a mailbox (i.e., [email protected]).

• An administrative account in the staging AD server with rights that permit manipulation of objects.

4. Request Receive-As Rights for BPOS-S Organizational Unit (OU)

Enter a support ticket at the Microsoft Online Services Administration Center website to request Receive-As rights for the organizational unit (OU) in BPOS-S.

These rights are not normally active, but are required for migration. Under the Support tab click Open a new service request. This opens a form to request Receive-As Rights for the duration of the migration. The ticket should be resolved in about one day, and will be posted in an email back to you, as well as listed in the Support area of the Administration Center.

5. Verify Current Domain

To retain your organization's current domain, verify it in the Microsoft Online Services Administration Center, under Domains. Type the domain name and set it as an external relay, and then follow the steps through the wizard. The verification wizard will ask you to add two CNAME records to your domain host.

The domain will not be verified and usable until it is recognized by this process.

6. Define the BPOS-S Migration Admin Profile in NME

In NME's Notes Migration Manager, in the Exchange Server Configuration screen, enter the Exchange server information for the BPOS environment (Microsoft should provide this). The Exchange credentials you enter here are for the admin account you created in BPOS. Note:

• If the Administrator user name is a fully qualified SMTP address, you need not enter the Administrator user domain.

• Under Exchange over the Internet: Mark the checkbox for Connect using Outlook Anywhere to open an Exchange Proxy Settings dialog box, where you must configure use of the RPC protocol:

• Under Connection Settings fill in the proxy server settings provided for the BPOS-S server for the migration account granted Receive-As rights in step 4 above. You may follow this link to find the Exchange proxy server for your region in Microsoft Online Services Help:

Microsoft Online Services Help: URLs for Microsoft Online Services To find the Exchange Server entry for the Exchange credentials box (either of two methods):

• Check the Outlook profile created by the BPOS Single Sign-On Client (the SSO Client) for the migration account for the Exchange Server name. Copy the Exchange Server name to the Exchange Server setting in the Exchange credentials box. —OR—

• Login to Outlook Web Access (OWA), then click Options and then About. From the About Outlook Web Access page, copy server name from the Client Access server name entry to the Exchange Server setting in the Exchange credentials box.

• Mark Connect using SSL only.

• Mark Only connect to proxy servers that have this principal name in their certificate, and fill the associated text box with the information provided by Microsoft.

• Mark both the On fast networks… and On slow networks… boxes.

• Verify the Proxy authentication settings is set to NTLM Authentication.

7. Set Application Timeout Feature

Set the Application Timeout feature (on the Edit menu of Notes Migration Manager) to 30. This value specifies the number of minutes of inactivity the Wizards will wait within a program run before concluding that a process has encountered a fatal error, and aborting the process.

The default value of 15 is well suited to most migrations to local servers, where shorter and higher-quality transmission paths make timeouts less common. But a BPOS-S migration typically generates more process timeouts than migration to a local server, and this becomes particularly problematic if you are migrating large numbers of large messages (usually due to large attachments). The Wizard may even abort its run altogether if it encounters too many timeouts. You should therefore set the timeout threshhold to 30 minutes to make the feature more patient and forgiving for a BPOS-S migration.

If you still encounter too many timeouts at 30 minutes, you could disable the timeout feature by setting Minutes to 0, which tells the Wizard to wait indefinitely (forever) for activity, rather than reporting that a fatal error has occurred after some period of time.

8. Run NME Directory Exporter, Define Collections

Run NME's Directory Export Wizard to populate the NME SQL database with users that will be synced into the BPOS-S environment. Then use NME's Collection Wizard to define your migration collections (sets of objects to be migrated). This can help moderate the migration of objects and data.

See the Directory Export Wizard and Collection Wizard chapters of the NME Administration Guide for complete information about these Wizards.

9. Provision the AD Staging Server

Merge Objects and Create Missing Objects

If the staging AD server is new, and without any user objects in it: Run NME's AD Object Merging Wizard for each collection. This Wizard will create a new user object in the AD staging server for any object in the collection that does not already exist in AD. If the Wizard finds an existing object in AD that corresponds to an object in the collection, it stamps the AD object with the appropriate mail address. (A new object created by the Wizard is not activated, and does not need to be mailbox enabled.) See the AD Object Merging Wizard chapter of the NME Administration Guide for complete information.

Provision Notes Groups in AD

Use NME's AD Groups Provisioning Wizard to provision groups in the AD staging server. See the AD Groups Provisioning Wizard chapter of the NME

Administration Guide for complete information.

10. Synchronize the Staging AD and BPOS-S AD

If your AD staging server includes any objects that you do not want copied to the BPOS-S hosted Active Directory server, remove them now. Then run Microsoft's DirSync tool to copy user objects from the AD staging server to the BPOS-S hosted AD server.

11. Enable Accounts in the BPOS-S Active Directory

Notes Migrator for Exchange cannot automatically batch-enable accounts in the BPOS-S Active Directory due to permissions issues that, at least in this release, are inherent in dealing with the remotely hosted BPOS-S services. Admins therefore must manually enable all users in the BPOS-S Active Directory, assign temporary passwords, and then notify users of their passwords. To do this:

1. Log into the Microsoft Online Services Administration Center with your admin account. Then click on the Users tab, and then the User List link. On the left side of the tab you should see links for:

All Enabled Users Administrators Disabled Accounts Never signed in

2. Check the boxes of the users you want to enable, and then Activate User Accounts by clicking on the named link to the right. The program will then lead you through several steps (for each user) to create the user mailbox and set a temporary password.

Users should then have active mailboxes to which mail can be migrated.

Important: Remember to send all users their temporary passwords!