hi

Trying to add a reporting point through powershell or the SDK with no luck.

Does any out there have any idea how to do this? We are trying to automate the process of everything.

When adding through powershell its a sucess with the role itself, but when accessing the reporting node the console crashes and the links are missing.

Any ideas or tips?

Regards

Hi,

the SDK states how to add a site System Server and role.

How does your script look like? Would you like to post it here so we can have a look where it might be faulty?!

As a start: http://www.david-obrien.net/2012/06/08/install-distribution-point-for-configuration-manager-2012/ Shows you how to install a new site System.

You could also query your Site Control File in the database, create the reporting Point manually, look at the site control file, run your script to create another one and search for differences.

Select SiteControl From vSMS_SC_SiteControlXML Where SiteCode = 'SITECODE'

This is how to Access the file in your database. Exhange 'SITECODE' with your actual Sitecode. DON'T EDIT the file! Do this in your test Environment!

Hope that helps!

David

Actually, we tried the Powershell command first

add-cmreportingservicepoint

and its wierd that the command exist, but does not work. Would be so much easier if one could do it that way instead but I guess we are missing something thats why it doesn't work.

looked at your script and registered the dll from sccm 2007 SDK. Tried it with no changes at all exept sitecode but it bails. so right now I do not have a script exept yours -:)

Exception setting "Path": "Cannot convert value "\.ROOTSMSSite_T01:SMS_SCI_SysResUse" to type "System.Management.Manage
mentPath". Error: "Invalid parameter ""
At C:\temp\sdk PS add role.ps1:30 char:3
+      $role_class.psbase.Path ="\.ROOTSMSSite_T01:SMS_SCI_SysResUse"
+      ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [], SetValueInvocationException
    + FullyQualifiedErrorId : CatchFromBaseAdapterSetValue

Ensure that the parameter values you're specifying are correct, and that they exist.  For example, you can't create a new site system with this cmdlet, the site system has to be previously set up.  Same for the account. Ensure you're specifying an account that exists.

We've seen one validation issue with the SP1 code - and fixed it with the upcoming cumulative update, but the cmdlet should work if you specify values that exist in your site.

Ensure that the parameter values you're specifying are correct, and that they exist.  For example, you can't create a new site system with this cmdlet, the site system has to be previously set up.  Same for the account. Ensure you're specifying an account that exists.

We've seen one validation issue with the SP1 code - and fixed it with the upcoming cumulative update, but the cmdlet should work if you specify values that exist in your

If you monitor the SMSPROV.LOG file at the time you submit the cmdlet, do you see it reporting back a

I checked back with our team.  It appears that we were still seeing this issue in the SP1 release, and it's been fixed in the next upcoming cumulative update. 

Sincerely,

Dave

Thank you for the info.

Is there a official bug list somewhere so one knows!

Do you know when the CU will be released?

reagrds

Lasse

I checked back with our team.  It appears that we were still seeing this issue in the SP1 release, and it's been fixed in the next upcoming cumulative update. 

Sincerely,

This was finally fixed in CU3 for SCCM 2012 R2 and I can confirm that it does work with CU4 for SCCM 2012 R2.

One note is that the cmdlet documentation is not 100% accurate.  For example, the example listed in get-help excludes required parameters.  Also, the parameter descriptions are not descriptive enough without knowing additional information about the role/point.  Here is what worked for me:

Add-CMReportingServicePoint-SiteCode$SiteCode-SiteSystemServerName$SCCMpriFQDN-DatabaseServerName$SCCMpriFQDN-DatabaseName"CM_$SiteCode"-ReportServerInstance$SCCMsqlDatabaseInstanceName -FolderName"ConfigMgr_$SiteCode"-UserName$CMAaccountConfiguredAsSSRSexecutionAccount