A common means for Windows hosts to be broken into is via weak passwords. In particular, the following accounts are often the target of break-ins:
- SCS Windows domain accounts.
- The local Administrator account on your PC.
You should make sure that your Windows domain password is a good password, and also change the local Administrator account password on your PC to a good password that you can remember (Facilities does not need to know this password). Also, you should make sure that the Guest account on your PC is disabled, since it allows passwordless access to your machine.
In addition, if you are install a networked service such as MS SQL server, you should make sure that any passwords for that service are reset to a strong password that is something other than the default (this is especially true of the sa account on SQL server).
How to choose a good password
A good password is one that is not easily guessed, even if a hacker tries millions of guesses (and hackers do have tools to do that sort of thing). See the document on how to choose good passwords for information on what makes a good password, and some tips on how to choose good passwords.
There are 2 ways in which you can change your SCS Windows domain password. You can use the Instance Manager Tool to change the password.
Alternatively, if you are logged into a Windows machine in the domain, it can be changed using the following instructions:
- Press ctl-alt-delete after you have logged in to your PC.
- Select Change Password on the dialogue box.
- Fill in the given fields on the change password dialogue box. Make sure that the domain is SCS.
Password lockout warning:
If you change your Windows password while logged on to other computers, your account might get locked out for up to 30 minutes. The solution is to log out from all other computers, change your password, and then log out and log back in.
What causes this: Computers, and smartphones too, use your Windows credentials to request network resources. When you change your password from one computer, the other computers will still request resources using the old credentials. Too many of these invalid requests will cause a lockout.