pantscat

Have you tried taking HDD from PC A and putting into PC B to see if it boots? Could be a disk controller issue or mobo, perhaps? [edit] re-reading this, I'm not sure what I was thinking as this wont actually prove anything... except being quite confusing if it *does* boot...

If you're stuck for free antivirus for servers - check out Comodo One - I'm currently reviewing it as an RMM platform and it has it's own av product. Although the whole suite is somewhat in its infancy, it shows promise for device monitoring and management.

No worries - shout if you need anything else!

No problem - to show your trunks: From the cli - do a "conf t", then "show trunk" This will list all the existing trunks. Then to create a new trunk "trunk a1,b1,c1,d1 Trk4 LACP" This will create an LACP trunk called "Trk4", of which ports A1, B1, C1, and D1 are members. It doesn't matter whether the ports are sequential or not. Ant

Yep... One device per trunk... otherwise how will the switch know which device the packets are meant for?

Interesting!

Did it activate ok?

Ah yes - that'll do it! Need more coffee... You're very welcome.

Looks like you've already got it in your switch config - "ip default-gateway 10.217.0.1"

You'd need to assign the switch an IP address for that VLAN, and then use that as the default gateway. Given that that the LA router has the first IP in that subnet - you might want to consider changing the switch IPs to be the final address - e.g. x.x.x.254

Have you got Windows Firewall turned on on the client?

Make sure you've got the TFTP client installed on the Windows workstation you're testing from (check and install under Windows components) - then from a command prompt try this: "tfpt -i 192.168.x.x GET boot.wim" - where 192.168.x.x is the IP address of your TFTP server.

Yep, as @lostsoul has said, it looks like VLAN99 is already earmarked for switch management - move the 10.217.3.x range there, and use VLAN1 for your servers.

PM sent.

It'll be fine - it's due to a Microsoft "feature" whereby you need a Windows 8/8.1/10 + RSAT or Windows 2012/2012 R2 to see and manage IE10 group policy. The group policy settings themselves are stored in SYSVOL so will replicate to every DC in your domain - so the clients will still pick up the settings regardless of which DC it physically downloads the policy settings from. Hope that makes sense. Ant

You could try increasing your TFTP block size - instructions here: System Center Configuration Manager: How to boost PXE TFTP Boot speed

Ok - all devices in VLAN 1 will need to all have the same subnet mask, and to talk to other devices in other subnets/vlans, the same and correct default gateway (which should be the IP of your core switch). Is 10.217.0.31 your DHCP server? Have you created scopes here for the other VLANs? ... and is the default gateway for the VLANs set to the appropriate VLAN IP on the core switch? Ant

Pretty much every time I've come across this it's due to a DNS issue. Check that you've got ageing and scavenging turned on - this is usually the culprit.

Depends rather on what you're running in the core and what you do and don't want your Macs to have access to.

I'd recommend switching to DHCP unless you've got a good reason to keep them static... seems like an unnecessary administration overhead.

It'll be just the currently logged on user.

That's really interesting - thanks, @exa_mark.

I've seen this happen with a Windows root certificate update... it basically tells the OS who and who not to trust.

I think you need to install the intermediary certificate either on the clients themselves, or in your AD cert services server.

That's a good point - assuming that they're using DHCP currently there are a couple of more steps you need to do: 1. setup a DHCP scope for the new VLAN 2. add an ip helper command to your core switch to point at your DHCP server. You may also need to change your main DHCP scope (and any static devices) to point at the core switch as a default gateway.