I am trying to install Teamviewer with a provided MSI with group policy. It works fine with Windows 7 clients, but I can't seem to get it to work with the Surface Pro 3 with 8.1. These are connected via wifi and it appears the wireless network isn't coming up in time on boot or is dropping some where during the process. I can do a gpupdate /force and policy applies, but msi has to install at boot and network isn't coming up properly. What can I do to resolve this?
You need to make sure the computer is connected to the network before it run is GPO. The issue with Wifi is that it require authentication on a user part (most of the time) so the computer doesn't have access to the network.
You could try this.
1. If you can target users for the deployment and make sure that you configure the WiFi to be connected before the user log on. Also in some case you still have to get this run by the computer you could try with loopback set.
Hi JasonSVEC,
The Surface has been connected to the Wifi well before, right?
Please configure the following group policy to have a check.
"Computer Configuration\Administrative Templates\System\Logon\Always wait for the network at computer startup and logon"
Best r
Are you sure that the computer can connect to the wifi without a user. Like i said before normally Wifi connection are configure for the user and no the machine.
The easy thing you could do is make the install rule base on user and configure the connect to the wifi before log on. so that the user can get the GPO and let us know if this works.
I setup a continuous ping and rebooted machine. I can't ping the machine even though it shows wifi connected at login screen. Soon as swipe up to login then I can ping it even though I haven't logged in yet? What is going on here? It's like the wifi card is asleep. Even though Windows 8 shows it is connected. This is a PSK network so no authentication is needed for user or computer.
Hi JasonSVEC,
It seems that there is no network during the logon screen.
As I stated before, we could try to deploy the "Always wait for netowork" group policy.
To make this group policy work, we should restart the machine.
Please ensure this group policy has been deployed, we could run "RSOP" to check the group policy result.
Then we could make a test with the MSI group policy.
In addition, this issue may also be related to WLAN driver.
Here is a similar symptom for reference:
Software Installation via GPO not Working on Wireless Clients
https://social.technet.microsoft.com/Forums/windowsserver/en-US/0f1ad264-6cfa-4010-b393-47d7308f8241/software-installation-via-gpo-not-working-on-wireless-clients?forum=winserverGP
Best regards
Hi JasonSVEC,
Are all the machine the same model? Will the group policy not be applied to all the machines?
As I posted before, this issue will occur if the connection to the network may not be made until a logon has been made. It depends on the WLAN driver.
For the group policy issue, we also try to ask for help from the following catalog. They may have some good advices for you.
Windows Server Group Policy
https://social.technet.microsoft.com/Forums/windowsserver/en-US/home?forum=winserverGP
Best regards