Yeah, sorry misread you where looking for how to do it from windows that why I added the exe 😃

@JaredBusch said in dbeato why are you migrating from Hyper-V to XCP-ng:

@DustinB3403 said in dbeato why are you migrating from Hyper-V to XCP-ng:

@JaredBusch I agree, Olivier's business model is the difficult part to look past.

XOA was a great tool from what I could tell with all the conversations here. But the price structure was something discussed quite a bit.

Which is why I exclusively use XOCE. $6000 a year isn't cheap for the highest teir of support and functionality.

@dbeato said in Windows 10 IOT Enterprise:

@dafyre said in Windows 10 IOT Enterprise:

@Dashrender said in Windows 10 IOT Enterprise:

Though - now that I think about it - does IOT require activation? I thought it was free?

If there is an enterprise version of IOT - I have no clue

In my reading, Windows 10 IOT will attempt to activate (nor will it complain) if you never connect the device to the internet. Of course, once you connect it, it will try to activate.

Interesting, I didn't understand this part

By default, KMS clients on your Windows IoT Enterprise with no additional configuration needed.

It will act like a regular desktop and activate against your KMS server if you hook it up to the network.

@dyasny said in Virt-manager: IDE disks:

@scottalanmiller said in Virt-manager: IDE disks:

They need to just get off of my lawn.

LOL, funny how I'd never have understood the joke before moving to NA and buying a house 🙂

HAHAHA

@scottalanmiller said in New Infrastructure to Replace Scale Cluster:

So if a VM dies, oVirt will provide non-FT failover, yes. And by having failover you might achieve HA. And oVirt is a critical part of making that possible. But it itself isn't HA, nor does it guarantee HA. It's just a failover component that you can use to "do" HA.

It's a component you buy (well, this one is opensource, but still), part of a solution that would cover other potential failure points. The solution in general is also something you can buy, in order to achieve a certain level of HA for those VMs

Worth the try checking it @dbeato thanks, will try it once I can remote back into the machine today

@DustinB3403 said in Sound Eklin TruDR eSeries - Error Opening Receptor 106:

@scottalanmiller said in Sound Eklin TruDR eSeries - Error Opening Receptor 106:

@DustinB3403 We did 😉

Gotta check every now and then. 😄

Someone has to ask the stupid questions. It was me the other day.

@scottalanmiller said in Replication Options for KVM to DR Site:

But that was my point, what's considered a reasonable, rational risk scenario to an invest bank sounds to normal people to be similar to meteor level extinction events. Hence why the "backups have to cover everything possible" rule can't work, even if you add the caveat of "within rational scope", it is clear that Fortune 100 rational is SMB crazy. And what is F100 crazy, is still Wall St. rational. And what is Wall St crazy, is big government rational.

Backups shouldn't stop being backups based on the impression of rational scope. A backup is a backup, the scope that it covers is its coverage scope. Otherwise no SMB's backups would be a backup to the enterprise, for example. But the viewpoint of the observer should not be the determination of what is or isn't a backup, but rather an intrinsic property of the backup itself. Otherwise, you force a crazy scope to happen and someone mentions meteors - which was my point.

Lets agree on DR solutions being able (or striving to at least) cover disasters of whatever the scoped level is for a given business. With this in mind, avoidance techniques still have to target specific errors, while recovery solutions cover data loss from all of those, plus any other failure (within the scope, yes. Nothing will cover the failure of Earth remaining a livable planet).

@IRJ said in Splunk vs iptables:

iptables -A OUTPUT -o eth0 -p tcp --sport 9997 -m state --state NEW,ESTABLISHED -j ACCEPT

Looks like the solution was
iptables -A INPUT -i lo -j ACCEPT
iptables -A OUTPUT -o lo -j ACCEPT

Or at least that got it working. 🙂

Great question actually. I don't use hyper-v much.

I am using version 2.4.0 and have an issue too, see below
f1fb6632-3fda-41fe-a529-0f397de63cf2-image.png
and this
13428c66-1c84-4ac7-94b9-5b887c659d5f-image.png

@FATeknollogee the install itself has been covered too many times to mention 🙂 Maybe if he runs into a specific issue and solves it, that would be a good thing to share

@gjacobse said in Add a User to Remote Desktop Users in Windows Remotely:

I seem to remember doing this via ScreenConnect CMD

Only works if SC is installed, which if it was, we'd not need to do it 🙂

Well I tried maintenance mode - out of service for 10 mins, then back on - no go.

I put the password back into the system - bam.. damn thing is registering again. 😞

If you want to play around with different OSs you should try for example:

