Currently LBFO using LACP allows the NICs to renegotiate to different speeds which is not allowed in LACP standard.

We've just had a 4 x 1Gb LACP team change to a 3 x 1Gb + 1 x 100 Mb team. LACP requires all link speeds are the same. If NIC was unable to stay at 1Gb, it should have been faulted and dropped from team. Allowing one NIC to drop to 100Mb reduced effective link speed to 100Mb. Gigabit standard requires (?) autonegotiation of individual link speeds - but LBFO should ensure compliance of team with LACP standard. This occurred while moving VMs off this host to another - thankfully I was watching the throughput graph when NIC changed to 100 Mb.

<Team running at 100Mb effective - two main flows, 2 VMs both moving from host 1 to host 2>

PS C:\Windows\system32> Get-NetLbfoTeam

Name : HV-Team
Members : {NIC3LAG1, NIC4LAG1, NIC5LAG1, NIC2LAG1}
TeamNics : LAG14GbTrunk_(NIC2-5)
TeamingMode : Lacp
LoadBalancingAlgorithm : Dynamic
Status : Up

PS C:\Windows\system32> Get-NetLbfoTeamMember

Name : NIC3_LAG1
InterfaceDescription : Broadcom BCM5709C NetXtreme II GigE (NDIS VBD Client) #55
Team : HV-Team
AdministrativeMode : Active
OperationalStatus : Active
TransmitLinkSpeed(Gbps) : 1
ReceiveLinkSpeed(Gbps) : 1
FailureReason : NoFailure

Name : NIC4_LAG1
InterfaceDescription : Broadcom BCM5709C NetXtreme II GigE (NDIS VBD Client) #56
Team : HV-Team
AdministrativeMode : Active
OperationalStatus : Active
TransmitLinkSpeed(Gbps) : 1
ReceiveLinkSpeed(Gbps) : 1
FailureReason : NoFailure

Name : NIC5_LAG1
InterfaceDescription : Intel(R) PRO/1000 PT Server Adapter
Team : HV-Team
AdministrativeMode : Active
OperationalStatus : Active
TransmitLinkSpeed(Gbps) : 1
ReceiveLinkSpeed(Gbps) : 1
FailureReason : NoFailure

Name : NIC2_LAG1
InterfaceDescription : Broadcom BCM5709C NetXtreme II GigE (NDIS VBD Client) #54
Team : HV-Team
AdministrativeMode : Active
OperationalStatus : Active
TransmitLinkSpeed(Mbps) : 100
ReceiveLinkSpeed(Mbps) : 100
FailureReason : NoFailure

<Disabled NIC @ 100 Mb via GUI>

PS C:\Windows\system32> Get-NetLbfoTeam

Name : HV-Team
Members : {NIC3LAG1, NIC4LAG1, NIC5LAG1, NIC2LAG1}
TeamNics : LAG14GbTrunk_(NIC2-5)
TeamingMode : Lacp
LoadBalancingAlgorithm : Dynamic
Status : Degraded

PS C:\Windows\system32> Get-NetLbfoTeamMember

Name : NIC3_LAG1
InterfaceDescription : Broadcom BCM5709C NetXtreme II GigE (NDIS VBD Client) #55
Team : HV-Team
AdministrativeMode : Active
OperationalStatus : Active
TransmitLinkSpeed(Gbps) : 1
ReceiveLinkSpeed(Gbps) : 1
FailureReason : NoFailure

Name : NIC4_LAG1
InterfaceDescription : Broadcom BCM5709C NetXtreme II GigE (NDIS VBD Client) #56
Team : HV-Team
AdministrativeMode : Active
OperationalStatus : Active
TransmitLinkSpeed(Gbps) : 1
ReceiveLinkSpeed(Gbps) : 1
FailureReason : NoFailure

Name : NIC5_LAG1
InterfaceDescription : Intel(R) PRO/1000 PT Server Adapter
Team : HV-Team
AdministrativeMode : Active
OperationalStatus : Active
TransmitLinkSpeed(Gbps) : 1
ReceiveLinkSpeed(Gbps) : 1
FailureReason : NoFailure

