The Managed Object Browser, commonly abbreviated as MOB, is a web-based interface used with VMware vSphere to inspect the live object model exposed by ESXi and vCenter Server. Instead of interacting with infrastructure only through the standard vSphere Client, administrators and developers can use the Managed Object Browser to navigate managed objects, inspect their properties, view relationships, and, where authorized, invoke methods.
The interface is particularly useful for troubleshooting and understanding the APIs behind VMware infrastructure. It is also more powerful than its name suggests. VMware’s documentation explicitly notes that MOB is not strictly read-only: methods exposed through the interface can make changes on the server.
That capability explains both its value to infrastructure engineers and the security controls increasingly placed around it.
What Is the Managed Object Browser?
The Managed Object Browser is a browser-accessible interface that exposes VMware’s managed-object model.
In vSphere, infrastructure resources are represented as objects with properties, identifiers, relationships, and methods. These can include virtual machines, hosts, datastores, networks, resource pools, managers, and other components.
MOB presents these objects in a navigable format.
A simplified model looks like this:
Web browser → MOB → Managed object → Properties / References / Methods
VMware documentation describes MOB as a web application that lets users examine objects on the server and navigate through the hierarchy of live objects. It populates the interface with actual runtime information rather than only static documentation.
This makes it valuable when the graphical interface does not expose enough detail for a technical investigation.
What Is a VMware Managed Object?
A managed object is an object exposed through VMware’s management infrastructure.
For an administrator, a virtual machine may simply appear as a VM named “Production-Web-01.” Internally, however, the VM has a specific managed-object representation containing references, runtime properties, configuration data, and methods.
The same principle applies to other resources.
A managed object can be thought of as a combination of:
- Identity
- Properties
- References to other objects
- Runtime state
- Methods
The Managed Object Browser provides a way to inspect these structures directly.
This is particularly valuable to developers because automation tools eventually interact with the same underlying management model.
What Can You Do With the Managed Object Browser?
The main purpose of MOB is low-level inspection and API exploration.
Depending on the VMware product and version, users can navigate objects and inspect information such as:
- Managed object references
- Object types
- Runtime properties
- Configuration information
- Relationships between objects
- Available methods
- Task-related information
For example, an engineer troubleshooting a virtual machine may need to determine which network backing is actually associated with it, inspect a particular object reference, or understand the properties returned by a vSphere API.
MOB can expose information that is not always obvious in the normal UI.
Is the Managed Object Browser Read-Only?

