MZ@ !L!This program cannot be run in DOS mode. $0QQQQQQcPQQQ=PQfPQRichQQPEd՘S"   .rsrc@@(0H`x     ? ~8Ph          ( 8 H X h x   X p#b1BV`h v  H <J`pD@}D4VS_VERSION_INFO++?StringFileInfo040904B0JCompanyNameIntel(R) CorporationDFileDescriptionVlan Resource4 FileVersion19.1.43.00InternalNameVLANResv)LegalCopyrightCopyright(C) 2001-2011 Intel CorporationFOriginalFilenameVLANResENU.Dllz-ProductNameIntel (R) PROSet for Windows* Device Manager8 ProductVersion19.1.43.0DVarFileInfo$Translation Untagged OS ControlledSuccess.SReceive Load Balancing will be disabled because there is a virtual NIC on the team.;A Switch Fault Tolerance team can include only two devices.<Cannot set team mode to VMLB. The Hyper-V role is required.All devices in a Static Link Aggregation team must be capable of running at the same speed. At least one device in this team is not capable of running at a lower speed.FThe team will lose connectivity momentarily. Do you want to continue?This change modified a setting that was part of the profile. The device is now configured to use Custom Settings instead of a profile.This profile changed the Jumbo Frame/Jumbo Packet setting. There may be a loss of connectivity if the Jumbo Frame/Jumbo Packet configuration for a device is incompatible with the switch settings.hYou must restart your system for the configuration changes to take effect. Do you want to restart now?WEnabling IPSec Offloading will disable Large Send Offloading. Do you want to continue?:RSS cannot be enabled while VMQ is enabled on this device.4One or more devices are members of an existing team.1You cannot include more than 8 devices in a team.{This team contains just one device. Add another device to the team to utilize teaming functions. Do you want to continue?HThe devices included in this team do not support the team type selected.Intel(R) Adapters configured as iSCSI Boot Primary or Secondary devices can not be teamed. You must change the Boot Priority setting to Disabled on all selected Intel Adapters before you can create the team.uThis device has a VLAN with a virtual NIC bound to it. You cannot team this device until you remove the virtual NIC.CIntel(R) PRO/100 and 10GbE devices cannot be part of the same team.mEach team must include at least one Intel server device or Intel integrated connection that supports teaming.Receive-Side Scaling is disabled for some devices and enabled for other devices. Receive-Side Scaling will be disabled for the team.{The team contains a device that does not support Receive-Side Scaling. Receive-Side Scaling will be disabled for the team.vThe team contains a device that does not support Receive-Side Scaling. Receive-Side Scaling is disabled for the team.This device s implementation of RSS is incompatible with multi-vendor teaming. Receive-Side Scaling will be disabled for the team. Disabling Receive-Side Scaling will negatively impact the performance of the team.One or more devices do not support true NDIS6.20 Receive-Side Scaling. Receive-Side Scaling will be disabled for the team. Disabling Receive-Side Scaling will negatively impact the performance of the team.One or more devices do not support true NDIS6.20 Receive-Side Scaling. Receive-Side Scaling will be disabled for the team. Disabling Receive-Side Scaling will negatively impact the performance of the team.This team does not support true NDIS6.20 Receive-Side-Scaling. Receive-Side-Scaling will be disabled for this device and the team. Disabling Receive-Side Scaling will negatively impact the performance of the team.This team does not support true NDIS6.20 Receive-Side-Scaling. Receive-Side-Scaling will be disabled for this device and the team. Disabling Receive-Side Scaling will negatively impact the performance of the team.fThis device does not support Receive-Side Scaling. Receive-Side Scaling will be disabled for the team.This team uses Receive-Side Scaling. Adding a device that does not support Receive-Side Scaling to the team will disable Receive-Side Scaling for the team. Disabling Receive-Side Scaling will negatively impact the performance of the team.gThis device does not support Receive-Side Scaling. Receive-Side Scaling will be disabled for the team.OReceive-Side Scaling will be disabled for the team. Do you want to continue?Receive-Side Scaling is disabled for one or more devices in the team. Receive-Side Scaling will be disabled for the team. Do you want to continue?dEnabling Receive-Side Scaling will enable it on all devices in the team. Do you want to continue?Receive-Side Scaling cannot be enabled for this device because it is a member of a team with one or more devices that do not support true NDIS6.20 Receive-Side Scaling.Receive-Side Scaling cannot be enabled for this device because it is in a team with other devices that do not support this feature.}Receive-Side Scaling is disabled for the device being added to the team. Receive-Side Scaling will be disabled for the team.}Receive-Side Scaling is disabled for the device being added to the team. Receive-Side Scaling will be disabled for the team.This team contains a device that does not support Receive-Side Scaling and therefore cannot use Receive-Side Scaling. Receive-Side Scaling is disabled for the team.One or more devices have a Receive-Side Scaling implementation that is incompatible with multi-vendor teaming. Receive-Side Scaling will be disabled for the team.Receive-Side Scaling is disabled for some devices and enabled for other devices. Receive-Side Scaling will be disabled for the team.zReceive-Side Scaling is disabled for one or more devices in the team. Receive-Side Scaling will be disabled for the team.yOne or more devices in the team do not support Receive-Side Scaling. Receive-Side Scaling will be disabled for the team.gThis device does not support Receive-Side Scaling. Receive-Side Scaling will be disabled for the team.One or more devices in the team do not support true NDIS6.20 Receive-Side Scaling. Receive-Side Scaling will be disabled for the team.One or more devices in the team do not support true NDIS6.20 Receive-Side Scaling. Receive-Side Scaling will be disabled for the team. Disabling Receive-Side Scaling will negatively impact the performance of the team.One or more devices in the team do not support Virtual Machine Queues. Virtual Machine Queues capability will be disabled for all team members. Do you want to continue?Virtual Machine Queues are disabled for one or more devices in the team. Virtual Machine Queues capability will be disabled for all team members. Do you want to continue?This device has Virtual Machine Queues enabled; however, Virtual Machine Queues is disabled for the team. Adding this device to the team will disable Virtual Machine Queues on the device. Do you want to continue?This device does not support Virtual Machine Queues. Virtual Machine Queues capability will be disabled for the team. Do you want to continue?Virtual Machine Queues are disabled for the device being added to the team. Virtual Machine Queues capability will be disabled for the team. Do you want to continue?sEnabling Virtual Machine Queues on this device will enable it on all devices in the team. Do you want to continue?Disabling Virtual Machine Queues on this device will disable Virtual Machine Queues capability for the team. Do you want to continue?Virtual Machine Queues cannot be enabled for this device because it is in a team with other devices that do not support this feature.This device has Virtual Machine Queues enabled; however, Virtual Machine Queues is not supported on the team. Adding this device to the team will disable Virtual Machine Queues on the device. Do you want to continue?All devices in a team must have the same value for Jumbo Frames/Jumbo Packets. The Jumbo Frames/Jumbo Packets setting for devices in this team will be changed automatically.The Jumbo Frame/Jumbo Packets size of the device being added to the team does not match the value for the team. The size for the team will be changed to match that of the new device.This device does not support Jumbo Frames/Jumbo Packets. Jumbo Frames/Jumbo Packets will be disabled for all devices in the team.sThe team does not support Jumbo Frames/Jumbo Packets. Jumbo Frames/Jumbo Packets will be disabled for this device.This device does not support Jumbo Frames/Jumbo Packets. Jumbo Frames/Jumbo Packets will be disabled for all devices in the team.uCannot enable Jumbo Frame/Jumbo Packets because another device teamed with this device does not support this feature.uCannot enable Jumbo Frame/Jumbo Packets because another device teamed with this device does not support this feature.The devices in this team use Jumbo Frames/Jumbo Packets. You are adding a device that does not support Intel PROSet. Jumbo Frames/Jumbo Packets will automatically be disabled on the devices currently in the team. You must disable Jumbo Frames/Jumbo Packets for the additional devices.All devices in a team must have the same value for Jumbo Frames/Jumbo Packets. The Jumbo Frames/Jumbo Packets setting for devices in this team will be changed automatically.`The profile cannot be selected because there is a team member that does not support the profile.sThe profile will be changed to Custom Settings on all team members that support profiles. Do you want to continue?The team members you have selected are configured with different profiles. All team members will be set to the team s current profile. Do you want to continue?A new member does not support the profile that is configured for the team. The team will be configured to use the Standard Server profile. The team will lose connectivity momentarily. Do you want to continue?The profile will be applied to other devices in the team. The team will lose connectivity momentarily. Do you want to continue?USome team members have DCB disabled. DCB will be disabled on all members of the team.ZDCB is disabled for the team. DCB will be disabled on the device being added to the team.XDCB is disabled on a device being added to the team. DCB will be disabled for the team.0DCB will be enabled for all members of the team.ZDCB cannot be enabled on this device because some devices in the team are not DCB capable.rOne or more devices do not support DCB. DCB will be disabled on all members of the team. Do you want to continue?This device is bound to Cisco AnyConnect. Adding it to a team will unbind it. You will lose all AnyConnect functionality, including MACsec. The device may lose link. Do you want to continue?This device is configured to access the remote management features of this system. If system management features are enabled, network access to them will be lost. Other network traffic will be handled by the team. Do you want to continue?A device being added to the team does not support Large Send Offload (LSO) capability over IPv6 connections. LSO over IPv6 connections will be disabled for the team. Do you want to continue?A device being added to the team does not support Large Send Offload (LSO) capability over IPv4 connections. LSO over IPv4 connections will be disabled for the team. Do you want to continue?jChanging Large Send Offload will set the same value for all devices in the team. Do you want to continue?Large Send Offload (LSO) is disabled on a device being added to the team. LSO will be disabled for the team. Do you want to continue?fLarge Send Offload (LSO) cannot be enabled because one or more members of the team do not support LSO.jChanging Large Send Offload will set the same value for all devices in the team. Do you want to continue?<Removing this device will leave just one device in the team.The device being removed has one or more VLANs configured. Removing the device will remove the VLANs. Do you want to continue?Removing a device from a team with VLANs. VLANs will be removed and QoS packet tagging will be disabled for the device. Do you want to continue?3The team will be removed. Do you want to continue?ZRemoving this team will remove all VLANs configured on the team. Do you want to continue?yRemoving this team will remove all VLANs configured on the team and disable QoS packet tagging. Do you want to continue?Each team must include at least one Intel server device or Intel integrated connection that supports teaming. Do you want to remove this device and remove the team?MA team name cannot contain tabs or any of the following characters: *:><|?"/\FThe specified team name already exists. Please enter a different name.*The team name cannot exceed 48 characters.Type a name for this team.0A team name cannot begin with a space character.The VLANs on this adapter cannot be moved to the team because the team has a Virtual NIC bound to it. Do you want to add this adapter to the team?lChanging Jumbo Frames/Jumbo Packets will set the same value for the parent device. Do you want to continue?Large Send Offload (LSO) is disabled for one or more devices in the team. LSO will be disabled for all team members. Do you want to continue?This device is part of a team that contains one or more devices that do not support Intel PROSet and may not support Large Send Offload (LSO). LSO will not be enabled for this device or on this team.uLSO over IPv6 is not supported by the team. LSO over IPv6 will be disabled on this device. Do you want to continue?\A device has Intel(R) Active Management Technology enabled and cannot be included in a team._This device has Intel(R) Active Management Technology enabled and cannot be included in a team.Teams support a maximum of 64 VLANs. The selected devices have more unique VLANs bound to them than are supported. Please remove the excess VLANs and try again.NReceive Side Scaling cannot be enabled while SR-IOV is enabled on this device.Intel PROSet is configured with a device, team, or VLAN that is bound to a virtual NIC. Intel PROSet cannot be uninstalled with this configuration. Please remove the virtual NIC and then attempt the uninstall or upgrade again.The system s virtual memory paging file is configured to use an FCoE drive. You must configure it to use a local drive before you can uninstall the device drivers. This adapter is either configured to boot from an FCoE drive or a paging file is located on an FCoE drive. This operation cannot proceed with the current configuration. Disable FCoE boot in the adapter s boot configuration and remove all paging files from FCoE drives.Intel(R) Adapters configured as iSCSI Boot Primary or Secondary devices are present in this system. You must change the Boot Priority setting to Disabled on all Intel Adapters before you can uninstall the device driver.There is a TCP Receive Segment Coalescing capabilities mismatch between the devices in the team. TCP Receive Segment Coalescing will be disabled for all members of the team. Do you want to continue?TCP Receive Segment Coalescing cannot be enabled on this device because it is a member of a team that does not support TCP Receive Segment Coalescing.}Changing TCP Receive Segment Coalescing on this device will change all members of the team to match. Do you want to continue?EOS Controlled is not supported on devices that are members of a team.^One or more devices is part of a Load Balancing and Failover (LBFO) team and cannot be teamed.QOne or more devices' DCB setting is currently OS Controlled and cannot be teamed.wJumbo Frames/Jumbo Packets has been disabled on this team. Jumbo Frames/Jumbo Packets will be disabled for this device.You have added an Intel AMT enabled device to this team. In order to preserve Intel AMT functionality, that device will be set to the team s primary device.AAMT enabled devices cannot be added to 802.3ad, SLA or VMLB teams5AMT enabled devices cannot be added to this team typeRThe team cannot be changed to this type because it contains an AMT enabled device.OThe priority cannot be changed because the team contains an AMT enabled device.The number of queues available for virtualization will be reduced if Data Center Bridging is enabled. This may impact performance of virtual machines. Do you want to continue?:SR-IOV was disabled because it requires VMQ to be enabled.Hyper-V* was disabled in Windows*. The Virtualization Server (Hyper-V*) profile is no longer valid for any Intel NICs in the system. The Standard Server profile should be applied instead. Some devices may lose connectivity momentarily. Do you wish to apply these changes now?Hyper-V* was disabled in Windows*. The VMLB team type is no longer useful and does not perform any load balancing. The team type has been changed to Adaptive Load Balancing instead.Enabling the Virtualization Server profile will enable Virtual Machine Queues on this device. VLANs are not supported on devices with Virtual Machine Queues enabled. The Virtualization Server profile will not be enabled on this device.mHyper-V* was disabled in Windows*. Virtualization performance profiles are no longer valid for any Intel NICs in the system. The profiles will be updated to a valid performance profile. Some devices may lose connectivity momentarily. Do you wish to apply these changes now? If you select no, then settings will not be changed, and performance may not be optimal.The team mode you have selected is not supported in this environment. Use the AFT or ALB team mode for teaming virtual function devices inside a Windows 2008 R2 guest running on an open source hypervisor. This setting cannot be modified.VLANs are not supported on devices with Virtual Machine Queues enabled. Virtual Machine Queues will be disabled on this device.This device is a member of a Microsoft Server 2012 NIC Team (LBFO); Data Center Bridging (DCB) cannot be enabled on it. If you wish to use DCB on this device, it must first be removed from the LBFO team.0A VLAN name cannot begin with a space character.JThe name cannot contain tabs or any of the following characters: *:><|?"/\FThe specified VLAN name already exists. Please enter a different name.The VLAN ID range specified includes one or more IDs already used on this connection. You must use a range that does not include a duplicate ID.fToo many VLANs included in the range of VLAN IDs. Cannot create more than 64 VLANs on this connection.fToo many VLANs included in the range of VLAN IDs. Cannot create more than 63 VLANs on this connection.YCannot create VLANs in the specified range of VLAN IDs. Valid IDs are between 0 and 4094.SCannot create the specified VLAN ID. Enter a VLAN ID number ranging from 1 to 4094.WThe VLAN ID specified is already used on this connection. You must use another VLAN ID.9You cannot create more than 64 VLANs for this connection.9You cannot create more than 63 VLANs for this connection.;The parent device is disabled. Cannot complete this action.<You cannot configure an untagged VLAN without a tagged VLAN.VLAN UnsupportedVLANs are not supported on devices with Virtual Machine Queues enabled. Virtual Machine Queues will be disabled on this device.This team contains a device that has Virtual Machine Queues enabled. VLANs are not supported on devices with Virtual Machine Queues enabled. Virtual Machine Queues will be disabled on this device.@The team has a Virtual NIC bound to it and cannot support VLANs.Adapter is a member of a team.CVLAN names are limited to 32 characters. Please use a shorter name.Please enter a valid VLAN name.9This setting cannot be changed when FCoE boot is enabled.VLANs with the same name or VLAN ID are configured on the selected devices. Only the first VLAN will be added to the team. The duplicate VLANs will not be added to the team.The adapters being added to the team have one or more VLANs configured. This team includes adapters that cannot use VLANs. Do you want to continue and remove all VLAN configured on adapters in this team?One or more of the adapters being added to the Team contains a disabled VLAN. If you continue, the disabled VLANs will be removed. Do you want to continue?One or more VLANs being added uses the same name or VLAN ID as those configured on the team. The duplicate VLANs will not be added to the team.The adapter being added to the team has one or more VLANs configured. This team includes adapters that cannot use VLANs. Do you want to continue and remove all VLANs configured on this adapter?This team will only function if the virtual devices are attached to different physical devices, and if the virtual devices are all on the same VLAN. Please contact your system administrator for this information.This device's MAC address is overridden by the Locally Administered Address advanced setting. You cannot add this device to a team.XThe setting cannot be modified because the device is currently configured for FCoE boot.This team has one or more VLANs configured. You are adding an adapter that does not support VLANs. Do you want to continue and remove all VLANs configured on this team?UOne or more of the listed adapters are virtual function devices and cannot be teamed.VThe command cannot be executed because the device is disabled or in a low power state.+Unable to get third party adapter settings."The specified VLAN does not exist.4This function does not support third party adapters.nUnable to set the adapter priority. The team must have a Primary adapter before assigning a Secondary adapter.Changing the team type from Virtual Machines Load Balancing will disable receive load balancing for virtual machines. Do you want to continue?The selected adapter is an Intel device but does not have an Intel driver installed and cannot run this command. Consult the user guide for more information.UThis setting cannot be modified. It is blocked by the device s current configuration.dThe setting could not be modified because the specified value is invalid for this device or setting.4Setting value is already set to the indicated value.:The %s does not support profiles or the specified profile.#Unable to set the adapter priority.This field is limited to 255 alphanumeric characters. It cannot contain spaces, tabs, or any of the following characters: *><|?"/\!You must enter a valid user name.(User name must be 1-127 characters long.Invalid subnet mask.Enter a valid IP address.%Please enter a valid Gateway address.`All Virtual Machine Load Balancing teams had their team type changed to Adaptive Load Balancing.yAll Intel Ethernet devices using a Virtualization performance profile had their profiles changed to appropriate profile.Changing this setting will modify the value on all partitions bound to the physical port and may cause each partition to momentarily lose link. Do you wish to continue?MThe minimum bandwidth percentage for all partitions cannot exceed 100 percenthThe minimum bandwidth percentage for all partitions must equal 100%, or all partitions must be set to 0%All partitions must have a have maximum bandwidth percentage that is greater than the minimum bandwidth percentage and must not exceed 100 percent.vTeams can contain only one NIC Partition per physical port. The following connections are on the same physical port: SR-IOV has been disabled outside of Windows on one or more devices. SR-IOV cannot be configured and will be set to disabled for the following devices: EEPROM Test FIFO Test Register TestInterrupt TestMAC Loopback TestPHY Loopback TestLoopback Test(s)Loopback Test(s)Speed/Duplex Online TestSpeed/Duplex Offline TestCable Online TestCable Offline TestConnectivity TestNVM Integrity TestConnection Test Mbps Gbps Half Duplex Full Duplex Not AvailableUnknown/DisabledLink Up Link Down Not Present 0 *H 01 0 +0L +7>0<0 +70 0!0 +#s$aҍ2<9l00W~|NYKw;0  *H 01 0 UZA10U Western Cape10U Durbanville10 U Thawte10U Thawte Certification10UThawte Timestamping CA0 121221000000Z 201230235959Z0^1 0 UUS10U Symantec Corporation100.U'Symantec Time Stamping Services CA - G20"0  *H 0 ITK %y"W*oܸ&Csk¿.PZvC%CE{t"״MD$k_E;DCsi+˙r&Mq1QaSI,xE/W?=ƒJ{3y uAQlie)`; tޒ"t|'JÞ-'}aqPK],e ؖ|NHDD h]jxdE`F~T|yq00U_n\t}?L.02+&0$0"+0http://ocsp.thawte.com0U00?U8060420.http://crl.thawte.com/ThawteTimestampingCA.crl0U% 0 +0U0(U!0010UTimeStamp-2048-10  *H  yY0h O]7_R DnmX|0i#s oG9*ÎY M1\*zzWLey@b%n7j!AW?wI*^8j"Q~0085njP0  *H 0^1 0 UUS10U Symantec Corporation100.U'Symantec Time Stamping Services CA - G20 121018000000Z 201229235959Z0b1 0 UUS10U Symantec Corporation1402U+Symantec Time Stamping Services Signer - G40"0  *H 0 c 9D#DIa Sۭ,Jn"hcSit<üu00m'v\Иr0  *H 01 0 UUS10U VeriSign, Inc.10U VeriSign Trust Network1;09U 2Terms of use at https://www.verisign.com/rpa (c)101.0,U%VeriSign Class 3 Code Signing 2010 CA0 120517000000Z 150530235959Z01 0 UUS10 UOregon10U Hillsboro10U Intel Corporation1>0<U 5Digital ID Class 3 - Microsoft Software Validation v210U LAN Access Division10UIntel Corporation0"0  *H 0 ʱi,30+ =Je jjwled0j+3HmjQg 01CSl_PyDEG9NMJ:!ʒ}0[hiMfI&^_$& AYnG4ɕIYA.Ml 5\Qԃ"Ɋ7 jF d1qsǹ?҈], ~sV{0w0 U00U0@U9070531/http://csc3-2010-crl.verisign.com/CSC3-2010.crl0DU =0;09 `HE0*0(+https://www.verisign.com/rpa0U% 0 +0q+e0c0$+0http://ocsp.verisign.com0;+0/http://csc3-2010-aia.verisign.com/CSC3-2010.cer0U#0ϙ{&KɎ&ҧ0 `HB0 +700  *H (_&̑% u^Ӌ9]/N|bJ#|L)|'xk)J;m=6hb1,7LwA jpt6'81|8#[Xߔm|hүyU[~+#콅sOI4eM8֙7+ފ/mDb쨢0 u'a[]k͆eⲾ#j GMy9a: W|Gfض]JGqC2 wߖqU&J@<& m%{Ͽ?/wƵVz;T0Sb4Z(LN~[uGr.4L~O =W0֦6րv.~4-00U00pU i0g0e `HE0V0(+https://www.verisign.com/cps0*+0https://www.verisign.com/rpa0U0m+ a0_][0Y0W0U image/gif0!00+kπjH,{.0%#http://logo.verisign.com/vslogo.gif04U-0+0)'%#http://crl.verisign.com/pca3-g5.crl04+(0&0$+0http://ocsp.verisign.com0U%0++0(U!0010UVeriSignMPKI-2-80Uϙ{&KɎ&ҧ0U#0e0 C93130  *H V"4aHVdٌĻ z"G8J-lq|pO S^tI$&GLc4E &sЩdmqE`YQ9XkԤyk Ar7" #?Da̱\=ҍB=e6Դ=@(#&K ː]L4<7o 4&ٮ Ś!3oX%|tXuc?1|Sv[퓺]!S‚Sc P=TR,=.ǓH10|001 0 UUS10U VeriSign, Inc.10U VeriSign Trust Network1;09U 2Terms of use at https://www.verisign.com/rpa (c)101.0,U%VeriSign Class 3 Code Signing 2010 CA'v\Иr0 +~0 *H  1  +70 +7 10  +70 +7 10 *.dll0# *H  1+