Loom Desktop

[IKWeb]

Hello All

 

Has anyone managed to package Loom Desktop into MSI for network install?

 

Any issues with it or did it work as you would expect?

[MYK-IT]

I enquired with LOOM support regarding installation location, silent deployment and if a MSI package was available, and they responded with

 

 

Default Installation Location / MSI Package

So sorry about this, unfortunately at this time there isn't a way to change the location. Both of these options are currently being worked on but there isn't a set ETA of when these options will be available.

 

Is it possible for the members of staff to use the Chrome Extension, will this option work for them?

 

Again, so sorry we don't have a solution right now but let me know if you have any other questions.

 

Silent Deployment

At the moment, silently deploying the install of Loom isn't possible. We do see the appeal and think this is a great suggestion!

 

We're in the process of developing this feature as we speak. However, I don’t have an exact ETA on when that might happen but if you'd like to add any further feedback to our public roadmap, we use this when we’re working on what to build next.

[eddyc]

I enquired with LOOM support regarding installation location, silent deployment and if a MSI package was available, and they responded with

 

 

Default Installation Location / MSI Package

 

 

Silent Deployment

 

I had the same replies to although they did say about installing it then dropping it on a network share. We did that and touch wood all seems well.

[hardtailstar]

We find that the Chrome extension works much better than the desktop version.

 

I think thats where they want to stay.

[Shan_uk]

Hi Everyone

 

Follow up from 1st post , has anyone been able to deploy loom desktop for network install. i will appreciate if someone can share their knowledge on how to deploy loom onto 90 pc's

 

Thanks

[eddyc]

Hi Everyone

 

Follow up from 1st post , has anyone been able to deploy loom desktop for network install. i will appreciate if someone can share their knowledge on how to deploy loom onto 90 pc's

 

Thanks

 

 

Hello,

 

We started to have issues with running it from our shared drive as I suggested above in the end.

 

What we did in the end was install it on one PC (it defaults to %appdata%).

 

We then grabbed that folder and placed it in \\domain\SYSVOL\domain\Distribution\Loom

 

We then used a machine start up script to call the following:

 

ROBOCOPY "\\domain\SYSVOL\domain\Distribution\Loom" "C:\Program Files\Loom" /e /s /mir

 

All users then has a desktop and start menu shortcut to "C:\Program Files\Loom\Loom.exe"

 

It seems to work really well and means that if there is a Loom update we just need to paste the new files in \\domain\SYSVOL\domain\Distribution\Loom and it will automatically update all client PCs on a machine reboot.

 

I hope this helps.

 

eddyc

[IKWeb]

What network are you installing this on? Vanilla? RM? etc?

[mrstrong]

This loom looks pretty cool! How are you using it, e.g. for teachers to record lessons ?

I guess you could do that with ms teams ?

[eddyc]

This loom looks pretty cool! How are you using it, e.g. for teachers to record lessons ?

I guess you could do that with ms teams ?

 

We don’t use teams but do use it for just that, a narrated presentation for all of our remote learning.

[_Jo_]

Has anyone had problems with applocker with Loom? It was fine for months but now applocker is blocking loom-recorder-production.exe no matter what applocker rules I set to allow it. Only happens for non-admins.

[_Jo_]

Has anyone had problems with applocker with Loom? It was fine for months but now applocker is blocking loom-recorder-production.exe no matter what applocker rules I set to allow it. Only happens for non-admins.

 

Ignore that, fixed it

[CaNNoN_1981]

Hi Jo

Please could you let me know how you fixed the recording issue in association to AppLocker?

 

Thanks

[_Jo_]

Hi Jo

Please could you let me know how you fixed the recording issue in association to AppLocker?

 

Thanks

 

 

Hi, for us it was a executable rule based on publisher :

 

"", in LOOM, from O=LOOM, INC., L=SAN FRANCISCO, S=CA, C=US

 

Publisher: O=LOOM, INC., L=SAN FRANCISCO, S=CA, C=US

Product name: LOOM

File name:

File version: *

 

 

Trying to allow the loom-recorder-production.exe file itself didn't help at all.

 

Jo

[CaNNoN_1981]

Hi Jo

 

Thanks for the quick reply, we already had that publisher rule in place and the app still crashes on record.

 

Do you have any other entries in AppLocker for Loom?

[CaNNoN_1981]

Still seeing the following error in event viewer:

 

%OSDRIVE%\USERS\TESTSTAFF\APPDATA\LOCAL\PROGRAMS\LOOM\RESOURCES\APP.ASAR.UNPACKED\DIST\BINARIES\LOOM-RECORDER-PRODUCTION.EXE was prevented from running.

 

Thats with that exact path allowed in AppLocker and with the Publisher rule.

[_Jo_]

Hi Jo

 

Thanks for the quick reply, we already had that publisher rule in place and the app still crashes on record.

 

Do you have any other entries in AppLocker for Loom?

 

a couple for the recorder exe file, similar to your own - I'll check as soon as I can log in.

[CaNNoN_1981]

This appeared to fix it for me, File Hash Rule:

 

Loom2: cmdmp3.exe, loom-recorder-production.exe

 

Edited February 2, 2021 by CaNNoN_1981

[_Jo_]

Still seeing the following error in event viewer:

 

%OSDRIVE%\USERS\TESTSTAFF\APPDATA\LOCAL\PROGRAMS\LOOM\RESOURCES\APP.ASAR.UNPACKED\DIST\BINARIES\LOOM-RECORDER-PRODUCTION.EXE was prevented from running.

 

Thats with that exact path allowed in AppLocker and with the Publisher rule.

 

 

My path rule for the loom-recorder-production.exe doesn't include a path, just the file name itself - though I originally tried it with a path with the wildcard for the username.

I've also got some hash rules for the loom-recorder-production.exe, but it continued to be blocked until I added the publisher rule. Looking at my logs, it's the publisher rule that is evaluated and allowed at runtime, but I've left them all in place because it caused chaos when it stopped working.

 

Jo

[_Jo_]

This appeared to fix it for me, File Hash Rule:

 

Loom2: cmdmp3.exe, loom-recorder-production.exe

 

 

Glad you got it working. It's not my favourite software to deal with at the moment!

[Michael]

Here's how to remove it silently -

 

Logon Script -

 

"C:\Users\%username%\AppData\Local\Programs\Loom\Uninstall Loom.exe" /currentuser /S

 

GPP Regedit (deletion, user configuration) -

 

HKCU\SOFTWARE\Microsoft\Windows\CurrentVersion\Run

Value: electron.app.Loom

 

This'll stop the application at logon, so no Notification Area icon.

 

GPP Folder (deletion, computer configuration) -

 

C:\Users\%username%\AppData\Roaming\Loom

C:\Users\%username%\AppData\Local\loom-updater

[CaNNoN_1981]

Just to note, that every time the software receives an update (and that's a lot at the moment as the software is still in Beta) that I'm having to add all the file hash rules into App Locker for each version.

[SpaceInvader83]

Is it me or is this software pretty terrible, a few tweaks to make it more enterprise friendly would make a huge difference. How are you all handling the auto updates with applocker? As above? Manual hashes per version? What about the DLLs that it calls on an update?

 

 

Thanks