Clearer workspace decisions
Bring users, applications, devices and access contexts into one discussion before selecting or assuming a hosted desktop approach.
Plan hosted desktop access around your Southbank users, applications, peripherals, profiles, connectivity and session requirements, with the proposed platform and scope confirmed before work begins.
A considered discussion begins with the environment you have today.
Virtual Desktop, with clear scope and ownership.
Start the Southbank conversation with the locations in use, remote-working needs and internally managed systems identified in the intake. Review hosted-workspace access alongside application, peripheral, user-profile, connectivity and session requirements before platform scope is set.
Southbank sits on the southern side of the Yarra River Birrarung, where the riverside promenade includes restaurants, hotels and city views.
The Melbourne Arts Precinct in Southbank brings together the National Gallery of Victoria, Hamer Hall, galleries, theatres, studios and arts education institutions.
A Virtual Desktop discussion can consider how users reach a hosted desktop or workspace from the office, home or another location, while confirming the systems, devices and access conditions involved.
Tell us what you need. We’ll help you understand the options and decide what comes next.
Use the enquiry form to tell us about your requirements.
Share the issue you’re facing, what you want to improve and any systems already in place.
We discuss your current setup, the people it needs to support and any practical requirements.
We explain suitable options and discuss the scope so you can decide how to proceed.
Support planning should distinguish the hosted workspace from the user's endpoint, application vendor, internet connection and any existing managed-service arrangement. vCloud's public material emphasises integrated cloud and managed IT context and reducing hand-offs, but the responsible party for each component still needs to be confirmed.
A Virtual Desktop discussion is not by itself a promise of continuous monitoring, help-desk coverage, onsite work, guaranteed resolution, recovery time or a particular support tier. User numbers, devices, access methods, applications and escalation boundaries should be recorded before delivery assumptions are made.
For a Southbank organisation in VIC, premises, remote-working arrangements and any equipment requiring hands-on attention should be discussed separately. Local coverage, travel, connectivity, platform, licensing, retention and session policies all require confirmation in the proposal.
Remote support for Virtual Desktop helps your Southbank team work through service questions and issues without needing an office visit.
You can access Level 1–4 support engineers for help with your Virtual Desktop requirements, from initial troubleshooting through to more involved technical investigation.
The discussion can stay focused on your Virtual Desktop setup, the issue you are experiencing and the access needed to investigate it remotely.
Support scope and remote access can be confirmed when you contact us.

This proposed service profile focuses on the decisions that affect a hosted desktop experience. The technology platform, licensing, provider relationships, availability and delivery terms are not assumed and must be confirmed for your organisation.

Map how each user would reach a hosted desktop or workspace.
Review office, home and other access contexts, including the devices and identity arrangements users may rely on. The final access method and platform are proposed for confirmation, not implied by this profile.Discuss this requirement
Identify the applications a hosted desktop must support.
Document application versions, dependencies, workflows and any specialist software used by your team. Compatibility, performance and ownership boundaries require assessment with the proposed environment.Discuss this requirement
Consider printers, scanners, audio, cameras and other connected equipment.
Peripheral behaviour can depend on the user device, connection and application. Discuss the equipment and workflows that matter, then confirm what the proposed design can support rather than assuming local-device parity.Discuss this requirement
Plan how user settings, files and working context should follow the user.
Review profile contents, personalisation, shared resources and sign-in patterns. The appropriate profile approach, storage arrangement and retention behaviour are proposed considerations that must be confirmed in scope.Discuss this requirement
Relate the hosted workspace to the connections users depend on.
Consider locations, internet paths, latency-sensitive work and network dependencies affecting the session. Suitability and resilience require review of the actual environment; no connectivity performance or fail-over outcome is guaranteed.Discuss this requirement
Define how sessions should start, operate, disconnect and reconnect.
Discuss concurrency, working hours, idle behaviour, reconnection expectations and user impact when a session ends. Any capacity, availability, recovery or session policy is subject to the proposed design and confirmed terms.Discuss this requirementBring the detail that affects your people, systems and decisions into one practical discussion.
Bring users, applications, devices and access contexts into one discussion before selecting or assuming a hosted desktop approach.
Surface application and peripheral dependencies early so suitability questions can be confirmed before implementation is proposed.
Use working patterns, profile needs and session expectations to shape a practical experience rather than a generic desktop specification.
Keep connectivity, identity, support boundaries and adjacent cloud or on-premises systems visible when defining the hosted workspace.
Different working environments bring different systems, rhythms and priorities into focus.

Candidate records, client communications and recruitment platforms need controlled access. Coordinate workplace tools and continuity requirements while keeping the applicant-tracking provider's responsibilities and personal-information obligations clearly identified.
Read perspective
Consultants often move between client sites, home and the office. Discuss secure access to project information, reliable communications and backup so the technology plan reflects mobile professional work rather than a fixed-desk assumption.
Read perspective
Policy records, client communication and specialist platforms should be considered as one working environment. Discuss access and recovery priorities while confirming professional obligations and keeping insurance-platform responsibilities separate from general IT support.
Read perspectiveFeedback from our clients.
Trevor and his team at vCloud helped me secure my windows desktop with Duo Security. Now, I can have peace of mind that every time my laptop is accessed, only I can authorise the access, because I need to allow connection from my mobile phone with DUO MFA. Highly recommended!

A Virtual Desktop architecture should connect the hosted workspace with users, applications, profiles, peripherals and the networks from which sessions are accessed. vCloud's public services describe virtual networks, workplace access, cloud and on-premises environments, and integration across cloud computing platforms; those references support a planning conversation, not a promise of a particular desktop platform.
The design may need to account for existing devices, office and remote locations, application dependencies, printing or other peripherals, identity arrangements and session patterns. Whether a hosted, hybrid or another approach is suitable, along with capacity, licensing, data location and resilience decisions, must be assessed and confirmed for the organisation.
This profile does not assume Azure Virtual Desktop, Citrix, Windows licensing, a provider partnership, a region, an office, a price or service availability. Those are proposed or unconfirmed scope items until documented in an agreed proposal.
Straightforward answers to help you understand your options.
It covers how users would access a hosted desktop or workspace, along with applications, peripherals, profiles, connectivity and session behaviour. The platform, licensing, provider, scope and availability would be assessed and confirmed before any work is agreed.
The platform is chosen around your applications, users and access needs. Azure Virtual Desktop, Citrix, Windows licensing or another option would need to be assessed and agreed; no particular product or vendor partnership is assumed.
It depends on the applications, devices, connection and proposed workspace design. Application versions, dependencies, printing, audio, cameras, scanners and other equipment should be assessed before relying on compatibility.
Planning covers personalisation, shared resources, sign-in, simultaneous users, idle sessions and reconnection. How user profiles are stored, the capacity needed, retention and session policies are agreed as part of the design.
Home and other work locations can be considered as part of the design. Suitability depends on devices, identity controls, internet connectivity and applications; supported access arrangements, performance expectations and availability need to be confirmed.
Tell us which equipment or workplace needs hands-on attention. We will confirm whether a visit is possible, along with local coverage, travel, availability and what the visit would include.
Tell us about your users, applications, devices, peripherals, locations and session expectations. vCloud can discuss whether a hosted workspace approach is suitable and identify the platform, licensing, connectivity, support and delivery questions that must be confirmed before work proceeds.