Unsolved
This post is more than 5 years old
1 Rookie
•
124 Posts
0
5592
January 24th, 2019 15:00
System Profile Settings: "Workload profile" compliance
I was wondering what was wrong as the compliance failed on half of my servers (Current Value = "Not Available") even though the remediation process apparently set the "VtOptimizedProfile" correctly.
Then I found this document (https://downloads.dell.com/solutions/general-solution-resources/White%20Papers/DfD%20-%20Workload%20Profile%20based%20Automated%20Server%20Configuration%20-%20rev1.1.pdf) which states:
Unlike other “Attributes”, the WorkloadProfile command does not set a “state”. As such, the “current value” will always report “Not Available”. This behavior is correct since the process simply acts similar to a batch job that sets a number of different attributes.
Now the question has become: Why do half of my servers report "VtOptimizedProfile" under "Current Value" in compliance? (since it should always be "Not Available")
*sigh*

