Script required to automatically connect to specific Wi-Fi network

W10 Tweaker said:

I never leave it plugged in when in sleep or shutdown states. I'd just have to remember to hit the power before opening the lid.

Michael,

Since you are happy to remove AC power then use hibernation instead of sleep and the wakeup problem disappears anyway.
- TS cannot wake from hibernation unless AC is available.
- This undocumented limitation has existed since WinXP if not earlier.
- The only exception I have seen has been for a computer that had S0 Modern standby.
- This solution would allow you to revert the network connection to automatically connect.

Denis

Try3 said:

Michael,

Since you are happy to remove AC power then use hibernation instead of sleep and the wakeup problem disappears anyway.
- TS cannot wake from hibernation unless AC is available.
- This undocumented limitation has existed since WinXP if not earlier.
- The only exception I have seen has been for a computer that had S0 Modern standby.
- This solution would allow you to revert the network connection to automatically connect.

Denis

Thanks for that idea. The OS is using an SSD so I've not been using hibernation since.
No S0 available on this PC.

I have to wonder about this intermittent behavior and if it could be related to the using the TS without AC power. Intermittent behavior with a digital device is certainly not logical.

I've reverted back to my original vbs & .bat files to accomplish the reconnect as I've been unsuccessful with 1 script file.
I've added an additional trigger as per Matthew's suggestion in post #42, to use Event 7001. Thanks Matthew.
I've removed the condition of 'Start the task only if the PC is on AC' until I'm satisfied that the process is reliable.
I've also reset the count on my reliability test to connect.
I'll try to keep this count updated where-ever it exists in the most recent post.


Reliability Count;
4 successful connects for the past 6 attempts.

Also, added trigger again, 'Start the task only if the PC is on AC'.

Matthew Wai said:

When I sign out, the Event ID is 7002. When I log on, it is 7001.



Michael may consider using the following settings:



See whether it is more reliable than "At log on", as Michael said the following:


Run the following line of commands via PowerShell. You should get a list of "User Logon Notification".

Get-WinEvent -FilterHashtable @{LogName='System';ID='7001'}|FT -AutoSize

Triggering on Event 7001 looks like a great idea, added new trigger. Thanks for that PS script, it appears that there have been many 7001 Events. I keep moving in & out of sleep to test functionality of the Task Scheduler script.

After I gain more confidence in the reliability, I'll remove 'At logon' and possibly 'After connection to a user session'.
I did try the following script without success. And yes I caught the originally missing 'connect'.

CreateObject("WScript.Shell").Run("C:\Windows\System32\netsh.exe wlan connect ""[ssid]"" ""{profile name]"" ""Wi-Fi"""),0


I tried a few tweaks, syntax etc but couldn't get it to function. I noticed in some earlier posted scripts, there was a space after 'run', does the '(' negate the requirement for a space?

Matthew Wai said:

Let's get back to basics. Copy the following line into this file: C:\Scripts\WLAN\Netsh.vbs

CreateObject("WScript.Shell").Run"%WinDir%\System32\netsh.exe"

Just double-click on "Netsh.vbs" and see whether the Netsh window will pop up.

Affirmative, this leaves a cmd window open. Thanks.

Matthew Wai said:

Neither a bracket nor a space is required in practice.

Thanks for that info. If the bracket or space are not required, is the purpose only to make the script easier to comprehend? Almost comparable to a rem statement?

Hello @W10 Tweaker,

W10 Tweaker said:

If the bracket or space are not required, is the purpose only to make the script easier to comprehend? Almost comparable to a rem statement?

Different people have their own set ways of writing code that suits them. I personally use spaces and code blocks etc as opposed to a long string of commands in one line because it makes the code easier to read and troubleshoot.

Paul Black said:

Hello @W10 Tweaker,




Different people have their own set ways of writing code that suits them. I personally use spaces and code blocks etc opposed to a long string of commands in my code because it makes the code easier to read and troubleshoot.

Thanks Paul, that makes sense to me. Anything we can do to make things more apparent just makes most everyone's life easier, in the long run. There's very little point to be secretive about this stuff.

Hello @W10 Tweaker,

W10 Tweaker said:

Thanks Paul, that makes sense to me. Anything we can do to make things more apparent just makes most everyone's life easier, in the long run. There's very little point to be secretive about this stuff.

You are VERY welcome.

I agree. I have OCD so it is slightly different for me. I think people are more inclined to run code given here if it looks structured, clean, and tidy, rather than long strings of code which are VERY hard to decipher.

Paul Black said:

… long strings of code which are VERY hard to decipher.

And hence very difficult or impossible to debug & maintain.

Denis