Right now, you can't do this. LMS is only supported on Windows 2003. If you want to go to 2008, you'll have to wait for LMS 3.2 due out this summer.
A virtual server is a good option as it gives you the flexibility to scale or move hardware. It's also great for disaster recovery as you can take snapshots of known good server states. With only 200 devices to manage, a VMWare ESX deployment will be fine.
Your server should have at least 3 GB of RAM with 2 GB dedicated to the LMS VM. It will need at least one 2.6 GHz (or equivalent) CPU. The more memory, and the more processors you throw at LMS, the better the performance will be. A nice performing server will have at least 4 GB of memory dedicated to LMS with two 2.6 GHz (or equivalent) CPUs.
Question We run asr9001 with XR 6.1.3, and we have a very long delay to
login w/ SSH 1 or 2 to the device compare to IOS device. After
investigation, the there is 1s delay between the client KEXDH_INIT and
the server (XR) KEXDH_REPLY. After debug ssh serv...
Introduction The purpose of this document is to demonstrate the Open
Shortest Path First (OSPF) behavior when the V-bit (Virtual-link bit) is
present in a non-backbone area. The V-bit is signaled in Type-1 LSA only
if the router is the endpoint of one or ...
Hi, I am seeing quite a few issues with patch install and wanted to
share my experience and workaround to this. Login to admin via CLI, then
access root with the “shell” command Issue “df –h” and you’ll probably
see the following directory full or nearly ...