@RojoLoco and that's what I appreciates about you RL.

@Obsolesce said in Finding specific file type that has no extension: Is there anything inside the file that can tell you? For example, if you write a script that cats each file or whayever and looks for specific string, then moves it if it matches. I don't know what those files are, so ya. Just thinking out loud without any info. No, because they are just ancient like ~20 + years old, no extension or really anything to hit on. Apple still supports Postscript Type 1 fonts, but nothing else does. I managed to get it to work with what I needed with the above. Additionally I created two reports 1) listing all of he postscript type 1 fonts and 2) listing truetype and opentype fonts. So now we can build a list of things that needs to get upgraded. To find the non-extension'd postscript type 1 fonts I used find . -type f -d -empty >> old-crap.txt To find the modern fonts I used find . -name '*.ttf' -d >> modern-font.txt and just replaced .ttf with .otf, .otc, .ttc, .tte and .dfont and appended the same modern-font.txt file for each of those.

@black3dynamite said in Unix Command line - Printer Details: @DustinB3403 said in Unix Command line - Printer Details: Here is the completed command. lpoptions -p <NAME> | grep -o "printer-make-and-model='Your Printer make and Model" That outputs the exact detail I needed! lpoptions -p SHCSL_209_ColorPrinter | sed -r "s/^.*(printer-make-and-model.*)'.*$/\1/g; s/'//g; s/printer-make-and-model=//g" This will remove all the unnecessary text, printer-make-and-model=, and the single quotes. Yeah I'm also able to just use lpoptions -p SHCSL_209_ColorPrinter | grep "'SHCSL_209_ColorPrinter'" and get what I need in a single line response.

@WLS-ITGuy give this a try, you may need to go back more than a year though.

@DustinB3403 said in Tar gzip file compression calculation without decompressing the file: @Pete-S So the simplest way I can think to explain this would be like this. You have a network share which is relatively organized You create a compressed tarball of any folder on that share and then move that tarball to offsite storage. How would I realistically get a hash of that folder pre and post tar and compression and have it make sense? They aren't the same thing, even if they contain the same things. @Pete-S said in Tar gzip file compression calculation without decompressing the file: Is it safe to assume that the gzip file is correct when it is created? This is what I'm looking to verify I'm assuming that files are static during backup. If you first of all run md5deep on all files in the folder, you'll create a textfile that contains md5 (or sha256 or what you want) signatures on every file in the folder. Place it into the folder so it ends up inside the backup and you'll always have the ability to verify any uncompressed individual file. If you really want to verify your tar.gz file after it's created I think you have to decompress the files to a temporary folder, run md5deep on the files to compare them with the original file. What you really are testing is that the backup-compress-decompress-restore operation is lossless on every file. It should be by design, but if there is an unlikely bug somewhere it's technically possible that it might not be. If you use the gzip compression with tar, gzip has a CRC-32 checksum inside that can be used to verify the integrity of the gzip file. Or to be even more certain you can create an md5 signature of the entire gzip archive with md5sum or md5deep. Then you can always verify that the archive has not been corrupted. If you ever need to restore the files you can verify the integrity of the restored files with the md5 you created on the original files, before you did the backup.

As an additional option, if you don't want your workstation to automatically connect to this network (on startup, while roaming etc) use this networksetup -removedpreferredwirelessnetwork Interface SSID That disables the autojoin functionality on OSX 10.14.6, but you would still have connected to the network from the initial answer.

This is a good starter video: Youtube Video

I've added this to a larger script that I use, but if you only wanted to automate the naming process the above would work for you. Else just remove the header #!/bin/sh and add the reset to any setup scripts that you have to automate this portion of the setup.

I'm marking this solved as I create a direction from / called scripts and that does what I need. No real need for a public shareable desktop when this works just fine.

Dont' use bullet/number lists in instructions and guides like this. it makes it annoying for those that want to copy and paste. This guide is assuming that you are running as root. If not prepend everything here with sudo. Install the salt-master package dnf install salt-master Open the required ports in the firewall firewall-cmd --add-port=4505-4506/tcp --permanent firewall-cmd --reload Enable the salt-master service to start on boow, and also start it now. systemctl enable --now salt-master.service

