Submit a ticketCall us

WebinarUpcoming Webinar: Should I Move My Database to the Cloud?

So you’ve been running an on-premises SQL Server® for a while now. Maybe you’ve moved it from bare metal to a VM, and have seen some positive benefits. But, do you want to see more? If you said “YES!”, then this session is for you, as James Serra will review the many benefits that can be gained by moving your on-prem SQL Server to an Azure® VM (IaaS). He’ll also talk about the many hybrid approaches, so you can gradually move to the cloud. If you are interested in cost savings, additional features, ease of use, quick scaling, improved reliability, and ending the days of upgrading hardware, this is the session for you.

Register now.

Home > Success Center > IP Address Manager (IPAM) > IPAM - Knowledgebase Articles > IPAM additional website errors when using custom properties

IPAM additional website errors when using custom properties

Table of contents
No headers

When viewing IPAM DHCP servers, scopes, groups or IP addresses from an additional website, certain items may not display.  This only applies to users who have created or modified any custom properties. The reason for this is that IPAM does not synchronize IPAM Custom Fields from the Main Poller to the Additional Web server.

When a custom property is created or modified you must copy over the IPAM SWIS schema from the main Orion server into each additional web server. 

The  default locations for the files that need to be copied over is:
"c:\Program Files (x86)\SolarWinds\Orion\Information Service\3.0\Schemas\IPAM.Attributes.xml"
"c:\Program Files (x86)\SolarWinds\Orion\IPAM-OrionReportWriter.Schema"

Last modified