Feeling like im getting a late start today, not sure of the reason for the delay other than milling around the internet this morning applying for jobs and checking to make sure my suit still fits as I haven’t been the best at keeping up with my diet as of late. Thankfully
it fits exactly the same as when I bought it, slightly snug. Was hoping to lose a few pounds but haven’t tried too hard in that endeavor.  Anyway lets get on to winning at studying and existing for the time being and get into some questions. The last lot was rather short in terms of the amount of explanation required for the questions. Mostly just helpful ideas rather than overly confusing ideas that lead down rabbit holes of a thought process. The first question is kind of on the same level:

This video is kind of long but it actually covers some good stuff. If you just want to see net-share that comes in around 9 min 40 seconds.

According to the TechNet article this line of cmd should still work in server or any os running a current version of PS. Ive run into a few instances where that actually is a problem.

The next thing I would like to take a look at is how to do this same action in file and storage services, I also have no idea what level you set permissions at when you set them in the previously noted PS command (being NTFS or basic share) im going to assume its share but nothing is specified in the technet article. Anyway there are a lot of videos about file and storage services but this one gets to the point and I think its abundantly clear that its much easier to do this in the GUI

---

This one im not even sure why exactly I thought it was hard enough to blog but I feel like there’s some interesting things about DHCP that go beyond the borders of this from a conceptual standpoint that are both very complicated and very testable. It seems obvious
to use a fail over sever to avoid conflict on your network but if you do have several scopes within one network how do you set that up and quickly recognize this on a new network that you are approaching. So like if I dont have a diagram of subnets how can I can I
quickly and reliably figure out what machines are on what subnet? Anyway here is the basic question:

As you can see creating a failover server on the same subnet is the way to go but what exactly does this mean? Can I create this any where within my network and give it assign it the same scope or does that server have to be configured with an IP in the same range?
So many questions to chase down here which lead this to being a much more complicated question than Im able to reliably answer. All of these questions lead me to this long video which is still is probably not reliably enough information to answer all the questions
that this example could lead to asking. But it does confirm that they have to be on the same subnet for this to work which we sort of knew but im not exactly sure what that means in an enterprise setting other than I need two servers on the same subnet but configuring an enterprise DCHP scope is still well beyond my understanding of DHCP currently however that is some thing an MCSA certified tech should be able to implement. One interesting note is that IPv6 cannot be protected by DHCP failover implementations at this point in time. Which is worth remembering.

This shorter video from CBT nuggets is also sort of helpful if you want a shorter version. However the IP configuration bit is the hardest part and its not really even discussed. This topic is an absolute youtube click hole but the understanding of the actual addressing
in terms of effective subnetting is hardly touched & ive found that to be the hardest bit to actually comprehend. However this one is basically a condensed version of the previous 45 min video. Im not even sure where to start researching actual subnetting.

---

Enabling SR-IOV should be easy right? Just need to make a new switch that has the feature enabled.

This dude is rocking some cool tunes

---

 

The last one you have to create a switch for, this one needs an adapter as the same scenario with the ACL but is still conceptually straight forward You just cant measure traffic if your using SR-IOV. It might also be interesting to know if port mirroring is
supported with SR-IOV as if that was the case then we could still measure traffic, I cant find anything to support this line of thought one way or the other.

---

 

Last question for this round and its actually somewhat confusing to me at this point in my server 2012 studies. Not as bad as DHCP but still its kind of a doozy. Its an interesting note that under some circumstance up to 32 adapters are supported for nic teaming however in Hyper-V 2 appears to be our limit.

The only thing that’s confusing here are the other options. This TCP chimney option comes up a lot but I have yet to see it being in use for an actual answer on an actual test or in MeasureUp