Quick answer
Before using client-owned virtual desktops for offshore MSP support, write your own requirements: who owns and administers sessions, what access is permitted, whether client data may be saved locally, what is logged, and how access ends. Then ask any provider to respond to each point in writing and mark unconfirmed items as such.
- Record who owns the desktop sessions, who can grant or remove access and who approves exceptions.
- Ask for controls in writing and never describe a control to clients that you have not verified.
- Plan for service disruption and exit: how staff are told, and how access is removed when someone leaves.
An MSP may want offshore staff to use a controlled desktop environment instead of copying client data locally. This article lists the questions to ask: session boundaries, access administration and operational dependencies. It does not describe any Web Design Davao arrangement beyond what has been confirmed.
An illustrative scenario
This is a hypothetical example, not a Web Design Davao client case.
Situation. An MSP wants offshore staff to use its controlled desktop environment rather than copy client data locally.
What happens. An MSP wants offshore staff to work only inside a controlled desktop environment. It writes its requirements first: who owns the sessions, what access is permitted, that no client data is saved locally, what is logged and what happens when access ends. It then asks any provider to respond to each point in writing.
Session boundaries
Establish who owns and administers the desktop sessions and who can grant or remove access. Use the session owner and permitted access fields. A client-owned environment means the client controls it. Write down who can approve exceptions and how quickly access can be removed.
Access administration
Define the local data policy, such as whether copying or saving files to the local machine is permitted, and the monitoring scope. Use the local data policy and monitoring scope fields. Do not assume a provider’s controls. Ask for them in writing and record what is confirmed and what is not. Do not describe controls to clients that you have not verified.
Operational dependencies
Plan for disruption and exit. Use the disruption plan and exit process fields. Ask what happens if the desktop service is unavailable, how staff are told and how access is removed when someone leaves the role. Keep the answers with your due diligence records.
VDI discovery checklist
Use this at the point described above. The workflow owner completes it and a named reviewer checks it. A completed row shows that the information, owner and next step are recorded; it does not prove the outcome. Keep it somewhere the team can edit, and keep it free of passwords, tokens and real client records.
Blank copy
| Session owner | Permitted access | Local data policy | Monitoring scope | Disruption plan | Exit process |
|---|---|---|---|---|---|
Illustrative completed row (hypothetical)
| Session owner | Permitted access | Local data policy | Monitoring scope | Disruption plan | Exit process |
|---|---|---|---|---|---|
| MSP operations manager | Access to named client tools only | No client data saved locally (client policy) | Session logs held by client | Plan agreed in writing | Access removed on exit |
Working through the completed row
The example records the MSP operations manager as session owner, access to named client tools only, no client data saved locally per client policy, session logs held by the client, a disruption plan agreed in writing and access removed on exit.
Common mistakes
- Assuming provider controls.
- Describing controls you have not verified.
- Having no exit step.
Questions to settle before you rely on it
- Who owns the virtual desktop session?
- What may be stored locally?
- What monitoring applies?
How you know it is complete
The checklist is complete when each field has a written answer and each unconfirmed item is marked as such. Record who reviewed it and the date.
Where you may not have the answer
A provider cannot state a control. Treat it as unconfirmed and do not rely on it. The handoff, not a guess, is the correct next step.
Your next action
Write your own requirements before speaking to any provider.
Discuss this role, required skills, working hours and review responsibilities with Web Design Davao. Outsourced staffing arrangements are agreed individually; nothing here assumes a particular service, role or timing is already available.
How Web Design Davao works
- Enquiries are generally answered within four hours during support hours (Monday to Friday, business hours), with after-hours help for emergency requests. Scope is agreed individually.
- Web Design Davao employs and manages its Davao-based staff, including HR administration and payroll, and provides them as an outsourced service to companies overseas. See how staff are managed and how staff are hired.
- The Davao office has a secure office environment, CCTV, controlled access, multiple fibre-delivered internet connections, enterprise-grade networking, a diesel backup generator with an automatic transfer switch, and an enterprise-grade UPS supporting core network equipment. Specific certifications, failover times, generator runtime and fuel duration are not stated here and should not be assumed.
Frequently asked questions
What does a client-owned virtual desktop mean?
It means the client controls the environment. Establish who owns and administers the sessions, who can grant or remove access and who can approve exceptions. Write down how quickly access can be removed, rather than assuming a provider’s controls.
What should an MSP ask about local data and monitoring?
Define the local data policy, such as whether copying or saving files to the local machine is permitted, and the monitoring scope. Ask for the provider’s controls in writing, and record what is confirmed and what is not. Do not assume.
What happens if the desktop service is unavailable or someone leaves?
Plan for disruption and exit. Ask what happens if the desktop service is unavailable, how staff are told and how access is removed when someone leaves the role. Keep the answers with your due diligence records.