|
Posted by cal on February 29, 2008, 9:29 am
Please log in for more thread options
platform: Windows 2003 Server
no domain, standalone, LGPO, ipsec portblocking and misc other
security settings put
in place via scripts &c -- so security is basically similar to a
Bastion-Host setup...
Before we apply our security segment "tasklist.exe /svc" used to get
the ps (process table)
listing on the local host works fine IOW it does not prompt any user
for the password and
then hang while doing so.
After we apply our security policy segment then the same command hangs
forever
prompting even the Administrator user for a password.
We end up with a lot of tasklist.exe processes totally hung waiting
for prompts that never get input because another process is looping
forever with intermittent
sleeps using tasklist.exe commands to grep through the process table
as part of a health
check mechanism to monitor if certain processes are running or not.
Anyone know what all the security policies are that effect
tasklist.exe password prompt behaviour?
And while we are at it ... why weren't pulist.exe and ptree.exe from
the resource kit
ever ported over to Windows 2003 Server from Windows 2000 Server? We
liked them
better than tasklist.exe, especially, we miss ptree.exe!
AAARRRGGGHHH.
| 
XML Sitemap