Hi All,
For one of the deployment types, we are using a requirement rule to check for the presence of a file. Like if the specific file is present then dont do the deployment and if not there then deploy it. So everything is working properly.
Twist is when we see the report most of the success result slowly moves to "Requirement not met". what i meant is when the deployment first run on the system it create the file system what i am using in the requirement to check. So after the successful deployment when the policies run for the second time, the requirement conditions are not met as the files are now there. This is my understanding, is i am thinking correct ? If yes is there is anyway so that we can see the reports correctly.
For one of the deployment types, we are using a requirement rule to check for the presence of a file. Like if the specific file is present then dont do the deployment and if not there then deploy it. So everything is working properly.
Twist is when we see the report most of the success result slowly moves to "Requirement not met". what i meant is when the deployment first run on the system it create the file system what i am using in the requirement to check. So after the successful deployment when the policies run for the second time, the requirement conditions are not met as the files are now there. This is my understanding, is i am thinking correct ? If yes is there is anyway so that we can see the reports correctly.