@black3dynamite said in CUPS Administration Job Info 1 Destination Mailbox: @DustinB3403 said in CUPS Administration Job Info 1 Destination Mailbox: While I found where OSX stores the user printer preferences, but copying a "working version of preferences" to the user workstation and directory doesn't set the preferences. Still investigating. May require a restart when doing this remotely. . . Full system restart or just the cups service? Just did a full system restart and no change. While the plist file is there, and the user has owner access to it, the changes don't appear to take effect. Not sure why.

@shortstack said in Saltstack and Brew Casks: @DustinB3403 i am also wondering what the workaround for this issue is, re: salt minion executing brew installs. did you ever figure out a clean way to get brew working, maybe runas a different user? I haven't had the chance to get back into this, other more pressing issues so I just went on with my day. Sorry

It is likely obvious, but as I know that some people are searching for this information, creating administrative users in this way can be done very easily from remote command lines such as ScreenConnect, ConnectWise, MeshCentral, and so forth.

Worth noting that using rsync worked very well, but there were issues with the Outlook profile on the existing user workstation and the end result. Not a huge issue for us as everything is stored in O365, but worth being mindful of if your email was hosted locally. Also because of username convention changes, I had to set the ownership of the user profile to match the new shortened name.

Have never looked at that.

Fixed a small typo.

@RojoLoco said in OSX Mojave - System Storage - Time Machine Disabled: @DustinB3403 said in OSX Mojave - System Storage - Time Machine Disabled: That seems unnecessary as this shouldn't be so difficult, nor should it ever occur. ...because everything apple does is perfect and never, ever malfunctions in any way, right? Yeah. . . no I get the stance. What makes no sense is there is no way for me to find where this bulk is coming from.

@DustinB3403 said in Nomad - Manage Mac OS in Windows/AD Environment - Anyone Used It?: I've heard of it, and it's supposedly a really good product, the issue with it is the cost. At least at the time. The product now is JAMF Connect. So it looks to be a dead product that was replaced. Interesting. I'll look into that. I didn't see any mention of jamf.

@DustinB3403 said in OSX Power Saving Settings: @black3dynamite said in OSX Power Saving Settings: Does that also prevent it from sleeping when the lid is closed? The lid closed is powernap

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

@dbeato said in lpadmin - remove printer with a space in the name: @DustinB3403 said in lpadmin - remove printer with a space in the name: Nevermind! lpadmin adds spaces as underscores! So with lpadmin -p I was able to find the list of printers. lpadmin -p Accounting_Printer And with lpadmin -x Accounting_Printer was able to remove the printer! Removed Accounting_Printer Good to know for central administration of Apple devices. What are you using right now? ARD and Unix cli

@wrx7m said in OSX 10.14.X Bug - Roaming AD Accounts unable to login when Off Network: @DustinB3403 said in OSX 10.14.X Bug - Roaming AD Accounts unable to login when Off Network: My co-worker thinks he may have a workaround, which involves backing up the user profile, deleting the existing one and restoring the files for the user. We're testing this currently to see if this actually "sticks". Did it work? Waiting to hear back

Just used this again today, as another script I have had this attribute. Not sure when the attribute was written to the script though. But it's working now. This is the full error. /bin/sh: bad interpreter: Operation not permitted

@scottalanmiller said in OSX Unix Using Brew to install software remotely: @DustinB3403 said in OSX Unix Using Brew to install software remotely: So I can just unpack the dmg file, and have an Copy job, copy the application to the Applications folder for any user. As my admin user account. All via Apple Remote Desktop. This works without issue. What I am trying to do is avoid having to locally download the app at all, unpack it and then have a Copy job to run. I'd like to streamline the process. That's what the script is doing already. Making your own "sudo friendly" script for your install might make sense. The issue is there is no way AFAIK without adding my local admin account to this group. Which is more work than it may be worth since the existing solution works but is annoying.

You might look at the tools that Apple is pushing (and thus supporting). I don't know if Munki will fit your requirements, but it may. Here is a list of several projects for managing macOS: https://simplemdm.com/2018/07/19/popular-open-source-tools-for-mac-admins/. NoMAD is pretty cool if you're in a Windows-centric environment.

@marcinozga said in Find the character break - sh script: @DustinB3403 you need to source .bash_profile after changing it, so bash picks up modified file. Either source ~/.bash_profile or . ~/.bash_profile Thanks for that, I was actually sorting out that bit as you posted. Short of setting up a few printers via the script I'm back in working order.