The host profile

Similar Questions

• How to configure the local and logging remotely using the host profiles, not with advance options

  Help, please

  Hello

  Local and remote syslog feature can be configured for a cluster of similar hosts using the host profiles.

  For more information, see guide installation and Set Up Syslog of the section of the Interface of host profiles in vSphere Installation.

  Connect the Server vCenter by using the vSphere Client.

  Click home.

  Under the administration section, click host profiles.

  Create a new profile or modify an existing profile.

  In the Edit Profile dialog box, set one or more of the five configuration options.

  If you configured using esxcli or advanced syslog configuration options and this has captured a host of reference, 5 configuration options are already visible in the Advanced Configuration option section.

  If syslog has not been previously configured, right-click the section of Advanced Configuration options and add a profile for each of the five configuration options.

  Save the profile and assign it to the hosts.

  For more information please see the documentation Center: (Documentation Centre of vSphere 5.5 )

• Disable / enable sharing (salting) memory in the host profile

  vSphere / esxi 5.1

  Does anyone know where is memory privileged share between virtual machines in the profile of the host?

  I disabled the salting after it has been put a patch last year, but now my cluster complains of being non-compliant and I cannot find the setting in the profile of the host.

  No matter which help out me?

  Looking for a Mem.ShareForceSalting in the profile of the host. Allows to set the value of salt.

  The current value can be discovered by esxcli system parameters list advanced o/Mem/ShareForceSalting. I guess you want to change to 1 (default is 2)

  You can edit this profile host to change the right profile---> advanced configuration Option---> Clik---> Add Profile. Create a new profile with OptionProfile at the bottom of this sheet.

  Expand OptionProfile---> Advanced Option---> select "configure a fixed option.

  On the first box, enter Mem.ShareForceSalting and on the second box set to 1 (I changed the salt value (default) 2-1)

  Then follow the standard-setting process and application of profile

• the host profiles and CVS?

  We have hosted 5300/5400 severa intels in a cluster of evc.  We did a profile of the host of one of these servers.  Then we added a new server intel 5600 to VC, but not in the evc cluster. We then applied the restarted host profile. We were surprised to see that vmware allowed us to vmotion virtual machine to a host in the evc cluster to 5600 host without complaining.

  My question is the hsot profiles modify the host server to match the settings of evc also?

  VCA is not included in the profile of the host. VCA is actually CPUID masking at the virtual machine level. If it is not a surprise that you can VMotion VM of EVC cluster to more recent host.

  ---

  MCSA, MCTS, VCP, VMware vExpert 2009

  http://blog.vadmin.ru

