There are no registered Microsoft Exchange Server available

[seocsitvmw]

Hi everybody!

I need some help on VDP appliance 6 and client for Exchange.

I've installed VDP for Exchange Server Client on an Exchange 2010 SP3 server and registered it using avregister.bat specifying dns name for VDP Appliance; the registration process ended successfully as per avagent.log

2015-10-20 09:17:37 avagent Info <7502>: Registration of client /clients/SERVERDNSNAME with MCS VDPDNSNAME:28001 successful.

2015-10-20 09:17:37 avagent Info <8422>: Creating clientlogs directory 'C:\Program Files\avp\var\clientlogs'

2015-10-20 09:17:37 avagent Info <5928>: Registration of plugin 3023 update successful.

2015-10-20 09:17:37 avagent Info <5928>: Registration of plugin 3001 Windows successful.

2015-10-20 09:17:37 avagent Info <5928>: Registration of plugin 3018 Exchange VSS Writer 2007 successful.

2015-10-20 09:17:37 avagent Info <5928>: Registration of plugin 3027 Exchange GLR successful.

2015-10-20 09:17:37 avagent Info <5928>: Registration of plugin 3015 VSS successful.

2015-10-20 09:17:37 avagent Info <5619>: Registration of client and plugins complete.

2015-10-20 09:17:37 avagent Info <7189>: first work request delayed for 180 seconds.

2015-10-20 09:20:37 avagent Info <7190>: first work request delay finished.

Everything looks ok but when I try to create a new backup job from VSphere web client I receive a msgbox stating "There are no registered Microsoft Exchange Server available".

I have to say that VDP Appliance backup user is in a different Active Directory forest than Exchange server and VMwareVDPBackupUser.

I'll appreciate any type of help

[RyanJMN]

Normally you register the VDP client as part of the agent install.  I believe you put the client in the wrong domain.  It should be in /clients/VDPApps not /client/serverdnsname.  I'd reinstall using the registration process documented in the VDP admin guide.

[seocsitvmw]

Thank you for your answer RyanJMN,

maybe there was a little misunderstanding: SERVERDNSNAME is an masked name for my Exchange server name and VDPDNSNAME is for my VDP appliance name.

I have to add news to this thread: IMO the cause of the problem could be the different AD membership of VDP service account and VMwareVDPBackupUser account using GLR functionality (reading EMC Avamar guide I found some additional conf to do for Exchange servers in child domains); so I uninstalled the client and reinstalled without GLR plug-in and now I can browse the Exchange server in the "New backup job" wizard, also drilling down the list of mail databases.

I will deploy a VDP Appliance in the same domain than the Exchange server to test if GLR plug-in works.