Capacity limits
Cloud capacity and owned servers have different limits.
Manage desktops for each client project.
Choose the location, application image and access rules each client requires. Add and remove project members from one admin view, and apply the client’s retention policy when the engagement ends.
Project teams change faster than laptops.
People join and leave client projects throughout an engagement. Each change means a laptop to image, ship, recover and wipe.
Indovance
Read the Indovance story- Before
- Citrix licensing
- Consultant dependency
- Quarter-long upgrade cycles
- After
- One desktop platform
- Run by the team
- Live in weeks
Apply each client’s requirements.
Clients can require different cloud accounts, regions, identity providers and retention rules. Set those requirements before creating desktops.
One admin viewSeats, images and access by client
Manages
Client A
Approved images
Project desktops
Access rules
Client B
Approved images
Project desktops
Access rules
- Deployment
Neverinstall Cloud, the client’s cloud account or the client’s own servers with Neverinstall Private Cloud
- Images
Approved applications maintained by your admins
- Administration
Seats, images and access by client in one view
- Capacity
Plan for the expected peak and review idle desktops
Desktops through a client project.
New project desktops
Choose the plan, region and idle behavior, assign the people, then create the desktops.
Client rules
Tag each client’s or engagement’s workspaces, and attach a policy to the tag for that client’s transfer rules.
Changing teams
Invite people, set their roles and see who is pending, active and assigned to which desktops.
Working hours
Start desktops before the working day and stop them after, so idle desktops do not run overnight.
Plan capacity and desktop cost for the project.
Cost scope
Compare contracted users, infrastructure and application licenses over the full project duration. Include peak and idle capacity.
Test project access and desktop cost.
Use one project’s roles and expected duration.
Client separation
Use accounts from two projects to test desktop, file, identity and network permissions.
For the project file
The allowed access matrix and blocked cross-project attempts.
Staffing and cost
Model project duration, contracted users, peak capacity, idle resources and licenses.
For the project file
A cost model for the expected project and staffing pattern.
Changes and closure
Add and remove users, update an image and revoke access. Check retained files and session records.
For the project file
The change results, retained-record locations and authorized reviewers.
Related
Questions from services teams.
Can each client choose its deployment and identity provider?
Yes. Run desktops in a chosen Neverinstall Cloud region, the client’s cloud account or the client’s own servers with Neverinstall Private Cloud. Federate each client’s identity provider and manage deployments from the same Console.
How are projects kept apart?
Use separate client environments with their own applications, access rules and images. Test desktop, file and network permissions with accounts from two projects.
What does a new team member need?
A supported browser or RDP client. Create the desktop from an approved image and assign project access, without shipping hardware.
Can engineers use GPU Desktops?
Yes. Size GPU resources, memory and images for their applications. Include application licenses, client support and engineering devices in the pilot.
What happens to records after the project closes?
Revoke project access and apply the client’s retention policy. Session events and any recordings remain available to authorized reviewers for the agreed period.
Who approves updates?
Agree on maintenance windows and change-approval responsibilities before rollout. Test the image update process during the pilot.
How are short projects priced?
Neverinstall Virtual Desktops is priced per contracted user, per month, with infrastructure listed separately. Compare project duration, peak users, idle capacity and application licenses when reviewing the quote.
Plan desktops for your next client project.
Tell us the user count, project duration and client requirements. We will review capacity, access and desktop costs with your team.