A few weeks ago I released the Company Portal System Tray tool. The post has received very good feedback and the tool was tested by some and also used productively. I have been working on developing the tool further and integrating more useful functions that can help with troubleshooting. The first version of the Company Portal system tray icon has many quick access possibilities to system tools or logs that are important for troubleshooting an Intune managed device. In addition, this tool has a quick access to open the Company Portal.
In this blog I want to introduce the new version of the Tool.
The new Features
Sync device
In the previous version there was only the possibility to sync apps. In this version there is also the possibility to sync the device compliance state.
Open Quick Assist
There is a button to open quick assist to connect remotely to the device. If you use another remote support tool you can also change this to TeamViewer or AnyDesk.
Get System Info
In this version is a menu with all important system information that can be important for supporting the device. You can see here for example the hostname, the IP, if the device is MDM managed and much more information. It is also not a big deal to add here more important information.
Change the Password of the login user
You will also find in the company portal system tray tool a quick access to change the password of the logged in user.
How to deploy the tool
In the version 1.0 of the Company Portal System Tray Icon the tool was deployed via a PowerShell script. In V2 I have decided to deploy the tool via a Win32 because it is better located in Apps as in scripts. This also simplifies the integration into your environment. Now I will explain how you can deploy the app:
- Download the intune.win file from my repository or create your own intune.win file based on the files in my repository. How to create an intune.win file is explained in deploy a Win32 app with intune cmtrace.
- Open the Intune admin center
- Navigate to Apps -> Windows
- Click Add
- Select Windows app (Win32) as App type
- Click Select app package file
- Click Upload and select the .intunewin file
- Click OK
- Give the application a name and customize the app information.
- Click Next
- Enter install.bat and deinstall.bat as install/uninstall command
- Change the Device restart behavior to No specific action
- Click Next
- Select 32-bit and 64-bit as operating system architecture
- Select a minimum OS Version
Hints: If you want to specify further requirements, such as minimum free disk space, you can do this in this step.
It is also possible to specify a file, a registry value or a script as a requirement.
- Select Manually configure detection rules as Rules format
- Click Add
- Select File as Rule type
- Enter “C:\Windows_Tools” as file path and “IntuneSystemTrayV2” as folder.
- The detection method is File or folder exists
- Click Next
- Skip the dependencies and supersedence step and click Next.
- Click Next
- Click Create
Conclusion
I hope I could help you with this little tool to simplify the troubleshooting process for the end user or to enable the end user who calls the support hotline to give more specific checks and answers. If you have ideas what I can add to the tool then let me know, I’m happy about any idea. You also have the possibility to add your own actions or checks that are specific to your environment.
Stay healthy, Cheers
Jannik
Excellent! An idea: Add an ‘Email the Helpdesk’ item. It could use a mailto: link formatted with everything from System Info automatically inserted into the body of a new message using the default mailto handler. Bonus points if the To address could be pre-filled using a .txt file that deploys during installation, but otherwise, the person could just type the helpdesk email address.
Or a simple web link to a custom Helpdesk portal address, with the System Info data in the user’s clipboard so they could be directed to paste it in.
Hey Garrett, nice idea. Let me include this.
I have created the app in MEM Portal by following the post. Where does the tool show up?
After the installation and an reboot you can find this tool in the system tray
I really love the idea of this little tray app! Thanks for sharing. Ever wondering how to refresh data gathered by the script without exiting the app and starting it all over?
Can you open an issue on github and I will include this
Hi Jannik,
I was successfully able to install the script as per your steps. but after restart I am anot able to see the Tool in the Notification area. I can see it has copied the contains in the C:\Windows\_Tools\ folder & also it has created Task Schedular too. When I check Task Schedular history, it is showing “Task Scheduler successfully completed task “\StartCompanyPortalSystemTray” , instance “{43f73ddc-7c61-4ae6-b9da-1e06ffa95a75}” , action “C:\windows\System32\WindowsPowerShell\v1.0\PowerShell.EXE” with return code 2147942401.”, so I believe task scehduler is not able to run that script successfully from C:\Windows\_Tools\ folder.
Also, I have tried to run the script Create-IntuneSystemTryV2 script from C:\Windows\_Tools\ folder, it is not runnning. It is throwing “cannot be loaded because running scripts is disabled on this system” error.
So, do we need to add any commands in “Create-IntuneSystemTryV2 script” at the beginning of the script something like;
Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope CurrentUser
Many thanks for the hint. Let me fix this tomorrow
Hi Jannik,
https://mrshannon.wordpress.com/2022/06/06/get-updated-quick-assist-and-webview2-for-standard-users/
But starting in June 2022, the built-in Quick Assist app no longer works and has been replaced with a version that’s available via the Store
Open Quick Assist
“`
explorer.exe shell:AppsFolder\MicrosoftCorporationII.QuickAssist_8wekyb3d8bbwe!App
“`
Hi @Jannik,
This looks great! Thanks for taking the time to build this. We are testing it out and seem to have run into an issue. Installing via InTune fails with an error that detection fails. Though no files are copied. Windows 10 19045 Build. Any suggestions?
Best,
Peter
The Detection should be C:\Windows\_Tools