Also Windows and IIS is a different ballgame. I would look at this guide
https://weblog.west-wind.com/posts/2016/Feb/22/Using-Lets-Encrypt-with-IIS-on-Windows
Also Windows and IIS is a different ballgame. I would look at this guide
https://weblog.west-wind.com/posts/2016/Feb/22/Using-Lets-Encrypt-with-IIS-on-Windows
@alesribic said in MeshCentral LE production cert:
@scottalanmiller I have set all as described in manual. Port 80 is open port 444 for SLL is also open
letsdebug.net shows green. But no certificate is created. Is there any log?
BTW: i have windows installation
Should be port 443 not 444
Maybe just dump that bad theme all together.
@DustinB3403 said in Joining 2 Windows 10 Machines:
@IRJ said in Joining 2 Windows 10 Machines:
If they had some valid reason why they couldnt just install the tools the need on one installation,
I've dealt with software that is bound of the serial of the CPU it's originally installed with/on in the past which would make this nearly impossible to move without involving the software vendor (but maybe you could go the other way with it).
In any case, there are valid reasons to need multiple installations accessible from a single footprint. (it's a benefit of virtualization and or dual-booting today).
But we're just speculating at this point.
Yeah I agree about virtualization, but I can't see a valid use case for dual boot with all the negatives it provides
@scottalanmiller said in Joining 2 Windows 10 Machines:
Another option.... avoid licensing issues by using a single OS install and making two user profiles instead.
I cant think of many scenarios where this isnt the answer.
If they had some valid reason why they couldnt just install the tools the need on one installation, then I think virtualization is the only try solution. Dual boot causes so many issues, because it isnt manageable on the network. Another huge disadvantage of dual boot is a loss in productivity. You have to run updates on two devices and dual booted system cannot run updates when it isnt booted.
@scottalanmiller said in Joining 2 Windows 10 Machines:
Another option.... avoid licensing issues by using a single OS install and making two user profiles instead.
I already said that
@Kelly said in Art applications:
@IRJ said in Art applications:
@Obsolesce said in Art applications:
Never heard of any of those except gimp.
Inkscape and Blender are very popular ass well
Freudian slip?
@Obsolesce said in Art applications:
Never heard of any of those except gimp.
Inkscape and Blender are very popular ass well
Isn't edge chromium based now? I'd be pushing that over IE for use.
@JaredBusch said in Fedora 30 Server Cron not included by default:
@RojoLoco said in Fedora 30 Server Cron not included by default:
@DustinB3403 said in Fedora 30 Server Cron not included by default:
Also why would someone downvote a question, looking at your @JaredBusch.
Whose @JaredBusch ? I didn't think he was owned by anyone...
Is this company publicly traded?
Seems like a blatant misuse of resources
@DustinB3403 said in How to possibly download older version of Windows 10:
@RojoLoco said in How to possibly download older version of Windows 10:
@DustinB3403 said in How to possibly download older version of Windows 10:
@Dashrender said in How to possibly download older version of Windows 10:
https://winaero.com/blog/download-windows-10-version-1809-iso-images-directly/
This link walks you through tweaking Chrome on MS's page to look like you're using an iPAD Pro to download 1809 or 1903 directly.
This would circumvent the EULA, no?
Are you constantly looking over your shoulder for the dreaded Microsoft police? And can you say that 100% of the MS licensing at your job and home are totally legal and compliant to their EULA? I've literally never seen anyone so concerned with MS licensing.
At home I am 100% compliant, where I work is another story as I don't manage it here and thus don't care.
@Pete-S said in AWS Catastrophic Data Loss:
@IRJ said in AWS Catastrophic Data Loss:
@dbeato said in AWS Catastrophic Data Loss:
@PhlipElder said in AWS Catastrophic Data Loss:
@dbeato said in AWS Catastrophic Data Loss:
@PhlipElder said in AWS Catastrophic Data Loss:
@Dashrender said in AWS Catastrophic Data Loss:
@BRRABill said in AWS Catastrophic Data Loss:
because the chances that MS's DC is going to blow up is extremely small
And yet, it is what this thread is about ... exactly that happening.
Except that it's Amazon, not MS.
MS was US Central this year or late last.
MS was the world when their authentication mechanism went down I think it was a year or so ago.
MS was Europe offline with VMs hosed and a recovery needed. Weeks.
MS has had plenty of trials by fire.
Not one of the hyper-scale folks are trouble free.
Most of our clients have had 100% up-time across solution sets for years and in some cases we're coming up on decades. Cloud can't touch that. Period.
And no updates correct right? to have 100 % Up-time you must never do updates.
In a cluster setting, not too difficult. In this case, 100% up-time is defined as nary a user impacted by any service or app being offline when needed.
So, point of clarification conceded.
Yes, I know you could do a cluster and that's how Cloud Providers give you that 99.9% up-time or SLA. Right now it is hard to believe no one has any issues, if cloud providers in a large scale have issues then smaller companies do have them as well. That said, no cloud provider provides any backups for anyone unless you set them up either through their offering or your company.
Yeah and you can only fault yourself, if you are one AZ that fails. Most serious deployments are in different regions as well.
Well, except that:
@Pete-S said in AWS Catastrophic Data Loss:
As we have further investigated this event with our customers, we have discovered a few isolated cases where customers' applications running across multiple Availability Zones saw unexpected impact
At some point, you have to be willing to accept some risks by by not using a different region, generally the risk is VERY, VERY low which is why many customers use AZs.
You have to do risk anaylsis, and see how often these events occur and how likely you would be to be one of the "few" that were impacted.
You can dig in the weeds all you want, but across multiple regions this wouldnt have happened. Which is true HA
@Pete-S said in AWS Catastrophic Data Loss:
@IRJ said in AWS Catastrophic Data Loss:
@dbeato said in AWS Catastrophic Data Loss:
@PhlipElder said in AWS Catastrophic Data Loss:
@dbeato said in AWS Catastrophic Data Loss:
@PhlipElder said in AWS Catastrophic Data Loss:
@Dashrender said in AWS Catastrophic Data Loss:
@BRRABill said in AWS Catastrophic Data Loss:
because the chances that MS's DC is going to blow up is extremely small
And yet, it is what this thread is about ... exactly that happening.
Except that it's Amazon, not MS.
MS was US Central this year or late last.
MS was the world when their authentication mechanism went down I think it was a year or so ago.
MS was Europe offline with VMs hosed and a recovery needed. Weeks.
MS has had plenty of trials by fire.
Not one of the hyper-scale folks are trouble free.
Most of our clients have had 100% up-time across solution sets for years and in some cases we're coming up on decades. Cloud can't touch that. Period.
And no updates correct right? to have 100 % Up-time you must never do updates.
In a cluster setting, not too difficult. In this case, 100% up-time is defined as nary a user impacted by any service or app being offline when needed.
So, point of clarification conceded.
Yes, I know you could do a cluster and that's how Cloud Providers give you that 99.9% up-time or SLA. Right now it is hard to believe no one has any issues, if cloud providers in a large scale have issues then smaller companies do have them as well. That said, no cloud provider provides any backups for anyone unless you set them up either through their offering or your company.
Yeah and you can only fault yourself, if you are one AZ that fails. Most serious deployments are in different regions as well.
Well, except that:
@Pete-S said in AWS Catastrophic Data Loss:
As we have further investigated this event with our customers, we have discovered a few isolated cases where customers' applications running across multiple Availability Zones saw unexpected impact
They didnt say regions though