PowerShell Module Missing Set-OVServerProfile

[Poyatier]

I've been working on writing a powershell script to change the firmware baseline and some BIOS settings in my OneView server profiles (OneView 8 & HPEOneView.800 powershell module) and while Set-OVServerProfile is listed in the contents, it doesn't actually appear to be there when I install it.

Is this still a cmdlet?  I don't have any templates associated with my profiles so I'm attempting to update the profiles via powershell directly.  The Update-OVProfile or Update-OVServerProfile cmdlets pertain to templates-- so I'm looking for something else.

Any ideas?  Thanks in advance.

[ChrisLynch · Accepted solution]

A few things:

1. You really should explore the use of Server Profile Templates.  This helps to reduce the adminsitrative overhead complexity when needing to manage many individual server profiles.  Especially when/if they share the same configuration.  If they already do, you can create a profile template from a profile, then assign that template to your profiles either through the UI or using the Join-OVServerProfileToTemplate Cmdlet.
2. Set-OVServerProfile was a placeholder Cmdlet that hasn't been developed yet.  To edit server profile objects, use the Get-OVServerProfile Cmdlet to get the needed profile, then change the properties within the object to the needed values.  You can then use Save-OVServerProfile to commit those changes.

[Poyatier]

Thanks for the reply-- somehow I missed the Save-OVServerProfile cmdlet.  Guess my eyes were fixated on the Set-OVServerProfile.

To the point about Templates-- couldn't agree more.  We have a lot of different frame configurations that result in many different templates and not everything within a given configuration can get upgraded quickly so we've been going without.  It would be nice if we could exclude enclosure groups from the template and have them be more EG agnostic but I understand the relationship so doubt it would ever happen.