Solution: Networking
Best Practices Analyzer: Run it on your server roles, not your loved ones
We in Windows Server are sorry to report a disturbing trend among IT professionals. Ever since Windows Server 2008 R2 was first released as a public beta, and Best Practices Analyzer for Windows Server roles was first available, we’ve been getting some alarming dispatches from the IT management front.
Windows Server 2008 R2 & Intel Slam Dunk iSCSI Performance Benchmark
With the release of Windows Server 2008 R2, the Windows Server platform has evolved into a robust and scalable platform aimed squarely at the heaviest data center loads – and we’re always looking at new ways to prove it.
Symantec solution available for “Network Path Not Found” and other errors.
Many folks have been encountering network connectivity issues and other errors when running older versions of Symantec Endpoint Protection and Symantec Antivirus. So I’m writing to let you know that a solution has been available for the past year and is highly encouraged as an upgrade.
Guest Post: Marathon and Microsoft fault tolerant computing
Hi, I’m Jerry Melnick, chief technology officer at Marathon Technologies. Today we announced an expanded development and marketing agreement with Microsoft that underscores industry recognition of the growing need to eliminate downtime for your most important applications. Working together, Marathon and Microsoft will bring sophisticated fault tolerant availability technology to Windows Server and Hyper-V.
Next Generation of Windows Networking at the IPv6 Summit
Ian Hameroff here; a first-time blogger, long-time reader. I’m a product manager within the Windows Server Division and am focused on the advanced networking technologies. I wanted to talk about a brand new networking stack coming in Windows Server “Longhorn” (and Windows Vista).
802.1x Authentication for Wired Networks – A vulnerability note
Thanks to Steve Riley for pointing out some of the vulnerabilities about my post with using 802.1x to secure wired networks: (The whitepaper from this post does address these concerns) Essentially, the vulnerability is a weakness in the 802.1x protocol — it authenticates only upon connection establishment and assumes all traffic after authentication is legitimate.