So with further testing, a restart is required if the user is using their system, otherwise they'll continue to get the notifications.

@Obsolesce said in Generating a list of Software to Reinstall on Windows 10: @dbeato said in Generating a list of Software to Reinstall on Windows 10: @Obsolesce said in Generating a list of Software to Reinstall on Windows 10: @scottalanmiller said in Generating a list of Software to Reinstall on Windows 10: @Obsolesce said in Generating a list of Software to Reinstall on Windows 10: @scottalanmiller said in Generating a list of Software to Reinstall on Windows 10: @Dashrender said in Generating a list of Software to Reinstall on Windows 10: @gjacobse said in Generating a list of Software to Reinstall on Windows 10: @Obsolesce said in Generating a list of Software to Reinstall on Windows 10: I usually just copy/paste a Chocolatey install command that does it all at once. Everything else is on separate media that requires no install. Example, copy over games, import them in... such as into Steam. I was going to mention... with Chocolatey tool choco list -lo just pipe it to a text file. But that only gives you things installed through Chocolatey. Dustin's OP gives you everything installed through the normal Windows installer process (and registers the install). I recall when chocolatey didn't use the windows installer process for everything - things are much better now. It is package by package. Lots of things, through Chocolatey or not, don't use the Windows installer process. I've not seen Chocolatey not register software installs in Windows, ever. I have. Many times. Most of the time I think that it does, but it is not Chocolatey that does it when it does. With what software specifically? Try installing Sysinternal tools, it will not register at all, that is one example. You can do so with Chocolatey. I never installed that stuff anyways. That Chocolatey doesn't is nothing new. I thought you wanted to know which applications would do that, but I guess I read wrong.

Yep, setting protected-mode to no did the trick. SELinux was re-enabled and stuff works. Now the question is can I get stuff to work with the most current version of Redis and on Fedora.

Skype for Linux (beta) has a 'normal' feel to it,.. really looks just like the Windows Version

@Dashrender said in Office365 Direct Send without Relay: @JaredBusch said in Office365 Direct Send without Relay: For only basic email traffic needs like scan to email, just setup a connector in Office 365. Exchange Online has various rate limits though. So if you think you will be even close to them, use postfix locally to send out and just add your local WAN IP to your SPF record. Why wouldn't your local relay still relay everything through Hosted Exchange in O365? or would that be rate limited as well? Exchange Online has limits. it does not matter from where the email originate. The software was actually setup to authenticate and send email directly with and Exchange Online account during testing. This quickly hit the rate limits as the client was sending out large amounts of price notifications to users that has signed up for such. So this site had a local CentOS 7 box setup and Postfix was configured to send mail out. The SPF record was updated and then a connector was also setup to make sure nothing was blocked for no reason.

@dafyre said: @scottalanmiller said: @dafyre said: @scottalanmiller said: Yeah, some definitely will. I wonder what that will do against Virtualization platforms like XenServer, VMware, et al... if an lxc-container is functionally equivalent to a VM... Would it be possible to run Windows in an lxc-container... That type of thing. No, we've had those containers for a decade and we are nowhere near having Windows in them. They all share the parents' kernel by definition. So no Windows coming on Linux containers. Much closer to PV Windows on Xen, at least that has been done in a lab. What about Containerization on Windows? Didn't OpenVZ or Virtuozzo...used to offer something like that? You can, in theory, make Windows containers on Windows. But you have to be on Windows already.