video technetvideo technetvideo technetNoMicrosoft Corporationinfo@microsoft.comhttp://technet.microsoft.com/video/
en-usFri, 28 Jun 2013 00:00:00 GMTFri, 28 Jun 2013 00:00:00 GMTvideo technetDidier Van Hoyehttp://technet.microsoft.com/video/ff832960.aspx?category=Didier%20Van%20HoyeHands on with Hyper-V Clustering Maintenance Mode and Cluster Aware Updating | TechNet VideoIn this session we’ll walk through using maintenance mode & cluster aware updating in a lab providing you with tips on how to make it work.In this session we’ll walk through using maintenance mode & cluster aware updating in a lab providing you with tips on how to make it work.http://technet.microsoft.com/video/Dn270361
Fri, 28 Jun 2013 00:00:00 GMTdn270361.en-us.msdn.10Didier Van HoyeDidier Van HoyeTechNet VideoMediaZuneiPodTechNet EdgeHomepageDidier Van HoyeBeluxHyper-VClusteringScreencastsKathy Davieshttp://technet.microsoft.com/video/ff832960.aspx?category=Kathy%20DaviesWindows Server 2012: Hyper-V and new solutions for small and medium organizations | TechNet VideoJeff Woolsey gives an overview of a few of the new, low-cost solutions in Windows Server 2012 that are available with Hyper-V and related technologies. This short, impromptu discussion with a customer was taped at the Hyper-V booth during TechEd North America.Jeff Woolsey gives an overview of a few of the new, low-cost solutions in Windows Server 2012 that are available with Hyper-V and related technologies. This short, impromptu discussion with a customer was taped at the Hyper-V booth during TechEd North America.http://technet.microsoft.com/video/JJ582885
Wed, 11 Jul 2012 00:00:00 GMTjj582885.en-us.msdn.10Kathy DaviesKathy DaviesTechNet VideoTechNet EdgeMediaZuneiPodHomepageKathy DaviesWin8Windows Server 8Hyper-VHigh AvailabilityWindows ServerVideosClusteringFile ServerRick Claushttp://technet.microsoft.com/edge/ff832960.aspx?category=Rick%20ClausEdge Show 19 - New Server Form factors, Continuous Availability - Oh My!Online Backup Beta for Windows Server “8” is now open. Registration and details can be found here. Keynote Speakers Announced for TechEd North America (June 11 – 14). Satya Nadella, President – Server and Tools Business will keynote North America and will be joined by Jason Zander, Corporate Vice President – Visual Studio.Online Backup Beta for Windows Server “8” is now open. Registration and details can be found here. Keynote Speakers Announced for TechEd North America (June 11 – 14). Satya Nadella, President – Server and Tools Business will keynote North America and will be joined by Jason Zander, Corporate Vice President – Visual Studio.http://technet.microsoft.com/video/Hh924729
Fri, 30 Mar 2012 00:00:00 GMThh924729.en-us.msdn.10Rick ClausRick ClausTechNet EdgeEdge ShowVideosHomepageWS8Windows Server 8ClusteringRick ClausiPodZuneMediaSymon Perrimanhttp://technet.microsoft.com/edge/ff832960.aspx?category=Symon%20PerrimanDisaster Recovery Cluster Deployment & Demo - Multi-Site Failover Clustering In this TechNet Edge video Technical Evangelist Symon Perriman walks through a real-world multi-site cluster deployment. While configuring a four-node disaster recovery demo, Symon recorded the steps and added slides showing the key deployment considerations. Learn more about disaster recovery planning, networking, security, faster failover, DNS replication, the quorum model and PowerShell. See how Windows Server 2008 R2 Failover Clustering can provide not only high-availability, but also automatic disaster recovery. In this TechNet Edge video Technical Evangelist Symon Perriman walks through a real-world multi-site cluster deployment. While configuring a four-node disaster recovery demo, Symon recorded the steps and added slides showing the key deployment considerations. Learn more about disaster recovery planning, networking, security, faster failover, DNS replication, the quorum model and PowerShell. See how Windows Server 2008 R2 Failover Clustering can provide not only high-availability, but also automatic disaster recovery.http://technet.microsoft.com/video/Hh306278
Tue, 09 Aug 2011 00:00:00 GMThh306278.en-us.msdn.10Symon PerrimanSymon PerrimanZuneTechNet EdgeiPodScreencastsWindows Server 2008 R2Failover ClusteringClusteringFile ServerDisaster RecoveryHigh-AvailabilityArchitectureSymon PerrimanMediaHomepageAdam Bombhttp://technet.microsoft.com/edge/adam_bomb.aspxNew Exchange Clustering and Virtualization Announcements from TechEdJim Lucey dropped by the Edge stage at TechEd in Atlanta to explain the new clustering and high availability support that Exchange announced at the event. Specifically, Unified Messaging is now supported in a virtual machine, and support for both DAGs and virtual machine clusters or failover solutions. You can find more details in this post on the Exchange blog:http://blogs.technet.com/b/exchange/archive/2011/05/16/announcing-enhanced-hardware-virtualization-support-for-exchange-2010.aspxJim Lucey dropped by the Edge stage at TechEd in Atlanta to explain the new clustering and high availability support that Exchange announced at the event. Specifically, Unified Messaging is now supported in a virtual machine, and support for both DAGs and virtual machine clusters or failover solutions. You can find more details in this post on the Exchange blog:http://blogs.technet.com/b/exchange/archive/2011/05/16/announcing-enhanced-hardware-virtualization-support-for-exchange-2010.aspxhttp://technet.microsoft.com/video/Hh204598
Tue, 24 May 2011 00:00:00 GMThh204598.en-us.msdn.10Adam BombAdam BombTechNet EdgeZuneiPodAdam BombTechEdTechEd 2011VideosExchangeClusteringVirtualizationMediaJump Starthttp://technet.microsoft.com/edge/ff832960.aspx?category=Jump%20StartVirtualization Jump Start (04): High-Availability & ClusteringThis module provides a great High-Availability Overview including software & hardware requirements and cluster deployment helping viewers to understand Hyper-V integration & scale. Next it moves into the more advanced components of Hyper-V High-Availability and Disaster Recovery. Viewers will see expert demos of flexible deployment & management options as well as recognizing the importance of automatic disaster recovery. About this Jump Start series: The “Microsoft Virtualization for VMware Professionals” Jump Start is specially tailored for VMware and Microsoft virtualization technology pros. This cutting-edge course features expert instruction and real-world demonstrations of Hyper-V, many components of the System Center Suite, including VMM 2012, and a myriad of VDI solutions. This course is designed for Data Center Managers, IT Professionals, IT Decision Makers, Network Administrators, Storage/Infrastructure Administrators & Architects. Expert IT infrastructure consultant, Corey Hynes, and Microsoft Technical Evangelist, Symon Perriman, leveraged an engaging "team teaching" approach which makes the class as entertaining as it is educational.This module provides a great High-Availability Overview including software & hardware requirements and cluster deployment helping viewers to understand Hyper-V integration & scale. Next it moves into the more advanced components of Hyper-V High-Availability and Disaster Recovery. Viewers will see expert demos of flexible deployment & management options as well as recognizing the importance of automatic disaster recovery. About this Jump Start series: The “Microsoft Virtualization for VMware Professionals” Jump Start is specially tailored for VMware and Microsoft virtualization technology pros. This cutting-edge course features expert instruction and real-world demonstrations of Hyper-V, many components of the System Center Suite, including VMM 2012, and a myriad of VDI solutions. This course is designed for Data Center Managers, IT Professionals, IT Decision Makers, Network Administrators, Storage/Infrastructure Administrators & Architects. Expert IT infrastructure consultant, Corey Hynes, and Microsoft Technical Evangelist, Symon Perriman, leveraged an engaging "team teaching" approach which makes the class as entertaining as it is educational.http://technet.microsoft.com/video/Hh181062
Tue, 19 Apr 2011 00:00:00 GMThh181062.en-us.msdn.10Jump StartJump StartTechNet EdgeZuneiPodJump StartTechNetVirtualizationVMwareMicrosoft Virtual AcademyVideosCorey HynesSymon PerrimanTeam TeachingInstructor-LedITDatacenterHyper-VHypervisorChris CaldwellClusteringDisaster RecoveryDRFAMediaJumpstartKimberly Boltonhttp://technet.microsoft.com/edge/ff832960.aspx?category=Kimberly%20BoltonMicrosoft Virtualization: Solutions to Fit Your Business Needs | TechNet VideoMicrosoft Virtualization helps you deploy solutions to the desktop at one-sixth the cost of competing solutions. Features like Live Migration and Clustering are included at no additional cost. However, as you may realize, the more you virtualize, the more complex your environment can become. Learn how to simplify the management of your virtual and physical environment, including the application layer, through one common integrated interface.Microsoft Virtualization helps you deploy solutions to the desktop at one-sixth the cost of competing solutions. Features like Live Migration and Clustering are included at no additional cost. However, as you may realize, the more you virtualize, the more complex your environment can become. Learn how to simplify the management of your virtual and physical environment, including the application layer, through one common integrated interface.http://technet.microsoft.com/video/Ff711596
Mon, 05 Apr 2010 00:00:00 GMTff711596.en-us.msdn.10Kimberly BoltonKimberly BoltonTechNet EdgeSystem CenterVirtualizationclusteringLive MigrationVideosEnglishKimberly BoltonZuneiPodJames O'Neillhttp://technet.microsoft.com/edge/ff832960.aspx?category=James%20O'NeillA quick introduction to HyperV live migration | TechNet EdgeLive Migration for Hyper-V is one of the major changes to Windows Server 2008 R2. In this screen cast we see how it it is configured, how a virtual machine is added to the cluster and what the process of migration looks like from the client's and server's points of view.Live Migration for Hyper-V is one of the major changes to Windows Server 2008 R2. In this screen cast we see how it it is configured, how a virtual machine is added to the cluster and what the process of migration looks like from the client's and server's points of view.http://technet.microsoft.com/video/Ff955808
Thu, 28 May 2009 00:00:00 GMTff955808.en-us.msdn.10James O'NeillJames O'NeillHyper-VclusteringClusterHyperVen-GBVideosLive MigrationWindows Server 2008 R2UKDPEEnglishZuneiPodTechNet EdgeScreencastsen-gbJames O'NeillJim Teaguehttp://technet.microsoft.com/edge/ff832960.aspx?category=Jim%20TeagueThe 10 Most Important Things About Failover ClusteringFailover Clustering in Windows Server 2008 (formerly known as Microsoft Cluster Service, or even “Wolfpack”) has undergone significant enhancement from previous versions, and as a result what you knew about Failover Clustering in Windows Server 2003 may no longer be applicable. This presentation will highlight ten major areas of change, and how to make them work for you.Failover Clustering in Windows Server 2008 (formerly known as Microsoft Cluster Service, or even “Wolfpack”) has undergone significant enhancement from previous versions, and as a result what you knew about Failover Clustering in Windows Server 2003 may no longer be applicable. This presentation will highlight ten major areas of change, and how to make them work for you.http://technet.microsoft.com/video/Hh710326
Thu, 10 Apr 2008 00:00:00 GMThh710326.en-us.msdn.10Jim TeagueJim TeagueTechNet EdgeMediaZuneiPodJim TeagueWindows Server 2008ClusteringVideosAdam Bombhttp://technet.microsoft.com/edge/adam_bomb.aspxNetwork Load Balancing (NLB) in Windows Server 2008 | TechNet EdgeWe throw ‘clustering’ around a lot at Microsoft. There are a few different technologies that we refer to as clustering, but they all serve very different roles: HPC/Compute Cluster Server Failover Clustering Network Load Balancing We’ve provided a fair amount of info about the first one, we’ve touched on (and will cover more about) the second one, but we’ve never really talked about NLB here on Edge. I thought I’d change that this week. Wait, is this new? Not really. It’s been around in Windows Server for a long time. There are a couple features that are new for Server 2008 though: Support for IPv6 A new NLB cluster creation Wizard instead of a control panel app Better security What does it do? Network Load Balancing is a way to configure a pool of machines so they take turns responding to requests. It’s most commonly seen implemented in server farms: identically configured machines that spread out the load for a web site, or maybe a Terminal Server farm. You could also use it for a firewall(ISA) farm, vpn access points, really, any time you have TCP/IP traffic that has become too much load for a single machine, but you still want it to appear as a single machine for access purposes. How does it work? It’s pretty straightforward. After you install NLB on a server, you add two or more machines to a NLB Cluster. The machines are configured with 2 IP addresses: their own private unique one, and a second one that is shared by all the machines in the cluster. The machines all run an algorithm that determines whose turn is next at responding to requests. They also exchange heartbeats with one another, so they all know if one server goes down and won’t allocate any more requests to him. You can have up to 32 machines in a cluster. You can do some smart stuff with regards to how requests are allocated too. You can set up affinity so that requests from one subnet will be responded to from Server A whenever possible, and that other subnets prefer Server B. Maybe you want 80% of all incoming requests to be handled by Server A, with the rest going to server B. You can do that too. There are a few other things you can do with affinity: Single affinity: connections initiated by a given ip address are handled by the same server in the cluster until cluster membership changes. This is useful for those applications that maintain sessions across multiple connections (e.g. E-commerce applications). Note that SSL connections will need single affinity to avoid re-negotiation at every attempt. No affinity: connections are load-balanced based on originating address and port. This is more efficient, as connections from the same client can be routed to several hosts. VPN and IPSec affinity: vpn and ipsec sessions will be preserved even if cluster membership changes. Class C affinity: useful when internet clients access the cluster through proxies that expose the same class-C addresses. Load balancing is based on the class-C subnet portion of the incoming address. How do I install it? I’ll give you three ways: From Server Manager, just click Add Feature and then select Network Load Balancing From a command line, type “ocsetup NetworkLoadBalancingFullServer” Use ServerManagerCmd! From a command line, type “servermanagercmd –install nlb” Is there somewhere I can get more information? Of course: NLB on TechNet The Clustering/NLB Team Blog (thanks to Giovanni and Hiroshi for their contributions to this post.)We throw ‘clustering’ around a lot at Microsoft. There are a few different technologies that we refer to as clustering, but they all serve very different roles: HPC/Compute Cluster Server Failover Clustering Network Load Balancing We’ve provided a fair amount of info about the first one, we’ve touched on (and will cover more about) the second one, but we’ve never really talked about NLB here on Edge. I thought I’d change that this week. Wait, is this new? Not really. It’s been around in Windows Server for a long time. There are a couple features that are new for Server 2008 though: Support for IPv6 A new NLB cluster creation Wizard instead of a control panel app Better security What does it do? Network Load Balancing is a way to configure a pool of machines so they take turns responding to requests. It’s most commonly seen implemented in server farms: identically configured machines that spread out the load for a web site, or maybe a Terminal Server farm. You could also use it for a firewall(ISA) farm, vpn access points, really, any time you have TCP/IP traffic that has become too much load for a single machine, but you still want it to appear as a single machine for access purposes. How does it work? It’s pretty straightforward. After you install NLB on a server, you add two or more machines to a NLB Cluster. The machines are configured with 2 IP addresses: their own private unique one, and a second one that is shared by all the machines in the cluster. The machines all run an algorithm that determines whose turn is next at responding to requests. They also exchange heartbeats with one another, so they all know if one server goes down and won’t allocate any more requests to him. You can have up to 32 machines in a cluster. You can do some smart stuff with regards to how requests are allocated too. You can set up affinity so that requests from one subnet will be responded to from Server A whenever possible, and that other subnets prefer Server B. Maybe you want 80% of all incoming requests to be handled by Server A, with the rest going to server B. You can do that too. There are a few other things you can do with affinity: Single affinity: connections initiated by a given ip address are handled by the same server in the cluster until cluster membership changes. This is useful for those applications that maintain sessions across multiple connections (e.g. E-commerce applications). Note that SSL connections will need single affinity to avoid re-negotiation at every attempt. No affinity: connections are load-balanced based on originating address and port. This is more efficient, as connections from the same client can be routed to several hosts. VPN and IPSec affinity: vpn and ipsec sessions will be preserved even if cluster membership changes. Class C affinity: useful when internet clients access the cluster through proxies that expose the same class-C addresses. Load balancing is based on the class-C subnet portion of the incoming address. How do I install it? I’ll give you three ways: From Server Manager, just click Add Feature and then select Network Load Balancing From a command line, type “ocsetup NetworkLoadBalancingFullServer” Use ServerManagerCmd! From a command line, type “servermanagercmd –install nlb” Is there somewhere I can get more information? Of course: NLB on TechNet The Clustering/NLB Team Blog (thanks to Giovanni and Hiroshi for their contributions to this post.)http://technet.microsoft.com/video/Ff711653
Thu, 14 Feb 2008 00:00:00 GMTff711653.en-us.msdn.10Adam BombAdam BombNetworkingWindows Server 2008ClusteringNLBEnglishArticlesAdam BombTechNet EdgeNeil Hutsonhttp://technet.microsoft.com/edge/neil.aspxWindows Server 2008 Clustering [SCREEN CAST] | TechNet EdgeThis week I had a chat with Adam about the new failover clustering capabilities within Windows Server 2008 and he showed this in action. After a discussion on the whiteboard, Adam walked me through the installation of clustering support on Windows Server 2008, which involved setting up the clustered configuration across two machines and finally selecting a clustered service, which is this case was to configure Hyper-V in a clustered environment. After starting the Hyper-V virtual environment on one physical machine, Adam failed over the virtual machine to the second physical machine while still maintaining all the state and the running applications. Pretty damm cool, all in less than a minute.This week I had a chat with Adam about the new failover clustering capabilities within Windows Server 2008 and he showed this in action. After a discussion on the whiteboard, Adam walked me through the installation of clustering support on Windows Server 2008, which involved setting up the clustered configuration across two machines and finally selecting a clustered service, which is this case was to configure Hyper-V in a clustered environment. After starting the Hyper-V virtual environment on one physical machine, Adam failed over the virtual machine to the second physical machine while still maintaining all the state and the running applications. Pretty damm cool, all in less than a minute.http://technet.microsoft.com/video/Ff710319
Fri, 08 Feb 2008 00:00:00 GMTff710319.en-us.msdn.10Neil HutsonNeil HutsonTechNet EdgeWindows Server 2008Hyper-VClusteringVideosEnglishNeil HutsonZuneiPodNeil Hutsonhttp://technet.microsoft.com/edge/neil.aspxHow to setup iSCSI on Windows Server 2008 [11 mins] | TechNet EdgeThis is the second in a series of “How To’s” with Adam Carter. This time around, he provided a quick introduction to iSCSI, which is a technology which is part of Windows Storage Server which allows SCSI commands to be shared over the network to enable cheap and simple network storage options. In this 11min screen cast, Adam walks through iSCSI basics on the white board and then sets up an iSCSI target disk to share on one machine and then connects to this disk over the network to a second machine using the iSCSI initiator. This creates a new disk on the second server machine, which he then formats and puts into action. This is very useful for creating clustering scenarios, reduces the complexity of managing shared nothing SCSI ID’s and can be a very cost effective storage scenario. While the simple setup shown in this video works fine in a lab environment, in real life you would connect to your iSCSI disk using a dedicated high speed network cards on a private network to reduce latency. Please watch this and comment.This is the second in a series of “How To’s” with Adam Carter. This time around, he provided a quick introduction to iSCSI, which is a technology which is part of Windows Storage Server which allows SCSI commands to be shared over the network to enable cheap and simple network storage options. In this 11min screen cast, Adam walks through iSCSI basics on the white board and then sets up an iSCSI target disk to share on one machine and then connects to this disk over the network to a second machine using the iSCSI initiator. This creates a new disk on the second server machine, which he then formats and puts into action. This is very useful for creating clustering scenarios, reduces the complexity of managing shared nothing SCSI ID’s and can be a very cost effective storage scenario. While the simple setup shown in this video works fine in a lab environment, in real life you would connect to your iSCSI disk using a dedicated high speed network cards on a private network to reduce latency. Please watch this and comment.http://technet.microsoft.com/video/Ff710316
Wed, 30 Jan 2008 00:00:00 GMTff710316.en-us.msdn.10Neil HutsonNeil HutsonTechNet EdgeWindows Server 2008iSCSIClusteringInternet Small Computer System InterfaceVideosEnglishNeil HutsonZuneiPodAdam Bombhttp://technet.microsoft.com/edge/adam_bomb.aspxiSCSI! | TechNet EdgeI’ve been doing Windows Clustering since back when we used to call it Wolfpack. Clustering is cool, but it can be painful to get it all up and running. Most of that pain often comes from trying to get the shared nothing storage configured properly, which in the old days meant sorting out all your SCSI ID’s for all the devices, or making sure your fiber channel optic cables were clean and connected. Fortunately, network speeds today are such that we can ease some of that pain by moving the storage connections to Ethernet. That process is made really easy by using iSCSI protocols, which are built in to Vista and Server 2008, and have been available as downloads for XP and Server 2003. iSCSI What does it do? Very simply, iSCSI takes commands or requests that the OS would make to a local hard disk, and sends them over the network to a storage array or other target. Disks look like local disks on your machine – you can see them in Disk Management, format them, partition them, etc., but they physically reside as files on the network. What are the components? There are two: · the iSCSI Initiator is the app that you run on your client to make the initial connection to the remote disk. This is included by default in Vista and Windows Server 2008 · an iSCSI Target runs on the storage that you’re connecting to. One is typically available for SAN or NAS hardware, and we include one in Windows Storage Server SKU’s. The iSCSI Target let’s you configure what disks are available to connect to, and what machines are allowed to connect. How do I do it? It’s actually really cool: · Set up an iSCSI Target. You have a few options. If you have a Windows Storage Server with the Windows Unified Data Storage Server add on (WUDSS), It includes a console that lets you configure iSCSI. There are also a few 3rd party iSCSI Target apps you can install on Windows Server. · Configure your iSCSI Disks. On Storage Server, you create some .vhd files, specifying the size. Note that these are just virtual disks, not whole machine images. · Configure which machines can connect to the iSCSI disks, and any security you want to put in place (you can require that the connection to the target use IPSec, for example) · Run the iSCSI initiator from the machines you want to make the storage available on. Connect to the Target, specify which disks you want to connect to, and the disks will show up in Disk Management, where you can assign them drive letters, partition them, etc. Why would I want to do this, again? · It makes Failover Clustering much, much easier. You can get real failover clustering running in an afternoon on a couple of laptops, if you wanted to. · In an Enterprise environment, you can easily leverage centralized storage without a capital investment in specialized storage equipment. Get started Windows Storage Server is normally available as part of an OEM storage device, but you can download an eval version if you want to take a look. Details are available on the Storage Solutions website, and you can register for eval downloads here. (make sure you select WUDSS to get access to the iSCSI Target components) There are also a few companies that make iSCSI Targets for Windows. Nimbus, Rocket Division and String Bean are a few of them (disclaimer: I haven’t worked with any of these products and can’t speak to their performance, reliability or support).I’ve been doing Windows Clustering since back when we used to call it Wolfpack. Clustering is cool, but it can be painful to get it all up and running. Most of that pain often comes from trying to get the shared nothing storage configured properly, which in the old days meant sorting out all your SCSI ID’s for all the devices, or making sure your fiber channel optic cables were clean and connected. Fortunately, network speeds today are such that we can ease some of that pain by moving the storage connections to Ethernet. That process is made really easy by using iSCSI protocols, which are built in to Vista and Server 2008, and have been available as downloads for XP and Server 2003. iSCSI What does it do? Very simply, iSCSI takes commands or requests that the OS would make to a local hard disk, and sends them over the network to a storage array or other target. Disks look like local disks on your machine – you can see them in Disk Management, format them, partition them, etc., but they physically reside as files on the network. What are the components? There are two: · the iSCSI Initiator is the app that you run on your client to make the initial connection to the remote disk. This is included by default in Vista and Windows Server 2008 · an iSCSI Target runs on the storage that you’re connecting to. One is typically available for SAN or NAS hardware, and we include one in Windows Storage Server SKU’s. The iSCSI Target let’s you configure what disks are available to connect to, and what machines are allowed to connect. How do I do it? It’s actually really cool: · Set up an iSCSI Target. You have a few options. If you have a Windows Storage Server with the Windows Unified Data Storage Server add on (WUDSS), It includes a console that lets you configure iSCSI. There are also a few 3rd party iSCSI Target apps you can install on Windows Server. · Configure your iSCSI Disks. On Storage Server, you create some .vhd files, specifying the size. Note that these are just virtual disks, not whole machine images. · Configure which machines can connect to the iSCSI disks, and any security you want to put in place (you can require that the connection to the target use IPSec, for example) · Run the iSCSI initiator from the machines you want to make the storage available on. Connect to the Target, specify which disks you want to connect to, and the disks will show up in Disk Management, where you can assign them drive letters, partition them, etc. Why would I want to do this, again? · It makes Failover Clustering much, much easier. You can get real failover clustering running in an afternoon on a couple of laptops, if you wanted to. · In an Enterprise environment, you can easily leverage centralized storage without a capital investment in specialized storage equipment. Get started Windows Storage Server is normally available as part of an OEM storage device, but you can download an eval version if you want to take a look. Details are available on the Storage Solutions website, and you can register for eval downloads here. (make sure you select WUDSS to get access to the iSCSI Target components) There are also a few companies that make iSCSI Targets for Windows. Nimbus, Rocket Division and String Bean are a few of them (disclaimer: I haven’t worked with any of these products and can’t speak to their performance, reliability or support).http://technet.microsoft.com/video/Ff711644
Thu, 17 Jan 2008 00:00:00 GMTff711644.en-us.msdn.10Adam BombAdam BombISCSIWindows Server 2003StorageClusteringEnglishArticlesAdam BombTechNet Edge