I find it disturbing that customers of yours have to wait so long for answers from you, and when you do answer - you fail to answer.
It is funny that when your CEO answers questions from his customers (life-blood of any company), he seems years behind technology. What does he mean "Window XP's release has influenced our plans"? When did Windows XP get released? Better yet, when was Windows 2000 released?
It appears the dates might have been different in Russia, but they were released in 2001 and 2000 (respectively). *what a joke*
He also mistakenly states that "Basically it satisfies what most of our customers told us they need." So your saying the majority of your customers are happy with the CPU loads RADMIN puts on windows 2000 systems? Where is the video hook for Windows 2000? I'm sorry, I guess adding a wonderful chat or voice conversation feature (which is bound to *increase* CPU load) is more important then fixing what a good portion of your customers have been complaining about? It makes perfect sense to me - why fix the video hook issue that causes high CPU loads, lets just add more semi-useless features. For our non-american readers - that was sarcasm!
I'm also unhappy you decided to include voice communications in your product before something useful like a network deployment feature. Maybe it is me, but in my work environment - we don't deploy speakers and microphones to users. I would guess that most companies are the same way.
How hard is it to develop a deployment program? How long have your users been asking for this?
Since it seems you can't take the couple hours of development time to make deployment tool. I'll *sell* you mine. I've wrote my own program to deploy your product - and it only took me about 2 hours. Guess what, it also works under Windows XP! Whoops, I forgot your program doesn't work well under XP (again - this is sarcasm).
I used to think a lot of your company, things have changed though. Congrats on being written up in the Windows .NET mag, to bad they didn't decide to take into account your piss-poor customer support. Perhaps instead of all your angry customers writing to you (like you really listen), we should instead inform Windows .NET mag (and others) about your lack of support.
