I applaud the people and companies that are signing your PowerShell scripts with certificates. For those of you who have not started signing your PowerShell scripts, it’s time to start. and the good news, it is very easy to do! Continue reading
Category: Security
So I do a lot of work creating AD users for different companies. One of the biggest and simplest things is determining what to use for passwords.
The worst thing you can do is to use a “default” passwords for new users and then have them change it when they first login. By default, users can read Active Directory (** gasp **). What that means is that average users can view most user information including when they were created. So, if I was a bad person (which I am not) I would simply check for new users and since the company gave me a “default” password for new users, I would simply try logging in as new users with the default password. So for those companies that have a “default” password – stop it.
Other companies generate a new random password for users. Some based on a predefined list of “safe” words and then adding random symbols and numbers to the end because it’s easy to remember simple words plus a few characters at the end.
My preferred method is really two lines of PowerShell.
Use PowerShell to quickly pinpoint, diagnose, and solve problems with your Windows Server environment, reducing the need for external tools, and ensuring you stay up-to-date with PowerShell as it quickly becomes one of the most useful tools in an administrator’s toolkit. Purchase your copy now on Amazon.