Well, there are a couple of options when it comes to setting up scripted external access to the database which don't involve changing the account (or password) the console itself uses. Which option to prefer depends on what you are actually using as an external tool, and how much setup work you want to do.
If you look on your GSS installation cd at the
Ghost\ReadMe.txt, there is a section in there which you can find by searching for "password". In that section is a fragment of Windows Script Host script that demonstrates how to do two things:
a) obtaining the username and password used by the console in a script
b) re-enabling the default DBA account with a password of your choice.
Now, in order to do either of those things, you have to be running an account with Administrator permissions.
If your scripts can use technique a) to obtain the credential set they need, that may allow you to avoid forcing all the systems to have identical credentials and also avoid needing to embed the credentials in the scripts (harder to maintain, and more likely to lead to a compromise).
Technique b) opens up the entire gamut of things you can do to the database, including creating additional accounts with specific permissions (for instance, restricting them to particular tables) so that your scripts can do what they need but you can mitigate the risk of password disclosure and having identical passwords on so many systems.