Hello, are you still looking for some input on this? If yes, I had experienced this type of problems. And, for all Microsoft NLB applications, We had to create networks on legacy network devices only. As per my discussions with one of the Microsoft teams, They had no plans to change the MAC address ( Non-RFC standard) to support SDN technologies like ACI We tried all possible ways like flooding enabled, gateway outside of ACI fabric --still, there is an intermittent disconnections. It is best not to connect these servers to Cisco ACI.

Update: This has now been posted as a Knowledge Base article. Manual po remontu akpp u660e. ===== Hi everyone, Alvin Morales here again. I recently came across several cases here in support where folks were looking for the steps needed to configure Microsoft Application Virtualization (App-V) with a Microsoft Network Load Balancer (NLB) setup so I thought I should probably get something published here in case anyone else was wanting to do the same thing. Microsoft NLB can be used with App-V to perform RTSP Server refresh and streaming, deploying several servers behind a virtual name. Keep in mind that this only applies to client refresh and stream using RTSP.

Microsoft XBox - This is Microsoft's XBox Visio stencil MTMnet - This site has network stencils for 3com, Adtran, Cisco, Clavister, Extreme Networks, and Foundry NetPlex - This is NetPlex's official set of Network stencils.

Vmware workstation 9 free download for windows 8 32 bit. Download VMware Workstation 9.0. VMware Workstation for Windows 32-bit and 64-bit with VMware Tools. VMware Workstation for Windows 32-bit and 64-bit with.

The App-V admin console cannot be opened using the virtual name because the virtual name is not an actual object in AD and delegation cannot occur, thus causing the connection to fail. For the Admin console to work you will need to continue to point to any of the individual server names.

1) Install each App-V server and configure the App-V management service to run under a domain account. Register the SoftGrid Service Principal name for each server to the domain account using the setspn tool: FQDN: setspn -A SoftGrid/server1.domain.x domain service-account setspn -A SoftGrid/server2.domain.x domain service-account NETBIOS: setspn -A SoftGrid/server1 domain service-account setspn -A SoftGrid/server2 domain service-account When the App-V server was installed it should register the SPN to the computer account in Active directory, thus causing duplicate SPNs on the network.

To avoid this, run the setspn command to delete the SoftGrid SPN registered to each server account in AD. A sample is provided below: These commands will list the existing SPN registered to the server account, verify the existence of the SoftGrid SPN, SoftGrid/server1.domain.x setspn -L server1 setspn -L server2 If the SoftGrid SPN exists delete it by running the setspn -d command against the computer account. Example: FQDN: setspn -D SoftGrid/server1.domain.x server1 setspn -D SoftGrid/server2.domain.x server2 NETBIOS: setspn -D SoftGrid/server1 server1 setspn -D SoftGrid/server2 server2 2) For redundancy, the content share must reside on a DFS share or NAS. You must configure each App-V server to use the UNC path of the virtual name of the DFS share or NAS in the system options in the Admin console as well as in the content registry path (HKLM Software Microsoft SoftGrid 4.5 Server SOFTGRID_CONTENT_DIR). The content share could reside on one of the servers but this will not provide the redundancy in case one of the servers should fail. Note If HTTP streaming is used you must configure NLB to use port 80 as well as creating the content virtual directory on each IIS server. 3) Install and configure the NLB service on each server and create the virtual name for the NLB cluster.