No.
This is one of the most important points to understand before using Managed Object Browser.
VMware’s own documentation states that, despite the word “browser,” MOB is not a read-only mechanism. The interface can expose an InvokeMethod action for managed-object methods, and invoking those methods can modify the server.
This means an administrator should not treat /mob as an ordinary information webpage.
It is better understood as a technical administrative interface with both inspection and action capabilities.
For that reason, experimentation should be performed carefully and only with appropriate privileges.
How Do You Access the Managed Object Browser?
When enabled, the traditional MOB endpoint is available through a URL such as:
text
CopyEdit
The exact behavior depends on whether the request is going to vCenter Server or directly to an ESXi host, as well as the specific vSphere version and configuration.
A user who enters the /mob path and receives an error should not automatically assume the service is broken.
In newer environments, disabling MOB is often intentional.
Why Is the Managed Object Browser Disabled?
Security is the primary reason.
Broadcom’s current VMware documentation states that the Managed Object Browser is disabled by default on ESXi starting with vSphere 6.0 to reduce the risk of malicious configuration changes or actions.
This is a logical security control because MOB exposes internal infrastructure objects and, in appropriate contexts, methods capable of making changes.
A publicly reachable management interface creates an additional attack surface. Even if authentication is required, organizations generally prefer to minimize unnecessary administrative endpoints.
The security principle is straightforward:
If a privileged interface is not required, do not expose it.
What Happened to MOB in vSphere 9?
The trend toward tighter security has continued.
Broadcom’s August 2026 knowledge-base documentation states that the vCenter Managed Object Browser is deactivated by default in VMware Cloud Foundation 9.0 to comply with Security Technical Implementation Guide requirements.
Administrators upgrading to current environments may therefore find that a previously familiar /mob URL no longer works.
The resulting page can explicitly report:
The MOB is disabled.
This should be treated as expected behavior rather than evidence of an application failure.
Why Does /mob Sometimes Return 503?
A 503 Service Unavailable response is another documented MOB issue.
Broadcom has published guidance for vCenter Server 7.x and 8.x showing that /mob can return 503 Service Unavailable or no healthy upstream when the enableDebugBrowse parameter in vpxd.cfg is disabled.
In other words, the vCenter services themselves can be operational while the MOB endpoint remains unavailable.
Administrators troubleshooting the problem should first identify the vCenter version and determine whether MOB has intentionally been disabled before changing configuration.
Why Does /mob Return 401?
A 401 Unauthorized response can have several causes.
One documented situation involves browser authentication policy.
Broadcom describes an issue where Chrome or Edge can return HTTP 401 when browser security settings prevent the Basic Authentication mechanism used by vCenter MOB.
That means a 401 response does not automatically indicate invalid credentials.
The investigation should consider both the VMware configuration and the client environment.
Managed Object Browser and API Development
MOB is particularly useful for engineers who work with the vSphere API.
The interface can help developers understand how a live environment represents objects rather than relying exclusively on abstract documentation.
A developer might use MOB to discover:
What is the managed object reference?
Which properties are available?
What related objects does this object expose?
What methods are associated with it?
The developer can then use that understanding when writing automation through supported SDKs, PowerCLI, or other API clients.
This makes MOB valuable as an exploratory tool even when it is not the preferred mechanism for long-term automation.
Managed Object Browser vs vSphere Client
The standard vSphere Client and MOB solve different problems.
| Capability | vSphere Client | Managed Object Browser |
| Routine administration | Excellent | Limited use |
| User-friendly interface | Yes | No |
| Object-model visibility | Moderate | High |
| Runtime properties | Selected | Extensive |
| API exploration | Indirect | Strong |
| Low-level methods | Abstracted | Exposed |
| Automation | Limited | Not the ideal tool |
| Risk of accidental changes | Lower | Higher |
The vSphere Client is built for administrators operating infrastructure through a supported graphical workflow.
MOB is closer to the underlying management model.
That makes MOB useful when the normal interface becomes too abstract, but it also means the engineer needs a better understanding of what a particular property or method actually represents.
Why Can MOB and the vSphere Client Show Different Information?
An apparent difference between the two interfaces does not necessarily indicate an error.
Broadcom has documented a specific example involving virtual machine networking in vCenter Server 7.x and 8.x. The vSphere Client enumerates individual virtual hardware devices, while MOB can display unique logical network backings. If multiple virtual NICs use the same port group, the two interfaces may therefore show different counts.
This is a useful lesson when interpreting MOB data:
Different representations can still describe the same underlying environment.
Engineers should first determine what level of abstraction each interface uses before comparing values.
Managed Object Browser and MOIDs
Another reason administrators use MOB is to inspect Managed Object IDs, commonly called MOIDs.
A MOID identifies a managed object within the relevant VMware environment.
For example, a virtual machine or datastore may have an internal managed reference that looks different from the human-readable display name shown in the vSphere Client.
This distinction matters for scripting and troubleshooting because names can change or duplicate, while the managed object reference is part of the API-oriented identity of the object.
MOB can therefore help bridge the gap between what an administrator sees and what automation tools operate on.
Is MOB Suitable for Production Automation?
Generally, no.
The Managed Object Browser is better suited to inspection, debugging, and understanding the object model than to repeatable production automation.
Production automation benefits from interfaces and workflows that can be:
- Version controlled
- Tested
- Reviewed
- Logged
- Reproduced
- Integrated with existing tooling
PowerCLI, VMware SDKs, REST APIs, and infrastructure automation platforms are usually more appropriate for those requirements.
A useful workflow is:
Explore with MOB → Understand the object → Automate with an API or scripting tool
That approach separates investigation from production operations.
Should You Enable MOB on a Production Environment?
Only when there is a defined reason.
CIS-oriented VMware security guidance recommends disabling MOB as a hardening measure, and notes that the interface can expose information and configuration capabilities that increase risk.
There can also be operational dependencies. Some third-party tools may rely on MOB, so disabling it should be assessed against the environment before making changes.
For environments that genuinely require MOB temporarily, access should be tightly restricted and the configuration should be returned to the desired security state after the task is completed.
A Practical MOB Troubleshooting Workflow
When the Managed Object Browser is unavailable, use a version-aware workflow.
Step 1: Identify the platform
Determine whether you are accessing ESXi, vCenter Server, or a VMware Cloud Foundation deployment.
Step 2: Determine the version
MOB behavior and defaults have changed across vSphere releases.
Step 3: Check whether MOB is intentionally disabled
A disabled endpoint may be a security control rather than an outage.
Step 4: Check the actual error
401, 503, no healthy upstream, and “MOB is disabled” point toward different areas of investigation.
Step 5: Review configuration carefully
For vCenter Server, Broadcom documents enableDebugBrowse as a relevant setting for MOB availability in certain releases.
Step 6: Consider browser authentication
A browser policy can affect authentication behavior independently of the VMware configuration.
This process is safer than blindly changing configuration files.
Managed Object Browser Security Best Practices
For infrastructure teams, several principles make MOB safer to operate.
Restrict network access.
Administrative interfaces should be available only from trusted management networks.
Use least privilege.
Grant the minimum permissions required for the diagnostic or operational task.
Avoid permanent enablement.
If MOB is needed temporarily, treat it as a controlled exception.
Document configuration changes.
Record who enabled the interface, why it was required, and when it was returned to the secure state.
Prefer supported automation interfaces.
Use MOB for exploration rather than building critical operational processes around manual browser interactions.
Final Takeaway
The Managed Object Browser is a powerful low-level interface into VMware’s vSphere object model. It allows administrators and developers to inspect live managed objects, understand runtime properties and references, and investigate behavior that may not be visible through the standard vSphere Client.
Its usefulness is balanced by its security implications. MOB is not purely read-only, and VMware has increasingly disabled it by default. On ESXi, the default-disabled behavior dates back to vSphere 6.0, while current VMware Cloud Foundation 9.x environments also disable vCenter MOB by default under security-oriented configurations.
For developers and infrastructure engineers, the best role for the Managed Object Browser is therefore as a diagnostic and exploration tool. Use it to understand the object model, identify managed references, and investigate complex behavior, then move repeatable production operations into supported APIs and automation tooling.
FAQ
1.What is the Managed Object Browser?
The Managed Object Browser, or MOB, is a web-based VMware interface that allows administrators and developers to inspect live vSphere managed objects and navigate their object relationships.
2.Is the Managed Object Browser read-only?
No. VMware documents that MOB can expose methods that may change server state when invoked.
3.Why is Managed Object Browser disabled?
VMware has disabled MOB by default in modern environments as a security measure because the interface can expose information and operational capabilities.
4.What does a 503 error on /mob mean?
For certain vCenter Server 7.x and 8.x configurations, Broadcom documents that a disabled enableDebugBrowse setting can cause /mob to return 503 Service Unavailable or no healthy upstream.
5.Is Managed Object Browser available in VMware Cloud Foundation 9?
Broadcom states that vCenter MOB is deactivated by default in VMware Cloud Foundation 9.0 as part of its security configuration.
6.Should MOB remain enabled?
It generally should not remain enabled without a clear operational requirement. Organizations should follow their security baseline and disable unnecessary administrative endpoints.
About the Author
Erika Balla is a Content Specialist at The Data Scientist and the founder of QuietFluence. With over eight years of experience, she helps businesses achieve sustainable growth through data-driven marketing and strategic content.
Contact: in**@**********ce.com | er***@**************st.com
Authoritative References & Educational Resources
For foundational scientific standards and peer-reviewed specifications, consult MDN Web Standards & API Specifications and World Wide Web Consortium (W3C) Technical Standards. For related domain research on our platform, explore our guides on Aspect-Based Sentiment Analysis and Hedonic Pricing Residuals: Quantifying Unobserved Execution Covariates in PropTech Valuation and Production Mobile App Engineering Lifecycle: A Ten-Stage Architecture, Telemetry, and Release Guide.
Fractional CAIO & Strategic Board Advisory
High-level fractional guidance on AI strategy, IP monetization, and corporate AI governance.