Failed to add windows 2022 vm manually

Infrastructure
,
1

Hello Expert,

I created one Windows 2022 VM in vCenter directly and then tried to add this vm to Morpheus manually.
When I added, the status is showing “available”, but after a while (2 or 3 mins), this vm will be deleted automatically.

I have disabled the firewall and started Windows Remote Management service on windows vm.

Is there any reason for this behavior? And any step I need to follow to add vm to Morpheus manually?

(actually i tested to add one CentOS vm as well but if failed with the same)

Thank you.
BR

after adding the vm, it is showing like below.

image
image1151×266 19.1 KB

After coupe of mins, it is deleted automatically.

image
image1174×200 12.1 KB

2

Hi @yingshuang try adding the vm to a cloud of type morpheus. Also could you submit this as a support case?

3

Thank you @aabraham.

I tried to add vm to a cloud of type Morpheus. this time it is not deleted automatically. but the status is showing available and power status showing question mark all the time.

Is this expected behavior?

As my understanding, at least the power and status should show green.

image
image1187×746 52.6 KB

4

@yingshuang

This is expected because we are not actually linking to any VM, rather a SSH or WinRM connection and treating it like a bare metal machine.

Really, you should be inventorying the resource pools / clusters you desire and we’ll sync all of the VM data. Otherwise, you are not going to have true life cycle management, (if you delete or power state change we’ll never make a change).

5

Hello @cbunge ,

Thank you for your explanation and understood now. But let me change my question.

Actually this is the request from one customer, they don’t want to use cloud discover capability to sync-up all the VMs at one shot, but instead they only want to add those VMs which they need to manage thru Morpheus, and meanwhile they don’t want to install Morpheus agent on them.

Is there a way to achieve this?

Thank you.

6

You’re going to have very limited, to no “management” capabilities.

You won’t have any:

  • Power controls
  • Teardown / Deletion
  • Resize capabilities
    • Add/remove disk
    • Add/remove CPU
    • Add/remove Memory
  • State Sync (Up/Down)
  • Health Statistics or Metrics
  • Guidance or Resizing Recommendations

You’ll basically only have WinRM and SSH against the box and no other functionality.

This would possibly be circumventing the licensing and our ELA.

7

hello @cbunge ,

thank you so much for your detail information and fully understood the behavior.

Thank you.

8

Hello @cbunge ,

I have one additional question about the lifecycle management for the VM which I added manually.

Lets say I manually add one VM and convert it to managed VM with agent installation. In this case, can we have below “management” capability for the VM?

  • Power controls
  • Teardown / Deletion
  • Resize capabilities
    • Add/remove disk
    • Add/remove CPU
    • Add/remove Memory
  • State Sync (Up/Down)
  • Health Statistics or Metrics
  • Guidance or Resizing Recommendations

Also, could you please explain some more about how “This would possibly be circumventing the licensing and our ELA”?

Thank you.

9
  • Power controls
    • Unsure, would have to test. I believe with proper RPC creds / Agent you can get power Operations
  • Teardown / Deletion
    • No.
  • Resize capabilities
    • No to all of these
  • State Sync (Up/Down)
    • Health will be based on Agent comms. State will be unknown most likely.
  • Health Statistics or Metrics
    • OS level health stats, yes with agent.
  • Guidance or Resizing Recommendations
    • Yes based on above health stats.

Also, I’m unsure of your current licensing model / agreement. I just wanted to highlight you may want to review if there are any definitions on cloud inventory.

10

We also have the requirement not to discovert all VMs on a vCenter in one go. We have implemented this by not globally authorising the service user used, but only on specific resources and objects. In this way, it is possible to authorise the user used in Morpheus to certain folders and thus only discover the VMs in these folders. If you want to manage a VM via Morpheus, you only have to move it in vCenter and start a sync in Morpheus.
With this solution it is also possible to reconfigure the VM, perform power controls, teardown etc. without the actual installation of the agent.

11

Yep setting with RBAC within vCenter or selecting specific Resource Pools / Clusters to sync in Morpheus are good options.