AngrySpider
IS-IT--Management
I am not currently having a problem with this issue, but I have seen it a few times and figured I would see if anyone else has run into it.
Combining older security keys with Windows XP (Home or Pro) would result in the Aloha Back of House's inability to "see" the software key. For example, a customer is forced to upgrade the file server, but the software key is 4.2xx or in some cases 5.0xx. I have seen this 3 or for 4 times, and the work around I had employed in this situation was simply to use Windows 2000 instead. I don't think I have ever seen the problem with 2k, and most customers don't give a rats booty what OS you put on it, as long as it works.. so it's not a huge deal.
In the instances where I did see it happen, the hardware used for the file server was always different. The only common elements among the installations was the keys were a few years old (I say 3 years or more). And I have had no issues with XP and newer keys.
Just curious.
Later!
Combining older security keys with Windows XP (Home or Pro) would result in the Aloha Back of House's inability to "see" the software key. For example, a customer is forced to upgrade the file server, but the software key is 4.2xx or in some cases 5.0xx. I have seen this 3 or for 4 times, and the work around I had employed in this situation was simply to use Windows 2000 instead. I don't think I have ever seen the problem with 2k, and most customers don't give a rats booty what OS you put on it, as long as it works.. so it's not a huge deal.
In the instances where I did see it happen, the hardware used for the file server was always different. The only common elements among the installations was the keys were a few years old (I say 3 years or more). And I have had no issues with XP and newer keys.
Just curious.
Later!