Mike, Since this page is something that I assume only admin users will be using as it will be a bit dangerous, I'd make it a separate app and I would use Windows Authentication for it I would turn off anonymous access in IIS and and then set up the app to impersonate the logged in user. <identity impersonate="true"/>
A logged-in user with admin privileges will be able to access the service. Giving the ASP.NET user admin priveleges means that every app on the machine running under the ASP.NET account will have admin priveleges. On 8/8/05, Mike Belcher <[EMAIL PROTECTED]> wrote: > I have the same problem this guy below has...... is this solution what I > need to do? I noticed my service is currently running under the Network > service account: ------------------------ Yahoo! Groups Sponsor --------------------~--> <font face=arial size=-1><a href="http://us.ard.yahoo.com/SIG=12hdvus2a/M=362335.6886445.7839731.1510227/D=groups/S=1705006764:TM/Y=YAHOO/EXP=1123559524/A=2894361/R=0/SIG=13jmebhbo/*http://www.networkforgood.org/topics/education/digitaldivide/?source=YAHOO&cmpgn=GRP&RTP=http://groups.yahoo.com/";>In low income neighborhoods, 84% do not own computers. At Network for Good, help bridge the Digital Divide!</a>.</font> --------------------------------------------------------------------~-> Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/AspNetAnyQuestionIsOk/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
