Access Proxmox Virtual Environment for PDS Server Management

draft · procedures virtualizationsetup-procedure

Generated by docuprocessor (prompt article/v3) · 2026-04-22 13:39

Source thread

thread_id: spaces/AAAA05BdS6s/threads/DDsHCkkznVg · 7 msgs · first 2024-11-26 · participants: Tech A

Tech A 2024-11-26 19:42

@all Guys, a reminder about the PDS setup: all of the RDS servers are VMs running on Proxmox VE (virtual enviroment). I've created an article and posted it here not long ago on how to access the proxmox servers. Here is a recap: thisis the info on idrac IPs, IPs, location of the VMs. https://docs.google.com/spreadsheets/d/1Gozk0rbBgytQWVANx76xBxldtmHnJdAsmz-91G2JHGI/edit?usp=sharing

application/vnd.google-apps.spreadsheet PDS Colocation IP info

Tech A 2024-11-26 19:44

and here is the KB on how to access the Proxmox servers in case your Windows is frozen https://docs.google.com/document/d/1EBNX8Wgy4mnB0c-1v1sdKEcpZxxhUwwgfoQKqTQX98c/edit?usp=sharing

application/vnd.google-apps.document Proxmox access for the PDS servers

Tech A 2024-11-26 19:45

each VM in LMI has the name of the physical server attached to it

image/png image.png

The image shows a network management console displaying search results for "pds 365" across 18 computers in an "All Field" category. All listed machines display a red exclamation point (!) alert indicator, suggesting an active alert or error state on each device. The listed hostnames include servers such as DB01, DB02, DC01, DENTRIX TEST (vmhost6), DOLPHIN, GW01 (GATEWAY), IMG01, NAS01 (BACKUPS), RDS05–RDS12, TS01, and VMHOST01, all under the domain **pdsmgmt.local**, with several entries noted as running on vmhost4, vmhost5, or vmhost6.

Tech A 2024-11-26 19:45

in case there is no name, it means the server is a physical device

Tech A 2024-11-26 19:46

Dolphin is an exception but its in a process of migrating to the proxmox VE as well

Tech A 2024-11-26 19:57

@all also, for ease of use, I've added shortcuts to all Proxmox server consoles from the NAS01 server

image/png image.png

**Browser displaying Proxmox Virtual Environment 8.2.4** at IP address `172.17.200.4:8006`. The browser shows a **"Not secure"** warning (HTTPS with certificate error). Browser bookmarks show multiple Proxmox nodes: **vmhost2, vmhost3, vmhost4, vmhost5, vmhost6, VMH3, and TS01**. The URL fragment indicates navigation to a QEMU VM resource (`#v1:0:=qemu%2F104:4::::::`).

Tech A 2024-11-26 19:58

its in Chrome

---
title: "Access Proxmox Virtual Environment for PDS Server Management"
category: procedures
tags: ["virtualization", "setup-procedure"]
source_thread_id: "spaces/AAAA05BdS6s/threads/DDsHCkkznVg"
source_space: "spaces/AAAA05BdS6s"
generated_at: "2026-04-22T13:39:18"
participants: ["Tech A"]
---

# Access Proxmox Virtual Environment for PDS Server Management

## Problem
PDS RDS servers run as virtual machines on Proxmox Virtual Environment infrastructure. Technicians need to access Proxmox consoles for VM management when Windows systems are frozen or unresponsive. The virtual machines are distributed across multiple Proxmox hosts (vmhost2, vmhost3, vmhost4, vmhost5, vmhost6, VMH3, and TS01) and require direct console access for troubleshooting.

## Resolution
1. Access the NAS01 server to use pre-configured Proxmox shortcuts
2. Open Chrome browser on NAS01
3. Use the bookmarked shortcuts for each Proxmox node:
   - vmhost2
   - vmhost3  
   - vmhost4
   - vmhost5
   - vmhost6
   - VMH3
   - TS01
4. Navigate to the appropriate Proxmox host based on VM location (check the Google Sheets reference for VM-to-host mapping)
5. Access the Proxmox Virtual Environment console at the respective IP addresses on port 8006
6. Identify VMs by checking the hostname suffix in LogMeIn - VMs display the physical host name (e.g., "vmhost6" appended to the server name)
7. Note: Servers without host name suffixes in LogMeIn are physical devices, not VMs
8. Exception: DOLPHIN server is currently physical but scheduled for migration to Proxmox VE

## References
- Source discussion: `spaces/AAAA05BdS6s/threads/DDsHCkkznVg`
- Attachments:
  - ![image.png](../attachments/DDsHCkkznVg.7LvbMyq8zuU/image.png) — **Browser displaying Proxmox Virtual Environment 8.2.4** at IP address `172.17.200.4:8006`. The browser shows a **"Not secure"** warning (HTTPS with certificate error). Browser bookmarks show multiple Proxmox nodes: **vmhost2, vmhost3, vmhost4, vmhost5, vmhost6, VMH3, and TS01**. The URL fragment indicates navigation to a QEMU VM resource (`#v1:0:=qemu%2F104:4:::::::`).
  - ![PDS Colocation IP info](../attachments/DDsHCkkznVg.DDsHCkkznVg/PDS Colocation IP info)
  - ![image.png](../attachments/DDsHCkkznVg.iQdIqnZ2-Yc/image.png) — The image shows a network management console displaying search results for "pds 365" across 18 computers in an "All Field" category. All listed machines display a red exclamation point (!) alert indicator, suggesting an active alert or error state on each device. The listed hostnames include servers such as DB01, DB02, DC01, DENTRIX TEST (vmhost6), DOLPHIN, GW01 (GATEWAY), IMG01, NAS01 (BACKUPS), RDS05–RDS12, TS01, and VMHOST01, all under the domain **pdsmgmt.local**, with several entries noted as running on vmhost4, vmhost5, or vmhost6.
  - ![Proxmox access for the PDS servers](../attachments/DDsHCkkznVg.mcy7hASg52c/Proxmox access for the PDS servers)

Generated article

draft