bshopp

OK, probably best at this point to open a support ticket to investigate further and see what is going on

Yep, machine with the less load the better on both the Orion server and on the DB side. NTA can be more DB intensive.

OK, this helps. Orion NPM 9.5 and NCM 5.5, which was released at the end of May, both now support SQL 2008. See here for what's new in NCM 5.5 See here for what's new in NPM 9.5

I would recommend what savell posted. If that is not an acceptable solution, I would also recommend looking into adding an additional poller to your deployment to distribute the workload

By default it will change it for everyone. However, if you have created a custom view, it will only change for those users that are using that view

We are still investigating, but it could be due to a special character in the password and a defect in the API.

Regarding #1, yes it is out, released yesterday

Yea you should be able to, regardless though you will need to go through support to get the link to download the bits, can you please open a support case and reference this thwack thread

Would it be possible to try removing it and re-adding that custom field?

Yeah, we upgraded from 10.0 to 10.1.3. Do you also have UDT installed? Trying to find some common traits between installs. Did you open a support ticket?

Sorry you had a rough time, but thank you for submitting this feedback. We made many changes in v10 to the install and upgrade process, but we realize there are still room for improvements and you have highlighted one here. We will look to enhance this in a future version.

Please open a support ticket to investigate further

Got them both logged into the system

It works by original design, however, we are currently working on a project to make this more seamless, but today this is how it works

No dates I can publicly commit to, we are in beta testing right now is about all I can say.

I think it really depends on your use case and how you want to use the Syslog server. Distributed or not? Volume? Archiving?

Check out my blog post here

You can launched Network Atlas or you can't login? What error are you getting?

We have a fix in test right now and are actively working on it.

An ESX box is basically a Linux box underneath and those don't have notions with drives, that is how they split it out, by directories.

We have some great online tutorials, including Map Maker if you have not already seen which should help guide you - http://www.solarwinds.com/support/tutorials.aspx

What kind of assistance are you looking for?

I would recommend an update to 10.1, I know we tweaked the Windows piece in that version.

Are you forwarding all logs from the exchange security mail box audit? Do you have any rule or filters defined on that log as to which to forward over to the Kiwi Syslog server? Do you expect the volume of this log to grow a large amount over time?

You will need to create a Universal Device Poller to gather that data, we do not do this out of the box

Are you able to add any of your ESX servers? If yes, do those have the web console enabled? We are using the VMWare web services API to gather info/data.

What version are you on? I believe we made some enhancements to this in 10.1. I know in previous version if the same node show up in different discovery profiles we did not merge the results. If you create a new discovery profile with just the node IP's you are monitoring, do you still get 2?

What other type of information would you be interested in seeing?

For Hyper-V, what information are you interested in seeing?

Follow the instructions in this thread and post back the info we requested here if possible http://thwack.solarwinds.com/thread/36892