keithmendez
asked on
How do I check App Pool, Security, Execute Permissions in IIS 7?
Based on an earlier issue, I need to check the following:
Vroot in IIS Properties
ClientWebService Directory: %ProgramFiles%Update Services\WebServices\Clien
Application Pool: WsusPool
Security: Anonymous Access Enabled.
Execute Permissions: Scripts Only
Where do I go to accomplish this?
Vroot in IIS Properties
ClientWebService Directory: %ProgramFiles%Update Services\WebServices\Clien
Application Pool: WsusPool
Security: Anonymous Access Enabled.
Execute Permissions: Scripts Only
Where do I go to accomplish this?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Right from the IIS Manual.
Select one of the options on this tab to configure the access that this handler requires to run in a virtual directory. This setting (together with the feature's access policy that is set on the Edit Feature Permissions dialog box) determines whether a handler can run.
Important
Make sure that the required access setting for a handler is correct or else it may be possible for the handler to run unintentionally. For example, if you change the handler's required access from Execute to Read for ISAPI-dll handler, ISAPI extensions will be able to run even if only Read is enabled in the feature's access policy.
Select one of the following options:
None: The handler will run even when no access policy options are enabled.
Read: The handler will run when Read is enabled in the access policy.
Write: The handler will run when Write is enabled in the access policy.
Script: The handler will run when Scripts is enabled in the access policy. This is the default selection.
Execute: The handler will run when Execute is enabled in the access policy.
Select one of the options on this tab to configure the access that this handler requires to run in a virtual directory. This setting (together with the feature's access policy that is set on the Edit Feature Permissions dialog box) determines whether a handler can run.
Important
Make sure that the required access setting for a handler is correct or else it may be possible for the handler to run unintentionally. For example, if you change the handler's required access from Execute to Read for ISAPI-dll handler, ISAPI extensions will be able to run even if only Read is enabled in the feature's access policy.
Select one of the following options:
None: The handler will run even when no access policy options are enabled.
Read: The handler will run when Read is enabled in the access policy.
Write: The handler will run when Write is enabled in the access policy.
Script: The handler will run when Scripts is enabled in the access policy. This is the default selection.
Execute: The handler will run when Execute is enabled in the access policy.
By your appPool definition, did you read this.
http://technet.microsoft.com/en-us/library/cc720452(WS.10).aspx
Cheers,
Hades666
http://technet.microsoft.com/en-us/library/cc720452(WS.10).aspx
Cheers,
Hades666
ASKER
Actually, no...I just looked thru my WSUS 3.0 documentation and don't see it in there, either. I'll take a closer look at it, thanks!
ASKER