• Alarm to monitor the deviation from host profile

  So, I used the creation of Luc alarm script and massacred to create (hopefully) an alert when a host deviates from his profile.  However while I first thought I cracked, I clearly do not have.

  Can we see something glaring by the following:

  # Variables

  $vc = "vcsa.lab.mdb - Lab.com.

  $credential = get-Credential

  $mailto = " " [email protected] "" "

  # Connect to vCenter

  SE connect-VIServer $vc - credential $credential

  $alarmMgr = get-view AlarmManager

  $dc = "London".

  $entity = get-data center $dc | Get-View

  # Create the AlarmSpec object

  $alarm = new-Object VMware.Vim.AlarmSpec

  $alarm. Name = "Violation of the host profile.

  $alarm. Description = "home deviation of profile screens.

  $alarm. Enabled = $TRUE

  # Alarm action

  $alarm.action = new-Object VMware.Vim.GroupAlarmAction

  $trigger1 = new-Object VMware.Vim.AlarmTriggeringAction

  $trigger1.action = New-Object VMware.Vim.SendEmailAction

  $trigger1.action.ToList = $mailTo

  $trigger1.action.Subject = "not compatible with the host profile.

  $trigger1. Action.CcList = «»

  $trigger1. Action.Body = «»

  # 1A - yellow transition-> red

  $trans1a = new-Object VMware.Vim.AlarmTriggeringActionTransitionSpec

  $trans1a. StartState = "yellow".

  $trans1a. FinalState = "red".

  # Transitional 1 b - red-> yellow

  $trans1b = new-Object VMware.Vim.AlarmTriggeringActionTransitionSpec

  $trans1b. StartState = "red".

  $trans1b. FinalState = "yellow".

  $trigger1. TransitionSpecs += $trans1a

  $trigger1. TransitionSpecs += $trans1b

  $alarm.action.action += $trigger1

  # 1 compatible host expression: profile

  $expression1 = new-Object VMware.Vim.EventAlarmExpression

  $expression1. EventType = $null

  $expression1.eventTypeId = "Host" compatible with the profile

  $expression1.objectType = 'HostSystem.

  $expression1.status = "yellow".

  # 2 expression - Profile non-compliant host

  $expression2 = new-Object VMware.Vim.EventAlarmExpression

  $expression2. EventType = $null

  $expression2.eventTypeId = "not compatible with the host profile.

  $expression2.objectType = 'HostSystem.

  $expression2.status = "red".

  $alarm.expression = new-Object VMware.Vim.OrAlarmExpression

  $alarm.expression.expression += $expression1

  $alarm.expression.expression += $expression2

  $alarm.setting = new-Object VMware.Vim.AlarmSetting

  $alarm.setting.reportingFrequency = 0

  $alarm.setting.toleranceRange = 0

  # Create the alarm.

  $alarmMgr.CreateAlarm($entity.) MoRef, $alarm)

  # Disconnect the vcenter

  Disconnect-VIServer $vc - confirm: $false

  I tried first with a green status instead of yellow... but then the script will not yet create.  In its current form, I get a load of the SOAP faults page...

  Any help would be (as always) greatly appreciated.

  -Mark

  With the help of Oynx I have it fixed.  Here's what it is today:

  # Variables

  $vc = "vcsa.lab.mdb - Lab.com.

  $credential = get-Credential

  $mailto = "[email protected]".

  # Connect to vCenter

  SE connect-VIServer $vc - credential $credential

  # Get the data center

  $dc = "London".

  $entity = get-data center $dc | Get-View

  # Create the alarmspec object

  $spec = new-Object VMware.Vim.AlarmSpec

  $spec.name = 'Deviation from host profile.

  $spec.description = 'home deviation of profile screens.

  $spec.enabled = $true

  # 1 expression: profile host is non-compliant

  $spec.expression = new-Object VMware.Vim.OrAlarmExpression

  $spec.expression.expression = new-Object VMware.Vim.AlarmExpression [] (1)

  $spec.expression.expression [0] = new-Object VMware.Vim.EventAlarmExpression

  $spec.expression.expression [0] .eventType = "HostNonCompliantEvent".

  $spec.expression.expression [0] .objectType = "HostSystem.

  $spec.expression.expression [0] .status = "red".

  # Create the alarm action

  $spec.action = new-Object VMware.Vim.GroupAlarmAction

  $spec.action.action = new-Object VMware.Vim.AlarmAction [] (1)

  $spec.action.action [0] = new-Object VMware.Vim.AlarmTriggeringAction

  $spec.action.action [0] .Act = new-Object VMware.Vim.SendEmailAction

  $spec.action.action [0].action.toList = $mailto

  $spec.action.action [0].action.ccList = «»

  $spec.action.action [0].action.subject = "not compatible with the host profile.

  $spec.action.action [0].action.body = «»

  $spec.action.action [0] .transitionSpecs = new-Object VMware.Vim.AlarmTriggeringActionTransitionSpec [] (1)

  $spec.action.action [0] .transitionSpecs [0] = new-Object VMware.Vim.AlarmTriggeringActionTransitionSpec

  $spec.action.action [0] .transitionSpecs [0] .startState = "yellow".

  $spec.action.action [0] .transitionSpecs [0] .finalState = "red".

  $spec.action.action [0] .transitionSpecs [0] .repeats = $false

  $spec.action.action [0] .green2yellow = $false

  $spec.action.action [0] .yellow2red = $false

  $spec.action.action [0] .red2yellow = $false

  $spec.action.action [0] .yellow2green = $false

  $spec.setting = new-Object VMware.Vim.AlarmSetting

  $spec.setting.toleranceRange = 0

  $spec.setting.reportingFrequency = 0

  _this $ = get-view-Id "AlarmManager-AlarmManager.

  # Create alarm

  _this $. CreateAlarm($entity.) MoRef, $spec)

  # Disconnect the vcenter

  Disconnect-VIServer $vc - confirm: $false

  I am now writing a block to edit the task scheduled every hour.

  -Mark

