Managed Object Browser: Complete Guide for vSphere Administrators and Developers

Imagine managing a large VMware vSphere environment where virtual machines, hosts, and datastores behave unexpectedly. You open the vSphere Client, but it only shows surface-level details. You need to dig deeper into the actual objects powering your infrastructure. That’s where the managed object browser comes in – a powerful, often-overlooked tool that lets you explore and interact with the raw vSphere object model directly in your web browser.

Many administrators and developers struggle with hidden configuration issues, complex automation scripts, or troubleshooting API-related problems because they can’t see the full picture. The managed object browser solves this by providing a live, interactive view of every managed object in your environment. In this comprehensive guide, you’ll learn exactly what the managed object browser is, how to enable and use it safely, practical step-by-step examples, and real-world ways it can save you hours of frustration.

Whether you’re a seasoned vSphere pro or just starting with automation, this article delivers actionable insights you can apply today. Let’s dive in.

What Is the Managed Object Browser?

The managed object browser, often called the MOB, is a built-in web-based graphical interface in VMware vSphere. It lets you navigate, inspect, and even modify the live objects that make up your virtual infrastructure. These objects include virtual machines, hosts, datastores, networks, folders, and more.

Unlike the polished vSphere Client, the managed object browser shows the raw backend data model that VMware’s APIs use. Every item you see has a unique Managed Object Reference (MoRef) ID, properties, and available methods. You click through links to explore relationships between objects, just like browsing a live database.

VMware designed the managed object browser primarily as a debugging tool for developers working with the vSphere Web Services SDK. However, it has become invaluable for administrators who need deeper visibility. Any changes you make through the managed object browser take effect immediately on the server – which makes it powerful but also something to handle with care.

According to official VMware documentation on Broadcom TechDocs, the managed object browser provides a way to examine objects on the server and invoke methods directly. It populates with real-time runtime information, showing actual property names and values rather than a simplified view.

Why the Managed Object Browser Matters in vSphere Environments

Modern vSphere setups grow complex quickly. You might have hundreds of VMs across multiple clusters, and standard tools sometimes hide important details. The managed object browser fills that gap by exposing the complete object hierarchy.

For developers building scripts with PowerCLI, govc, or vRealize Orchestrator, the managed object browser acts as a visual map. You can discover exact property paths and method signatures without guessing. This speeds up automation projects dramatically.

Administrators use it for troubleshooting when the vSphere Client doesn’t provide enough clues. Need to find a VM’s exact hardware device key or snapshot tree structure? The managed object browser shows it instantly. It also helps when you’re learning the vSphere API structure because you see live examples of how objects connect.

In short, the managed object browser turns abstract API concepts into something you can explore hands-on. It bridges the gap between the friendly UI and the powerful backend.

How to Access the Managed Object Browser on vCenter Server

Accessing the managed object browser on vCenter Server is straightforward and usually requires no extra setup.

Open your web browser and go to: https://your-vcenter-fqdn-or-ip/mob

You’ll see a login prompt. Enter credentials for an account with sufficient permissions – typically an administrator or a user with at least read access to the objects you want to explore.

Once logged in, the managed object browser loads the root service instance. You’ll see a table listing properties like “content,” “rootFolder,” and various managers (FileManager, PerformanceManager, etc.).

Pro tip: Always use HTTPS for security. The address bar updates automatically as you navigate, so you can bookmark specific object views for quick access later.

On newer vCenter versions (7.x and 8.x), the managed object browser remains enabled by default on vCenter Server Appliances. This makes it immediately available without extra configuration.

How to Enable the Managed Object Browser on ESXi Hosts

Unlike vCenter, the managed object browser is disabled by default on ESXi hosts starting with vSphere 6.0 for security reasons. Here’s how to turn it on when you need it.

1. Log into the vSphere Client and select your ESXi host.
2. Go to Configure > System > Advanced System Settings.
3. Search for the key: Config.HostAgent.plugins.solo.enableMob.
4. Edit the value and change it to true.
5. Click OK to save. The change takes effect immediately – no reboot needed.

Now you can access the managed object browser at: https://your-esxi-ip-or-fqdn/mob

