Using the system account will prevent your using Kerberos for the client
logon - for Kerberos, the service must be running under a domain account
with specific domain rights. This means you'll need a less secure client
logon (e.g. client authorization or passing a userid & password), which is a
potential security issue.
"DB2" <pi****@yahoo.com> wrote in message
news:11*********************@c13g2000cwb.googlegro ups.com...
Hello, everyone.
Does anyone know what potential security issues when running DB2
services (start-up) using local system account instead of the DB2 admin
account?
DB2 environments:
Windows Server
DB2 all editions
Thanks.
JJ.