I appreciate you sharing the script, but please note that the password is stored unencrypted and visible to others in both the script itself (if you edit the code) and in the registry.
You might want to consider using the Autologin-tool from Mark over at Windows SysInternals instead. It's a great tool to add autologin to kiosk-computers and such, while keeping the credentials safe since they will be encrypted. https://docs.microsoft.com/en-us/sysinternals/downloads/autologon To turn it back off, you simply run the tool again and disable the autologin feature.
In other situations, there's also a Cmdlet to gather credentials and store the password as a secure string which is handy. You can try the following to test it out:
#Running this first line will open a prompt for you to enter username and password and store it in $Credentials
$Credentials = Get-Credential
#Running the second line will output the UserName that was entered previously, and in a readable formt
$Credentials.UserName
#Running the third line will output the Password as a secure-string (non readable)
$Credentials.Password
#You can then use the stored information when running the Invoke Cmdlet for example (ie running a scriptblock on another computer), or when connecting to Office 365.
#Furthermore it's possible to convert the secure-string into an unreadable text format so you can save it in plain text but without the risk of having it compromised.
#Running the fourth line will convert the password from a SecureString and store it in $Password
$Password = $Credentials.Password | ConvertFrom-SecureString
#You can then compare the output of $Credentials.Password and $Password by running them separately. The first one will show the SecureString-data, and the second will show the same information but in plain text while it can also be exported/saved for future use, unlike a securestring.
#Running the fifth line will export the password in an unreadable plaintext-format and save it as a file, so you can import this at a later point in time (ideal when running scripts with the task scheduler where the script needs credentials in order to proceed).
Set-Content "C:\temp\MyPasswordData.txt" $Password
#Running the sixth line will import the password and convert it back to a securestring so you can use it in your scripts.
$ImportedPassword = Get-Content "C:\temp\MyPasswordData.txt" | ConvertTo-SecureString
Hope this helps!
Hi where can i download an older version of Pulseway Agent, the new version removed the login feature, but on windows 7 it works ok for me and i need that,
the last version i think was 6.1.1 agent for windows that had the login feature
dtoxic got a reaction from Shiroe93 in Login feature missing
dtoxic got a reaction from Paul in Agent 7.0 crash
dtoxic got a reaction from Mohamad in Older Version