psydii

same as @Chuckster. Though some systems have dedicated switches in NVRs. Which is great for installation engineers, and dramatically less great when the Network Manager has to troubleshoot three years later.

Which HDMI/USB3 Fiber cables do you use? We have found them to be as hit and miss as copper based ones

Probably really my last call about this - deadline is Wednesday this week! That said, I've heard of a couple of installations now that just upgraded themselves after years of being stuck on 1.x

Shhhh. Stop spilling the secrets of a super geek. One thing to check though would be how the cameras behave if they power up before the dhcp server. Likely they will either come up on their old address, or they will come up with an APIPA address. If the later, do they revert to the DHCP allocated address a while after the DHCP Server comes up? If they don't and they stick with APIP you might wish you had allocated static addresses. FWIW I've been DHCP on cameras and Printers since 2009 and the occasional painful hour or two doesn't out strip the benefit of the magic self-documenting IP ->Device database.

I would only be happy to upgrade the new hardware if the software platform (windows) was going to stop being supported on the old hardware in the lifetime of the support contract. I haven't looked too closely but their 2019 card readers appear to be running some form of Windows CE. Perhaps the newer ones are running a more recent platform and yours (and mine tbh) are actually currently unsupported? The head unit we have is running an 2016 LTSB branch of windows 10, so that wouldn't need replacing on renewal this year, but would in three years time.

Modern macs phone home during the OOBE (to use MS parlance) to determine whether they should be enrolling in an MDM. This was previously called DEP https://simplemdm.com/blog/definitive-guide-to-the-apple-device-enrollment-program-apple-dep/ presents a reasonable precis of how this works. It is possible that your mac might not have been enrolled in DEP out of the box, and the original owners only enrolled it after it had their removable profile installed. The refurb company would have been able to re-image it in a clean environment (with out internet) and shipped you a clean machine (because it never had a chance to phone home and learn it was in fact in the DEP now)... but then you reset it without taking precautions to prevent it from phoning apple, and boom, it learns its a DEP member and joins the original owners MDM in a immutable (for you) way. So, in short, if there was no management profile present when you first got it, then it is very unlikely the original owners had any control over it until you reset it.

Final Call - y'all need to have done this by next Wednesday otherwise you are going to have a very bad start to the academic year.

So disabling NTLM used to be a recommendation. But these days its is gone and we're all probably really talking about NTLMv2, which also really should be disabled, but *always* breaks something when you do. Apparently with a lot of effort you can selectively allow systems and services that need it... however based on my experience poking a network built in 2014 you have to make so many exceptions, that you shouldn't have bothered. You might of course choose to design from the ground up with the principle that NTMLv2 is disabled by default and refuse to implement anything that requires you to compromise. Not sure how far you'd get though.

I can confirm that setting it to deny breaks pretty much everything that isn't a domain joined windows PC, and even those stop working properly. Even things I was convinced were already using Kerberos properly broke when I tried it "just to see what would happen". - (Got to love the school holidays when on occasional days its just you, a receptionist watching netflix and the premises team) I doubt what ever settings you may had were actually denying it before, even if you had it configured to. Perhaps 2019 honours some setting that it previously ignored. Microsoft's most recent blog on the matter (2009 but occasionally updated) advises that disabling NTLM is currently a resume generating event. https://techcommunity.microsoft.com/t5/ask-the-directory-services-team/ntlm-blocking-and-you-application-analysis-and-auditing/ba-p/397191 However a colleague of the author at Microsoft just release a PowerPoint deck on removing NTLM completely, which further illustrated the challenges

I say this a lot, but might be worth dropping £440 on a call to Microsoft support, which is something I've done a couple of times on my on credit card when something big breaks at the weekend.

I'm not having a good week with my choice of words. Replace dominant with "in the top 5" and my meaning should be clearer. Based on what has happened to the rest of the market, the only reason sims is still dominant is because they have not pushed users to their cloud MIS(1), for that way lies the corpses of the competition(4). (1) yeah yeah, not ready etc etc. but objectively neither were the competition's and they did push users which is why(2) they are all as good as dead. (2) alright they also did not have pockets as deep(3) as Capita's (3) and yet, Bromcom. (4) Remember I am talking about those vendors who had a strong on premises MIS product that then tried to move to the cloud, not the new entrants disrupting the market with their cloud-first products.(3)

I would guess they are trying to tread a line between their customers, the CMO, and their shareholder. As for how your would prove that you had considered taking up the break clause... well if you really were considering it seriously there would be an email/minutes from meetings between at least some of IT / Data / Senior Management / Finance / Governors, I would imagine an email with a cost model and a proposal, and an email saying "we don't have time" would do.

