Technology news and Jobs
The Linux distillery
An update on the war against Microsoft's war against Linux
The Linux distillery
An update on the war against Microsoft's war against Linux | An update on the war against Microsoft's war against Linux |
|
| by David M Williams | |
| Monday, 05 May 2008 | |
|
Page 3 of 3 Interestingly, the networks were not physically separate. All city administration users can connect to the education network and some education users were permitted to access the city administration network. So, presumably the two networks were one physical mix of computers and access was restricted by way of policies, Active Directory and LDAP constraints and the like.Featured Whitepaper
5 Best Practices for Smartphone Support
Nevertheless, the networks experienced virus outbreaks also which cost money to fix as well as draining resources. A server technician explained this, understandably, happens as a result of having such a large network with company equipment being used on home and other less secure networks. It highlighted the need for the city to have greater control over their devices as well as track and control user access. As an aside, it looks like there weren't any problems with file sharing or printing, obviously the Linux servers were collaborating fine with network resources. Ok! Here’s where we roll our sleeves up. What did the city do? Which Linux server products did they check out? Who gave them advice? The very next paragraph reads, “TrueSec, a Microsoft Gold Certified Partner, was one of the city’s technology partners for maintaining the network ... When the enhancements to Network Access Protection (NAP) in Windows Server 2008 were announced, the consultants considered NAP technology to be a way to address those challenges.” A Security Consultant at TrueSec says, “We proposed the idea of adopting NAP to Upssala ... to increase the security of the city’s administration network.” And that was pretty much it. The case study goes on about how TrueSec and the city participated in the Microsoft Rapid Deployment Program in order to get Windows Server 2008 pre-release version early. They made a test network, they purchased new hardware, they made a pilot deployment in January 2008 in the city administration network and things are looking ok so far. The deployment is still in early stages. So, what do we learn? Firstly, the existing platform was far more of a Windows environment than a Linux one. The Windows-exclusive network was insecure. A third-party company who maintained the network – and who were a Microsoft partner – recommended new features in Windows Server 2008 that would help. So far, the Windows-exclusive network has been partially upgraded. Hang on? Where’s the Linux aspect? Why is this on Microsoft’s site? Weren’t we promised we’d be told why customers are choosing Windows Server 2008 over Linux? Oh yeah, there was a single reference hidden away. “If you go with Linux, you can never be sure of what kind of support you’re going to get” a server technician said. “Maybe the product is free, but you still have to put in the staff hours to basically support the product yourself.” So, in other words, the City uses partners – like TrueSec – to perform most of the maintenance. They had a Microsoft Gold Certified Partner who they could draw upon for any and all Windows work, but didn’t have any similar vendor for the Linux side. That’s it. Once again, this is a case study that says “The latest version of Windows is better than the last version of Windows” with a throw-away line about Linux, perpetuating myths of arcane and impenetrable ways. Microsoft, this is rubbish. Tell me what you’re going to do about it.
Some questions to readers ... |
| < Next story in category | Previous story in the category > |
|---|




Tags




