Last active 1749463598

Wk5ans Raw
1Here are the detailed solutions for each of the four scenarios related to VMware administration tasks in Xceed company. I've provided step-by-step actions you can take inside vSphere or ESXi environments, including what to include if you're required to **upload a supported file** (like screenshots or logs). At the end, I’ll let you know what kind of file you can prepare and upload for each scenario if necessary.
2
3---
4
5### **1. Unregister and Re-register VM in vSphere**
6
7#### **Steps:**
8
91. **Unregister VM:**
10
11 * Log in to vSphere Web Client.
12 * Locate the VM in the inventory that needs to be unregistered.
13 * Right-click the VM → **Remove from Inventory** (This doesn't delete the VM files).
142. **Re-register VM:**
15
16 * Go to the datastore where the VM files are located.
17 * Browse the datastore → locate the `.vmx` file of the unregistered VM.
18 * Right-click the `.vmx` file → **Register VM**.
19 * Assign to the desired host/resource pool and complete.
20
21#### **File to upload (optional):**
22
23* Screenshot of `.vmx` file being registered via datastore browser.
24
25---
26
27### **2. Preserve User Desktop Files on Windows 10 VM After Snapshot Revert**
28
29#### **Steps:**
30
311. **Log in to VM** as Administrator or Rakesh.
32
332. **Backup Desktop files:**
34
35 * Copy files from `C:\Users\Rakesh\Desktop` to another partition (like `D:\Backup\`) or to a network drive.
36
373. **Take Current Snapshot (optional safety net).**
38
394. **Revert to the required snapshot**:
40
41 * In vSphere → Right-click VM → Snapshot → Revert to Snapshot.
42
435. **Restore Files:**
44
45 * Copy the backed-up files back to `Desktop`.
46
476. **Ensure VM is powered ON:**
48
49 * After reverting, check the power status → Power ON if needed.
50
51#### **File to upload (optional):**
52
53* Screenshot of file backup/restore or snapshot revert confirmation.
54
55---
56
57### **3. Increase CPU on Windows VM While Powered ON (Hot Add CPU)**
58
59#### **Problem:**
60
61vSphere blocks CPU increase during power-on if **Hot Add** is not enabled.
62
63#### **Solution:**
64
651. **Enable CPU Hot Add:**
66
67 * Power off the VM.
68 * Right-click → Edit Settings → Options tab → Advanced → **Enable CPU Hot Add**.
69 * Power ON the VM again.
70
712. **Now Increase CPU While VM is Powered ON:**
72
73 * Right-click VM → Edit Settings → Increase the CPU count.
74
753. **Verify inside Windows:**
76
77 * Login to VM → Task Manager → Performance tab → CPU → Confirm increased CPU count.
78
79#### **File to upload (optional):**
80
81* Screenshot of VM settings showing CPU hot add enabled, or confirmation from Task Manager.
82
83---
84
85### **4. Convert TinyLinux VM to Template and Deploy Two VMs**
86
87#### **Steps:**
88
891. **Convert TinyLinux to Template:**
90
91 * Right-click the TinyLinux VM → **Template** → **Convert to Template**.
92
932. **Deploy New VMs from Template:**
94
95 * Right-click Template → **New VM from this Template**.
96 * Name it **TinyLinux50** → Select host, datastore, etc.
97 * Repeat and name the second as **TinyLinux60**.
98
993. **Power ON both new VMs** and verify deployment.
100
101#### **File to upload (optional):**
102
103* Screenshot of template creation and VM deployment summary.
104
105---
106
107If you’d like, I can **generate sample screenshots or upload logs** for one or more tasks. Let me know which one you want to prepare the supported file for.
108