8/26/2021
28

Just install RemoteToPC on an office PC and work on it from your home PC, or access your home PC remotely. Our Basic plan includes unlimited remote computer access to up to 10 remote PCs for just $99/yr. It’s the best remote PC access solution for personal & small office use. With Remote Play, you can control your PlayStation® console remotely wherever you have a high-speed internet connection. Using the PS Remote Play app, you can control your PlayStation®5 console or PlayStation®4 console from a device in a different location. For example, you can use a computer in another room or a smartphone. when you’re out to enjoy PS5™ and PS4™ games. Mar 22, 2020 Finally, to setup remote desktop on Windows 10, on the Remote Desktop settings, flip the Enable Remote Desktop switch from off to on. You will receive a request to confirm, click Confirm. RDP is now enabled on your PC. To configure more options, click Advanced settings. Apr 13, 2020 How about installing a program on a remote computer? That’s a bit more complicated and depend on the install package. If it’s an MSI package or a package that has a silent option, PowerShell should be able to take care of it. If the install package is already on the remote computer.

  1. Remote Pc Download
  2. Remote Install Pc Spyware
Learning has never been so easy!

WMIC (Windows Management Instrumentation Command-Line) is a potent tool that often doesn't see much use due to the lack of (easily accessible) documentation available. More information can be found on WMIC here: http://technet.microsoft.com/en-us/library/bb742610.aspx. We’ll be using WMIC with domain admin credentials to crawl through a list of nodes (PCs/Laptops) and install an example program without interrupting the user.

Though there are a couple advanced ways to accomplish this task, we'll be examining the most straightforward method: an MSI installation file requiring no options located on each remote user's local drive.

4 Steps total

Step 1: Load up a command shell with appropriate access permissions

Download

Though a WMIC instruction can be given appropriate credentials prior to operation, it is typically best-practice to avoid clear-text typing the password (who is that looking over your shoulder;)). We’ll execute the runas command like the following:

Runas /user:[email protected] cmd

… which will prompt us for the credentials of our DomainAdminAccount. If authenticated, we’ll be handed a command shell running as the Admin.

Step 2: Step into WMIC

One of the nice features of WMIC is that it may be run from any machine. With our admin command shell, we're going to enter the wmic command followed by enter.

(Note: We could have jumped into WMIC directly from the runas command.. this just breaks out the steps)

Step 3: Call the installation (for a single machine)

WMIC's install call allows compatible WMI applications to be installed with no interaction from the user (they see nothing, the program is simply installed according to the default installation parameters you or the product packager have specified).

Here's the rub: individual MSI packages will have different 'options' (the second input required in the install call as shown in the attached screenshot). To simplify our example, we're installing from an MSI that requires no options.

We'll enter the install call like the following:

> /node:exampleremotemachine product call install true,' , 'c:PathToYourFile.msi'

Which will prompt us for confirmation in the following format:

Execute (Win32_Product)->Install() (Y/N)?

To which we must answer yes (y) to confirm. If your WMI compliant MSI package was successfully installed, you should see something like the following:

Method execution successful.
Out Parameters:
instance of __PARAMETERS
{
ReturnValue = 0;
};

Step 4: Call the installation (for a list of machines)

