A logistics company keeps automation on a Windows host and wants a PowerShell session to list Intersight server profiles, with no agent installed on the servers. Which tool matches that host?
Select an answer to reveal the explanation.
Short Explanation
This job lives on the Windows desk the operator already uses. You open a PowerShell session there and use the Intersight module to list server profiles, with no agent on the servers. A leaf Python shell or a first-boot script is not that Windows session.
Full Explanation
Cisco publishes a PowerShell module that talks to Intersight from a Windows host. The session authenticates to the Intersight API and can list server profiles without installing an agent on the servers or on a fabric interconnect. That matches the logistics host and the no-agent requirement. The Python interpreter on a Nexus switch is an on-box tool for that switch's CLI and files. Server profiles are not stored in a leaf's running configuration. POAP runs when a switch boots without a startup configuration and is looking for an initial script. It is not a Windows session, and it is not the way an operator lists Intersight profiles. Guest shell is a Linux environment on a switch, including an MDS if that platform has it enabled. It is not the Intersight profile database, and a SAN switch does not become the compute profile store. Caveat: the PowerShell session still needs an API key or user credentials that are allowed to read those profiles, or the module connects and the list stays empty. Operational check: from the Windows host, connect with the Intersight module and list the server profiles, and confirm no agent process was installed on the servers to do it.