• How to disable the device Alias in the profile of the host

  Hi all

  Could someone tell me how this is acutally done, documentation VMwares seems to go in the circle on the subject:

  VMware KB: Remediation of host profile fails with an error device alias

  Apparently if you have guests who are not identical, but you still want to use the host profiles to configure items on a new host you can disable the device alias but they never say how.  The closest thing is to change the profile of the host and remove the sub profiles do not require you, I found, but it does not work.

  Any help with this would be greatly affect.

  Thanks again,

  Thought that it

  Just wrap everyone is facing it:

  

  Simply remove the Alias Configuration of device in the profile of the host and this error will disappear.  Yet only once if your hosts are not exactly the same.

• See the profile of the host Application

  I just want to check that vCenter 5.1 (b) Auto deploy does not apply the profile of the host, he attaches it only. I understand that IP address entry/configuration is necessary when the profile of the host application, but I was wondering if it was possible to automate even that. I can't think how that would be accomplished but thought that I would check to see if anyone had discovered some creative automation.

  As long as the profiles of the host requires any input it will not apply and ESXi will remain in maintenance mode.

  Here's what you need: http://blogs.vmware.com/vsphere/2011/09/sample-scripts-for-automating-auto-deploy.html. I use the ad - update.ps1 a script pre fill the host profiles answer file and it really works.

  MAC addresses will be automatically generated if it is not specified.

  -ep4p

• Profiles of the host and ESX

  I wonder if the host profiles can be used to create user accounts in the ESX Server service console?

  Thank you

  Hello

  No problem. Here is your answer. Glad it helps!

  Best regards

  Edward L. Haletky

  Host communities, VMware vExpert,

  Author: VMware vSphere and Virtual Infrastructure Security,VMware ESX and ESXi in the 2nd business edition (c to mid-January)

  Podcast: the Podcast for security virtualization of resources: the virtual virtualization library

• Profiles of the host cannot create, license error.

  I tried to right click on a host, or just create a new profile and select a host and I get the same rror.

  License not available to perform the operation.

  The Vsphere 4 enterprise license for host XXXXX does not include profiles of the host.  Update the license.

  Then it is said in the recent tasks: license not available to perform the operation?

  I thought that the enterprise license came with host profiles?  I didn't liked company was necessary.

  You must have Enterprise more than license for the host profiles

  http://KB.VMware.com/kb/1010579

• ESXi host profile

  Greetings,

  I'm currently upgrading my 5.1 to 5.5 however ESXi hosts, it is not a rhythm in upgrade more as a new installation since I'm changing some resources on my servers. I create a profile of the host of one of my hosts, but my question is, can I still use the host profile Version 5.1 on version 5.5 hosts?

  Thank you!

  Yes, you can and it works perfectly.  However, if you have any questions you should carefully test this.

