DHCP Client Service will not start and shows “Access Denied” error

It’s unclear where this problem is coming from, but it appears to be an issue with the way the registry hives are combined when building boot images. You can see this while editing layers, in published images (in App LAyering 4) or in edited desktops (Unidesk 2). To fix this, you need to edit the permissions on a registry key.

Give “Full control” permission to these three users:

  • DHCP
  • Network Service
  • Add local admin: MachineNameadministrator

for the Registry folder “Tcpip” located at:


Click Advanced, and in that page, check the “Replace all child object permission with inheritable permissions from this object” box. DHCP and Network Service should already be listed, so just set them to Full Control. You will need to manually Add a new record for your local Administrator account, and set that to Full Control as well.

This can be done in the published image, or in each layer as you find the problem, but if you preemptively do it in the OS Layer itself, you should find that the fix automatically propagates out to the layers and images (and desktops in Unidesk 2), so you don’t have to do it each time you find it elsewhere.


Leave a Reply