What Neo can do with HPE GreenLake
- Read each HPE device’s current support level, contract level, start and end date, and its past and future coverage
- List the servers, storage and network devices whose coverage ends in a quarter, per customer
- Add a customer’s device by serial number and product number, so HPE returns its coverage
- Read subscriptions, their tier and end date, and claim a subscription key
- Read HPE’s proactive notices about a customer’s hardware, and open an HPE support case for one
- Read locations, tags, users and roles, audit logs and reports
Each call acts in one customer tenant
An MSP workspace in HPE GreenLake holds each customer as a tenant workspace. Neo names the tenant on every call with a token HPE GreenLake issues for that tenant only. On a ticket, Neo acts only in the tenant the ticket’s company is mapped to. HPE GreenLake takes no per-customer key on the card: an API client of an MSP workspace reaches every tenant, so Neo keeps one connection and narrows each call to the mapped tenant itself. Keep each customer’s devices in your workspace or in that customer’s tenant workspace.Your tenants are mapped to companies
Neo matches your HPE GreenLake tenant workspaces to the companies in your PSA and keeps the mapping on the card’s Organization Mapping tab, refreshed on each PSA metadata sync. An exact name that matches exactly one of your PSA companies, or a match you confirm, is handed straight to your agents. Every other match waits for you on the Organization Mapping tab. A mapping you set by hand survives every later sync. See HPE GreenLake API for the permission groups.Next steps
Connect HPE GreenLake
Create an API client and save it in Neo.