OliverPG's questions

I'm pulling my hair out over an issue I'm having with Intune. I've deployed a VPN profile using a custom configuration profile to my users and most users have received the VPN profile on their laptops (W10) without any issue. Some however have not. When checking the devices belonging to the users who haven't received the profile, I see that they Intune policies seem to be applying with the System Account instead of the user.

An example of a working users device configuration status: All policies successfully applied on the device using the primary users UPN.

An example of the device configuration status of a user who isn't receiving the VPN profile: Client settings are applied using the System account but the VPN profile (user setting) won't apply, stating 'Not applicable'.

The 'User status' of the VPN profile configuration profile is showing 100+ 'Not applicable' for System Account. So 100+ of my users aren't picking up the policy. 119 instances of 'System Account' / 'No applicable'.

Some example machines I checked are showing the correct primary user. The VPN configuration profile is targeting 'All Users'.

Any idea why this policy is applying to some users machines using their UPN (and succeeding) and some devices trying to apply the policy using the System Account (and not succeeding)?

Any help would be greatly appreciated.

I am trying to configure a Windows 2019 RRAS VPN server to use DHCP for VPN address assignment from a specific network.

RRAS VPN Server - 192.168.1.20

DHCP Server - 192.168.1.10

VPN Network / Scope - 192.168.10.0 /24

My DHCP server is located on the same network as the VPN server but the IP addresses I want to assign to my VPN clients are that of another network (192.168.10.0/24). These servers are virtual machines running on Hyper-V (on the same host). The DHCP server has multiple scopes configured to serve the physical VLANs in our office. The DHCP server knows which scope to assign addresses to these VLANs from due to IP helper addresses on the physical switches.

How can I configure RRAS on the VPN server to request addresses from the 192.168.10.0/24 scope on the DHCP server?

At the moment, the VPN server is on the 192.168.1.0/24 network (the same network as the DHCP server). If a VPN client connects, it will send out a DHCP request to the DHCP server but how do I control which scope it receives an address from?

I want it to receive a 192.168.10.xxx address and not an address from any of the other scopes being served by that DHCP server. Is this possible with RRAS and Hyper-V virtual switching?

Any help appreciated.