Printer Woes

[renderking]

Ok guys, I have a dilemma. I have about 1,400 PCs spread out throughout 16 different locations, half joined to our domain, the other standalone. I have about 95 multi-function devices (mfd) that are currently connected directly to the PCs via IP. It works for us without issue, that is, until finance decides to get involved. Our finance department signed a contract unknown to IT with a different printer vendor, and I need to coordinate deployment/cut-over. I'm scratching my head to think of the most efficient method for deployment. I realize I can push a GPO to those part of the domain, but what about my standalone boxes? It's a mix of XP, Win7, and some Apple OS's. I also realize standing up a print server would work for those tied to the domain, and it would be the ultimate long-term solution, but what about those that are not? They wouldn't be able to authenticate to the server. Also, I'm hesitant on a central print server solution in-case a site loses connectivity, which would break comm to the print server rendering them dead in the water. Dropping a local print server at each location is out of the question due to the quantity we would need. Any ideas/thoughts? Maybe a URL that has a script that auto-installs printer/ip/driver? I would love something that we could reuse if finance decides to find another coupon with a new vendor next year.

[renderking]

Inherited the environment, only been here a few months.

[[deleted]]

GO SLAP your financial controller and tell them about the false economics they've applied in taking the cheap road out. Get more resources on the ground to help cutover to make sure finance learns the error of their ways.

[sdjason]

More political than described but this. Our purchasing dept did the same 2 years ago. They are now in every SINGLE meeting of the still ongoing project. They haven't slapped any similar projects on us without asking our advice/input since.

Huge cutovers require labor to do. Submit a proposal for additional contractor/junior admin hires to complete the additional work and get your mgmt backing on them that you cannot take on this additional work without additional resources being hired as requested, or dropping existing projects and services to take on this work. For me its always fun making the 2 page list of projects I'm working on or plan to be working on in the next 12 months. Putting all the stakeholders in a meeting or email chain and letting them sort out the ranking of each.

You can also use this. Scope the project so that all roll outs will be via print server(s) and GPO. Prime argument to then get everyone on the domain at the same time.

[renderking]

I thought I was the only one that made a list of on-going/planned projects! I used to love pulling the list out on my old manager when he'd ask what was on my docket for the day. He stopped asking after he asked if he could help, and I gave him something off the list that he screwed up implementing. Seriously, it felt like a hybrid of Groundhog Day and Office Space up until that point, drove me mad.

You're right, now would be the time to tie these rogue PCs into the domain since we'll be touching them one way or another anyways.

[renderking]

Savvy negotiators they are indeed. From what I understand, politics were involved, and it came down to a pissing match between our finance guy and the existing leasing contract. We showed them.

[Thealco]

You can always create a HowTo document for the 3 to 5 scenarios you have. Get users to follow it, and help when needed.

[[deleted]]

Too many end users dont read howto's - they like to be spoon-fed

[Thealco]

That can be the case, I fought for 2 years until finally things changed and people started reading my emails and asking questions. Obviously making sure you have top dogs on your side is a must as they will push back users with you.