If you are referring to client computers, then you cannot unless you have a central service managing logins.
For Wi-Fi, this would require your Wi-Fi to be set up using an enterprise profile rather than the consumer standard WPA2. It needs a server to manage the user ids and passwords.
For client computers, you need a central service that is capable of enforcing password policies. Typically, this would be something like a Windows Domain Service. The user ids and passwords would be controlled by the domain and policies are enforced at login.
UPDATE:
You can set up a "Windows" Domain using a Linux computer. The software that does the job is called SAMBA which is likely to be installed on most standard Linux distributions. However, I warn you, setting up a Windows Domain using SAMBA is not necessarily trivial. It also requires you to have a PC turned on all the time which isn't cheap (depending on the cost of electricity in your country).
It also requires everyone to actually log in to the domain rather than logging in locally and that needs changes to the Windows PC's. Assuming you can get the server set up, create new user ID's for each user and get them to log in, you should then go round each PC to:
- Copy any user data and settings from the local login to the domain login
- Delete the local login's
- Make sure that SAMBA is configured correctly to expire the users password at the desired interval and requires a reasonable level of password complexity.
Here are a couple of articles to point you in the right direction for setting up a domain with Samba:
Note that what you are setting up is called a "Domain Controller" or "Primary Domain Controller". The Windows Server component that controls domain controllers is called "Active Directory".