silvestre

Easiest fix is an in place upgrade which will fix the corruption as someone mentioned above. Other than that you need to check the cbs.log.

Did you update MDT and ADK?

https://community.spiceworks.com/how_to/116865-add-drivers-to-mdt-all-versions-total-control-method

Add the Ethernet drivers to the boot image for that particular model

What did you try? Did you add drivers ? Where did you add the drivers ?

From the error it looks like you need to add your network drivers form the new pc in your boot image

np , i hope you find the solution

needs further diagnosing, without access im afraid will be very difficult.

Hi remove the trafic filters first and redeploy if you can access everything. Once you get it working with it being fully open to the subnet you can then make further changes.

paste your xml again

if the route is not showing then yes there is an issue with your xml

how are you deploying the profile?

single nic is supported with rras. try with route 10.0.0.0/8 to include your entire range and redeploy the profile. you can check with powershell on the client to show route if the route is added. You do not need to deploy a User tunnel unless you plan on using NRPT.

you will also need the DNS servers used on th e VPN server added to the route in DT.

you have one route specified and that too its incorrect. 10.42.92.0/32 (10.42.92.0 is not a valid IP . With a /32 subnet you need to provide an actual ip for example. 10.42.92.20