Export all data option for key nodes
I would like the ability to right-click various nodes, eg packages, applications, task sequences, etc and export the data for that node to a file, eg csv which could easily be read back in via powershell. This would allow test environments to be set up quickly and might even help provide an a way to restore a production environment if all else fails...
Brian Moffet commented
I'd like an export button with options such as xls, csv, in the data view area of the console. For example, I pull up a list of devices failing production client deployment. I can see the involved machines but have to take screen shots or get creative. I know there are ways to do this in powershell but not all of us are powershell experts.
Simon Bond commented
I appreciate we already have the Export-CMapplication, Export-CMPackage, etc but it would be great if via a right-click, a script with the correct information for that node was automatically created, a bit like the option you have to save the powershell when you create a domain controller. You could right-click the parent application/package node for example and a script would be created for all the packages that you could then potentially import into another environment and create the same applications, packages, etc. It would save a lot of time. I guess it'd require a wizard to answer one or two questions.
AdminAdam Meltzer (ConfigMgr Product Team) (Software Engineer, Microsoft Endpoint Configuration Manager) commented
Can you expand on what data you're interested in exporting/importing? We already support many import/export scenarios in PowerShell today.