Hazmat would have been there anyway

Have you run the usual checks like sfc /scannow repeating until it comes up clear, DISM (I forget the switches) and chkdsk /r also until it comes up clear?

It is Windows after all.

I'm thinking that you want the firewall turned on. Not sure. I'm out. Good Luck

@WrCombs File & printer sharing, firewall rules setup / enabled, network discovery, windows managed homegroup is bumpkis crap, file sharing wizard isn't all that great either.

Can you ping by name? Not the share, the host

@DustinB3403 said in Why IT Builds a House of Cards:

@scotth said in Why IT Builds a House of Cards:

@DustinB3403 Remember to answer the air gapped phone in the bottom right drawer.

What?

Same geometry teacher would take out the rubber chicken, beat it on the desk and then pretend to answer the deskphone in his bottom right drawer. All I can say it that it got our attention.

@DustinB3403 Remember to answer the air gapped phone in the bottom right drawer.

Try the rubber chicken. Worked for my geometry teacher

Well, as @DustinB3403 said, windshield time.
You could have the site power cycle the switches and zone router / firewall if the credit/debit processor makes you use one.

EDIT: If you have any dumb switches in the mix, I'd power cycle them 1st and last.

Wow. Event viewer, address conflict, check the metrics if two NICs, restart. That's most of the list. It looks like you've checked the boxes.

@WrCombs And gateways?

In most cases when I've dealt with POSs, the addresses to all devices are known. If nothing else, check to see if it's autoassigned. That's a good starting point for one way communications when one adapter is public.

Odd that you can remote in to a public network. Someone has permissions set to allow on public. Have you checked to see if it's setup to an autoassign address? If so, do the diagnose to get an address or static address the thing.

@scottalanmiller said in Comparing MeshCentral 2 to ScreenConnect:

@scotth said in Comparing MeshCentral 2 to ScreenConnect:

@Ylian said in Comparing MeshCentral 2 to ScreenConnect:

@scotth Note that MeshCommander is built into MeshCentral. Once you get MeshCentral running, click on a device and if it has Intel AMT, you will see a "Intel AMT" tab. The content of that tab is MeshCommander.

If you just want a Intel AMT console and connect to AMT devices on the local network or using a VPN, use MeshCommander. If you want a more completely management solution with AMT support included use MeshCentral.

Hope it helps.

That's clear. We have over 20 sites on VPN and will follow your advise.
Thanks

That's what I was thinking, just one central machine.

It keeps getting sweeter. Unfortunately, I had to power down and backup my installation from March. I added drives to our hosts and will be able to spin it back up.

And as luck would have it, ..... Windshield Time.

@Ylian said in Comparing MeshCentral 2 to ScreenConnect:

@scotth Note that MeshCommander is built into MeshCentral. Once you get MeshCentral running, click on a device and if it has Intel AMT, you will see a "Intel AMT" tab. The content of that tab is MeshCommander.

If you just want a Intel AMT console and connect to AMT devices on the local network or using a VPN, use MeshCommander. If you want a more completely management solution with AMT support included use MeshCentral.

Hope it helps.

That's clear. We have over 20 sites on VPN and will follow your advise.
Thanks

@scottalanmiller said in Comparing MeshCentral 2 to ScreenConnect:

@scotth said in Comparing MeshCentral 2 to ScreenConnect:

Not extra. These sites have a site controller PC for the POS with a management port and a camera PC also with a management port. I expect that we'll be adding more remote sites in the coming years and if it's available to move to MeshCentral/MeshCommander, then why not. Even the larger sites only have 5 or 6 cameras

You had mentioned moving to single devices, but if you can access remotely, why not "no" devices?

Vended POS, camera PC to reduce data across the VPN, UPS for local, non-fuel delivery equipment electrically isolated from the remainder of the site.

@scottalanmiller said in Comparing MeshCentral 2 to ScreenConnect:

@scotth said in Comparing MeshCentral 2 to ScreenConnect:

@scottalanmiller said in Comparing MeshCentral 2 to ScreenConnect:

@scotth said in Comparing MeshCentral 2 to ScreenConnect:

Since we have so many sites with so little at some of them, it would benefit us to be able to move more to single devices that do more than one thing.

How does that play in to these tools?

If we get the onboard management, ie. VPro or whatever flavor, we then have the ability to power cycle equipment at isolated sites since we are, by law forbidden to have all of the equipment on UPS's (designated explosive environment). If we can get eyes on site, even without access to the control room at the site, we can get the go ahead to power cycle, in this case, via onboard management if needed. The interface makes it really convenient -- single pane of glass and all that.

That's why you want remote access. But why extra equipment per site?

Not extra. These sites have a site controller PC for the POS with a management port and a camera PC also with a management port. I expect that we'll be adding more remote sites in the coming years and if it's available to move to MeshCentral/MeshCommander, then why not. Even the larger sites only have 5 or 6 cameras.
Btw, we have and have always had remote access to all of our sites.

@scottalanmiller said in Comparing MeshCentral 2 to ScreenConnect:

@scotth said in Comparing MeshCentral 2 to ScreenConnect:

Since we have so many sites with so little at some of them, it would benefit us to be able to move more to single devices that do more than one thing.

How does that play in to these tools?

If we get the onboard management, ie. VPro or whatever flavor, we then have the ability to power cycle equipment at isolated sites since we are, by law forbidden to have all of the equipment on UPS's (designated explosive environment). If we can get eyes on site, even without access to the control room at the site, we can get the go ahead to power cycle, in this case, via onboard management if needed. The interface makes it really convenient -- single pane of glass and all that.

@scottalanmiller said in Comparing MeshCentral 2 to ScreenConnect:

@scotth said in Comparing MeshCentral 2 to ScreenConnect:

I scanned the docs and didn't see where I might see if I can run meshcentral 2 and meshcommander on the same device or vm. Am I missing something obvious?

I had the impression that Central 2 was on the path to replace Commander as it is integrating those features, I believe.

That'd be cool. I did watch a couple of videos and during the session, he pointed MeshCentral2 to the MeshCommander install.

Since we have so many sites with so little at some of them, it would benefit us to be able to move more to single devices that do more than one thing.

I scanned the docs and didn't see where I might see if I can run meshcentral 2 and meshcommander on the same device or vm. Am I missing something obvious?