![]() LogOutput " An error occurred installing Quick Assist: $($_.Exception. ![]() LogOutput " The Windows store version of Quick assist has successfully installed and the old version has been removed." LogOutput " Attempting to remove the old version of Quick Assist." # Using the DIMS function instead and path to the network shareĭISM.EXE /Online /Add-ProvisionedAppxPackage /PackagePath:"\\Network\Share\path_to_package\QuickAssist.AppxBundle" /SkipLicense LogOutput " Installing the Windows Store version of Quick Assist." LogOutput " Old version of Quick Assist has been uninstalled" Remove-WindowsCapability -Online -Name '~~~~0.0.1.0' -ErrorAction 'Silentl圜ontinue' ![]() LogOutput " lets uninstall the old version" LogOutput " Windows Store version of Quick Assist is already installed" $InstallAppX = Get-AppxPackage -allusers MicrosoftCorporationII.QuickAssist LogOutput "***This script is used to install the new Quick Assist app that is from the Microsoft Store. "$($LocalComputer) $(get-date -Format 'MM/dd/yyyy HH:mm') $($Message)" | Out-file -FilePath $LogFile -Append -Force $LogFile = "\\Network\Share\QuickAssist\Quick-Assist-install.log" Insure all users have Modify access to this share # Added $LocalComputer to tag the computer name at the begining of every log lines #Switches used are "-install" and "-uninstall" #This script will install the new Quick assist and remove the old version Just update the network paths to your own. You can compare it side by side to DroidKid’s script if you want to see the 3 minor changes. This is a copy paste of the modified script (sanitized). And as always: TEST BEFORE DEPLOYING TO THE WHOLE ORGANISATION Note that for the GPO, I used it as a user logon script, not computer and used those parameters: -Noninteractive -ExecutionPolicy Bypass -NoprofileĪt the time of typing, this it is still in my test environment but it’s good enough to pass on the knowledge. I know right, it’s dumb and why didn’t we think of this before? This allows me to host the package on a network share and pass the script in a GPO. I used the image deployment logic: DISM.EXE instead of Add-AppxProvisionedPackage. So may treads, no solutions to this problem. All I did was some very minor modifications (disabled switches, logging PC name and updating 1 function) To allow certain users and groups to connect to user desktops, click Set Viewers and add the names of users/groups to the list.I must give massive credit to DroidKid since he took care of all the heavy lifting. Play a sound on client: Begging and end of session.Show session notification icon on taskbar: True.Prompt user for Remote Control permission: True.As a rule, it is better to ask a user permission on remote connection and display a notification if the session is active. Just like with Google Assistant, Amazon Alexa is available on select 2020, 2021, and 2022 TVs Once Alexa has been set up, you can control your device’s basic functions, like the volume level or channel, with voice commands.You can even ask Alexa to find certain movies or search for songs via Amazon Music. Usually, the settings are selected according to the Remote Control policy used in the company. Require network level authentication on computers that run Windows Vista operating system and later versions – specifies if the computers running Windows Vista or higher have to pass NLA authentication.Allow permitted viewers to connect by using Remote Desktop connection – allow users connect using RDP.Manage Remote Desktop settings – RDP settings. ![]() Manage unsolicited Remote Assistance settings – management of RA settings if a user has not initiated a connection request.Play a sound on client – play the sound notifications on the remote user connection/disconnection.Show session connection bar – is a more prominent notification of session connection as a separate bar.Show session notification icon on taskbar – sets if an icon of session connection has to be displayed on the taskbar.Permitted viewers -the list of users or groups having Remote Control permission.Access level allowed – shows the level of access to the user session (View only or Full Control).Grant Remote Control permission to local Administrators group – specifies if Remote Control permission has to be given to local Administrators group.Prompt user for Remote Control permission – if a user must confirm permission for a remote connection to the computer.Allow Remote Control of an unattended computer – sets if it is possible to connect to a computer with a locked screen or without user session.Users can change policy or notification settings in Software Center – allows users to change remote connection and notification policies.Let’s consider the main customizable settings: To let the clients accept the incoming remote connections, check Enable Remote Control on client computer and set firewall profiles to make the connection using Remote Tools possible.
0 Comments
Leave a Reply. |