Qubes OS (safety OS where everything is run in VMs) TinyCoreLinux (extremely small, low resource desktop OS, ~11 MB) Lubuntu (light weight desktop OS based on LXDE, suitable for older hardware) LinuxFromScratch (if you want to roll your own linux) FreeBSD or OpenBSD (if you want to try some BSD)

@JaredBusch said in WordPress admin page redirecting to IP:

Is the site URL correct in the settings

Been there many times :angry_face:

@maximus said in Restaurant Purchasing System:

@travisdh1 said in Restaurant Purchasing System:

@maximus said in Restaurant Purchasing System:

@WrCombs said in Restaurant Purchasing System:

@maximus said in Restaurant Purchasing System:

@WrCombs said in Restaurant Purchasing System:

@maximus said in Restaurant Purchasing System:

Hi,

Anybody here using restaurant purchasing system? what purchasing system are you using?

What are you looking for exactly - Restaurant Purchasing Systems - What does that mean exactly?

the system will document the food items that will be bought. it will also keep track of history requisitions. some system are attached to the inventory system. but we are just looking for a purchasing system for now.

oh you're looking more to track inventory?

not yet inventory, just purchasing system. inventory systems are a nightmare.

FTFY

So the usual inventory is - you buy 100 pcs, the users will dedect 1 pc when they use it. Now on food, you buy 1 box of cooking oil, the box has 12 cans inside, the user will use 200 grams. So you need to swim on a freaking conversion table from box to grams. LOL.

That's how most businesses making an actual product operate. How you receive raw materials never matches the widgets leaving the door (or kitchen in your case.) Thus why I say all inventory systems are a nightmare.

@Jimmy9008 keep in mind that resulting availability and risk aren't the same thing. Any five nines system is expected to hit six nines nine out of ten years. It's the average over the operating lifespan, not over a set interval. Otherwise any normal interval that you select would have 100% uptime.

So there are two ways to look at it reasonably...

Resulting Availability Over Operational Lifetime Expected Availability Over Operational Lifetime

The first is what an individual system actually provides. The second is the average of all systems configured identically, over all of their operational lifetimes.

The first you measure. The second you project with simulations.

In extremely large systems, like BackBlaze, they get close approximations to the later through measurement because they look only at small components (like hard drives) of which they have substantiation numbers to create a reasonable approximation to a full number.

When I was on Wall St., we had 80,000 servers in our pool and so we had actual risk and availability numbers for the industry in datacenters like ours. But it still only told us about a handful of server models, and only under our exact conditions. And it still took a decade or more to produce meaningful numbers, and those numbers only applied to the servers of the past, not the ones being installed new.

I would recommend to use the UEFI PXE Boot and that any UEFI boot settings on the devices to be deployed have UEFI settings enabled, including the UEFI Network stack (At least on dell devices).

For testing I always run a VM to test my deployments before using on a Desktop and prepare it as much as I can and then deploy it to the devices. It helps to add all the drive packs from the Hardware Manufacturer (Say Dell, HP and so forth).
Dell
https://www.dell.com/support/article/us/en/04/sln312414/dell-command-deploy-driver-packs-for-enterprise-client-os-deployment?lang=en
HP
http://ftp.hp.com/pub/caps-softpaq/cmit/HP_Driverpack_Matrix_x64.html
http://ftp.hp.com/pub/caps-softpaq/cmit/HP_Driverpack_Matrix_x86.html
Lenovo
https://support.lenovo.com/us/en/solutions/ht074984
Acer
https://www.acer.com/sccm/
Microsoft
https://docs.microsoft.com/en-us/surface/deploy-the-latest-firmware-and-drivers-for-surface-devices

With Pre-Staging machines you need to rely on adding the device mac addresses manually or use Microsoft AD to add them with a Script or Manually to be ready to WDS. This makes it that you can add the devices before hand and only those devices will get the deployment. However you can setup an specific network or VLAN to have the WDS

For Multicast, I like this article
https://specopssoft.com/blog/wds-multicast-configuration/
However I like the option to disconnect the clients when their speeds go way low and then go unicast instead of multicast. Multicast makes sense that way that way the slow clients do not slow the faster clients.

I am still not sure why MDT is not being implemented but that is for another post.

@fuznutz04 said in FreePBX and DNS settings:

@scottalanmiller said in FreePBX and DNS settings:

@fuznutz04 said in FreePBX and DNS settings:

@Scott says not to set it. You say to set it to 127.0.0.1 and the Vultr DNS.

No, Scott says he doesn't use it, not that you shouldn't. Not the same thing 😉

But doesn't this just write it to the /etc/resolve file anyway? I could set DNS statically via the file, but I'm still unclear what the best practice is for FreePBX in regards to DNS.

To not fuck with it unless you have a reason to.

FreePBX is an appliance. A software appliance, but an appliance. You don’t fuck with it under the hood unless you have a good reason to do so.