Name : NIC2_LAG1
InterfaceDescription : Broadcom BCM5709C NetXtreme II GigE (NDIS VBD Client) #54
Team : HV-Team
AdministrativeMode : Active
OperationalStatus : Failed
TransmitLinkSpeed(Mbps) : 0
ReceiveLinkSpeed(Mbps) : 0
FailureReason : NicNotPresent

<Team now running reliably at 3 x 1 Gb>

I am a microsoft trainer for about 8 years so i think its important for you to hear my suggestions about windows server 2016 (the latest update).
Win server 2016 has so many bugs and you are losing your customers.
Everyone tells me that master please dont tell me about winserver 2016 any more its not reliable and has so many issues.
So if you as microsoft server team want to know about all of the problems please send me an email so i will tell you all about the problems that im sure you dont know aboute all of them.
Thaks
Mahyar safaei

Full Disclosure: I'm the guy who added the URI parsing and connection scheme in CoRD. That was a feature I wanted, so I baked it when I started contributing to the development of the app 10 years ago. https://github.com/dorianj/CoRD/wiki/Command-Line-Use

The Current URI scheme looks like it was written by interns with no supervision. Either your engineers completely ignored RFC 3986, or they thought they were more clever than they really are. Chief among the trespasses is the lack of ability to use the hostname/IP address baked into the scheme, requiring the use of the "full address" parameter, which for some reason has a SPACE in it.

The URI scheme has the ability to bake in user, host, port, and path info, without resorting to query strings. There's a reason this stuff is standardized, and the RDC client (on all platforms) should adhere to that standard.

Virtual disks that are created with storage pools cannot be expanded when tiered storage is used. VDisks created with tiered storage must be created as fixed disks making it impossible to expand later. Either change the process so that tiered VDisks can be created as thin provisioned disks or a process that will allow the expansion for fixed VDisks. It is impossible to determine how large a file server will grow over a period of years and not practical to create 30 TB disks when you only start 5 TB of data. Disk expansion is a must for today's ever grow storage requirements.

There should be an Active Directory Object for main office and other/field locations, Members tab to add bulk users and a drop-down menu in every user account to simply choose which office do they belong to as well. Also, it would be awesome to have a drop-down menu for every user account to bind with domain-joined or non-domain joined PC.
This makes Active Directory and User management way easier, System Administrators can also keep a track of assigned devices to every user, change the location details easily of course for bulk users by creating an office location object and adding multiple users into that location as members. I understand there are powershell scripts to complete bulk action - but still, as said, it makes AD look much more cleaner and could make management way more easier.

Thanks

Hi,

Anti-Spoofing Face Recognition- Even for a Simple Cameras

We are looking for partnership, using this unique patent.
Can we send a demo to you?

Face-spoofing is a killer to most face recognition systems
Static Pictures & Video (dynamic) pictures are killers to all systems

Anti-Spoofing Face Recognition- Even for a Simple Cameras
Full resistant agonist static pictures & dynamic video spoofing

Using a simple normal $5 web-camera
Or using an IP-Camera.
It cannot be bypassed or cheated.

Please have a look at these videos
https://www.youtube.com/watch?v=uqDdxZ3HnGA&feature=youtu.be

A demo video for the software
https://youtu.be/Ew7l7Q1cgk0

https://www.youtube.com/watch?v=Ew7l7Q1cgk0&feature=youtu.be

Finally, we would like to cooperate & work with your company in this field
This patent can be sold to the following sectors”

1. IP-Camera manufacturers


2. ATM cash machines


3. POS machines


4. Time attendance solutions


5. Networks & Security Systems


6. Mobile phones companies


7. Robots & military solutions


8. ERP Solutions, banks, and business

Thanks

Hassan
00201227771020
gm@1topsystems.com
hsheimy@gmail.com