As a follow on post to the post on Importing Computers via CSV, I wanted to also share with you the method for importing information about the software installed on those computers. Neil Lydick, one of the developers on our team, put together the resources you’ll need:
You’ll need to import the management pack file into SCSM first since the mapping file depends on it to import the data correctly.
Keep in mind that the System.SoftwareItem class has a compound key comprised of these five properties:
Each unique combination of those represents a new Software Item. If you import a data file with this data:
You will get 2 instances of Software Item – one for the one published by ‘Microsoft’ and another one published by ‘Microsoft Corporation’. Because the first and third rows have the exact same values for all the key properties the third row will just create a new relationship between mycomputer2 and the software title that will already exist because it was created by importing the first row.
Note: If a Windows computer with the principal name specified does not already exist a new one will be created.
Software Update also has a compound key comprised of the following two properties:
Attached are the necessary files.
Hello Travis, what are the chances we can get a how to for importing and assigning assets to users from a csv file? The existing documentation demonstrates how to do this with existing CIs, but I can't find anything for a custom CI. I have a custom ci created, and can import the assets without issue, but for the life of me I cannot get the "System.ConfigItemOwnedByUser" field to be populated by the AD user name.
You'll need to create a type projection which spans your custom class and the ConfigItemOwnedByUser relationship type. Then you can create a CSV data file which has two columns - user domain, user name. That will create the relationship to the user.
You can get more informatio on CSV import here:
It would be nice if we could just grab this from Configuration Manager since it has all this, the perfect solution would be to get it from SCCM on a Re-occurring Schedule.
It is a part of the SCCM-SCSM connector already. This is just an option for people that don't have SCCM.
This is really nice article and has also helped me in getting in to the concept...Thanks a lot..