Anyone Attempting Deploying Printers through SaltStack?
-
@scottalanmiller said in Anyone Attempting Deploying Printers through SaltStack?:
@jaredbusch said in Anyone Attempting Deploying Printers through SaltStack?:
I cast my part-time person to set up printer deployment via power shell. And I know we have that working with a few caveats that still need testing.
We might do that if we can't get this figured out in a better way.
Like what?
There's no actual Salt module or Salt states module specifically for printers. This means you'll need to do it via the win_lgpo module and PowerShell.
The win_lgpo module uses the local admx/adml files, so make sure those are up to date on your Windows systems if you use any of them.
-
@obsolesce said in Anyone Attempting Deploying Printers through SaltStack?:
@scottalanmiller said in Anyone Attempting Deploying Printers through SaltStack?:
That's pretty much it. Windows desktops (and laptops) and we'd like to try using Salt to deploy printers instead of going through traditional Group Policy or login scripts. Anyone attempted this or know the recommended approach?
I was thinking of looking in to this because there are some issues where, through Group Policy Preferences, Windows machines do not get printers/copiers deployed to them (via GP) unless the printer's driver had been previously installed.
It was only an issue on Win10 machines where the logged in user was not a local admin.
SS is good at getting stuff done, so I had thought about looking in to this a while ago, but haven't yet.
I solved this with GPO GPP by having a print server with the drivers, so the Win10 machines could reference the print queue for the driver, yet set them up as an IP (direct) printer. You can set the ability to install the drivers even as non admin via GPO as well.
-
@dashrender said in Anyone Attempting Deploying Printers through SaltStack?:
@obsolesce said in Anyone Attempting Deploying Printers through SaltStack?:
@scottalanmiller said in Anyone Attempting Deploying Printers through SaltStack?:
That's pretty much it. Windows desktops (and laptops) and we'd like to try using Salt to deploy printers instead of going through traditional Group Policy or login scripts. Anyone attempted this or know the recommended approach?
I was thinking of looking in to this because there are some issues where, through Group Policy Preferences, Windows machines do not get printers/copiers deployed to them (via GP) unless the printer's driver had been previously installed.
It was only an issue on Win10 machines where the logged in user was not a local admin.
SS is good at getting stuff done, so I had thought about looking in to this a while ago, but haven't yet.
I solved this with GPO GPP by having a print server with the drivers, so the Win10 machines could reference the print queue for the driver, yet set them up as an IP (direct) printer. You can set the ability to install the drivers even as non admin via GPO as well.
I am already deploying them via GPP via a print server. I cannot deploy them via TCP/IP, they need to be deployed as "Shared" or the PaperCut software won't work correctly. Unless that's changed within the last 3 years, I have to keep doing it via "Shared" method in Group Policy Preferences.
It was working out perfectly for the last few years... it's only recently the issue came up. Something in Win10 changed compared to how it was previously, where any new printers deployed to a computer via GPP where the printer driver wasn't previously installed will not install unless a user with local admin privs logs in to do it first.
I'd rather not hijack this thread about that, it's a very infrequent thing because new images have the drivers on them already. So not really worth discussing in a new topic as I'm not worrying about it anymore.
I'm still interested in sometime seeing if SaltStack would be able to deploy printers to computers as effectively or more so than current methods. I may look in to it more soon, but the priority is low because things are working fine as they are.
I'm mainly focused on getting SaltStack to manage the more global configurations first... before getting into more granular configurations like printer deployments.
-
@obsolesce said in Anyone Attempting Deploying Printers through SaltStack?:
@dashrender said in Anyone Attempting Deploying Printers through SaltStack?:
@obsolesce said in Anyone Attempting Deploying Printers through SaltStack?:
@scottalanmiller said in Anyone Attempting Deploying Printers through SaltStack?:
That's pretty much it. Windows desktops (and laptops) and we'd like to try using Salt to deploy printers instead of going through traditional Group Policy or login scripts. Anyone attempted this or know the recommended approach?
I was thinking of looking in to this because there are some issues where, through Group Policy Preferences, Windows machines do not get printers/copiers deployed to them (via GP) unless the printer's driver had been previously installed.
It was only an issue on Win10 machines where the logged in user was not a local admin.
SS is good at getting stuff done, so I had thought about looking in to this a while ago, but haven't yet.
I solved this with GPO GPP by having a print server with the drivers, so the Win10 machines could reference the print queue for the driver, yet set them up as an IP (direct) printer. You can set the ability to install the drivers even as non admin via GPO as well.
I am already deploying them via GPP via a print server. I cannot deploy them via TCP/IP, they need to be deployed as "Shared" or the PaperCut software won't work correctly. Unless that's changed within the last 3 years, I have to keep doing it via "Shared" method in Group Policy Preferences.
It was working out perfectly for the last few years... it's only recently the issue came up. Something in Win10 changed compared to how it was previously, where any new printers deployed to a computer via GPP where the printer driver wasn't previously installed will not install unless a user with local admin privs logs in to do it first.
I'd rather not hijack this thread about that, it's a very infrequent thing because new images have the drivers on them already. So not really worth discussing in a new topic as I'm not worrying about it anymore.
I'm still interested in sometime seeing if SaltStack would be able to deploy printers to computers as effectively or more so than current methods. I may look in to it more soon, but the priority is low because things are working fine as they are.
I'm mainly focused on getting SaltStack to manage the more global configurations first... before getting into more granular configurations like printer deployments.
I only mentioned Direct IP printing because that's what I'm doing, but shared should work just as well.
-
@obsolesce said in Anyone Attempting Deploying Printers through SaltStack?:
It was working out perfectly for the last few years... it's only recently the issue came up. Something in Win10 changed compared to how it was previously, where any new printers deployed to a computer via GPP where the printer driver wasn't previously installed will not install unless a user with local admin privs logs in to do it first.
That changed early last year. New drivers now need to be signed and it is taking printer manufactures forever to get them signed the way Microsoft wants them to... it's bitten us more then once.
-
I've created a Salt execution module before, and it wasn't that hard, anyone with a bit of Python experience should be able to make one. I imagine a state module wouldn't be much harder.
- Here is how I would tackle this:
- Take a look at how you would do this in powershell
- Use Process Monitor so see anything behind the scenes that is being done
- If Powershell isn't enough, reverse engineer lgpo
- I haven't done this before so I don't know if there might be a better way to do this other than
- Process Monitor
- Look at the Salt source code to see what interfaces they provide to interacting with Windows already
- Create module
- Take a look at how you would do this in powershell
- Here is how I would tackle this:
-
@flaxking that thought had crossed my mind, and as we use Salt broadly with many clients, it could easily make sense to invest the time in that.
-
@obsolesce said in Anyone Attempting Deploying Printers through SaltStack?:
@scottalanmiller said in Anyone Attempting Deploying Printers through SaltStack?:
That's pretty much it. Windows desktops (and laptops) and we'd like to try using Salt to deploy printers instead of going through traditional Group Policy or login scripts. Anyone attempted this or know the recommended approach?
I was thinking of looking in to this because there are some issues where, through Group Policy Preferences, Windows machines do not get printers/copiers deployed to them (via GP) unless the printer's driver had been previously installed.
It was only an issue on Win10 machines where the logged in user was not a local admin.
SS is good at getting stuff done, so I had thought about looking in to this a while ago, but haven't yet.
Did the issue with GPP and Windows 10 have to do with the point to print issue and the driver not being a packaged driver?
-
@scottalanmiller This makes me miss my old job. I was working on replacing all of our GPOs with Salt and printer deployment was coming up. However, as a solo SMB IT employee, I had an insane amount of time on my hands.
-
@flaxking said in Anyone Attempting Deploying Printers through SaltStack?:
@scottalanmiller This makes me miss my old job. I was working on replacing all of our GPOs with Salt and printer deployment was coming up. However, as a solo SMB IT employee, I had an insane amount of time on my hands.
We're more the opposite - needing to invest in good management to ensure we are not too busy later.
-
@flaxking said in Anyone Attempting Deploying Printers through SaltStack?:
@scottalanmiller This makes me miss my old job. I was working on replacing all of our GPOs with Salt and printer deployment was coming up. However, as a solo SMB IT employee, I had an insane amount of time on my hands.
I am a solo SMB employee and have no time on my hands.
We just hired about 10 people in the last 4 weeks and 2 start in a week and 2 more possibly the week after. No real time to do anything more than setup new employees. -
@wrx7m said in Anyone Attempting Deploying Printers through SaltStack?:
@flaxking said in Anyone Attempting Deploying Printers through SaltStack?:
@scottalanmiller This makes me miss my old job. I was working on replacing all of our GPOs with Salt and printer deployment was coming up. However, as a solo SMB IT employee, I had an insane amount of time on my hands.
I am a solo SMB employee and have no time on my hands.
We just hired about 10 people in the last 4 weeks and 2 start in a week and 2 more possibly the week after. No real time to do anything more than setup new employees.What makes new employee setup so labour intensive at your SMB?
I used to get notified of new employees on their start day :ogre:
On my to-do list was to make a way for HR to handle most of what was required with new employees. A lot of stuff required pairs more nicely with HR than with IT, IT just need to provide a friendly abstraction on top of automation for them to use.
-
@flaxking said in Anyone Attempting Deploying Printers through SaltStack?:
@wrx7m said in Anyone Attempting Deploying Printers through SaltStack?:
@flaxking said in Anyone Attempting Deploying Printers through SaltStack?:
@scottalanmiller This makes me miss my old job. I was working on replacing all of our GPOs with Salt and printer deployment was coming up. However, as a solo SMB IT employee, I had an insane amount of time on my hands.
I am a solo SMB employee and have no time on my hands.
We just hired about 10 people in the last 4 weeks and 2 start in a week and 2 more possibly the week after. No real time to do anything more than setup new employees.What makes new employee setup so labour intensive at your SMB?
We onboard something like 5-6 per day, seven days a week, for just a single client
10 in four weeks would be a vacation. We had five leave just since noon today! -
@wrx7m said in Anyone Attempting Deploying Printers through SaltStack?:
@flaxking said in Anyone Attempting Deploying Printers through SaltStack?:
@scottalanmiller This makes me miss my old job. I was working on replacing all of our GPOs with Salt and printer deployment was coming up. However, as a solo SMB IT employee, I had an insane amount of time on my hands.
I am a solo SMB employee and have no time on my hands.
We just hired about 10 people in the last 4 weeks and 2 start in a week and 2 more possibly the week after. No real time to do anything more than setup new employees.HR and Workday handles most of the onboarding and the rest is automated.
-
@black3dynamite said in Anyone Attempting Deploying Printers through SaltStack?:
@wrx7m said in Anyone Attempting Deploying Printers through SaltStack?:
@flaxking said in Anyone Attempting Deploying Printers through SaltStack?:
@scottalanmiller This makes me miss my old job. I was working on replacing all of our GPOs with Salt and printer deployment was coming up. However, as a solo SMB IT employee, I had an insane amount of time on my hands.
I am a solo SMB employee and have no time on my hands.
We just hired about 10 people in the last 4 weeks and 2 start in a week and 2 more possibly the week after. No real time to do anything more than setup new employees.HR and Workday handles most of the onboarding and the rest is automated.
I am talking about account creation and computer setup, installation etc.
-
@wrx7m said in Anyone Attempting Deploying Printers through SaltStack?:
@black3dynamite said in Anyone Attempting Deploying Printers through SaltStack?:
@wrx7m said in Anyone Attempting Deploying Printers through SaltStack?:
@flaxking said in Anyone Attempting Deploying Printers through SaltStack?:
@scottalanmiller This makes me miss my old job. I was working on replacing all of our GPOs with Salt and printer deployment was coming up. However, as a solo SMB IT employee, I had an insane amount of time on my hands.
I am a solo SMB employee and have no time on my hands.
We just hired about 10 people in the last 4 weeks and 2 start in a week and 2 more possibly the week after. No real time to do anything more than setup new employees.HR and Workday handles most of the onboarding and the rest is automated.
I am talking about account creation and computer setup, installation etc.
I can't think of any business case for why IT has to handle account setup. Most of the time it's just a technology deficiency as to why HR doesn't have the ability to do so.
98% of the time computer setup and software installation can be completely automated. Even when the software support says it can't. So you might be dealing with the 2%, or you could be bogged down with so much technical debt that you haven't been able to dedicate the cycle required in order to automate
-
On and Offboarding is very labor intensive and if it's not that's possibly because your team may have streamlined the experience. However, every business by far isn't streamlined. That is a fact.
-
@krisleslie said in Anyone Attempting Deploying Printers through SaltStack?:
On and Offboarding is very labor intensive and if it's not that's possibly because your team may have streamlined the experience. However, every business by far isn't streamlined. That is a fact.
Sometimes this is an advantage of an outside firm, they have more clout, or just a fresh set of eyes, to evaluate the process.
-
@scottalanmiller I totally agree, but every company can't afford an outside firm on top of an internal person/team at same time in the scale I'm in.
I have often looked at using a 3rd party for not only the finance and HR. Get's expensive and some functions don't get performed with a 3rd party which leaves you still to fill a gap or take it upon yourself.
Totally doable, in 5 and maybe 10 man companies but when you get hit with dose of growth and you can't effectively scale, it comes back to haunt.
#ghostlybooooooo -
@scottalanmiller said in Anyone Attempting Deploying Printers through SaltStack?:
@krisleslie said in Anyone Attempting Deploying Printers through SaltStack?:
On and Offboarding is very labor intensive and if it's not that's possibly because your team may have streamlined the experience. However, every business by far isn't streamlined. That is a fact.
Sometimes this is an advantage of an outside firm, they have more clout, or just a fresh set of eyes, to evaluate the process.
This is so frustrating... and sadly so damned true.
Internal resources are frequently ignored because the people in charge forget that they are paying the internal resources... but with an outside firm - that's always first and foremost in their mind, and if they are paying, well by god we should be doing what they say because otherwise why in the world are we paying them?
Now if only they applied that same logic to the employees they employ.
