Got it with this.

lpadmin -p Printer-Name -E -v ipp://printer-address -o printer-is-shared=false -o printer-make-and-model="Canon iPR Svr G250 V1.0 US" -P "/Library/Printers/PPDs/Contents/en.lproj/Canon iPR Svr G250 V1.0 US"

@Dashrender said in lpadmin Printer drivers are deprecated and will stop working in a future version of CUPS:

@DustinB3403 said in lpadmin Printer drivers are deprecated and will stop working in a future version of CUPS:

Keeping a system out of date on purpose for this though. . . ugh kill me now.

Better get used to it - it's exactly what those shops running old XP machines on million dollar printing presses had to do.

:anguished:

@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.