Hello Steve, Did you ever get this solved. I'm having the same problem when importing devices. I can' get the Description property loaded.
I am sorry to say, no. Your's is the only response I received.
right now that doesn't seem to be tracked at all, it would be useful though - sounds like a good 'idea'.
I don't see a reason why we cant push value for description while importing device into BSA. Though I am yet to test this but I have seen while importing a server we can push values for various properties.
It should work in the same way while importing devices. I will give a try tomorrow on this.
If not then its a good idea for future enhancement.
1 of 1 people found this helpful
it would be better if it happened during auto-discovery..
Bill will you please brief about the auto-discovery ? I did not get you.
Pxe boot the device, after it loads winpe/gentoo it talks to the appserver and the mac is registered w/ bsa.
Thx for spending the time to research this, but what I was looking for is a method of doing this at auto-discovery time as Mr. Robinson mentions.
I'm using BSA 8.2.01.290 and I still can't import the field DESCRIPTION with the following import file (I've also tried using different file extension *.csv / *.txt for the import file):
Also, since we are on the same suject, we do not want to auto discovery the devices into BSA. We want to able to import the devices manualy (before provisioning) because we have different properties that have defined to automate the provisioning process. (of course unless there is another way of doing this)
1.When we import the devices into BSA we also import the Host name, IP Address, Subnet, & Gateway of the device.
2. We then use these properties in the system package (Basic Config tab & Network tab)
3. We create the provisioning job for the system package and then when selectiing the DEVICE we don't need to add any information for the host such as host name, ip address, & subnet (just to automate a little bit)
Which brings up another question:
How can we automate the process just defined above when creating a virtual guest job when creating VMs.
How can we use these propeties (more convenient if we can use the same properties in DEVICE) or other properties when creating a Virtual Guest Job? I do not want to spend hours typing in the host name, ip address, subnet mask, gateway each time a create a virtual guest job. What is the best method to automate this?
Here is an example of what my device import file looks like at the end:
And finally why is the Description property so important for me.
The Description property is important because when creating a provisioning job and when selecting the devices, BSA does not show any devices by smart groups nor any other readable fashion. It only shows two colums:
1. Host name (MAC addresss)
I want to be able at least know what machine i'm provisioining to in case I make a mistake and this is why I wanted to fill the Description property with the host name.
If you are not opting for auto discovery and manually importing devices before provisioning then you can refer to my previous post in this thread. To import list of devices a simple *.txt file will do.
what i'm trying to explain to you is that the import did not work when importing the "MAC" and "Description" properties with my version of BSA. It might be a bug?
In 8.2.01.281 it is working fine.
can you share the result/ error you have encountered ?
In fact, there is no error message when importing. Once imported, the DESCRIPTION property is not filled. That's it.