• "General system error" when you try to create a host profile

  I have a cluster including 3 ESXi 5.5 knots. I'm trying to implement the compliance of the profile on this cluster, but I am not able to generate the host profile, use one of the nodes in the reference host.

  The error on nodes 1 and 2 is:

  A general error occurred:

  Call "HostProfileManager.CreateProfile" to "HostProfileManager" object on the server vCenter Server '< vcenter server >' failed.

  The error on node 3 is slightly different:

  A general error occurred:

  Call "HostProfileManager.CreateProfile" to "HostProfileManager" object on the server vCenter Server '< vcenter server >' failed.

  Specified value is out of range. Range: 1 to 256

  Specified value is out of range. Range: 0 to 16

  Specified value is out of range. Range: 1 to 256

  Specified value is out of range. Range: 0 to 16

  Specified value is out of range. Range: 1 to 256

  Specified value is out of range. Range: 0 to 16

  Specified value is out of range. Range: 1 to 256

  Specified value is out of range. Range: 0 to 16

  Specified value is out of range. Range: 1 to 256

  Specified value is out of range. Range: 0 to 16

  Specified value is out of range. Range: 1 to 256

  Specified value is out of range. Range: 0 to 16

  Specified value is out of range. Range: 1 to 256

  Specified value is out of range. Range: 0 to 16

  Specified value is out of range. Range: 1 to 256

  Specified value is out of range. Range: 0 to 16

  Specified value is out of range. Range: 1 to 256

  Specified value is out of range. Range: 0 to 16

  Specified value is out of range. Range: 1 to 256

  Specified value is out of range. Range: 1 to 256

  Specified value is out of range. Range: 0 to 16

  Specified value is out of range. Range: 1 to 256

  Specified value is out of range. Range: 0 to 16

  Specified value is out of range. Range: 1 to 256

  Specified value is out of range. Range: 0 to 16

  Specified value is out of range. Range: 1 to 256

  Specified value is out of range. Range: 0 to 16

  Specified value is out of range. Range: 1 to 256

  Specified value is out of range. Range: 0 to 16

  Specified value is out of range. Range: 1 to 256

  Specified value is out of range. Range: 0 to 16

  Specified value is out of range. Range: 1 to 256

  Specified value is out of range. Range: 0 to 16

  Specified value is out of range. Range: 1 to 256

  Specified value is out of range. Range: 1 to 256

  Specified value is out of range. Range: 0 to 16

  Specified value is out of range. Range: 1 to 256

  Specified value is out of range. Range: 0 to 16

  Specified value is out of range. Range: 1 to 256

  Specified value is out of range. Range: 1 to 256

  Specified value is out of range. Range: 0 to 16

  Anyone has an idea why I am unable to generate these profiles? I added the other stand-alone hosts (in other data centers) to test and I am able to generate profiles of those without problem. I tried to take one of the above 3 nodes in the cluster to generate the profile, but I got the same errors as above.

  I was getting exactly the same problem in my environment who you are. Here's a knockout that help me solve the problem.

  http://KB.VMware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalID=2065692

• Help with Host Profiles and necessary PowerCLI

  Hello

  I have 2 questions about using PowerCLI for edit vSphere Host Profiles:

  (1) how can I clone a host profile, using PowerCLI?

  (2) how can I change the host profiles, using PowerCLI, update these settings?
  (a) name of host - DNS configuration - configuration networking
  (b) setting up authentication - setup of Active Directory - domain name

  
  Thank you!

  Kind regards
  Harold

  (1) there, in the current version no cmldets to clone a hostprofile.

  But you can use the API. Something like that

  $hostProfileName = "MyProfile" $prof = Get-VMHostProfile -Name $hostProfileName 
  
  $profMgr = Get-View HostProfileManager
  $spec = New-Object VMware.Vim.HostProfileCompleteConfigSpec $spec.Annotation = $prof.ExtensionData.Config.Annotation$spec.ApplyProfile = $prof.ExtensionData.Config.ApplyProfile$spec.CustomComplyProfile = $prof.ExtensionData.Config.CustomComplyProfile$spec.DisabledExpressionList = $prof.ExtensionData.Config.DisabledExpressionList$spec.Enabled = $prof.ExtensionData.Config.Enabled$spec.Name = $prof.ExtensionData.Config.Name + " - COPY"
  $profMgr.CreateProfile($spec)
  

  (2) changing the settings in hostprofiles can be done, but the ILO requires a thorough knowledge of the workings of

  See for example my change of the root password in host and profiles of the host .

