In our environment I have to clear the clients' peer information on the server and the NMC and than clear all the peer informations on the client itself. Don't know if deleting the nsrladb will do the job. Maybe you have to do nsradmin on the client, list the peer informations and delete again if necessary ...

Good luck

Christian

Hi christian....yes!

Hi JayJay,

did you delete the peer informations on the client, the server and the NMC?

Christian

Which user groups do you mean? On the networker server? I created an administrator entry *@ .

I cannot put *@* in the remote access field because the client wizards stops right away. I can create a client by copying another client. Networker doesn't complain then. But I use the wizard so that I can choose the DAG and so on.

Hi Jayjay,

Have you checked the user groups?

Make sure you have *@exch2013_server , *@Physical_node1 and *@Physical_node2in the required groups. (same for all physical and virtual nodes).

Also add *@* in the Remote access field (just for testing, you can modify that later on).

Thank you,

Carlos

JayJay,

How did you add *@host_name on the server?

add it on Application Admin, DB admins and all other required groups.

Thank you,

Carlos

Nope.

I tried to client a client by copying another. That worked. But I dont't know how to specify the save set entry on that client to backup the exchange server.

I have attached the configuration guide for Exchange  with NMM 3.0. This should help you configure the backups manually.

I did all that, nothing worked. *@* in alle user groups.

I also deleted the peer information twice.

I have the feeling it is something on the client side.

Do you already have another instance for the same client create on the server ?

Hi Drew!

Sorry, I was not able to get this working.

Software versions (NW 8.1 and NMM 3.0) are too early bird for our company policies. I'm gonna try again in a few months.

If you achieve any success, would be great if you share it.