WOL / Impero / HP Machines

[timbo343]

This post covers a number of things so i thought Hardware would be the best place to put it.

 

We usually power machines on via WOL through impero and it's been working great for years however we have suddenly come across a problem, HP machines will not WOL at all even though there hasn't been any changes and they have been powering on without any issues. Sorry tell a lie, they've been re-imaged to Windows 10 and that's it. We managed to turn on a full suite of HP 8000 machines yesterday which had the new image on without any problems, today the same suite will not power on via WOL and cant think what the problem is.

 

We thought the problem was with impero, it turns out even a free program wakeonlan doesnt turn the machines on. Impero will turn on Dell machines without any problems. Nothing in the BIOS has been changed either. Would drivers cause this problem? I cant see this causing this issue.

 

Another problem we have found is Impero's WOL feature. For some reason when in wake a suite of machines up, why do other machines in other rooms come on too? This is something that i have always wondered. I'm surprised impero doesn't keep a list of MAC addresses.

 

We are stumped and would appreciate another head on this issue.

 

Thanks

[damiend]

@timbo343 We recently had this issue with our HP machines and WOL. You need to turn off fast startup - I know it doesn't sound like thats it but trust me it is!

 

If it is on the network cards get turned off at shutdown. If its off the network card remains on.

 

 

• Search for and open “Power options” in the Start Menu.
  
• Click “Choose what the power buttons do” on the left side of the window.
  
• Click “Change settings that are currently unavailable.”
  
• Under “Shutdown settings” make sure “Turn on fast startup” is disabled.
  

 

Hope that helps!

Edited August 9, 2016 by damiend

[timbo343]

Thank you, my tech also found this out tonight after posting the original post. We will give it a try tomorrow.

 

Ive just found this which should make life easier too via group policy rather than visiting each machine http://www.download3k.com/articles/How-to-Enable-or-Disable-Fast-Startup-in-Windows-10-01399

 

Hopefully this thread will help others too.

[timbo343]

We found the problem.

 

It's nothing to do with the fast startup, its to do with the driver on the HP 8000s and the HP 8200 (@ictdirect_dave you might want to read this).

 

In windows 10, these HP machines automatically use the default drivers. These are Version 12.12.50.6 from 20/03/2015 and its looking at %windir%\system32\Drivers\e1i63x64.sys which is completely the wrong driver. We downloaded the latest Intel ProWinX64 driver pack, tried to install it but it said it couldn't find any intel network cards in the system. After about an hour of trying different things, i forced the NIC to use the ProWinX64 driver by first extracting the files from the EXE with 7zip then Right Clicking the driver in device management > Properties > Driver Tab > Update Driver > Browse My Computer > Let me pick from a list of drivers > Have Disk > Browse to the extracted files and drill down through PROWINx64 > Pro1000 > Winx64 > NDIS65 and click on e1c65x64. When the list of compatible cards appeared, we selected the Intel 82579LM. It gave us a warning but we agreed to it, anyway it installed.

 

Now looking into the driver properties > Advanced tab, we had to enable "Enable PME".

 

We powered off a test machine, used Impero to WOL and the machine powered on without any issues.

 

Now, if any anyone knows of a way to force this driver on machines via group policy or even a script and change the advanced setting so that Enable PME is Enabled. We need to visit each machine now so a script would be really handy now.

[Mic_Impero]

Hi all,

 

I've been watching this thread with interest. We don't ordinarily get involved with scripting or GPO of this type for obvious reasons but I'll put it to the team and if we can be of any help, post back.

 

Mic, Support Manager @ Impero

[free780]

I found this registry key worked.

http://support.hp.com/ph-en/document/c04947950

I didn't disable fast startup. I'm using the driver from windows update. Though using mc-wol not impereo.

[timbo343]

Hi all,

 

I've been watching this thread with interest. We don't ordinarily get involved with scripting or GPO of this type for obvious reasons but I'll put it to the team and if we can be of any help, post back.

 

Mic, Support Manager @ Impero

 

Mic, the original problem was with the drivers on the HPs. DELL, Lenovos and Gateway machines all worked fine but if there was a way to change a driver and force it to use another type of driver via a script or command would be great as we now have to remember to make this change everytime we image a machine.

 

One issue we are seeing on Windows 10 running 5.3.32 is a very slow connection between the clients and console. What i mean by this is sometimes shutdown commands dont always work, batch logons dont always work and ive had to put a rule in one of my GPOs for the impero services to start automatically delayed as some machines (various makes and models) wouldnt start the service automatically.

Edited August 10, 2016 by timbo343

[Mic_Impero]

@timbo - our in house infrastructure and systems manager is a bit of a hero (and reports into me) so i'm going to go to him for some help with that script / GPO and see if there's anything he can come up with.

 

In terms of the windows 10 issues since 5.3.32, that's not seeming familiar in terms of support cases I've seen coming through the team, but I'll ask Phil to get in touch about it to see what we can do to help and investigate further. We do test on Windows 10 machines and haven't seen that in house so there's got to be a difference.

[timbo343]

@timbo - our in house infrastructure and systems manager is a bit of a hero (and reports into me) so i'm going to go to him for some help with that script / GPO and see if there's anything he can come up with.

 

In terms of the windows 10 issues since 5.3.32, that's not seeming familiar in terms of support cases I've seen coming through the team, but I'll ask Phil to get in touch about it to see what we can do to help and investigate further. We do test on Windows 10 machines and haven't seen that in house so there's got to be a difference.

 

Many Thanks Mic. We will have to see how win10 goes in Sept / Oct when everyone is back. Only then can we get a real picture of whats happening.

 

What about the issue with powering on machines in one suite and then other random machines are coming on as well? Do you know what causes this? It would be great to.stop this happening.

[Mic_Impero]

Sorry Tim I can't be much help there either but chat it through with Phil when he calls, sounds like something spooky. Either there's a problem with the way the machines are being address or there's a problem whereby when you address a computer in a group it applies the action to the rest of the group perhaps. Phil can get that tested though.