powershell network mac address remote computer

At this time Microsoft has repeatedly suggested that PowerShell not be used for logon scripts due to its heavy footprint. It is a single source of failure and will slow down the logon process. You should not be running this much complex script in a logon script. Laptops in a domain will keep their accounts locked down as long as you keep the DCs secure. Password must be complex and changed frequently. YOu need to enforce security via the logon system.

MAC addresses can and are easily spoofed. YOu fail to explain how this will improve security. The MAC will never change unless someone installs a new network card. GetMAc /s can always retrieve the mac remotely.

If you have to install PowerShell then that is when you should gather the info that is NOT in AD. Note also that PowerShell is NOT installed on all PCs or Laptops by default so the script may not work. Are you a student volunteer or is this a paid job? It soulds like someone at your scholl stuck you with a job but failed to provide you with training. The remainder (OS.Manufacturere, Service Pack) are all recorded in AD when the computer is joined. The MAC can always be taken from the IP and the IP is always registered in teh Event LOg. Why would you collect this on every logon as it would bethe same as when the PC was joined to the network.

Powershell network mac address remote computer