Thank you Gautam, we managed to solve the issue. It was user rights missing issue.
The document for all Microsoft NMM don't have exact user privileges. If you have a detailed requirements for each user client (SQL Server, Exchange, Sharepoint ...) it would be very helpful.
Every application has it's own rights requirement. I think it should be mentioned in the Guide, if not let me know which applications you need the user rights for and I will try to find the answer for you.
Thank you again, we are working on a new environment with the following application :
- MS SQL Server 2012
- MS Sharepoint 2013
- MS Exchange 2013
We already checked the EMC Guides, Any further help would be appreciated, thank you
Below is the output from NetWorker Module for Microsoft 9.0 SharePoint User Guide,
Provide the required permission so that the SYSTEM user can run SharePoint
PowerShell. The nsrnmmsv command runs under the security context of SYSTEM
n For SharePoint Server 2010 and SharePoint Server 2013, perform both the
1. Use the command: Add-SPShellAdmin -UserName "<DOMAIN>\<HOSTNAME>$"
This command must be used on each web front-end server and the Search
Verify that the SYSTEM account is added to SPShellAdmin by using the
2. In the Microsoft SQL Server Management Studio > Security > Login > Login
Properties page, grant the SQL Server system dbcreator, public, and sysadmin
permissions to the Windows login account. Provide these permissions to the
NTAUTHORITY\SYSTEM user and the DOMAIN\HOSTNAME$ user on a
For SharePoint Server 2007, grant the SQL Server system dbcreator, public, and
sysadmin permissions to the Windows login account. Provide these permissions
to the NTAUTHORITY\SYSTEM user on a stand-alone farm and to the DOMAIN
\HOSTNAME$ user on a distributed farm.
Similarly it's there for SQL in the "SQL VDI User Guide" and Hyper-V and Exchange in their respective guides.
Not sure if you are using any other version of the Product.
Thank you again,
Actually we managed to make it work for SQL VDI, but not for Sharepoint and Hyper-V, as i mentionned the prerequistes are not sufficient.
For SQL you should create the client with the wizard and after the client is created you should remove the login and password from the remote login (the ones you entered in the wizard). That was the solution.