equipmenttypes
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| equipmenttypes [2011/04/01 13:39] – [Add IP device complains] faltin | equipmenttypes [2011/04/03 06:56] (current) – [Equipment Types] faltin | ||
|---|---|---|---|
| Line 2: | Line 2: | ||
| - | This page contains a list of types that may be unknown to NAV (we say **may** because they may have been included in a later patch/ | + | This page contains a list of types that may be unknown to NAV (we say //may// because they may have been included in a later patch/ |
| - | You can use this list directly and bulk in the types in your NAV installation using the " | + | You can use this list directly and bulk in the types in your NAV installation using the " |
| + | |||
| + | :!: Please note that when you seed a new IP device of an unknown type into NAV, NAV will automatically create a new type record. The data in this type record may be a bit unreadable and you should then edit the typename, vendor and description using Seed database|Type. | ||
| Line 34: | Line 36: | ||
| </ | </ | ||
| - | :!: When you add an IP device to NAV that is of an unknown type, you may follow a link to add the new type. Here the sysObjectID will be filled in, which means you can skip the procedure above. **Note:** You will not be given this option when you bulk import. | ||
| - | |||
| ===== Get the official typename ===== | ===== Get the official typename ===== | ||
equipmenttypes.1301665194.txt.gz · Last modified: by faltin