Hi There,
Just blew a whole day trying to figure out what was going wrong with my OSD task sequences. I deploy server images using SCCM and WDS and this generally works fine, to give you a quick run down of our environment:
Virtual machines talk across a vDS which is physically attached to two load balanced nics using the following core switch config:
switchport
switchport trunk native vlan 2
switchport mode trunk
no ip address
wrr-queue cos-map 1 2 2
wrr-queue cos-map 2 1 3 4 6
spanning-tree guard root
and give access to three VLANs as shown below:
To provision servers prior to update 2 I would use computer association, enter the GUID, MAC, and name assign it to an OSD collection and off she went. Now it just brings me to the task sequence wizard that is generally reserved for F12/Unkown Computer provisioning. We have only applied update 2 to the test cluster at this stage and was planning to put it into production on the weekend but I need this resolved first. Provisioning still works in production, it goes straight to the assigned task sequence as expected.
If anyone has seen this or vmware would just like to acknowledge it as a bug that would be great.
JF