Thanks for posting!  Depending on how complex your alert and discovery setup is, it might be easier to just recreate them.  If you want to move the old db to the new system, just stop the SQL services on your default instance of SQL and copy the database and log files over, then start the services.  If you recreate your discovery ranges and alert setup, most likely your servers will discover easily as long as you use the same IP address and SNMP community string as your old ITA box.  If you install a newer version of ITA, updating OMSA on your servers is a good idea.

Make sure you install SNMP and configure it first!

Thanks Jeff.  I ended up doing a fresh install.  After a few hiccups, it all finished.  HOWEVER, ( and you knew that was coming didn't you?) from the management server itself, I cannot open the It Assistant.  I log on and immediately get an error that my session has timed out and I should modify the Session Timeout via the Preferences option at the top of the page.  I can't get to that option if I"m not logged in to the application!

I can open it fine from my own workstation, and I did set the Session Timeout there to DISABLE the session timeout.

I am logging on to the management server, as well as the application, as the domain admin.

Any ideas?

Yes, I could smell your "HOWEVER" a mile away!

I'm not sure exactly why it is doing that, but likely causes are security policies or settings on the browser, which can prevent installing ActiveX controls and Java.  I suggest making the server a trusted site and lowering the security settings for the trusted site zone.  If that doesn't fix it, look at any GPOs you might have.

It is a trusted site.  

IE security is wide open. 

IPSEC is disabled, Windows Firewall is disabled, BFE is disabled.

I can access the application/web interface,  from any other server in my domain https://itassist:2607, without any problems, so it is indicative of this box only. 

There are a ton of errors in the event log that refer to 'Windows Filtering Platfrom has blocked a bind to a local port'.  That's where I found the advice to disable the firewall (which I usually have to do anyway on W2K8) and WFP and BFE.  Not sure this error has anything to do with this particular problem, but what the heck right?

Getting smellier isn't it?  lol

As far as I know I have completely disabled IPv6 on this system, but will follow your instructions and post back what happens.

Thanks!

KBeau

That did it!  Thank you so much!