How to launch local apps using Parallels Client

Parallels
74 followers
1 Video View·Feb 24, 2026
In this video, learn how to launch local applications using the Parallels Client. We'll demonstrate how to extend this functionality to apps launched by Parallels Browser Isolation (PBI) for added security and flexibility.
Watch as we walk you through managing and launching traditional, local, and SaaS applications, all while maintaining centralized control and seamless user experience. Perfect for admins looking to optimize their app management and boost security with PBI.
Learn more details here
https://docs.parallels.com/parallels-ras-administrators-guide-20/parallels-ras-20-administrators-guide/publishing/publishing-local-applications
AI Generated·May contain errors
The first screen you're presented with in PBI is the dashboard. So this gives you an overall view
of user sessions, the applications that have been accessed, policy violations, which are,
as we'll see later when we configure policy, any user does something that goes against that policy
that is recorded as an attempted action. I can also see the domains I visited, which users are
actually violating those policies the most, and then where those users have actually connected
from. Top violated security controls, we'll see those in a separate video when we look at policies.
So that's the PBI dashboard. Administering applications in PBI is pretty straightforward.
Every application has a tile in the admin pane that corresponds to an icon the user would see
when they log in. I can enable and disable an application by using a simple toggle switch,
so that when the user then refreshes, the application either appears or disappears,
depending on what the administrator has chosen. Each application has a series of settings,
so I can view the application. I can also edit the application configuration from here,
and we'll see that in just a second, what the options are available there. We can copy the
application URL. Now, we will come back to that a little bit later. We can delete the application
from here as well. Now, importantly, there are two types of application I can publish with PBI,
a secure browser and a secure web application. A secure browser gives a user a location bar at
the top, and they can navigate to other domains by default. A secure web application does not.
It restricts the user to that URL on its own by default. So, let's just have a look at
both those applications in action. I'm adding a secure browser application here,
so I can select an icon file if I want to. I put in the URL for where I want that browser
application to point to. In this case, I'm looking at office.com. Now, I can add users here. I can
select all users or some users, depending on what I want to do. I can also do the same with groups.
So, these are the groups that are coming from your identity provider that you've configured
already. We can also configure policies here. Now, policies are going to be covered in a separate
section, so we'll come back to that a little bit later. Now, if I configure a secure web application,
very, very similar options inside the secure web application. So, I give it a name. This time,
I'm going to, just for the sake of this video, refer to the fact that this is a web application,
point it to the URL that I want it to start in, and then just as before, we can choose the users
or the groups that are coming from the IDP. Now, if we have a little look at what visual difference
that makes to the user, if we just refresh that page, you can see the applications have appeared.
If I open the browser application, the thing to note here when I'm launching a secure browser app
is the location bar across the top. So, I've got that blue location bar, and I can sign in. I can
do what I'd normally do, but this connection itself is secured. That's the point of a secure
browser application. The connection is secured. With a web app, not only is the connection
secured, but I'm not letting the user navigate to any other URL through this connection unless I
have enabled it. So, they get no location bar across the top, and now when I try and sign in,
because that's going to a different URL to do the sign-in process, that is not permitted. So,
that's blocked by default. Now, obviously, that's not practical because that means a user can't sign
into their application, but we're going to rectify that now. So, we're going to edit the web app,
and one of the settings a web app gets that you don't get with a secure browser is this allowed
domains option. So, I can add domains in addition to the starting URL, which allow my user to operate
that application successfully. So, I can add them manually. I can add them either individually or
from a file, or I can do what's called auto discover. What auto discover is going to do
is it's going to launch the application in effectively a kind of learning mode,
which I then click on the buttons or the links or go about my kind of business process,
navigating around the parts of the application that I as an administrator want my user to be
able to navigate, and it's capturing those URLs. So, now it said, okay, well, these are the URLs
that were instigated as part of the action you did. I update that. That is now inside my secure
web app. Now, you don't need to do that with a secure browser because by default, secure browser
is clicking the opposite stance. It's allowing all those domains, and then I can restrict which
domains I access. So, now I reopen the same web app, but I've added those two extra URLs because
I need my user to be able to log in. Now, when they sign in, it completes successfully because
I've allowed those URLs to be part of the application. And that concludes this section
on PBI applications. If we now take a look at policies in PBI. So, this is where you deliver
restrictions to applications or particular parameters or visual effects that you want
the particular application to use. So, I can view and edit and delete policy from here. I can add
a new policy. So, I give it a name. I can optionally give it a description as well.
Now, policies get applied to applications inside PBI, but optionally, you can also
apply a policy only to a specific group of users if that's what you want to do. So,
the policy will be applied to the application, but also whatever settings you're setting here
can be applied to a specific group, for example. I can also determine what hours this policy becomes
active. So, for example, I could have, let's say, three sets of users all intending to work
at a different time of day. I can ensure that this policy only applies during the time they
either are at work or not at work. And then I can then perhaps disable the application
for those groups of users that shouldn't be using the application at that time of day,
for example, from a security point of view. I can also only apply policies to a particular
location if that's what I want to do. And then I've got additional security controls. So, I can
either allow or deny access to the application. I can allow keyboard to be used or not. I can allow
the user to print from that application or not. Can they copy to and paste from the application?
Also, do I allow downloads? Now, here I can actually deny the downloads by file type. Again,
there might be one particular file type or a selection of file types that I need to allow the
user to download to their client, but I can perhaps restrict all other file types. So, for example,
I could deny everything apart from a PDF in this example. So, that really depends on the application
that I'm administering, but it's nice and easy. I can configure that from here.
I can also stop a user uploading anything into the application as well. Then I've got some visual
settings. So, I can give a blue border or I can indicate this is a secure browser by a tab or a
pop-up notification. Watermarking puts the user's username diagonally across the screen the entire
time to kind of discourage the whole screenshotting process and that kind of stuff. And I can also add
domains specifically that I'm going to block with policy here as well. Now, we're having a look at a
policy that's already been configured. You can see I've denied a whole load of things. I've denied
keyboard, clipboard, downloads, those kind of things. And I've also blocked access to
Microsoft.com for the sake of the demo because I wanted to actually instigate that blocked policy
so you can see the effect of the policy in action. Now, if we go and have a look at applications,
you can see where those policies are applied. In this case, if I edit the application and scroll
all the way to the bottom, I can see that the policy we've just seen has been applied. I can
add multiple policies to this application if I wish. So, I'm now going to go and see what the
impact of that policy is on the application. So, we get the user to open the application in question.
That application then launches. You can see it's a secure browser because I've got that URL bar,
but I've restricted pretty much everything. So, I'm trying to, for example, type my username in here
and it's saying I can't use the keyboard. I can copy that text or at least attempt to copy that
text and it says I'm not allowed to do that either. I'm like, right, okay, well, let's try a different
location. So, now I'm accessing a Microsoft.com link that is going to be blocked because of my
organization's policy as well. So, you can start to see how some of this stuff builds up. Now,
why would you disable keyboard, for example? Well, a user might be logging in using a different
authentication method. So, they could log in through the IDP. They don't actually perhaps
need access to their keyboard for that specific application. And that concludes this video
section on policies. If we take a look at insights, that is designed to give us an overview
of what's going on right now and what's happened in the past. So, I can look at the number of
sessions that have been launched, how many different domains have been kind of visited,
what the traffic has been like, what the most visited domains are, but also things like security
controls. So, when we set up security controls and policies that were in a previous video section,
we decided whether we want to, for example, disable the clipboard and that kind of stuff.
And this measures who is trying to do that but has hit up against a policy. It allows you to
perhaps administrate a little bit better or deliver some training to a particular set of
users, for example. And we've also got where those users are coming from. So, I can see globally
what the kind of distribution is of my users using the applications at any one time.
I can also have a look at live reports. And they're going to show the active user sessions
that are happening right now and then the URL they are accessing in order to go about their work.
User events is literally every event that has happened from a user point of view. So,
which users have accessed applications, which users have, for whatever reason, not being able
to access. It also allows me to see where access has been denied, for example. So, when I'm on a
web app and I go to a URL that's not permitted, that's been opened by that administrator,
it will show up here as denied. And that's actually quite useful from a troubleshooting
point of view. When you first launch that web app, you may have missed a URL, for example.
It gets denied, it's audited in here, and then you could just manually add it into the web app.
We've also got administration events as well. So, whenever an administrator makes a change,
you can see I've made some policy changes here. I've added apps, I've changed icons,
that kind of stuff. You can see how that is all logged inside admin events inside here.
And that concludes this video section on insights. The user management section inside PBI shows me
the list of users who have either connected or have been manually set up. Now, there's no need
to populate this section. What you do is you connect to your identity provider, and then when
an authenticated user connects to PBI successfully through the IDP, they will automatically be added
in here. You can add users in advance if you want, but there's no requirement to do so.
Now, what you do do is you add groups in here that refer to groups that already exist in the
IDP, because then you can assign groups to applications and policies and those kind of
things rather than adding usernames individually. Administrators, you also need to add in here
manually. Now, it'll prompt you initially for your first kind of administrator or group when
you first set up PBI, but now you can come in here and adjust that, remove administrators,
add new administrators or groups, and that kind of stuff as well.
And then we've got custom branding. So custom branding allows you to do a number of things.
One of them is to have kind of a customized URL subdomain on the front of pbi.parallels.com to
make it much more specific to you as an organization. It allows organizations perhaps
to do some kind of front-end filtering on those kind of devices as well. So when a user logs in,
they get a custom URL appearing for them right there. We could do a number of other things too.
So we could change the header text that appears at the top of the page. So if I just put in some
different text in there just to show you where that appears, that's going to appear at the top
of the page. As you can see, it also appears in the tab that the user sees in their browser as well.
Now you can change the header logo as well. I can change the color of the bar that's across the top.
So if I just change that color just to show you what the impact of that is,
and then we save that, you can see that it gives me a different colored kind of bar across the top
if that's what you want to do in order to change that. Now the alternative to choosing a solid
color is to choose blur. So that's kind of this kind of modern translucent kind of style of header
that goes across the top, and that's the default. So if I change it back to blur, you'll see that
it's kind of like a semi-see-through title bar across the top of there as well.
Now you can change your background. So I can upload a separate image if that's what I want to do
and save that. Now this is only navigable through that custom URL. So I've got that there, and you
can see I can change the background. So I could have my organization's kind of splash screen,
if you like, to make it a little bit more corporate aligned from a look and feel point of view.
And I can change the favicon as well. The favicon just changes that kind of tab icon,
and that concludes the video section on user management. So we can also integrate our PBI
applications into other delivery methods, and this is where the copy application URL
piece comes in. So once we've copied the application URL, that can be used from any
trigger you like. We can literally paste it into a browser and it directly launches PBI.
I can also launch that application URL from any other source. So I can have a customized front
end if I wanted to. You don't have to use the PBI kind of user interface, but equally I can
integrate this into other application delivery methods such as Parallels RAS. So that's what
we're going to do now. So we copy the application URL from PBI. We go into Parallels RAS. Now
Parallels RAS has a feature called local applications. So I can put an icon on the
user screen, but rather than going into Parallels RAS, it actually launches a local application,
and we're going to utilize that feature in order to launch PBI. So in this example, I'm leaving
the executable blank, which means it's going to use the user's local default browser that will
launch the URL specified, which in this case is that PBI application URL. So when a user using
the Parallels client or the user interface clicks on the icon, just like all their other icons,
this is going to launch a secure browser PBI session. When they click on a different icon
for example, an AVD desktop, that desktop is going to launch directly into Microsoft APD.
And when they launch a local application, this is truly going to open on their local client.
That local application is also launched. But the important thing here is from a user's point of
view, they see just a list of application icons. They have these icons to do their work,
and those icons are presented in a consistent way. So at the point of consumption,
I may be providing my user with published applications, published desktops, AVD desktops,
but also secure SaaS applications, and the user has this consistent experience.
