Add site system role through automation, SCCM 2012 Sp1

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
Lasse
shaggys

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

Similar Messages

  • "Add Site System Role" is greyed out in the SCCM console

    SCCM 2012 R2 CU3
    Single Primary Site
    Issue where “Add Site System Role” is greyed out in the SCCM console. We can install roles through PowerShell, however in the console we cannot add roles, remove roles, or change the properties of the site server.
    The account we are using is full administrator in SCCM. It was used to install sccm infrastructure.
    Any suggestions
     

    Anything related to these?
    https://social.technet.microsoft.com/Forums/en-US/4226f698-1114-4a62-bc25-705788432955/add-site-system-roles-remove-roles-greyed-out?forum=configmanagergeneral
    https://social.technet.microsoft.com/Forums/en-US/76bb0064-9d5a-4b0e-b955-472fb5e9e833/the-add-site-system-role-is-grey-out-after-deleted-the-cloud-distribution-point?forum=configmanagerdeployment#5347193f-997b-41a6-8011-5320e3dd8a9e

  • SCCM R2 CAS Missing "Add Site Systems Role" menu

    Working with SCCM R2 in a lab environment and I'm Stumped.  I expanded my primary site into a hierarchy and on the new CAS I don't have the add site systems role menu when connected to the CAS. 
    This is what I see when connected to the primary site:
    This is what I see when connected to the CAS:
    Logged on as the domain administrator account used to install both roles, full administrator on both sites.  I can't find any documentation that this is a designed change.
    Any Ideas?

    At this point that's not relevant, I'm not even getting the menu item to start the wizard.  I'm logged in with the account that did the installation yet it's almost like I have view-only permissions. I'm beginning to think there's a trust issue between
    my systems so I'm starting over (i.e. applying the snapshots before I installed) and resetting the trust for my CAS system.

  • Add Site System Roles (Management Point)

    To resolve an issue I was having with the management point role I have removed it.
    I left it for an hour and then restarted the server and the role had been removed. When I tried to re-add the role the option is greyed out. I believe this is due to the Server being the primary site but am finding it hard to get any definitive answer on
    how to re-add the role.
    Currently my site has no management point.
    My question is HOW DO I RE-ADD THE ROLE OF "MANAGEMENT POINT"?
    Will the configuration management setup wizard allow me to do this, whilst retaining the current roles and config?

    I thought it was a permissions issue at first to. Signed into the server with the service account used to install SCCM and also explicitly named my domain account as a local admin despite me being a domain admin. Furthermore, I have access to remove the
    roles from the server and permission to add and remove roles to all other servers.
    Adding role
    In management console Administration>Site Configuration>Servers and Site System Roles
    This bring up the list of servers and when left clicked their roles. I right click on the server in question and the option to "add site system roles" is greyed out as are the sub-options under start and the option to delete.
    Will screen shot in the morning

  • [Forum FAQ] Reporting Service Point cannot be installed on a Site System Server running SQL Server 2012 SP1

    Symptom: When you install Reporting Service Point role on a Site System Server running SQL Server
    2012 SP1, you may encounter an issue that the Reporting Service Point role cannot be installed. The error log “srsrpMSI.log” and “srsrpsetup.log” may throw the error as shown in Figure 1 and Figure 2.
    03:32:03:764]:
    MainEngineThread is returning 1618
    Figure 1: Error -1
    <03/03/14 03:32:03>
    srsrp.msi exited with return code: 1618
    Figure 2: Error -2
    Reason: All the two logs indicate an error return code 1618. From the KB below you may know what
    the return code means.
    ERROR_INSTALL_ALREADY RUNNING 
    1618
    Another installation is already in progress. Complete that installation before proceeding with this install.
    KB link:
    http://support.microsoft.com/kb/290158 “it is related to an Office Suite KB, anyway, the MSI return code is the same meaning”
    You can look into Resource Manager and Event Viewer to find the other currently running MSI installation. You may get a warning in Event Log that means the MSI wants to install a SQL Server
    related Component (Figure 3). The Resource Manager confirms this (Figure 4).
    Event Log:
    Event ID: 1004
    Source: Msinstaller
    Level: Warning
    Detection of product '{A7037EB2-F953-4B12-B843-195F4D988DA1}',
    feature 'SQL_Tools_ANS', component '{0CECE655-2A0F-4593-AF4B-EFC31D622982}' failed.  The resource '' does not exist.
    Figure 3: Event Log
    Figure 4: Resource Manager
    Resolution: the error is exactly what the following KB describes.
    KB Link:
    http://support.microsoft.com/kb/2793634
    After we resolve the SQL Server 2012 issue, the Reporting Service Role is installed successfully.
    Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

    This implies that ODP.NET does NOT need to be installed on a client. However, I cannot find OraOPs9.dll on a machine with Client Release 9.2 installed. Should OraOps?.dll automatically come with a Client installation of 9.2 or higher?
    ODP.NET needs to be installed on the client. OraOps9.dll is part of ODP.NET, not the Oracle Client.
    Also, if an application is built with the 10g ODP.NET, can it be run from a machine with OraOps9.dll?
    If an application is built with 10g ODP.NET, it can be run with 9.2 ODP.NET as long as you do not use any 10g APIs. The new features in 10g ODP.NET are included in the doc and the ODP.NET FAQ for your reference.

  • Add site system roles disabled

    SCCM 2012 SP1 R2 , One primary , no CAS
    I added a cloud distribution point for testing and learning. Today I removed the cloud distribution point and deleted my azure subscription as wel..
    After removing the distribution point I noticed that local distribution point on primary is removed too. and When I to site server and right click to add " Add site server roles" . The setting is disabled.
    How to enable this setting back ?
    Thanks

    Then you should call Microsoft support (CSS) to get that fixed (as you need to modify the database in order to get things up and running again).
    Torsten Meringer | http://www.mssccmfaq.de

  • Endpoint Protection Role fails after SCCM 2012 SP1 upgrade 0x8004ff84

    We have been in the process upgrading our SCCM RTM to SP1 in order to get to R2 in the end. After upgrading the PRimary Site server to SP1 it seems the Endpoint protection update did not succeed. I removed the role and after that tried it to install again,
    results below.
    EPSetup.log
    I<09/26/14 14:24:25> Installing the SMSEP
    <09/26/14 14:24:25> Passed OS version check.
    <09/26/14 14:24:25> File E:\BO\Microsoft Configuration Manager\Client\SCEPInstall.exe version is 4.4.304.0.
    <09/26/14 14:24:25> EP version 2.2.903.0 is already installed.
    <09/26/14 14:24:25> EP 2.2.903.0 is installed, version is lower than expected installer version 4.4.304.0.
    <09/26/14 14:24:25> Invoking process "E:\BO\Microsoft Configuration Manager\Client\SCEPInstall.exe" /s /q /noreplace /policy "E:\BO\Microsoft Configuration Manager\Client\EP_DefaultPolicy.xml" 
    <09/26/14 14:24:25> CreateProcess: E:\BO\Microsoft Configuration Manager, "E:\BO\Microsoft Configuration Manager\Client\SCEPInstall.exe" /s /q /noreplace /policy "E:\BO\Microsoft Configuration Manager\Client\EP_DefaultPolicy.xml" 
    <09/26/14 14:25:00> CreateProcess: -2147156092
    <09/26/14 14:25:01> SCEPInstall.exe returns 0x8004ff84
    <09/26/14 14:25:01> SMSEP could not be installed. The return code was -2147156092
    <09/26/14 14:25:02> ~RoleSetup().
    When I manually try to run the SCEPInstall.exe setup asks for certain msi files it cannot find. Anyone seen this behaviour before? I'm not able to find information on this one.

    It seems the uninstallation of the current SCEP client fails. It uses the new SCEPinstall.exe version to do the uninstall which fails. I copied the old version from another computer and used that to do the uninstall manually scepinstall.exe /u
    It asks a few times for a location to find the msi files used to do the uninstallation. You have to point at a temporary map created at the drive root location. The Uninstall succeeds.
    Now the Endpoint Protection role can be added again and will also succeed.

  • New SCCM 2012 client machines still getting SCCM 2012 SP1 client not the new SCCM 2012 SP1 CU3 client

    Hi,
    I've successfully (as far as I can tell) deployed SCCM 2012 SP1 CU3 and all my existing clients are showing a client version of 5.00.7804.1400.  But when I setup a new client system recently I noticed that the client version was showing 5.00.7804.1000,
    and not 5.00.7804.1400. 
    For new client systems, do I need to redeploy the packages that were created for SCCM 2012 SP1 CU3 so that the new systems get the new SCCM 2012 SP1 CU3 client? 
    Thanks,
    Nick

    Hi,
    Here's some good information to look over:
    http://sccmfaq.wordpress.com/2013/09/24/sccm-2012-include-cu-in-osd/
    I haven't followed these instructions myself, since I haven't really had any good reason to include CUs during the initial installation process. I use this method instead and I've never run into any problems:
    http://www.ronnipedersen.com/2013/06/installing-sccm-2012-sp1-cu2-quick-start-guide/
    Don't retire TechNet! -
    (Don't give up yet - 12,575+ strong and growing)

  • SCCM 2012 SP1 Beta Site System Roles Installation issues

    My apologies if this isn't the correct place to post this, but I didn't see any SCCM 2012 forums to post this. If there is a better place for this post, please direct me to the proper location. In the meantime this is my scenario:
    I am currently evaluating SCCM 2012 for our company. I have installed SCCM 2012 SP1 Beta on a test server running Server 2012 and SQL 2012. I am testing its ability to manage Windows 8. The server is a member of our company domain. I have enabled Active
    Directory Forest Discovery and CM has detected our forest and domain and set up boundaries automatically.
    I am trying to add the Application Catalog Web Service and Website Roles. When I start the wizard I get exclamation marks next to Active Directory forest and domain fields in the wizard. It shows our proper forest and domain names but won't proceed
    because it insists that the FQDN for my forest/domain is invalid. If I enter any other forest/domain name (e.g. yahoo.com, google.com, help-me.com) the exclamation marks clear and the wizard will proceed. SC seems to recognize our forest/domain name and
    denies it. Adding different suffixes (e.g. .net, .org, .local) changes nothing. I've even flipped our forest-domain name (e.g. "a-b.com" to "b-a.com": we have a "-" in our name) and it STILL denies it. If I add a prefix to the forest/domain name, the
    wizard is happy and lets me proceed (e.g. "domain.a-b.com") Did I miss something in initial setup? If this is a bug in the SP1 beta, how do I let anyone know about this? Any help/suggestions would be appreciated. Thanks.

    Since no one has answer this post, I recommend opening  a support case with CSS as they can work with you to solve this problem.
    Garth Jones | My blogs: Enhansoft and
    Old Blog site | Twitter:
    @GarthMJ

  • SCCM and ForeFront Endpoint Protection point site system role

    Thanks for looking at this......I am working with SCCM 2012, and ForeFront Endpoint Protection has been set up as an Endpoint Protection point site system role.  Up to now we just haven't had to mess with it much, it just has worked.  I
    have been busy packaging applications for the eager public. I have one pc that has had the Endpoint client self destruct.  Had to remove it via the control panel.  I next did a machine policy retrieval and evaluation cycle (among others) and sccm
    shows that it is aware that this particular machine needs FEP. It lists it as "To Be Installed".  How long will this take?  I have things set for "as soon as possible".   Am I at the mercy of Sccm?  Also, is there
    a way to force the install?  Thanks for any light you can shed on this!

    This will depend on your SCCM client policy settings to allow SCEP installation outside of maintenance windows (if you have any).
    It will also depend if you are using 2 hour deployment "randomizer" option in your SCCM client policy.
    Lastly, you can install it with BITS that have already been downloaded with SCCM client install.
    c:\windows\ccmsetup\scepintall.exe

  • SCCM Site System Roles - Installation/Configuration chronological order

    Hello folks,
    I have been reading quite a few documents in order to expertise my SCCM knowledge. I wonder is there any best practice that we need to follow while implementing the Site System Roles.. Like 1. SUP, 2. MP, 3. DP? and what makes the difference in doing so?
    Thanks,

    This cannot be answered in a single forums thread because there are too many factors involved (business needs, customer's environment, LAN/WAN setup, budget etc). Adding multiple roles will provide load balancing (kind of) and high availability (also
    kind of). 
    Torsten Meringer | http://www.mssccmfaq.de

  • Can I have an SCCM 2012 R2 server and a SCCM 2012 SP1 server in the same site?

    We are currently using SCCM 2012 SP1/MDT 2012 Update 1 to deploy Windows 7, and to migrate existing XP installs to Windows 7 (using the offline USMT functionality in MDT).  We are moving forward with Windows 8.1, and understand that
    we need to upgrade our SCCM infrastructure to SCCM 2012 R2/MDT 2013.  We also understand that this will cause us to lose the ability to migrate XP machines, since MDT 2013 uses a newer version of USMT that doesn’t support XP.
    What do we need to do to continue to support our XP migrations, and enable deployments of Windows 8.1?
    Can we have two SCCM servers in the same Site running different versions of SCCM? Do we need a separate site? 

    You don't explicitly need ConfigMgr 2012 R2 to support Win 8.1. SP1 CU3 will suffice although managing a few things like boot images is a little more difficult: http://blogs.technet.com/b/configmgrteam/archive/2013/10/21/how-to-enable-windows-8.1-deployment-in-sc-2012-configmgr-sp1-cu3.aspx
    You could create two separate site hierarchies, but that would be painful and involve tons of duplication. There would be other issues also if the systems are located on the same subnets and in the same AD forest.
    The best option is to get rid of XP. EOL is in less than 30 days!
    Next best is to stay on SP1 CU3 until you get rid of XP. I know that sucks, but keeping XP around is the root cause of this and many other coming issues in any organization wanting to keep it around.
    Jason | http://blog.configmgrftw.com

  • Site System Roles - Best Practices

    Hi all -
    I was wondering if there wwere any best practice recommendations for how to configure Site System Roles? We had a vendor come onsite and setup our environment and without going into a lot of detail on why, I wasn't able to work with the vendor. I am trying
    to understand why they did certain things after the fact.
    For scoping purposes we have about 12,000 clients, and this how our environment was setup:
    SERVERA - Site Server, Management Point
    SERVERB - Management Point, Software Update Point
    SERVERC - Asset Intelligence Synchronization Point, Application Catalog Web Service Point, Application Catalog Website Point, Fallback Status Point, Software Update Point
    SERVERD - Distribution Point (we will add more DPs later)
    SERVERE - Distribution Point (we will add more DPs later)
    SERVERF - Reporting Services Point
    The rest is dedicated to our SQL cluster.
    I was wondering if this seems like a good setup, and had a few specific questions:
    Our Site Server is also a Management Point. We have a second Management Point as well, but I was curious if that was best practice?
    Should our Fallback Status Point be a Distribution Point?
    I really appreciate any help on this.

    The FSP role has nothing to do with the 'Allow
    fallback source location for content' on the DP.
    http://technet.microsoft.com/en-us/library/gg681976.aspx
    http://blogs.technet.com/b/cmpfekevin/archive/2013/03/05/what-is-fallback-and-what-does-it-mean.aspx
    Benoit Lecours | Blog: System Center Dudes

  • Windows 8.1 system with new Office 2013 install not pulling down any Office 2013 updates from my SCCM 2012 SP1 server

    Hi,
    I've just setup a new Windows 8.1 system and added to my SCCM 2012 SP1 server and all is good and it pulled down all the correct Windows updates and pulls down automatically the FEP updates that are distributed from SCCM 2012 daily. 
    I just installed Office 2013 on this system and have activated it as necessary.  The problem is that the system doesn't seem to be pulling down any of the Office 2013 updates that have distributed thru SCCM.  I have other systems with
    Office 2013 installed and they have pulled down Office 2013 updates in the past when I published them.
    If I look at the Office 2013 updates in the SCCM console software section, I can see that for example it shows that Office 2013 SP1 (x86) is needed by one system and installed on 8 other systems and shows as downloaded and deployed.
    I've restarted the new system multiple times and also tried to force a software update check from the Configuration Manager applet but nothing seems to happen.
    What can I check to try and determine what the problem is?
    Thanks in advance,
    Nick

    Yes, the 8.1 system is a member of collection where the update deployment is targeted.
    Are there any specific logs I should check in the client?  If I check the WindowsUpdate.log I can see messages about the machine pulling down the FEP updates but that's all it appears to be doing.
    in CCM\logs, focus on the updatehandler and updatedeployment, to begin with
    Don
    (Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
    This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

  • Deploy Windows 8 To Go through SCCM 2012 SP1

    First a little backgroud:
    I have SCCM 2012 SP1 with MDT 2012 Update 1 integrated. I am using an MDT UDI task sequence to deploy windows 8 and it works perfectly. My Windows 8 image is fairly thin (only containing OS updates and C++ runtimes), and I am using the MDT database
    and an MDT task sequence in SCCM 2012  to dynamically set a list of SCCM Applications to install as well as settings based on location. 
    Now I want to get Windows To Go provisioning working in SCCM 2012 SP1. I had a powershell script that preparied the drive and applied a thick image (including office and other apps) to it then updated unattend.xml with a computer name and the domain join
    info.  That worked for me however I'd like to levarage the dynamic task sequence that I described above to build these To Go sticks the same as my other Windows 8 machines without having to keep updating the thick image evertime something changes. 
    There isn't much info out there that Iv'e found on setting up SCCM 2012 SP1 to provision windows to go here are the two that I have found 
    http://ixrv.blogspot.com/2012/10/provisioning-windows-8-to-go-with.html
    http://technet.microsoft.com/en-us/library/jj651035.aspx
    I followed the instructions in the first link and was able to run the Windows to Go Creator program and apply the prestaged wim to the USB stick. I rebooted from the USB stick Windows PE started and started to run my task sequence then it errored out on
    the apply image step. At this point it occured to me that the MDT SCCM task sequence was probably not setup for prestaged media and or Windows To Go. 
    So my question is am I on the right track? Do I just need to examine each step in my task sequence and make sure that it will work properly with my Prestaged/Windows To Go stick? If so has anyone actually gotten this to work that could give me some advice?
    Or is it asking too much to have a dynamic Windows To Go task sequence and I should just be building a thick image and using a second task sequence specifically for Windows to go? 
    are there any other resources for Windows To Go with SCCM that I'm missing? 
    Thanks, 
    Tony

    First of all sorry I missed your last three posts I have to check my email notifications. I'll try to answer all of them even though I think the last part is the only one where you are still stuck. 
    When I created my prestaged media I didn't put anything into it except for the the OS image and my PE image. On the Select Application and Select Package screen in the prestaged media wizard remove any application or packages that are added automatically.
    The task sequence is supposed to be smart enough to know if the version of the package that is on the prestaged media is out of date and go to a DP to get it but that didnt work for me. The only way I was able to get it to work was to remove all the packages
    from the prestaged media even the Customsettings package, the MDT toolkit package, USMT, etc.. 
    http://social.technet.microsoft.com/Forums/en-US/configmgrosd/thread/d729d0ff-829f-4af8-91af-2131b3355fd0/
    This thread which is about prestaged media in SCCM 2007 helped me to understand how prestaged media is supposed to work. Basically what I learned is that once the computer is rebooted from the ToGo stick into PE the task sequence will run the same as any
    other task sequence installing any applications and setting up your ToGo stick just like any other computer that runs the task sequence they dont need to be in your prestaged media for this to happen. 
    You shouldn't need to worry about partitioning WTGCreator.exe will partition the ToGo stick for you I'm just using the standard MDT Integrated partitioning in my task sequence. The one thing that I did was set the Windows To Go Creator package to "run from
    distribution point" which speed things up because then it didnt download the prestaged wim then apply it to the USB drive. 
    Is it booting into PE then rebooting? Did you check the "Allow unattend operating system deployment" check box when you made your prestaged media? If so it wants you to have set the task sequence to run in a task sequence variable SMSTSPreferredAdvertID
    to the task sequence ID you want to run. I'd just remake the media and leave that box unchecked. 
    Good luck and let me know how it works for you. I'll check back sooner this time I promise. 

Maybe you are looking for