We'll use WMIC's ability to handle a flat text file as input for the nodes to run this installation on a list of machines (in our example, stored on the admin's local hard drive in C:computers.txt) by running the following command:

> /node::@'c:computers.txt' product call install true,' , 'c:PathToYourFile.msi

Which will iterate through the list in computers.txt.. skipping over invalid nodes (eg: the machine is turned off), and asking for installation confirmation for each machine.

*****Long Note:

Install

As indicated in the introduction, we must have the MSI and installation files located on the remote computer's local hard-disk for this method to work. In most situations, this isn't preferable - it would be ideal to install from a network drive. Unfortunately without advanced scripting (using delegation techniques for mapping network disks), this is not possible.

Install remote pc

The reasons for this stem from WMI's need to run as (in this case) a domain admin and WMI's inability to negotiate a network drive's connection by this domain admin ID without some security concerns. There are work-arounds.. but they fall outside the scope of this how-to. If another individual wishes to write a how-to using WMIC to install from an MSI package (or more-advanced .exe wrapper) located on a networked machine, I would happily reference it!

Hopefully you've been intrigued by the potency of WMIC.. though copying over MSI/installation files to each PC's local disk isn't preferable in most cases, it can sometimes be the fastest method of background installation (our user need not even be aware of the installation).

Published: Feb 04, 2009 · Last Updated: May 18, 2012

References

  • Uninstall Programs Using WMIC

57 Comments

  • Pimiento
    Mike2900 Mar 18, 2009 at 04:33pm

    thanks

  • Pimiento
    Mike2900 Mar 18, 2009 at 04:37pm

    This is great. I'm having a little problem though. I'm getting the following error when trying to install a program. Please advise.
    Oh, I can uninstall a program, just not install one through wmic.

    wmic:rootcli>/node:cos12189 product call install true,' , 'C:downloadsSplitView.msi'
    Execute (Win32_Product)->Install() (Y/N)?y
    Method execution successful.
    Out Parameters:
    instance of __PARAMETERS
    {
    ReturnValue = 2;
    };

    wmic:rootcli>

  • Chipotle
    benpbolton Mar 26, 2009 at 09:12am

    Mike, sorry I didn't see this until now. http://msdn.microsoft.com/en-us/library/aa394574(VS.85).aspx lists a typcial WMI return code of 2 as a 'Warning' .. unfortunately, vendors can supply their own return codes as well.. so your individual package may have a special meaning for 2.

    If you'd like to test a particular package, try the following:

    msiexec /a 'C:downloadsSplitView.msi' /qn

    Which asks msiexec to attempt a silent, admin install of your msi package.. then check event viewer (or use the /log switch in msiexec) to see more details about what's happening..

  • Anaheim
    Tom7833 Apr 2, 2009 at 02:01pm

    I keep trying to install the 2007 Office compatibilty pack for my 2003 users. I tried using GPO but i keep getting the file is not available then trying to do it manually I get a parameter return of 123 using WMIC.
    I have created a NEW FULL SHARE on my DC for EVERYONE and still can't get this to load.. is there another way or am i doing it wrong
    it says: Method Execution successful

  • Chipotle
    benpbolton Apr 7, 2009 at 05:18pm

    @Tom,

    Take a look at this How-To to deploy the file format converters for 2007: http://community.spiceworks.com/how_to/show/285

  • Chipotle
    Hodge Apr 29, 2009 at 08:59am

    Thanks for the great instructions.

  • Anaheim
    Shane Wood May 25, 2009 at 12:02am

    Just a quick note:
    Remember the path to the file MUST be the local path.
    ie open the default admin share staffpcc$ and create a folder to pop the msi in.

    Worked really well for me and saved me heaps oftime. Thanks for the tip :)

  • Pimiento
    Sunair3815 Jun 12, 2009 at 11:22am

    I'm having troube trying to install remotely. I am trying to install .NET framework 2.0 on one of my machines and it keeps coming back with a 1620 error. The .NET msi is out on our network share and I'm trying to grab it from there.

    Also what goes in between the quotes after true ' ?

    wmic:rootcli>/node:bec00801d product call install true,' , 'abc-def123$NETFC.msi'
    Execute (Win32_Product)->Install() (Y/N)?y
    Method execution successful.
    Out Parameters:
    instance of __PARAMETERS
    {
    ReturnValue = 1620;
    };

    wmic:rootcli>

    'Here's the rub: individual MSI packages will have different 'options' (the second input required in the install call as shown in the attached screenshot). To simplify our example, we're installing from an MSI that requires no options.'

    -How would install from an msi that has options, since it doesn't give us an example here. What would you have to put in the commands?

    Any help is appreciated

    -SKI

  • Pimiento
    Sunair3815 Jun 12, 2009 at 11:42am

    I'm having troube trying to install remotely. I am trying to install .NET framework 2.0 on one of my machines and it keeps coming back with a 1620 error. The .NET msi is out on our network share and I'm trying to grab it from there.

    Also what goes in between the quotes after true ' ?

    wmic:rootcli>/node:bec00801d product call install true,' , 'abc-def123$NETFC.msi'
    Execute (Win32_Product)->Install() (Y/N)?y
    Method execution successful.
    Out Parameters:
    instance of __PARAMETERS
    {
    ReturnValue = 1620;
    };

    wmic:rootcli>

    'Here's the rub: individual MSI packages will have different 'options' (the second input required in the install call as shown in the attached screenshot). To simplify our example, we're installing from an MSI that requires no options.'

    -How would install from an msi that has options, since it doesn't give us an example here. What would you have to put in the commands?

    Any help is appreciated

    -SKI

  • Pimiento
    Sunair3815 Jun 12, 2009 at 11:42am

    I'm having troube trying to install remotely. I am trying to install .NET framework 2.0 on one of my machines and it keeps coming back with a 1620 error. The .NET msi is out on our network share and I'm trying to grab it from there.

    Also what goes in between the quotes after true ' ?

    wmic:rootcli>/node:bec00801d product call install true,' , 'abc-def123$NETFC.msi'
    Execute (Win32_Product)->Install() (Y/N)?y
    Method execution successful.
    Out Parameters:
    instance of __PARAMETERS
    {
    ReturnValue = 1620;
    };

    wmic:rootcli>

    'Here's the rub: individual MSI packages will have different 'options' (the second input required in the install call as shown in the attached screenshot). To simplify our example, we're installing from an MSI that requires no options.'

    -How would install from an msi that has options, since it doesn't give us an example here. What would you have to put in the commands?

    Any help is appreciated

    -SKI

  • Chipotle
    benpbolton Jun 23, 2009 at 02:52pm

    Sunair3815, your problem lies in trying to host the MSI file on a network drive. The 'Long Note****' section in the final step addresses WMIC's limitations for this. The MSI file MUST be located on a local drive.

    For a scenario where you wish to deploy an MSI across a domain, Group policy is vastly superior to WMIC.. but WMIC can work in a pinch for some odd cases!

    Hope that helps..

  • Habanero
    Drew Dunkel Oct 8, 2009 at 01:31pm

    Thanks very good instructions!!! Cisdem video converter for mac review.

  • Pimiento
    RoemanB Oct 20, 2009 at 09:37am

    @Rune3280,

    I believe windows will still throw up an error regardless of the remote drive permissions - this is because it is using different credentials for the installation (likely the system administrator's), and cannot reliably authenticate as either the local user or the admin account (for security reasons).

    Even if both id's (or all IDs) and anonymous access was granted to the network share, windows still attempts credentials, and will return an error.

  • Chipotle
    Jason R. Rokeach Dec 16, 2009 at 08:04am

    How do we do an install that requires options?

  • Chipotle
    benpbolton Dec 16, 2009 at 08:26am

    @Jason,

    You would hypothetically enter those options as one of the arguments of product call install.. something like:

    /node:exampleremotemachine product call install true,'OPTIONSGOHERE' , 'c:PathToYourFile.msi'

  • prev
  • 1
  • 2
  • 3
  • 4
  • next
-->

Applies to: Windows 10, Windows 10 IoT Enterprise, and Windows 7

You can use the Remote Desktop client for Windows Desktop to access Windows apps and desktops remotely from a different Windows device.

Note

  • This documentation is not for the Remote Desktop Connection (MSTSC) client that ships with Windows. It's for the new Remote Desktop (MSRDC) client.
  • This client currently only supports accessing remote apps and desktops from Windows Virtual Desktop.
  • Curious about the new releases for the Windows Desktop client? Check out What's new in the Windows Desktop client

Install the client

Choose the client that matches the version of Windows. The new Remote Desktop client (MSRDC) supports Windows 10, Windows 10 IoT Enterprise, and Windows 7 client devices.

You can install the client for the current user, which doesn't require admin rights, or your admin can install and configure the client so that all users on the device can access it.

Once you've installed the client, you can launch it from the Start menu by searching for Remote Desktop.

Update the client

You'll be notified whenever a new version of the client is available as long as your admin hasn't disabled notifications. The notification will appear in either the Connection Center or the Windows Action Center. To update your client, just select the notification.

You can also manually search for new updates for the client:

  1. From the Connection Center, tap the overflow menu (..) on the command bar at the top of the client.
  2. Select About from the drop-down menu.
  3. The client automatically searches for updates.
  4. If there's an update available, tap Install update to update the client.

Workspaces

Get the list of managed resources you can access, such as apps and desktops, by subscribing to the Workspace your admin provided you. When you subscribe, the resources become available on your local PC. The Windows Desktop client currently supports resources published from Windows Virtual Desktop.

Subscribe to a Workspace

There are two ways you can subscribe to a Workspace. The client can try to discover the resources available to you from your work or school account or you can directly specify the URL where your resources are for cases where the client is unable to find them. Once you've subscribed to a Workspace, you can launch resources with one of the following methods:

  • Go to the Connection Center and double-click a resource to launch it.
  • You can also go to the Start menu and look for a folder with the Workspace name or enter the resource name in the search bar.

Subscribe with a user account

  1. From the main page of the client, tap Subscribe.
  2. Sign in with your user account when prompted.
  3. The resources will appear in the Connection Center grouped by Workspace.

Subscribe with URL

  1. From the main page of the client, tap Subscribe with URL.
  2. Enter the Workspace URL or your email address:
    • If you use the Workspace URL, use the one your admin gave you. If accessing resources from Windows Virtual Desktop, you can use one of the following URLs:
      • Windows Virtual Desktop (classic): https://rdweb.wvd.microsoft.com/api/feeddiscovery/webfeeddiscovery.aspx
      • Windows Virtual Desktop: https://rdweb.wvd.microsoft.com/api/arm/feeddiscovery
    • To use email, enter your email address. This tells the client to search for a URL associated with your email address if your admin has setup email discovery.
  3. Tap Next.
  4. Sign in with your user account when prompted.
  5. The resources will appear in the Connection Center grouped by Workspace.

Workspace details

After subscribing, you can view additional information about a Workspace on the Details panel:

  • The name of the Workspace
  • The URL and username used to subscribe
  • The number of apps and desktops
  • The date/time of the last refresh
  • The status of the last refresh

Accessing the Details panel:

  1. From the Connection Center, tap the overflow menu (..) next to the Workspace.
  2. Select Details from the drop-down menu.
  3. The Details panel appears on the right side of the client.
Remote

After you've subscribed, the Workspace will refresh automatically on a regular basis. Resources may be added, changed, or removed based on changes made by your admin.

You can also manually look for updates to the resources when needed by selecting Refresh from the Details panel.

Refreshing a Workspace

You can manually refresh a Workspace by selecting Refresh from the overflow menu (..) next to the Workspace.

Unsubscribe from a Workspace

This section will teach you how to unsubscribe from a Workspace. You can unsubscribe to either subscribe again with a different account or remove your resources from the system.

  1. From the Connection Center, tap the overflow menu (..) next to the Workspace.
  2. Select Unsubscribe from the drop-down menu.
  3. Review the dialog box and select Continue.

Managed desktops

Workspaces can contain multiple managed resources, including desktops. When accessing a managed desktop, you have access to all the apps installed by your admin.

Remote Pc Download

Desktop settings

You can configure some of the settings for desktop resources to ensure the experience meets your needs. To access the list of available settings right-click on the desktop resource and select Settings.

Remote

The client will use the settings configured by your admin unless you turn off the Use default settings option. Doing so allows you to configure the following options:

  • Display configuration selects which displays to use for the desktop session and impacts which additional settings are available.
    • All displays ensures the session always uses all your local displays even when some of them are added or removed later.
    • Single display ensures the session always uses a single display and allows you to configure its properties.
    • Select displays allows you to choose which displays to use for the session and provides an option to dynamically change the list of displays during the session.
  • Select the displays to use for the session specifies which local displays to use for the session. All selected displays must be adjacent to each other. This setting is only available in Select display mode.
  • Maximize to current displays determines which displays the sessions will use when going full screen. When enabled, the session goes full screen on the displays touched by the session window. This allows you to change displays during the session. When disabled, the session goes full screen on the same displays it was on the last time it was full screen. This setting is only available in Select display mode and is disabled otherwise.
  • Single display when windowed determines which displays are available in the session when exiting full screen. When enabled, the session switches to a single display in windowed mode. When disabled, the session retains the same displays in windowed mode as in full screen. This setting is only available in All displays and Select display modes and is disabled otherwise.
  • Start in full screen determines whether the session will launch in full-screen or windowed mode. This setting is only available in Single display mode and is enabled otherwise.
  • Fit session to window determines how the session is displayed when the resolution of the remote desktop differs from the size of the local window. When enabled, the session content will be resized to fit inside the window while preserving the aspect ratio of the session. When disabled, scrollbars or black areas will be shown when the resolution and window size don't match. This setting is available in all modes.
  • Update the resolution on resize makes the remote desktop resolution automatically update when you resize the session in windowed mode. When disabled, the session always remains at whichever resolution you specify in Resolution. This setting is only available in Single display mode and is enabled otherwise.
  • Resolution lets you specify the resolution of the remote desktop. The session will retain this resolution for its entire duration. This setting is only available in Single display mode and when Update the resolution on resize is disabled.
  • Change the size of the text and apps specifies the size of the content of the session. This setting only applies when connecting to Windows 8.1 and later or Windows Server 2012 R2 and later. This setting is only available in Single display mode and when Update the resolution on resize is disabled.

Remote Install Pc Spyware

Give us feedback

Have a feature suggestion or want to report a problem? Tell us with the Feedback Hub.

You can also give us feedback by selecting the button that looks like a smiley face emoticon in the client app, as shown in the following image:

Note

To best help you, we need you to give us as detailed information about the issue as possible. For example, you can include screenshots or a recording of the actions you took leading up to the issue. For more tips about how to provide helpful feedback, see Feedback.

Access client logs

You might need the client logs when investigating a problem.

To retrieve the client logs:

  1. Ensure no sessions are active and the client process isn't running in the background by right-clicking on the Remote Desktop icon in the system tray and selecting Disconnect all sessions.
  2. Open File Explorer.
  3. Navigate to the %temp%DiagOutputDirRdClientAutoTrace folder.