<div>
<div class="content wysiwyg-content">
We're using a freeware component to provide polling: isPollCat.dll from <a href="http://www.pollcat.com" rel="ugc">www.pollcat.com</a>. &nbsp;The component is expected to run in a web page that is accessed via a user account, and that account is suppossed to be in the Administrator group. I set up an 'fcwpoll' account so that staff could access the poll admin page. But of course it is a security risk to have that account in the Administrators group.<br />
<br />
As far as I can tell, the only reason that account needs to be an Administrator is so that it can read and write to the registry. How can we alter our security policy so that the 'fcwpoll' local account has that priviledge, but is not a member of the Administrator group?<br />
<br />

</div>
</div>


We're using a freeware component to provide polling: isPollCat.dll from www.pollcat.com.  The component is expected to run in a web page that is accessed via a user account, and that account is suppossed to be in the Administrator group. I set up an 'fcwpoll' account so that staff could access the poll admin page. But of course it is a security risk to have that account in the Administrators group.

As far as I can tell, the only reason that account needs to be an Administrator is so that it can read and write to the registry. How can we alter our security policy so that the 'fcwpoll' local account has that priviledge, but is not a member of the Administrator group?



System account

Windows Server 2003 was based on Windows XP and was released in four editions: Web, Standard, Enterprise and Datacenter. It also had derivative versions for clusters, storage and Microsoft’s Small Business Server. Important upgrades included integrating Internet Information Services (IIS), improvements to Active Directory (AD) and Group Policy (GP), and the migration to Automated System Recovery (ASR).