Harsh. More-or-less unenhanced since 2012 perhaps would be more accurate. If the general SIMS user was prepared to put up with a dramatic change, then more schools would already have left. But they aren't, the user base is conservative, and a big new UI would be missing features that some depend upon, and nobody would be happy. Eventually other factors overcome this reluctance to accept change and schools seek alternatives. I don't believe I am mistaken in saying that no major MIS has successfully redesigned its UI and architecture and remained dominant since the SIMS ->SIM.NET transition in the 2000's. Bromcom might be a contender, depending on whether you believe its MIS to be a new product or a revision of its earlier on premises eSchool suite of products - but back then you would struggle to have called that suite a 'major' MIS. Home unfortunately, you will see innovation and change slow again as more people use the alternatives, to the point that new SIMS might start having to be innovative, wouldn't that be a turn up for the books!

"looks too good to be true" I haven't clicked the link or googled, but there is an axiom involving these very words.

In my experience, the problem is not related to phones, people just don't look. I am glad the change has raised awareness - the behavior around busy turning/crossings has improved dramatically since this surfaced in the national discourse. Even the worst people crossing at junctions now think "ooh. do i have right of way here? Yes!" and then stop to look around to check to see if they get to exercise their right.

Not sure if you are referencing to my fist or second points. On the first point, I conceded that I escalated to "must" when the text did not support that, consider it instead to be shorthand for "wait or risk getting run over because fast moving vehicles might not actually stop in time, and whose fault it is will be somewhat moot - you're still run over". On the second I perhaps used prohibition a little more loosely than many would, but SHOULD NOT is still a prohibition, while MUST NOT is a legally enforceable one. If you choose to undertake an action you have been advised that you should not, then it will be up to you to defend that decision should the matter end up in a court. edit: Also I used the phrase "right of way" which is also explicitly incorrect, and priority is the correct term.

"At a junction you should give way to pedestrians crossing or waiting to cross a road into which or from which you are turning" and "If you have to step into the road, look both ways first... ...Always show due care and consideration for others" "At a junction. When you are crossing or waiting to cross the road, other traffic should give way. Look out for traffic turning into the road, especially from behind you, and cross at a place where drivers can see you. If you have started crossing and traffic wants to turn into the road, you have priority and they should give way (see Rules H2 and 170)." My reading of that is that, when there is traffic, pedestrians need to come to a complete stop before proceeding, otherwise they were never 'waiting'. They can't just walk out ignoring the already moving traffic on the road. If a vehicle is in motion and arrives at the junction roughly at the same time as you, it is not going to be able to stop safely, you must wait until it is safe to cross. Once you are waiting you get the right of way, and other vehicles must now stop to let you cross. My personal favorite improvement are these two. "You should not cut across cyclists, horse riders or horse drawn vehicles going ahead when you are turning into or out of a junction or changing direction or lane, just as you would not turn across the path of another motor vehicle. This applies whether they are using a cycle lane, a cycle track, or riding ahead on the road and you should give way to them" "...Take extra care at junctions. You should... ...remain behind cyclists, horse riders, horse drawn vehicles and motorcyclists at junctions even if they are waiting to turn and are positioned close to the kerb" Which means motor vehicles are explicitly prohibited from overtaking and then cutting up horses/cyclists through junctions.

To answer your specific question though, we have a web.config file in that folder. (this post was delayed because cloudflare prevented me from posting anything after the above yesterday. Thanks @localzuk and @Dos_Box helping me out!)

This is definitely the sort of problem I'd burn £220 on with a call to Microsoft Support. That said I have a horrible feeling this is related to the DCOM changes that occurred recently.

If you did one switch at a time, why would it fail over, and if it did why would that be a bad thing? If active-active it should just keep chugging along in a degraded state. If passive/active then move the active unit first and it fails over through backup/passive unit until the move of the first unit is complete? Or am I missing something (never run a cluster, so genuinely curious)

Just pinging this back up - the clock is ticking!

While the app should definitely be the primary go-to in this scenario, in the interests of resiliency through diversity getting registers etc onto paper is important. I'd have thought papercut could be configured to have an queue usable in emergencies that over-rides all charging options and just lets the job print. Also when I last did this (back when winfolder was a thing) we sent the emergency registers to two printers at either end of the building, so in the event that the incident had already taken out the school office, another the office could take over.

Wow. Some people really do just want to watch the world burn.

Large school so it's quite a few classes. Salamader/SDS provisions new ones anyway, they just ignore them and reanimate the archived class. We rename provisioned classes where we know they will be required multi-year. This is to ensure everybody can identify them quickly and differentiate them from the disposable year-by-year classes.

Here, for multi-year coursework heavy courses staff re-use last years classes. For everything else they use that years new classes, and re-use only occasional bits and bobs from archived classes. Though I am talking about Salamander/Teams rather than Classroom, but I imagine the broad principle remains.