Since Windows 10 doesn't include an XP mode, is it possible, on a new PC that includes a Windows 10 OEM licence with Windows 7 downgrade rights, to install Windows 10 and then install Windows 7 as a virtual machine under Windows 10? And then use XP mode within the Windows 7 virtual machine.

Or to put it another way, does the OEM licence allow you to install both Windows 10 and Windows 7 on the same machine (one as a virtual machine), or can you only install one or the other.

Failing that, what are the alternatives for licencing a Windows 7 or XP VM on a Windows 10 PC?

I've never understood Windows licencing.

@scottalanmiller said in Cyber Security Business:

A potential customer is a potential customer because they know that they are likely crap, though.

Really? Maybe I'm not their target market.

@FiyaFly said in Cyber Security Business:

I would change the wording on this to "...Small businesses don't always have the budget for sufficient security to prevent these attacks"

I know a one-man IT shop or two who might take offense to that original wording.
Marketing. Saying the same thing as the other guy, but saying it better.

Me to.

It currently says "Many small companies skimp on cyber security because of costs. " and "Small business generally have little to no security. "

This might be true (not in my limited experience, but it might be), but aren't you at risk of offending your potential customers by making the claim? Kind of "we think you're probably crap, so employ us"

@guyinpv said in Suggestion for decent, free, ticketing with simple needs?:

I already have an account on Freshdesk which is an actual ticketing system, but I have it set up more for public support at our ecommerce, not internal tickets.

Can you not just create another Freshdesk site and use that?
So have:
https://mysite1.freshdesk.com (public)
https://mysite2.freshdesk.com (internal)

@JaredBusch said in Email query:

I'm on the road in posing

I'm now picturing you getting photographed for Victoria's Secret on a highway somewhere.

It sounds fairly straightforward.

Oh, ok. I was just following the instructions that @JaredBusch linked to about creating a connector. So you configure Postfix to login in to O365 with a username and password? Nothing needs to be done on O365? Is that simple to do?

@scottalanmiller said in Email query:

And if you run the relay in house, it's free.

Hardly free. Roughly how much would you expect an MSP to charge to install, manage, support and patch an on-premise mail relay?

I'm still not sure about the purpose of using a relay. You still have to create a connector in O365 to accept mail from the relay. And you still need to put restrictions in, either by IP address or by a certificate on the relay. So what difference does a relay make compared with just having the application use the connector directly, as suggested by @JaredBusch? The relay seems redundant here.

A domain is about 10 bucks a year!

Then use a different domain, as I suggested earlier. Or whitelist by IP address. Which is really more or less the same as your instructions for creating a connector. You're just allowing non authenticated connections to bypass any filters.

I'm not suggesting Direct Send as a solution, by the way. I'm just questioning why it would fail.

Yeah, they also say:

Limitations of direct send
Your messages will be subject to antispam checks.
Sent mail might be disrupted if your IP addresses are blocked by a spam list.
Office 365 uses throttling policies to protect the performance of the service.

I'm making the assumption that IP address isn't blocked by a spam list and that throttling policies won't feature. Normal antispam checks can be mitigated by whitelisting the domain and adding an SPF record.

@Dashrender said in Email query:

@Carnival-Boy said in Email query:

Then you could use a different domain address.

Sure, as long as you don't get bit by those other things that Scott mentioned. O365 will be doing pretty much all of them to protect it's uses against spam.

I guess what I'm talking about is Direct Send. Microsoft used to recommend this approach with O365. Are you all saying this is no longer supported, or it is just very unreliable?

@scottalanmiller said in Email query:

• SPF records are sometimes required.

You can create an SPF record for the IP address of the application sending the e-mail.

Then you could use a different domain address.

@scottalanmiller said in Email query:

But with modern security, that's never realistically possible.

Why not?

If I want to send an e-mail to @bishnitro I can just make an SMTP connection to his server and send him an e-mail, can't I?

Why do they need to authenticate to send an e-mail to someone in their organisation?

@bishnitro said in Email query:

we are using office 365 and it doesn't work on it, so we are looking for alternative.

Why doesn't it work?

@Dashrender said in The MSP Model fails more often than not.:

The rub is most SMBs are just cheap - aren't willing to put the expenses where perhaps they should be, and instead cheap out, hense so many of the posts we have at SW.

I can only really speak from personal experience. My company pays for several different IT companies to support us (MSPs etc), so we get training, and we get access to many different IT experts to help, support, and advise us. We don't run internal IT because we're cheap.

@scottalanmiller said in The MSP Model fails more often than not.:

How does the internal IT people get that knowledge in a way that the MSP would not do identically? Two people, same role, same seat, same business - they'll get the same business knowledge.

And why wouldn't internal IT get the same IT knowledge that the MSP would - two people, same role, same access to MSPs for advice, help and training. You just seem to keep going round and round saying MSPs are better but not really explaining how. On the one hand you say MSPs are different (and so better), on the other hand you say MSPs are exactly the same (as so no worse). It's like having your cake and eating it. If you can only see upsides to MSPs and no downsides, then I can't really say anything else, I'm afraid.