Submitted by Anonymous on Tue, 08/27/2013 - 07:48
In my last post I talked about Microsoft’s implementation of Software-Defined Networking with Hyper-V virtual networking. Hyper-V virtual networking can dramatically improve an organization’s agility, allowing for the quick provisioning of supporting network resources in a virtualized infrastructure.
Submitted by Anonymous on Tue, 08/20/2013 - 07:28
In the networking field there’s been a lot of talk over the last few years about “Software-Defined Networking”. What exactly is Software-Defined Networking (SDN)? What are the benefits of SDN? Does it require the purchase of new networking gear to support it? Are there any interoperability issues? In this post I’ll speak to each of these areas.
Submitted by Anonymous on Wed, 08/14/2013 - 11:12
Recently I had the opportunity to join host Richard Campbell on the popular IT Professional podcast RunAs Radio. Richard and I had a great conversation on the topic of Hyper-V Network Virtualization (HNV) and more broadly, Software-Defined networking (SDN). Software-defined networking is a compelling new feature included with Hyper-V and System Center Virtual Machine Manager (SCVMM) 2012 SP1.
Submitted by Anonymous on Tue, 08/13/2013 - 13:11
It’s an exciting time to be working with Microsoft private cloud technologies like Hyper-V. With the release of the Windows Server 2012 operating system, many new and compelling features have been included to enable private and hybrid cloud computing scenarios. One of the newest features is Hyper-V network virtualization (HNV). HNV is Microsoft’s vision for Software-Defined Networking (SDN). HNV is implemented using a network overlay, with configuration managed and maintained with System Center Virtual Machine Manager (SCVMM) 2012 SP1.
Submitted by Anonymous on Mon, 08/12/2013 - 12:31
Welcome to the Iron Networks Cloud Infrastructure blog! My name is Richard Hicks and I am the Director of Sales Engineering for Iron Networks. As the lead author for this site I wanted to start off with a brief personal introduction and outline the direction and subject matter for this new blog. I am a network and information security expert specializing in Microsoft technologies.
Submitted by George on Wed, 08/07/2013 - 09:47
As many of you know, back in March we changed our name from nAppliance Networks, to Iron Networks. The reason for this change was that as we shifted our focus away from traditional network edge security and access products towards building up products focused on cloud-based infrastructures, so the nAppliance moniker no longer fit…it no longer represented what we were trying to accomplish.
Submitted by inder on Mon, 08/05/2013 - 13:11
DirectAccess was first introduced as a feature within Windows Server 2008 R2 and Windows 7 Client. DirectAccess overcomes the limitations of traditional VPN connectivity by automatically establishing a bi-directional connection from client computers to the corporate network wherein users never have to manually establish a connection to the enterprise network. The biggest advantage of DirectAccess is that IT administrators can manage remote computers outside the office just as they would manage machines connected insi
Submitted by lan on Wed, 05/02/2012 - 13:40
Single Sign-on for Office365 with Forefront TMG
In my first contribution to the Forefront Security blog, I will explain how to extend the Office 365 single sign-on experience to remote users by publishing ADFS 2.0 with Forefront TMG.
(Single sign-on allows users to use their corporate (Active Directory) user ID and password in order to access Office 365 services located in the cloud).
Submitted by inder on Fri, 04/06/2012 - 16:05
Most of our customers who have UAG appliances deployed also have a few Mac machines in their organizations and the issue of whether remote desktop connections can be used is something which comes up frequently on sales or technical calls.
Submitted by inder on Thu, 03/15/2012 - 15:37
Your computer can't connect to the remote computer because the Remote Desktop Gateway server reached its maximum allowed connections. Try reconnecting later or contact your network administrator for assistance