IT Monkey:   Click Here to Help Me Build the Agenda for Upcoming Cireson Webinars!

Moving navigation and kb's to new environment

Eivind_OsbakEivind_Osbak Customer Adept IT Monkey ✭✭

Hi.

I'm moving from SCSM 2012R2 to 2016.

I've done a fresh installation of SCSM and Cireson Portal.
I've installed all apps for 2016 on the new server.
I've ran the Lifecycle Management tool and copied everything but the workitems.
I've copied the Customspace directory.

As far as I can see so far, all that's missing is to get the new installation up and running (except the workitems) is to get the navigation and kb's from the old portal to the new one.

What would be the best way of doing so?

Answers

  • Brian_WiestBrian_Wiest Customer Super IT Monkey ✭✭✭✭✭
    Sounds like a good feature request for the Lifecycle App. 
    Hopefully someone from support will comment on this. 
    I would assume coping some specific SQL tables from the ServiceManagement DB for 2012 into the new DB will accomplish this request.
  • Tom_HydeTom_Hyde Customer Advanced IT Monkey ✭✭✭
    Agree with @Brian_Wiest would be a good feature request.

    We did the following to get our KB's in our 2016 environment.
    1. Right click on your ServiceManagement 2012 db
    2. Select Tasks
    3. Select Generate Scripts
    4. Click Next
    5. Choose Tables – dbo.KnowledgeArticle, dbo.KnowledgeArticle$Comment and dbo.KnowledgeArticle$Rating
    6. Click Next
    7. Click Advanced
    8. Scroll down to Types of data to script
    9. Change to Data Only
    10. Click on OK to close the advanced script options window
    11. Click next and generate your script
    12. Open script and run against your ServiceManagement 2016 db
    Hope this helps.
  • Eivind_OsbakEivind_Osbak Customer Adept IT Monkey ✭✭

    The KBs were easy once i found the https://support.cireson.com/KnowledgeBase/View/1341#/ although it removed everything from navigation. But that didn't matter to much as I was to copy it from the old one anyway.

    But i failed on the navigation.After importing dbo.NavigationNode and dbo.ViewPanels to the new db i ended up with what seems like the default navigation, but the db shows all the correct entries from the old portal.

  • Rod_MartenRod_Marten Customer IT Monkey ✭
    We are trying to automate promoting changes among our environments.  Having challenges with Navigation Node.  We can replicate DisplayString, NavigationNode, and ViewPanel pretty much straight across. GroupMapping_CI$DomainGroup_NavigationNode is a bit more challenging as the Group IDs don't match and need to be mapped.

    When we do this, the navigation looks pretty close, but the Navigation tool in the admin screen shows blank.

    What are we doing wrong and is this a reasonable approach?

    Thanks
    Rod
Sign In or Register to comment.