We have a list of prioritized SSID's. We want the computer to connect to the SSID with higher priority, if in range. No matter if it has -80db and the existing connection has better db.    With Windows native supplicant we see that Windows change when only when the connection is poor or lost, and as we see it there is no way to tweak around that without drilling down into registry and drivers.   With the NAM, it does not connect to the higher prioritized/favored SSID until we actually open the list of SSID's, until then it's sticking with the existing connection with lower priority.   Question 1: Is NAM supposed to be able to do automatic switching to higher prioritized SSID? Question 2: Is, what we see with the "opening list of SSID's to change network", a bug? Question 3: In NAM, when the connection is lost for the top prioritized SSID, we see that it at least retries 20 times before giving up and connecting to a lower prioritized SSID. Is there any way to tweak this? ... View more

Hi. I have seen a strange problem on all of our 3750-X switches that have been running for 36 weeks now. They came delivered with 12.2.55.SE3, but we downgraded them to 12.2.53.SE2 to keep all the switches in the system on the same software version. While downgrading the software they had to downgrade some controller firmware also, took about 40 minutes. All the switches has been running on the 12.2.53.SE2-image without any trouble. But now, when we were going to install a new switch into one of the stacks, we (naturally) got version mismatch. (Since the new one is running 12.2.55 and the ones running for some time now are running 12.2.53.) Then when we started to copy out the 12.2.53-image from the master switch to the new stack member, we saw that it was running on filename ! (See the attachment - 3750X_sho_ver.txt). We have done a MD5 verification on the image ( ! ) and it is the correct image, and as you can see; the switch have booted and are running on the file named !. I know this must either be actually the switch renaming the filename, or that this is only a cosmetic bug in the CLI. We are planing to upgrade all our 3750-*.* switches to 12.2.58 in time, and are sure that this problem resolves itself then. We have been checking the release notes and the caveats for the newer versions, and cannot see anything about this bug. Out of curiosity we want to know if anyone have seen this before? ... View more

Hi, This question is mainlty for Cisco Systems: Why don'n you make a Hyper-V OVA (virtual appliance) for Prime Infrasctructrue? I have a lot of customers standardizing on Hyper-V, and forcing them to use ESXi is a hard pitch. Hope you can be more up to date on this on the coming versions. And just to be clear, this apply to all the OVA products, not only Prime Infrastructure. ... View more