Chclark

This was the issue we had so had to redesign how it worked with them. We have a server onsite which hosts console which feeds all staff from ad into it and this syncs to a central instance and then pushes all staff data down when they scan in using their badge, which is also synced in to the console with there scan code importer so staff have no need to auto code etc.

As a shared device which self propels through the enrollment they won't work and hp say they don't have a fix. They should work as a 121 device where the user is prompted to log in with there Azure login to continue enrolment.

The cons been on a single server is if the link to the server drops your fire relays in the software won't work, however we have looked into this as the rules in our area state this cannot be used, and to be compliant each acu must have a physical fire relay and breakglass, we are currently retro fitting these where needed. But anything new now must be installed with this as standard. We haven't tried the lockdown stuff but have a routine in place at one site which if they scan a certain reader twice it holds the vehicle gate open permanently till a different reader is scanned twice by a certain card. This works really well for them in the holidays unsure if the VPN dropped if this would continue working or not as not sure sure if this config sits on the local acu or server but suspect it's on the server. The only other thing we have found is if making alot of permission changes we have multiple for each site of there's alot of change been made on the profile at once it can cause doors to hang while it pulls all the changes.

These are the only ones I've had issue with that so far haven't been able to resolve device driven enrollment. The dells that came from the DfE did have a issue but a bios update fixed them.

Yea the hope was to have them as generic shared devices, suppose can set then up as 121 devices which get issued for home use.

Well that sucks as the warranty is out as they was DfE devices. So that's 20 odd laptops destined for the trade in pile. Unless anyone knows what hp does to fix it?

Did anyone get a resolution for the hps I updated the bios but same error on preparing during the autopilot enrollment.

We have been quoted £30.95 per core per year for vsphere standard with phoenix.

we have vpns between all our sites so just have a central net2 server now that salamander makes all the users into syncs the photos over from arbor, then writes the card number back into AD for papercut and inventry to sync into their systems.

Not much not the company I use to work for, for 11 years. CC4 is end of life now from what I'm hearing they are trying to charge 10k to de-cc4 a network now.

Interesting are you in the swgfl area? As they have told me that pricing cannot be used by anyone outside of it.

From what we have been told the net2 relay can't be relied upon, and that to meet requirement a physical relay as well as a breakglass is required for fire routes. We now install audible break glasses so when the kids lift the covers an alarm is triggered.

We are in the same boat, phoenix price is 4x the amount we paid 3 years ago. We looked around and lgfl offer pricing and it was cheaper, however sophos are saying as a exisiting customer we are not eligible, informed them they need to sort the pricing or we will be looking elsewhere. Phoenix seem more interested trying to sell bitdeffender at the swgfl pricing. Interested to hear what others are doing.

We don't use sign-inapp we don't think it will do what we want. We have inventry. So salamander handles all the user creation but also makes the Paxton user accounts sets the access control etc. At this point a engineer programs/prints a card salamander will on next run write this card number back out of Paxton to ad pager field, this is used for papercut as we programmed all our mfd card readers to understand the Paxton format. Salamander makes a CSV file for us that rights details inventry needs to import into the central server console which syncs our staff to inventry central which pushes down to all of our school screens. This generally makes the whole process for the end user seamless. Apart from the getting the photo and printing the I'd badge from Paxton.

Do you use salamander as they handle our Paxton user creation and leavers.