We have one hyper-v server that powered off uncorrectly. After that it lost all registry information about Hyper-V Virtual Switch Extension Adapter. And all cmd-lets that work vs VMSwitch return error. I reinstall server on the top of previous installation. That solves the problem vs VM switch. Now we have 2 new problems:
1) when i move servers from rds farm on reinstalled hyper-v server our clients from remote office are disconnecting from farm and can not connect while rds servers are on reinstalled hyper-v. Offices are connected by site-2-site vpn, dns records resolved successefully, hosts are pinged too. When users try to connect they see first credentials request to rds and than second to rd gateway, when they enter their creds they see popup error message "there is some error on remote pc". On the normal situation rd gateway not used.
But local clients works fine vs RDS farm while remote got error.
2) we have some vms vs virtual FC adapters. After reinstalling hyper-v host they lost their livemig ability. What i see - there are new initiators on SAN storage. I register it and make some livemig moves between hyper-v host and register all new initiators, before it i delete all inactive initiators. So what i have - is growing initiators count. There is the table of wwnn's ends and SP's endpoints:
08-B1
08-A1
09-B0
09-B1
09-A1
09-A0
0A-B0
0A-A0
0B-B1
0B-A1
0B-B0
0B-A0
I see that i have an odd connectivity pair for 09 and B0 wwnn's, but if i remove some of them live mig stop working between hosts. For example i remove first of odd pair and vm stop move between hv-01 and hv-02 hosts or if i remove other odd pair vs stop move between hv-02 and hv-03.
What i do wrong?