WiseSvc<GUID> with sysadmin security context in MSSQL server 2005.
Updated: 21 Sep 2010 | 2 comments
The Wise Package Studio ver 8.0 installation creates the following Account:
WiseSvc with the sysadmin role on creation and defaults to the master database.
These type of accounts with such security are not allowed in our organization.
Would the effect of changing the account to default to the wise_workbench database, and granted the db_owner role to wise_workbench, wise_services and wise_software_mgr be benign?
Much thanks..
discussion Filed Under:
Comments
You make changes at your peril
If you are running up against organisational issues with access to an SQL server, then I would strongly recommend that you set up a local SQL server, perhaps on the server hosting your WPS install, or even on your workstation if you are running a single instance (Using SQL Server Express).
There is no published information on how WPS permissions are set up in SQL as this process is all automatic during install. Consequently, the only people who can specifically answer your question are the support team at Symantec, so you will need to raise a call if you want an absolute answer.
However, there are many past posters who have had problems with their WPS operation due to trying to change the default settings to comply with company standards, so once again I would recommend avoiding all that and having your own SQL install associated with WPS where the company SQL mafia will not interfere.
If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.
Thanks for the support
Unfortunatly we had to piggy back on another groups SQL server and in either case the DBA's manage all things Database related.
I appreciate the input and recommendations. I've forwarded them along to our Server, Security and DBA teams.
Looks like I'll be incontact with Symantec.
Much appreciated.
Would you like to reply?
Login or Register to post your comment.