the above setting failed. the expected setting is "Prompt for credentials" and the actual setting is "Prompt for credentials", but still failed. could you please help to make it passed.
can someone response to this issue.
Hello M M,
I am looking into this, can you tell me what Windows version you are running the check against?
Window Server 2008 R2 Standard.
version 6.1 SP1
Hi M M,
I have escalated the issue to development.
Looks like the default value of 3 and the value of 1 mean the same configuration setting but the CID only accounts for the value of one of them (the "1").
I will update when I get confirmation from the engineering team a little later today.
have you got any update from engineering team?.
I apologize for the delay, I was waiting to get some more detail from engineering.
They have responded with some partial information. Development confirmed that the setting you submitted is missing and that the issue was caused by Microsoft changing how this setting is made on the new Windows flavors. To date, we have included Windows 2008 and Windows 2008 R2 in the same technology, but to address this issue, they are considering which approach is best. They may decide to create a new control just for this scenario.
I am waiting on the dev team to meet so they can discuss.
I will post the update with I receive it.
Thanks for the update. i will wait for further update.
I will check with Engineering. The discussion at hand is whether to seperate out Windows 2008 R2 as it's own technology or how to address using the current model.
I will see if I can get a response on the topic today.
I apologize for the delay, I am waiting on response from PM. I reforwarded the query. Product Managemnt and Engineering will make the call on this topic. As soon as I get an update, I will post the status.
I checked with the development manager for signatures and was informed that are going to add a new control for that item. They have started creating controls for 2008 R2 explicitly. For example:
So many customers are using the Windows 2008 controls that splitting the techs would have too great an impact on existing policy reporting.
I should be able to get an update on this specific check after the holidays but have reforwarded this request to development management.
appreciate your efforts
Do i need to open a case with support regarding this issue?.
I had discussed this request directly with the manager of the signature engineering department who develop PC controls and is looking into it directly. They are based in CA so it will be a few hours before I can get an update from him. In response to this last request, I have also forwarded the information to Support for ticket creation as well.
I hope to have a status update today and had actually spent some time yesterday reviewing your control request.
If you want to forward me you contact information, I can confirm I have the correct contact to associate your contact information and your organization with the support-ticket. I beleive I met with your organziation last quarter.
Posting a recent update from enginneering:
Control 7439 released for this task so you should see it in production today or tomorrow.
thanks for the update. i will check it tomorrow.
Appreciate your efforts.
We need your help for CID 1484 which is behaving the same way like CID 2587. Most of our assets were showing last updated date in December 2012 or February 2013. Is there any other CID which is released as replacement for 1484.
Awaiting for your reply,
Retrieving data ...