• 0 Votes
    7 Posts
    766 Views
    scottalanmillerS

    @IgnaceQ said in If starting from scratch, would you suggest learning BASH or Ansible?:

    Besides anisble there are other tools for remote tooling. In a linux world you need bash. this is a basic need.
    On top of bash, it really depends on the environmnet you're in. I would suggest python on top of this. You can use python in ansible, chef, terraform, etc... Also on non linux environments, python is availlable (bsd, windows).

    He needs Ansible because he's doing an Ansible based certification path.

  • 0 Votes
    3 Posts
    631 Views
    JaredBuschJ

    @openit said in Offsite backup and CentOS Upstream - looking for suggestions.:

    CentOS Upstream: Isn't okay for Production Servers anymore?

    I assume you mean CentOS Stream?

    Honestly it is a more viable solution for a Linux server than CentOS ever was as it is no longer so out dated.

    But, I would give the entire RHEL ecosystem a wide berth at this point.

  • 0 Votes
    7 Posts
    3k Views
    dbeatoD

    @openit said in Microsoft 365 group Mailbox Full -How Backup and Delete emails to free up space?:

    @dbeato said in Microsoft 365 group Mailbox Full -How Backup and Delete emails to free up space?:

    1- It only deletes the individual message they received.
    2- The only tool is to do a E-discovery search for email sent to this Group and then exporting that to a PST.
    3- Yes, 50 GB is the maximum storage for an Office 365 Business Basic and Standard
    https://docs.microsoft.com/en-us/office365/servicedescriptions/exchange-online-service-description/exchange-online-limits#mailbox-storage-limits
    You might want to setup an archiving addon for that mailbox or bump the license to E3 so they get 100 GB of Mailbox storage and then archiving is included as well.
    4- YOu can setup a retention policy that deletes all items that is 2 years old and then apply to the mailbox and force the Retention Policy to apply then it will take a day or so but it will run faster.
    https://docs.microsoft.com/en-us/microsoft-365/compliance/set-up-an-archive-and-deletion-policy-for-mailboxes?view=o365-worldwide

    https://docs.microsoft.com/en-us/powershell/module/exchange/start-managedfolderassistant?view=exchange-ps (To force the retention policy)

    Not sure if you misunderstood. I got confirmed that deleting any emails on Group Mailbox won't any member's mailbox items. Yes, did it that way, went well. Yeah, not an option for me now. Seems nice and faster action, than PowerShell commands Microsoft guys running.

    I wrote the answer 1 in a confusing way. The emails don't get deleted from each user mailbox that received it so no issue there.

  • 0 Votes
    36 Posts
    3k Views
    openitO

    @IRJ said in System Admin - checklist for Don'ts and Important points please!:

    @gjacobse said in System Admin - checklist for Don'ts and Important points please!:

    @Pete-S said in System Admin - checklist for Don'ts and Important points please!:

    Maybe I'm alone but on the top of my list:

    Only use Microsoft as a last resort when all other options have been explored. If you get paid by the hour disregard #1.

    Option 1. - What do you say / do when the Owner specifically states, Windows Only environment. NIX and Apply need not apply -

    Look for another job

    Lol 🙂

  • 0 Votes
    9 Posts
    923 Views
    scottalanmillerS

    @JaredBusch said in Yealink T46S Double Tap while on Conference call:

    @CCWTech said in Yealink T46S Double Tap while on Conference call:

    @JaredBusch said in Yealink T46S Double Tap while on Conference call:

    DTMF

    Is that on the ext in advanced? It's set to RFC4733

    Both the Phone and Asterisk have settings for this. They need to match.

    They do, we checked that last night.

  • 2 Votes
    1 Posts
    540 Views
    No one has replied
  • 4 Votes
    6 Posts
    1k Views
    ObsolesceO

    I ran into a language issue the other day when writing a PowerShell script that uses net localgroup and thought it could be useful to others:

    Depending on the language your Windows device is set to, the local Administrators group will be different, so the typical net localgroup administrators domain\user /add command will fail.

    Implementing the following will grab the actual name of the group by it's SID first, then use that result.
    Note that this is written to work in PowerShell, not CMD.exe.

    # Gets the name of the local Administrators group in appropriate language $localAdminGroupName = (Get-WmiObject win32_group -filter "LocalAccount = $TRUE And SID = 'S-1-5-32-544'" | Select-Object -Expand name) Write-Output "Local Administrators group detected as: [$localAdminGroupName]" # Sets the users as a local admin using appropriate local Administrators group name net localgroup $localAdminGroupName domain\user /add # Gets local Administrators group members net localgroup $localAdminGroupName
  • It's Scott's Fault

    Water Closet
    11
    1 Votes
    11 Posts
    2k Views
    jt1001001J

    With a picture of a flaming fireball shot

  • 0 Votes
    36 Posts
    4k Views
    scottalanmillerS

    @dashrender said in What exactly imaging software, any open source or free options ?:

    @dustinb3403 said in What exactly imaging software, any open source or free options ?:

    To throw a wrench into this conversation.

    UrBackup is a backup solution that can be run constantly and allows you to restore the backup or any part of it to different hardware.

    So while it falls in the "Backup" category it also blurs the lines a bit.

    Most modern backup solutions can do this.

    Yup, imaging is the process of recreating replicas which are the most common foundation of modern backups.

  • 0 Votes
    35 Posts
    4k Views
    DashrenderD

    @tim_g said in Why restart works ? Technical reason ?:

    @jaredbusch said in Why restart works ? Technical reason ?:

    @tim_g said in Why restart works ? Technical reason ?:

    @jaredbusch said in Why restart works ? Technical reason ?:

    @tim_g said in Why restart works ? Technical reason ?:

    @tim_g said in Why restart works ? Technical reason ?:

    @eddiejennings said in Why restart works ? Technical reason ?:

    I'll often have users do a restart, but if the issue is recurring, then I'll take the time to try to find the root cause.

    We do a minimum of forced weekly reboot of computers with updates, regardless of whether or not updates are installed.

    It's been helping a LOT, and is a free way to fix or prevent many issues that waste time and effort from nobody rebooting.

    There are (as always) some exceptions.

    I did this years ago. And no exceptions. The owner buys in to it or he doesn't.

    The reduction of support costs is always the winning decision.

    Yes, from the perspective of a company using service provider.

    But I get paid hourly, so from this companies perspective, it costs the same regardless.

    No it does not. Because you are wasting time (money) doing tasks that are not needed if you would have the reboots scheduled.

    It may be the same to your paycheck, but it is not the same to the company. That is always the point of people trying to justify their jobs. Or of the SMB owner thinking he is saving money by using internal staff of lower skill.

    Yeah, but there are exceptions... not my decision, not my argument.

    of course, if the decision is out of your hands, absolutely that's not on you - just like Mike Davis spending 4 hrs working on a PC issue and costing more than the value of the PC - because the decision maker told them to.

  • 0 Votes
    6 Posts
    2k Views
    H

    Gather knowledge from different websites and after doing depth research for the topic, you can write for the same topic in your blog too with your own words. But rewrite the same article by changing words and sentences is not good and you should have to suffer from legality.

    For you second question,

    Technical steps for the same topic remain mostly the same for all articles. So if you think for write the topic which you have suggested here "Installing Snipe-IT on CentOS 7" then also technical steps remain the same which is the legal. But that doesn't mean that you can copy/paste in place of write in your own words.

    Content flow is also important to make content more interesting for users. This article will help you to know how to write the article in the proper way.

  • 2 Votes
    8 Posts
    3k Views
    EddieJenningsE

    @scottalanmiller Ah, yes. That would be a more efficient way of doing it. I was too excited from finally gaining some understanding of mount point concepts, I didn't think though the best way to move the data. 🙂

  • 2 Votes
    1 Posts
    2k Views
    No one has replied
  • 3 Votes
    3 Posts
    2k Views
    scottalanmillerS

    @johnhooks said in Linux: Looking for Large Folders with du:

    I've always just used -h for human readable. I never realized -m would give you the MB size.

    I have the "advantage" of having learned this stuff before the human readable flag was added 😉

  • 1 Votes
    6 Posts
    4k Views
    scottalanmillerS

    @tonyshowoff said in Linux: Zip and 7Zip:

    Sorry if this was mentioned but I didn't see it directly mentioned for clarity:

    If your compression is unavailable directly in tar (-J being essentially 7zip, my favourite), you can tar it first (without compression) and then compress the tar, this maintains both Unix metadata and also gives the benefit.

    Also, if you compress something already compressed you won't get the best benefit, at least not when it comes to using something as powerful as LZMA/7zip.

    I believe that that is mentioned in the tar article.

  • 3 Votes
    8 Posts
    4k Views
    scottalanmillerS

    It doesn't update as "new" when I just update the list. Only if I comment on the thread.

  • 5 Votes
    16 Posts
    5k Views
    scottalanmillerS

    @Dashrender said in From Windows to UNIX: Monolithic to Modular Design:

    I suppose it's less of an issue as well, since Linux Distros are free, you just have another VM running the other software.
    Windows, you'd have the Windows tax.

    Exactly. A VM or a container or an application jail. Lots of options for mediation if you want the conflicting packages.

  • 3 Votes
    9 Posts
    4k Views
    scottalanmillerS

    @Dashrender said:

    Most storage devices in this range also lack the support options that enterprise servers do.

    This sentence is the third italicized block of text seems odd.

    Fixed, thanks.

  • 2 Votes
    4 Posts
    2k Views
    scottalanmillerS

    The "working data" that I mentioned that scrolls by quickly before our summary chart appears from this example looks like the below output. Generally we can ignore this, but it can be useful should there be an error to see where something has gone wrong.

    $ yum update Loaded plugins: fastestmirror Loading mirror speeds from cached hostfile * base: mirrors.lga7.us.voxel.net * epel: mirror.cs.princeton.edu * extras: mirror.lug.udel.edu * updates: mirror.trouble-free.net Resolving Dependencies --> Running transaction check ---> Package NetworkManager.x86_64 1:1.0.0-16.git20150121.b4ea599c.el7_1 will be updated ---> Package NetworkManager.x86_64 1:1.0.6-27.el7 will be updated ---> Package NetworkManager.x86_64 1:1.0.6-29.el7_2 will be an update ---> Package NetworkManager-adsl.x86_64 1:1.0.6-27.el7 will be updated ---> Package NetworkManager-adsl.x86_64 1:1.0.6-29.el7_2 will be an update ---> Package NetworkManager-bluetooth.x86_64 1:1.0.6-27.el7 will be updated ---> Package NetworkManager-bluetooth.x86_64 1:1.0.6-29.el7_2 will be an update --> Processing Dependency: libbluetooth.so.3()(64bit) for package: 1:NetworkManager-bluetooth-1.0.6-29.el7_2.x86_64 ---> Package NetworkManager-glib.x86_64 1:1.0.6-27.el7 will be updated ---> Package NetworkManager-glib.x86_64 1:1.0.6-29.el7_2 will be an update ---> Package NetworkManager-libnm.x86_64 1:1.0.6-27.el7 will be updated ---> Package NetworkManager-libnm.x86_64 1:1.0.6-29.el7_2 will be an update ---> Package NetworkManager-team.x86_64 1:1.0.6-27.el7 will be updated ---> Package NetworkManager-team.x86_64 1:1.0.6-29.el7_2 will be an update ---> Package NetworkManager-tui.x86_64 1:1.0.6-27.el7 will be updated ---> Package NetworkManager-tui.x86_64 1:1.0.6-29.el7_2 will be an update ---> Package NetworkManager-wifi.x86_64 1:1.0.6-27.el7 will be updated ---> Package NetworkManager-wifi.x86_64 1:1.0.6-29.el7_2 will be an update ---> Package NetworkManager-wwan.x86_64 1:1.0.6-27.el7 will be updated ---> Package NetworkManager-wwan.x86_64 1:1.0.6-29.el7_2 will be an update ---> Package avahi.x86_64 0:0.6.31-14.el7 will be updated ---> Package avahi.x86_64 0:0.6.31-15.el7 will be updated ---> Package avahi.x86_64 0:0.6.31-15.el7_2.1 will be an update ---> Package avahi-autoipd.x86_64 0:0.6.31-15.el7 will be updated ---> Package avahi-autoipd.x86_64 0:0.6.31-15.el7_2.1 will be an update ---> Package avahi-libs.x86_64 0:0.6.31-15.el7 will be updated ---> Package avahi-libs.x86_64 0:0.6.31-15.el7_2.1 will be an update ---> Package bind-libs.x86_64 32:9.9.4-29.el7_2.2 will be updated ---> Package bind-libs.x86_64 32:9.9.4-29.el7_2.3 will be an update ---> Package bind-libs-lite.x86_64 32:9.9.4-29.el7_2.2 will be updated ---> Package bind-libs-lite.x86_64 32:9.9.4-29.el7_2.3 will be an update ---> Package bind-license.noarch 32:9.9.4-29.el7_2.2 will be updated ---> Package bind-license.noarch 32:9.9.4-29.el7_2.3 will be an update ---> Package bind-utils.x86_64 32:9.9.4-29.el7_2.2 will be updated ---> Package bind-utils.x86_64 32:9.9.4-29.el7_2.3 will be an update ---> Package ca-certificates.noarch 0:2015.2.4-71.el7 will be updated ---> Package ca-certificates.noarch 0:2015.2.6-70.1.el7_2 will be an update ---> Package coreutils.x86_64 0:8.22-12.el7_1.2 will be updated ---> Package coreutils.x86_64 0:8.22-15.el7 will be updated ---> Package coreutils.x86_64 0:8.22-15.el7_2.1 will be an update ---> Package cronie.x86_64 0:1.4.11-13.el7 will be updated ---> Package cronie.x86_64 0:1.4.11-14.el7 will be updated ---> Package cronie.x86_64 0:1.4.11-14.el7_2.1 will be an update ---> Package cronie-anacron.x86_64 0:1.4.11-14.el7 will be updated ---> Package cronie-anacron.x86_64 0:1.4.11-14.el7_2.1 will be an update ---> Package cyrus-sasl-lib.x86_64 0:2.1.26-19.2.el7 will be updated ---> Package cyrus-sasl-lib.x86_64 0:2.1.26-20.el7_2 will be an update ---> Package device-mapper.x86_64 7:1.02.107-5.el7 will be updated ---> Package device-mapper.x86_64 7:1.02.107-5.el7_2.1 will be an update ---> Package device-mapper-libs.x86_64 7:1.02.107-5.el7 will be updated ---> Package device-mapper-libs.x86_64 7:1.02.107-5.el7_2.1 will be an update ---> Package filebeat.x86_64 0:1.1.0-1 will be updated ---> Package filebeat.x86_64 0:1.2.1-1 will be an update ---> Package glibc.x86_64 0:2.17-106.el7_2.1 will be updated ---> Package glibc.x86_64 0:2.17-106.el7_2.4 will be an update ---> Package glibc-common.x86_64 0:2.17-106.el7_2.1 will be updated ---> Package glibc-common.x86_64 0:2.17-106.el7_2.4 will be an update ---> Package htop.x86_64 0:1.0.3-3.el7 will be updated ---> Package htop.x86_64 0:2.0.1-1.el7 will be an update ---> Package initscripts.x86_64 0:9.49.24-1.el7 will be updated ---> Package initscripts.x86_64 0:9.49.30-1.el7 will be updated ---> Package initscripts.x86_64 0:9.49.30-1.el7_2.2 will be an update ---> Package kernel.x86_64 0:3.10.0-327.13.1.el7 will be installed ---> Package kernel-tools.x86_64 0:3.10.0-327.4.5.el7 will be updated ---> Package kernel-tools.x86_64 0:3.10.0-327.13.1.el7 will be an update ---> Package kernel-tools-libs.x86_64 0:3.10.0-327.4.5.el7 will be updated ---> Package kernel-tools-libs.x86_64 0:3.10.0-327.13.1.el7 will be an update ---> Package kexec-tools.x86_64 0:2.0.7-19.el7_1.2 will be updated ---> Package kexec-tools.x86_64 0:2.0.7-38.el7 will be updated ---> Package kexec-tools.x86_64 0:2.0.7-38.el7_2.1 will be an update ---> Package kpartx.x86_64 0:0.4.9-85.el7 will be updated ---> Package kpartx.x86_64 0:0.4.9-85.el7_2.1 will be an update ---> Package krb5-libs.x86_64 0:1.13.2-10.el7 will be updated ---> Package krb5-libs.x86_64 0:1.13.2-12.el7_2 will be an update ---> Package libblkid.x86_64 0:2.23.2-26.el7 will be updated ---> Package libblkid.x86_64 0:2.23.2-26.el7_2.2 will be an update ---> Package libgudev1.x86_64 0:219-19.el7 will be updated ---> Package libgudev1.x86_64 0:219-19.el7_2.7 will be an update ---> Package libmount.x86_64 0:2.23.2-26.el7 will be updated ---> Package libmount.x86_64 0:2.23.2-26.el7_2.2 will be an update ---> Package libssh2.x86_64 0:1.4.3-10.el7 will be updated ---> Package libssh2.x86_64 0:1.4.3-10.el7_2.1 will be an update ---> Package libteam.x86_64 0:1.17-5.el7 will be updated ---> Package libteam.x86_64 0:1.17-6.el7_2 will be an update ---> Package libuuid.x86_64 0:2.23.2-26.el7 will be updated ---> Package libuuid.x86_64 0:2.23.2-26.el7_2.2 will be an update ---> Package mariadb-libs.x86_64 1:5.5.44-2.el7.centos will be updated ---> Package mariadb-libs.x86_64 1:5.5.47-1.el7_2 will be an update ---> Package nss-util.x86_64 0:3.19.1-4.el7_1 will be updated ---> Package nss-util.x86_64 0:3.19.1-9.el7_2 will be an update ---> Package numactl-libs.x86_64 0:2.0.9-5.el7_1 will be updated ---> Package numactl-libs.x86_64 0:2.0.9-6.el7_2 will be an update ---> Package openldap.x86_64 0:2.4.40-8.el7 will be updated ---> Package openldap.x86_64 0:2.4.40-9.el7_2 will be an update ---> Package openssh.x86_64 0:6.6.1p1-23.el7_2 will be updated ---> Package openssh.x86_64 0:6.6.1p1-25.el7_2 will be an update ---> Package openssh-clients.x86_64 0:6.6.1p1-23.el7_2 will be updated ---> Package openssh-clients.x86_64 0:6.6.1p1-25.el7_2 will be an update ---> Package openssh-server.x86_64 0:6.6.1p1-12.el7_1 will be updated ---> Package openssh-server.x86_64 0:6.6.1p1-25.el7_2 will be an update ---> Package openssl.x86_64 1:1.0.1e-51.el7_2.2 will be updated ---> Package openssl.x86_64 1:1.0.1e-51.el7_2.4 will be an update ---> Package openssl-libs.x86_64 1:1.0.1e-51.el7_2.2 will be updated ---> Package openssl-libs.x86_64 1:1.0.1e-51.el7_2.4 will be an update ---> Package polkit.x86_64 0:0.112-5.el7 will be updated ---> Package polkit.x86_64 0:0.112-6.el7_2 will be an update ---> Package procps-ng.x86_64 0:3.3.10-3.el7 will be updated ---> Package procps-ng.x86_64 0:3.3.10-5.el7_2 will be an update ---> Package python-boto.noarch 0:2.38.0-2.el7 will be obsoleted ---> Package python-perf.x86_64 0:3.10.0-327.4.5.el7 will be updated ---> Package python-perf.x86_64 0:3.10.0-327.13.1.el7 will be an update ---> Package python-pyudev.noarch 0:0.15-7.el7 will be updated ---> Package python-pyudev.noarch 0:0.15-7.el7_2.1 will be an update ---> Package python2-boto.noarch 0:2.39.0-1.el7 will be obsoleting ---> Package screen.x86_64 0:4.1.0-0.19.20120314git3c2946.el7 will be updated ---> Package screen.x86_64 0:4.1.0-0.23.20120314git3c2946.el7_2 will be an update ---> Package selinux-policy.noarch 0:3.13.1-60.el7 will be updated ---> Package selinux-policy.noarch 0:3.13.1-60.el7_2.3 will be an update ---> Package selinux-policy-targeted.noarch 0:3.13.1-23.el7_1.21 will be updated ---> Package selinux-policy-targeted.noarch 0:3.13.1-60.el7_2.3 will be an update ---> Package sudo.x86_64 0:1.8.6p7-16.el7 will be updated ---> Package sudo.x86_64 0:1.8.6p7-17.el7_2 will be an update ---> Package systemd.x86_64 0:208-20.el7_1.6 will be updated ---> Package systemd.x86_64 0:219-19.el7 will be updated ---> Package systemd.x86_64 0:219-19.el7_2.7 will be an update ---> Package systemd-libs.x86_64 0:219-19.el7 will be updated ---> Package systemd-libs.x86_64 0:219-19.el7_2.7 will be an update ---> Package systemd-python.x86_64 0:219-19.el7 will be updated ---> Package systemd-python.x86_64 0:219-19.el7_2.7 will be an update ---> Package systemd-sysv.x86_64 0:219-19.el7 will be updated ---> Package systemd-sysv.x86_64 0:219-19.el7_2.7 will be an update ---> Package teamd.x86_64 0:1.17-5.el7 will be updated ---> Package teamd.x86_64 0:1.17-6.el7_2 will be an update ---> Package topbeat.x86_64 0:1.1.0-1 will be updated ---> Package topbeat.x86_64 0:1.2.1-1 will be an update ---> Package tuned.noarch 0:2.4.1-1.el7 will be updated ---> Package tuned.noarch 0:2.5.1-4.el7_2.1 will be updated ---> Package tuned.noarch 0:2.5.1-4.el7_2.3 will be an update ---> Package tzdata.noarch 0:2015g-1.el7 will be updated ---> Package tzdata.noarch 0:2016c-1.el7 will be an update ---> Package util-linux.x86_64 0:2.23.2-26.el7 will be updated ---> Package util-linux.x86_64 0:2.23.2-26.el7_2.2 will be an update --> Running transaction check ---> Package bluez-libs.x86_64 0:5.23-4.el7 will be installed --> Finished Dependency Resolution --> Running transaction check ---> Package kernel.x86_64 0:3.10.0-229.7.2.el7 will be erased ---> Package kernel.x86_64 0:3.10.0-229.11.1.el7 will be erased --> Finished Dependency Resolution Dependencies Resolved
  • 2 Votes
    18 Posts
    4k Views
    scottalanmillerS

    @travisdh1 said:

    @johnhooks The difference is 6 compared to a half dozen (at least in this case.)

    I used to know a reason why you would use less or more in certain cases, but it's been so long that I no longer remember what caused a difference.

    I know of no case where you use more. I always used it because I learned it first, but less is the only one you would actually want to use.