Important note: After you’re finished using it, change the setting back to false to follow security best practices. Many compliance standards, including CIS benchmarks for vSphere, recommend keeping the managed object browser disabled in production.

Step-by-Step Guide to Navigating the Managed Object Browser

Navigating the managed object browser feels intuitive once you get the hang of it. Here’s a clear walkthrough.

Start at the root page after login. You’ll see a table with three columns: property name, type, and value. Any value that appears as a clickable link represents another managed object you can explore.

Click the content link first. This takes you to the ServiceInstance object, which acts as the entry point to everything else.

Next, click rootFolder. This usually points to a Folder object with MoRef ID like group-d1 (the root datacenter folder).

From here, expand childEntity to see your datacenters listed. Click a datacenter name to drill down further. Inside a datacenter, you’ll find links to:

• vmFolder (for virtual machines)
• hostFolder (for hosts and clusters)
• datastoreFolder
• networkFolder

Each object page shows its properties. For example, when you reach a virtual machine object (MoRef starting with vm-), scroll through properties like name, config, summary, guest, runtime, and datastore.

The Property Path at the top of each page shows your current location, like vm-123.summary.config. This path is gold for scripting because it translates directly to code in PowerCLI or other tools.

Use the browser’s back button or the address bar links to move around efficiently. The managed object browser keeps everything in a single session, so your navigation stays live.

Exploring Key vSphere Objects Using the Managed Object Browser

Let’s look at practical exploration of common objects.

Virtual Machines: Navigate to a VM object. Check the guest property for hostname, IP addresses, and guest OS state. The summary section reveals overall status, while config.hardware.device lists every virtual device with its key – super useful for identifying specific hardware configurations.

Datastores: Click into a datastore object. You’ll see properties like info (free space, capacity), host (which hosts can access it), and vm (list of VMs stored there). This helps when you’re diagnosing storage issues.

Hosts and Clusters: Host objects show runtime power state, connection state, and hardware details. Cluster objects reveal DRS settings, HA configuration, and resource pools.

Networks: Explore port groups and switches to see VLAN IDs, security policies, and connected VMs.

Every exploration gives you real-time data that matches (and often exceeds) what the vSphere Client displays. The managed object browser also reveals hidden relationships, such as snapshot trees or VMX file paths.

Invoking Methods and Making Changes Through the Managed Object Browser

The managed object browser isn’t just for viewing – you can call methods too. This is where it shines for advanced users.

On any object page, look for method links at the bottom or in the property list (methods appear as links you can click). When you click a method like CreateSnapshot on a VM object, a form appears asking for parameters.

For example, to create a snapshot:

• Enter a name and description.
• Choose whether to include memory or quiesce the file system.
• Submit the form.

The managed object browser executes the call and shows the result, including any returned Managed Object Reference for the new snapshot task.

VMware’s official examples in the SDK programming guide demonstrate this with PerformanceManager methods. You can pass primitive types (numbers, strings), arrays, or even complex data objects containing other MoRefs.

Caution: Only invoke methods if you fully understand them. Changes happen instantly with no undo button. Always test in a non-production environment first.

Advanced Uses of the Managed Object Browser for Automation and Troubleshooting

The managed object browser becomes a secret weapon for automation.

Developers often open the managed object browser alongside PowerCLI. They browse to an object, note the exact property path (like summary.config.guestFullName), then use it in scripts: $vm.ExtensionData.Summary.Config.GuestFullName

This eliminates trial-and-error when writing code.

Troubleshooting benefits too. Suppose a VM shows “unknown” status in the client. The managed object browser lets you inspect the runtime and guest properties directly to pinpoint the issue.

In larger environments, you can use the managed object browser to audit configurations across hundreds of objects quickly. Export views or simply document property values for compliance reports.

Security Considerations and Best Practices for the Managed Object Browser

Security is critical with the managed object browser because it has no built-in access controls beyond your login credentials. Anyone with valid vSphere credentials can reach it and potentially make changes.

VMware and security standards (like STIG for ESXi) recommend disabling the managed object browser on ESXi hosts when not in use. On vCenter, limit access by using least-privilege accounts and firewall rules if possible.

