Helpful folks,
We have recently migrated from V7 to V8 of UDB on Windows 2003. We are
now in the process of setting up a rollout deployment to upgrade all
of our user clent PC's from the V7 client to the V8 client using a
response file. The process seems to go smoothly except for one major
glitch. All of our users have the DB2 Security Service running on
their machines set to start automatically. When the V8 migration takes
place, it seems to reset the DB2 Security Service to a manual start
setting. This is definitely NOT a workable situation. None of the
myriad parameters in the response file seem to address this issue.
Has anyone run accross this problem, and if so could you point me to a
solution?
Thanks in advance for any and all suggestions.
Sean
We have recently migrated from V7 to V8 of UDB on Windows 2003. We are
now in the process of setting up a rollout deployment to upgrade all
of our user clent PC's from the V7 client to the V8 client using a
response file. The process seems to go smoothly except for one major
glitch. All of our users have the DB2 Security Service running on
their machines set to start automatically. When the V8 migration takes
place, it seems to reset the DB2 Security Service to a manual start
setting. This is definitely NOT a workable situation. None of the
myriad parameters in the response file seem to address this issue.
Has anyone run accross this problem, and if so could you point me to a
solution?
Thanks in advance for any and all suggestions.
Sean
Comment