Endpoint Management and Virtualization Trusted Advisors Community merge into SED TA Community

Back again...

So we have some custom resource types, and have created numerous custom resources based on those types in our DEV environment.  Now we need to export them from DEV into PROD so we don't have to re-create them all.  Exporting from DEV is easy enough (Manage > Assets > (our custom folder) > right-click the Resource and Export), but I can't see how to import them again.  If I just right click the (our custom folder), they ARE imported, but don't show up in the "resource container" (I guess that's what you'd call it) in that location; you just see the Resource Type configuration screen when you click the folder under Assets.

I also tried installing the Migration utility for 6.x/7.0, but that doesn't seem to allow you to export 7.1 items aside from Core solution functionality, unless I just missed it somehow.

So how do you do it?  AM I going to have to use the ImportExport utility?  Am I just doing it wrong? :)

So for anyone playing along at home, we got it sorted out with a push in the right direction from our consulting partners at ExpressAbility.  Basically you have to create a "Bulk Resource Export Rule" at Settings > All Settings > Notification Server > Connector > Import/Export Rules > New --> Bulk Resource Export Rule for the Resource Type, include all of the associated dataclasses and associations you also want to export, and save it.  Be sure to check the box for "Export NSE header" or the import won't work.  After you test, then run it, you'll have a directory full of .XML files which you can browse to see all the data in them.  To load them, just copy them up to the \nscap\EvtQueue folder on your production SMP and they should be loaded.

One tip: while testing, set the "maximum resources per file" to a low number (I used 2, and had 61 resources to process) so I could load them slowly into the Prod SMP box a few .xml files at a time until you're confident that everything is working properly.

You could also export the resource types as XML from dev and import to prod, add them to the Asset View, and then setup a connector rule (using OLEDB) to import all resources for those resource types from your dev database.

Thanks Andrew, I may look at this as another option as the other is a bit more labor intensive, unless you set the output directory to the evtqueue directory on the prod ns! :-)

You could also try using importexportutil.exe instead of using the GUI.