Search Engine: Elastic

Article ID: 117116, created on Sep 5, 2013, last review on May 9, 2014

  • Applies to:
  • Operations Automation 5.x


Exchange provisioning failed as follows:

error_message = Could not find the following Exchange 2010 services for provisioning:  
Exchange2010Mailstore (mailboxes),
Exchange2010Mailstore (public folders), Exchange2010SMTP, Exchange2010SMTPAuth, Exchange2010OAB, Exchange2010POP3, Exchange2010IMAP4, Exchange2010Protocols, Exchange2010Autodiscover.  

Please check the following requirements are met:  
1) all necessary services are installed in one AD domain;
2) all services have the specified attributes ('Exchange 2010');
3) there are some mailbox stores on mail-store services which have the specified attributes ('');
4) there exist ready to provide mailbox and (or) public folder stores;
5) branding is configured.

In poa.debug.log on POA management node, the following message can be found:

Aug 15 12:01:21 osscore : INF [1:18864:b65f6b90:3576 1:19050:b5af6b90 Exchange]: [txn:518616 Exchange::Utils::ServiceFilter::resolveService] [Service selection] Skipping service (id=156) because domain 'domain2.local' is required, but the service belongs to 'domain1.local'

AD domain 'domain2.local' either does not exist at all or does not have any Exchange services deployed, and you expect 'domain1.local' to be used for provisioning.


In the Hosted Exchange resource type activation parameter, the value for 'FQDN of AD domain used for provisioning' is not configured correctly.

If you only have one domain with Exchange hosting, you can leave 'FQDN of AD domain used for provisioning' blank, POA can figure out the correct domain automatically. However, if an incorrect domain is explicitly specified, provisioning will fail.


Change the value of parameter 'FQDN of AD domain used for provisioning' to a proper one, e.g. 'domain1.local' in this example:

Top> Service Director> Provisioning Manager> Resource Types> Hosted Exchange> Activation Parameters
FQDN of AD domain used for provisioning : domain1.local

Alternatilvely it can be done at service template level:

Top> Service Director> Provisioning Manager> Service Template> [Problem template] > Parameters

caea8340e2d186a540518d08602aa065 5356b422f65bdad1c3e9edca5d74a1ae 2554725ed606193dd9bbce21365bed4e e12cea1d47a3125d335d68e6d4e15e07

Email subscription for changes to this article
Save as PDF