Windows 10: Deployed software via Group Policy won't install PC requires a restart

Hi all,



Driving my self insane with this one -- hoping someone can put me out of my misery.


I have created GPO which deploys LAPS to the local domain PCs. I am using a network share on the domain controller to host the .MSI


'I believe' I have set everything up correctly:





^ I have tried 30, 60 90 and 120 seconds and nothing helps. ^




but, every time I go onto the PC and do GPUPDATE /FORCE the above message shows. I then say "Y" so it reboots — which it does. After it reboots, I go into APPWIZ.CPL and LAPS isn't installed. If I run GPUPDATE /FORCE again the same message is shown in CMD? It's just a constant loop?!

It isn't a compatibility or version issue because I can install it manually by going to the network share and also using msiexec /I “\\DC.CORE.THINKING-SOFTWARE.COM\LAPS\LAPSx64.msi” /quiet. I ran CMD and Administrator.

I've even temporarily disabled UAC even though I know it wouldn't help the issue.

I've gone through everything and it should be deployed, but it isn't.

Any suggestions are appreciated.

:)

 

Wireless Network Deployed Through Group Policy Becomes Corrupted

In our organization we have three wireless networks that we deploy to all PCs using Group Policy. This allows users to automatically connect to the wireless networks with pass-through Windows credentials. The SSIDs of the wireless networks are hidden for
security purposes.





Randomly, the networks will quit being recognized by the computer, and it will no longer automatically connect. For the users to connect, they must scroll to the bottom of their wireless networks listed and click on "Hidden Network." They are then prompted
for the SSID of the network and then asked for their Windows credentials.





The only solution we have found for this is to either delete the Windows user profile on the PC, or remove the network from Group Policy (which removes it from all PCs in the organization), then delete the network from the PC and add it back to Group Policy.
Neither one of these is a good solution.

We cannot delete the network using netsh because we get a message saying the network is deployed with Group Policy and is read only. I've also tried deleting the network from the registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WlanSvc\GroupPolicy\Profiles.
However, this seems to have no effect.

Is there any way to deal with this wireless network profile corruption other than the two poor solutions I have found?

 

Wireless Network Deployed Through Group Policy Becomes Corrupted

I've re-posted in the correct forum. The new thread is:
https://social.technet.microsoft.com/Forums/en-US/b86fbbfc-dff1-4ed6-8dc1-6d1136a7a0d1/wireless-network-deployed-through-group-policy-becomes-corrupted?forum=win10itpronetworking

 

Couldn't connect to windows group policy service????

Hi,

Thank you for posting in Microsoft Community, we appreciate your interest in Windows 10.

I understand the inconvenience you are facing as with error: Couldn't connect to windows group policy service, we will help you with this issue.

Do let us know when exactly you received this error code?

This issue might have occurred due to corrupted user profile, User Profile Service or Group Policy Client service stopped working, or Antivirus software conflicts.

I suggest you to check with the following and check if it helps.

Group Policy Client service, this service is responsible for applying settings configured by administrators for the computers and users through the Group Policy component. If the service is disabled
the settings will be applied and applications and components will not be manageable through Group Policy.

Step 1: Stop the Group Policy Client service.

• Press Windows Key + R on the keyboard and type
  services.msc, Services window gets opened.
• Search for Group Policy Client service, right click on it and click on
  Stop.
• Restart the computer.

Step 2: Start
the service and set it to Automatic:

• Press Windows Key + R on the keyboard and type
  services.msc, Services window gets opened.
• Search for Group Policy Client service, right click on it and click on
  Properties.
• Start the service, set
  Startup type to Automatic.

Hope it helps. Reply to the post with an updated status of this issue for further assistance.