201–210 of 269 posts
Earlier quoted context omitted.
Interesting, I found the opposite. My MS office doesn't even have 'export to PDF' and Libre has it.
Sounds like you're comparing a 10 year old Office version to a current LibreOffice version.
Earlier quoted context omitted.
Windows has done this forever with enabled apps like SCCM. I think it was released in 2008. It allowed us to remove hundreds of local depot servers unless there was an SLA on reimaging.
Yes, but you needed to configure that. This comes enabled by default. And on Windows Home/Pro, it downloads updates from third-parties on the internet too.
What's the problem? I guess it still receives the hashes signed from Microsoft.
Earlier quoted context omitted.
I switched about 10 years ago. Before that I was windows 100% on desktop. I had similar issues at first but gradually became pretty comfortable with Ubuntu and Linux in general. Some things are more of a pain and may always be in Linux but overall the experience for me has been that things have been getting easier with time. I think that for better or worse as more applications move to the web the change will be easi…
I don't mind the questions at all. I hope you didn't want the TL;DR version. Some of my pain points. Many probably have solutions, but I'm stuck between spending time dealing with it the way it is, and spending time finding a solution. These are not in any particular order: 1. Serial communication(terminal, for interfacing with console ports). I tried a few programs that didn't really work right away, and settled on…
1) sounds definitely like a permission problem. Is your user member of the dialout group? If not, add it there, re-login and try again. You should not be forced to use the root user.
2) Exchange is a problem. There are several solutions, none of them is all that great: a) use Evolution, b) use Thunderbird with the proprietary plugin, c) use a proxy like davmail (davmail.sf.net).
3) There is Earth Pro for Linux too, it just isn't advertised. After installing the regular Earth, it will install also a repo for updates. Check what else is there in the repo - in the .rpm repo, there is the pro version. It has some bugs though - every time I try to use GPS tracing, it crashes.
5) Most distribution have a utility to make a boot drive. There are also other ways. If you intend to boot via UEFI, there's no need for special utilities to make the USB key. Just copy the iso content to the USB stick, on FAT{16,32}-formatted partition. If the UEFI bootloader can find the EFI directory in the root and it's content, it will boot fine.
This will not work for some windows editions, thought. For example, Windows 2012R2 has install.wim larger than 4 GB, so it won't fit on a FAT filesystem.
6) Do not fight the NetworkManager with ifconfig. If you want to use NetworkManager (and you want, if you use wifi, wwan, etc), change the IPs with nmcli. It's command line interface to the NM, so it will take note of this change and it won't cause difference between what the config files say and what is the reality on the interfaces.
Earlier quoted context omitted.
I didn't event understand why people use Excel. There's no ERP software in this company? Excel teach bad habit about having list every where not maintained.
Because it's the best spreadsheet software out there. It really is first-class, and LO Calc has a lot of catching up to do (and they are quite aware of this). My theory is that Excel's userbase includes the guys who actually sign the cheques , so MS has to get it right.
Due to lack of other tools, people learned to do absolutely crazy things with the Office - from saving screenshots in the Word files to drawing in PowerPoint.
Earlier quoted context omitted.
I went through the same thing last year. I spent two months trying to plug all the holes in the enterprise version, for a medium sized healthcare client, and eventually gave up. The LTSB edition looks promising but I haven't put it under the microscope yet.
From what I've heard from people running LTSB it's absolutely awful. Driver support is abysmal and lots of desired Windows features don't exist on it. There's apparently some new LTSB on its way but this aside it is not the panacea this thread makes it out to be.
Earlier quoted context omitted.
Windows pain costs few hundred $ more :)
Only if your time is worthless.
Earlier quoted context omitted.
> Using proprietary operating systems because Linux isn't there yet is a great way to keep Linux from getting there. It's a chicken and egg problem. What would you prefer: getting your privacy thourougly invaded by a proprietary operating system, or being there to help Linux gain market share and tip the scales? Even if it's not perfect, it's more than enough, and supporting it is the best choice. The vast majority o…
I used to study with a guy that openly said "Linux is only free if your time has no value". I've tried Linux so many times, and my longest streak was when having a VMWare Workstaion to run Windows in it. Eventually, I just got fed up. First and foremost, I need my systems to just WORK. When I sit down to code, the last thing I want to do is debug why it is not properly displaying on all of my monitors.
Yeah, I have heard that one before.
At work, I am a sysadmin/helpdesk monkey taking care of a network of ~80 users and a dozen servers, all on Windows, and let me tell you: Windows has its fair share of weird problems, inexplicable failures, stuff that "worked yesterday"...
Windows may "just work" often enough, but unlike Linux, it also "just stops working" so often, it's just not funny any more. On Linux, once one has it working, at least it keeps working.
Earlier quoted context omitted.
> We just need a billionaire benevolent dictator to fund a distribution of Linux I might be missing the joke here, is this a jab at Mark Shuttleworth?
Not intended, but I do think Ubuntu was a missed opportunity by trying to innovate instead of focusing on stability, familiarity, and user-friendliness.
Earlier quoted context omitted.
It's kind of interesting, is it common for you to have Win10 systems in scope for PCI compliance? It seems unusual to me if any desktop systems are anywhere close to card data, IMHO usually you'd have in scope only a bunch of servers (so, Linux or Windows Server for normal businesses who don't have a reason to wrestle mainframes) in an isolated network, but most of company computers including all the user desktops sh…
Wouldn't call centers for online retailers need compliant desktops? How do they deal with customers who prefer to call an agent and read their card number over the phone?
For phone authorizations (if they are used - it may be a regional thing as most smaller online retailers here won't do it at all, banks really frown on merchants who do so because of risks and make it really expensive), generally the agent would use a similar interface as an online customer (encrypted channel, yadda yadda), and the card information would not be stored anywhere on that machine. Whether all kinds of PCI DSS security requirements would apply to these workstations is debatable, your mileage may vary, I've seen them considered out of scope - but in that case it wasn't really a call center for taking transactions but a support call center that might also handle a phone authorization in rare cases.
In any case, for a call center the biggest PCI compliance problem IMHO is handling the sensitive data in call recordings.