LGfL and Salamander

[fiza]

Are there any LGfL schools that also utilise Salamander? If so how do you provide Salamander with Remote access to the Salamander Integration Suite server?

[Olliedawg]

Not a LGfL school.. But we do use Salamander, its great, and the support team are also great.

 

I use the remote access/support via their Salamander Integration Suite software (I believe it uses an API to send data about your configurations/workflows to the assigned support technician.) Requires a certain version of PowerShell to run I believe? (don't quote me on that). Always worked well for us, just enable it for the day you submit a ticket. Can be extended if required.

[psydii]

Yep. It just works? We have got Head Teach approval for remote access though.

[fiza]

Yep. It just works? We have got Head Teach approval for remote access though.

 

I take it you are at an LGfL school? Did you have to create USO accounts for the Salamander Technicians to give them remote access? IF so how many accounts did you create and were they named. PM a response if it helps.

Thanks

[psydii]

Yonks ago I gave them local AD accounts that allowed them in through our remote desktop gateway. More recently they just use their built-in tools direct to the server, we haven't had to enable their RD/AD accounts for a long while now.

[fiza]

Yonks ago I gave them local AD accounts that allowed them in through our remote desktop gateway. More recently they just use their built-in tools direct to the server, we haven't had to enable their RD/AD accounts for a long while now.

 

Did you have to submit a MIP to LGfL for them to be able to use their built-in tools?

[psydii]

No? We have MIPs but I don't recall any being used for Salamander. (I've got ADSync on a dedicated IP for historical reasons, but otherwise nothing to do with user account provisioning is on its own MIP).

 

We did have to get remote access authorized though otherwise TeamViewer / logmein etc were all blocked. I suspect that might be the underlying mechanism that enables Salamander to do remote work for us.

 

I have heard others have issues USO accounts and keep the MFA token in the IT office, providing auth only when the support company are specifically engaged (coordinating over the phone / email).

 

I also think/recall that it is possible for 3rd parties to get a special 3rd party account from LGfL and that account be given remote access via the LGfL VPN service - but I don't think I've ever seen that in practice so it may never have made it past the drawing board.

[PaddyNewman]

You can be a registered 3rd party, get allocated an account and MFA then you can add their account no problems.

[bigstan48]

We give access via the Salamander Integration Suite and if that doesn't work then it's TeamViewer.

Over the years I've learnt to provide access to support companies as and when required.

[fiza]

You can be a registered 3rd party, get allocated an account and MFA then you can add their account no problems.

 

Hi Paddy - Do you mean Salamander can register with LGfL and then they get allocated an account with MFA?

I was told by support that each of their techs that needs to connect would need an account.

[PaddyNewman]

An account 'should' reflect an individual. Its for traceability as if their account is compromised, you can locate the source. Sharing an inbound account can be problematic. I'm not saying people do not share these accounts, but typically I imagine their support team is a sensible number of people and they have a 'manager' as it were. They could register and just maintain their support team with USO accounts or as I say... they could bend the rules and we would be none the wiser, I know it happens.

[psydii]

I think the Salamander team can't bend the rules in this way because they are all wfh. Also they may well not be prepared to take the risk - I would imagine a compromised salamander account in most schools is a fast track to getting the Domain *and* the 365 tenant comprehensively 0wn3d.

[PaddyNewman]

Agreed, its a bend in policies and comes with risks!