• ESX to ESXi using host profiles

  I was wondering if anyone has tried to use the host profiles to facilitate the migration?

  That is to say take a profile of a host ESX and then install ESXi and then apply the profile of the host that you just do to this host?

  I think it should work.

  Stephen

  Note also that Host profile does not apply tweaks, like frames.

  And that vSphere 5 you can upgrade an ESX 4.x (but it have a previous update to 3.x) to ESXi 5 with most of its parameters

  André

• Host profiles

  Hello

  are host profiles associated with specific licenses for vSphere? It includes with vSphere advanced?

  also, I sow a demo configuration setting profile such as firewalls, host and telnet host, how can I do

  Is a one-stop shop with all of the same parameters as this configuration on a host directly not through profile host

  host profiles?

  Profiles of the host is a characteristic of the level Enterprise Plus license - http://www.vmware.com/products/vsphere/buy/editions_comparison.html.

  Most of the options that you configure in the host profiles comes the various screens in the Configuration screen.  There is not just a window that exposes all of the options that you can configure.

• Active Directory authentication via host profile

  I am trying to use apply a profile host through powershell script that will add an esxi host to my domain active directory.

  $vCenter = Read-Host "Enter vCenter.

  $esxhost = Read-Host "enter the domain the ESXi host's FULL name.

  $ADdomaincreds = $host.ui.PromptForCredential ("Enter Credentials", "Please enter your user name Active Directory and password.", "", "")

  $hostprofile = Read-Host "Enter HostProfile to apply"

  SECURESTRING #CONVERT

  $CONVERT_AD_PASSWORD = http://System.Runtime.InteropServices.Marshal: SecureStringToBSTR($ADdomaincreds.Password)

  $AD_PASSWORD = http://System.Runtime.InteropServices.Marshal: name ($CONVERT_AD_PASSWORD)

  SE connect-VIServer $vCenter

  $hostprof = get-VMHostprofile-name $hostprofile

  $applyhost = get-VMHost $esxhost

  Game-VMHost - VMHost $applyhost - State "maintenance".

  $additionalConfiguration = apply-VMHostProfile - ApplyOnly - $hostprof profile-entity $applyhost - confirm: $false

  $additionalConfiguration = $ADdomaincreds.username

  $additionalConfiguration = $AD_PASSWORD

  $additionalConfiguration = apply VMHostProfile - $hostprof profile-entity $applyhost - Variable $additionalConfiguration - confirm: $false

  It runs without error, but when I look at the esxi host he always says that he uses local authentication.  If I apply the host through the VI Client profile, it works without problem. Is this what I need to put in the variable?

  I also tried using the Set-VMHostADDomain of LucD function.  This works, however, if I then apply the profile of my host to complete the configuration of the other components such as syslog, ntp, etc., authentication gets restore local authentication after a reboot.

  Hello

  There is a bug in the Apply-VMHostProfile cmdlet that is already filed in our bugtracking system. The fix will be available in a future release.

  The problem is caused by using an incorrect version of the API (4.0) which is not taken in charge of operations active directory.

  Here are possible solutions:

  1. join the domain without using the host profile feature. Here's a simple script that can do for you:

  function JoinDomainWithAD ($vmhost, $domainName, $domainUser, $domainPassword) {
     $vmhostView = Get-View -id $vmhost.ID
     $authenticationManagerView = Get-View $vmhostView.ConfigManager.AuthenticationManager
     $hostActiveDirectoryAuthenticationMoRef = $authenticationManagerView.SupportedStore | where { $_.Type -eq 'HostActiveDirectoryAuthentication' }
     $hostActiveDirectoryAuthentication = Get-View $hostActiveDirectoryAuthenticationMoRef
     $hostActiveDirectoryAuthentication.JoinDomain($domainName, $domainUser, $domainPassword)
  }
  

  2. apply the solution profiles host with direct API calls (Get-View)

  Let me know if you need anything that anyone else.

  Kind regards

  Nedko Nedev

  PowerCLI development team