Where I think everyone is missing this argument is in the TCO. Yes, Linux is cheaper.
However, converting apps from Windows to Linux takes developers and $$$$$$. Not to mention the cost of training users to navigate a new OS.
I recently had a proposal turned down to make an Intranet server Linux based instead of NT. The company did not feel comfortable with an OS that only a few people on staff new how to handle.
The bottom line is, it doesn't matter how little you pay for the OS. It is how it is perceived in the marketplace.
This is obviously just a ploy by cDc to legitimize a trojan horse app, that in 99% of all cases will be used to break into an unsuspecting user's machine.
I have been involved in dozens of SMS rollouts. SMS is a network analysis tool, that has the capability to remote control client workstations on the network.
In order for SMS to do this, you must install the SMS Client on a machine in the same Windows NT domain. This installation process will *not* run in the background, and will pop up several boxes to the user. Once the client is installed, the client configuration app must be opened, and the machine must be set to allow remote control. You also have the option of a dialog box show up informing you that someone is connected.
Along with these settings, every user that logs on to a network that is SMS aware, knows that the client is installed, because it pops and SMS configuration dialog box during every logon.
This remote control feature of SMS is used primarily for network admins that need to remote control servers than client desktops. In fact, out of all the installations I have done, the only machines that have this option turned on are the servers.
BTW, the SMS Admin tool that allows you to connect to the clients requires Windows NT, a valid logon to the Windows NT Domain that you want to administer, and a SQL server logon with appropriate rights to administer SMS.
Slashdot Mirror
Where I think everyone is missing this argument is in the TCO. Yes, Linux is cheaper.
However, converting apps from Windows to Linux takes developers and $$$$$$. Not to mention the cost of training users to navigate a new OS.
I recently had a proposal turned down to make an Intranet server Linux based instead of NT. The company did not feel comfortable with an OS that only a few people on staff new how to handle.
The bottom line is, it doesn't matter how little you pay for the OS. It is how it is perceived in the marketplace.
This is obviously just a ploy by cDc to legitimize a trojan horse app, that in 99% of all cases will be used to break into an unsuspecting user's machine.
I have been involved in dozens of SMS rollouts. SMS is a network analysis tool, that has the capability to remote control client workstations on the network.
In order for SMS to do this, you must install the SMS Client on a machine in the same Windows NT domain. This installation process will *not* run in the background, and will pop up several boxes to the user. Once the client is installed, the client configuration app must be opened, and the machine must be set to allow remote control. You also have the option of a dialog box show up informing you that someone is connected.
Along with these settings, every user that logs on to a network that is SMS aware, knows that the client is installed, because it pops and SMS configuration dialog box during every logon.
This remote control feature of SMS is used primarily for network admins that need to remote control servers than client desktops. In fact, out of all the installations I have done, the only machines that have this option turned on are the servers.
BTW, the SMS Admin tool that allows you to connect to the clients requires Windows NT, a valid logon to the Windows NT Domain that you want to administer, and a SQL server logon with appropriate rights to administer SMS.
How many checks like this does BO2K do?
Regards,
eg