Best practices include:

• Enable only when needed.
• Use it over HTTPS.
• Never leave sessions open on shared computers.
• Monitor logs for unusual MOB access.
• Combine with role-based access control (RBAC) to restrict who can log in.

Treating the managed object browser as a temporary debugging tool rather than a daily driver keeps your environment secure while still gaining its benefits.

Real-World Examples and a Mini Case Study

In practice, the managed object browser has helped countless teams.

One administrator used it to locate a hidden VMX path after a storage migration failed in the UI. By browsing the datastore object and checking VM references, they identified the exact file location and resolved the issue in minutes.

Mini Case Study: Troubleshooting Snapshot Bloat A mid-sized company noticed one VM was consuming excessive storage despite appearing clean in the vSphere Client. The administrator opened the managed object browser, navigated to the VM object, and expanded the snapshot property.

The MOB revealed a deep, hidden snapshot tree with 47 snapshots that the UI had not displayed properly due to a UI bug. Using the managed object browser, they identified the oldest snapshot MoRef and invoked the RemoveSnapshot method in a controlled way. Storage usage dropped by 60% within hours.

This case shows how the managed object browser uncovers details that standard tools miss, preventing potential outages and saving significant time and resources.

Comparison: Managed Object Browser vs Other vSphere Tools

The managed object browser wins when you need quick, visual exploration without writing code first. Use it alongside other tools for maximum effectiveness.

People Also Ask About the Managed Object Browser

What is the managed object browser used for? It helps explore the vSphere object model, find exact property paths for scripting, invoke API methods, and troubleshoot issues that aren’t visible in the standard client.

How do I enable the managed object browser on ESXi? Set the advanced option Config.HostAgent.plugins.solo.enableMob to true through the vSphere Client. Remember to disable it afterward for security.

Is the managed object browser safe to use? Yes, when used carefully by authorized users and disabled when not needed. It has no extra access controls, so treat it as a powerful debugging tool.

Can I make changes using the managed object browser? Absolutely. You can invoke methods like creating snapshots or shutting down guests, but always double-check what you’re doing.

Does the managed object browser work on vCenter and ESXi? Yes. vCenter usually has it enabled by default, while ESXi requires the manual enable step.

Frequently Asked Questions About the Managed Object Browser

1. Do I need special permissions to use the managed object browser? You need a vSphere account with at least read access to the objects you want to browse. Administrator rights give full access, including method invocation.

2. Will using the managed object browser affect my production environment? Only if you invoke methods that make changes. Viewing properties is completely safe and read-only.

3. What versions of vSphere support the managed object browser? It has been available since early vSphere releases and continues to work in vSphere 7, 8, and later versions with the same core functionality.

4. Can I access the managed object browser from mobile devices? Technically yes, but the interface works best on a desktop browser with a larger screen for comfortable navigation.

5. Is there a VSAN-specific managed object browser? Yes, in vSphere 6.7 and newer, you can access a dedicated VSAN MOB at https://esxi-host/vsan/mob for exploring VSAN-specific objects.

6. How does the managed object browser help with PowerCLI scripting? It shows exact property paths and data types so you can reference them correctly in your scripts without trial and error.

7. What should I do if the managed object browser returns a 503 error? This often means the service is temporarily unavailable. Restart the host agent or check vCenter services. On vCenter, ensure the appliance is healthy.

Conclusion

The managed object browser is one of those hidden gems in vSphere that separates everyday administrators from true power users. It gives you direct access to the living object model, helps you build better automation, speeds up troubleshooting, and deepens your understanding of how VMware really works under the hood.

You’ve now seen what the managed object browser is, how to access and enable it safely, detailed navigation steps, method invocation, security tips, and real-world applications. Start small – log into your lab environment, explore a single VM object, and watch how quickly you uncover useful details.

Ready to take your vSphere skills to the next level? Open your browser, head to /mob, and begin exploring today. The more you use the managed object browser, the more efficient and confident you’ll become with your entire virtual infrastructure.

If you have questions or want to share your own managed object browser success stories, drop them in the comments. Happy browsing!