Sometimes, using SCVMM on a new Hyper-V cluster to deploy a new VM may result in an operational timeout. This is an example:
Although the error message did not state "timeout" directly, you would see the following exact error when you execute "winrm helpmsg" on the error code given (in this example 0x80338029):
C:\> winrm helpmsg 0x80338029
The WS-Management service cannot complete the operation within the time specified in OperationTimeout.
The Hyper-V hosts may need longer time to respond to the VMM server using Windows Remote-Management (winrm). To increase the time-out period and to increase more concurrent operations that can be performed by the VMM server, execute the following commands on the affected Hyper-V hosts:
winrm set winrm/config @{MaxTimeoutms = "1800000"}
winrm set winrm/config/Service @{MaxConcurrentOperationsPerUser="400"}
net stop winrm
net start winrm
net start vmmagent
For other "Not Responding" host status issues on SCVMM 2008 R2, refer to this useful guide on Microsoft official site.
Thank you for giving the great article. It delivered me to understand several things about this concept. Keep posting such surpassing articles so that I gain from your great post.
ReplyDeleteevs full form
raw agent full form
full form of tbh in instagram
dbs bank full form
https full form
tft full form
pco full form
kra full form in hr
tbh full form in instagram story
epc full form