Questo sito utilizza cookie di profilazione (propri e di terze parti) per ottimizzare la tua esperienza online e per inviarti pubblicità in linea con le tue preferenze. Continuando a utilizzare questo sito senza modificare le tue preferenze acconsenti all’uso dei cookie. Se vuoi saperne di più o negare il consenso a tutti o ad alcuni cookie clicca qui>
The website that you are visiting also provides Arabian language. Do you wish to switch language version?
يوفر موقع الويب الذي تزوره المحتوى باللغة العربية أيضًا. هل ترغب في تبديل إصدار اللغة؟
The website that you are visiting also provides Russia language Do you wish to switch language version?
Данный сайт есть в английской версии. Желаете ли Вы перейти на английскую версию?
The customer created some full-copy VMs ,and the assigned them to multi users before, but one day when they try to add other users to the VM,it failed.
The task failed with the alarm like below:
1: We checked the AD service status and the communication between ITA and AD, both are normal;
2:During the VM assignment process, ITA will communicate with the VM through winrm service, so we login the VM by VNC, and check the winrm service, it is running;
3:But when we run the command " netstat -aon|find "5985" ",the result is empty,this means the winrm service is not listening on the port 5985,so ITA will fail to communicate with the VM through winrm,and the assignment task will fail.
4:Manually create the winrm listener by the command "winrm quickconfig",then the issue can be resolved.
1: The direct root cause is the winrm service was not listening on the port 5985,but this shouldn't happen internally with the user VM, also the customer feedback they didn't face any issue before ,so there must be something changed in the environment.
2: We ask the customer what has been changed for these VMs which facing the assignment issue, the customer feedback the OU had been changed.
3:We collect the GPO details of two VMs,one VM in the old OU without the assignment issue, another VM in the new OU with the assignment issue happening.
Then we find there is difference:
For the VM in the old OU without the assignment issue, there are many denied GPOs as below screenshot:
But for the VM in the new OU with the assignment issue happening, there is no denied GPOs:
4:It means there is some GPO blocked the winrm listener in the new OU ,so the VM assignment task failed.
5:Then we ask the customer to move the VM from new OU back to the old OU or deny the same GPOs as old OU, the issue resolved.
Manually create the winrm listener by the command "winrm quickconfig", or ask the customer to deny the GPO which will block the winrm service listener .
For VM provisioning or assignment issue, must make sure the winrm service is running properly.