Deploying printers via group policy

[Southwell]

Does anyone know where i can get the console printmanagement.msc?

 

Thanks.

[cookie_monster]

It's part of 2003 R2 if you're running that then you can add it into an MMC.

[Southwell]

We have it installed and we still can't see it :s

[cookie_monster]

So if you open an MMC and select add you don't get a Print Management option?

 

Have you added the print management componant in add remove windows componants?

[cookie_monster]

http://www.windowsitpro.com/Articles/ArticleID/93954/93954.html?Ad=1

[Southwell]

So if you open an MMC and select add you don't get a Print Management option?

 

Have you added the print management componant in add remove windows componants?

 

There is no component in there. :?:

 

Thanks for your help btw 8)

[cookie_monster]

What about if you follow the winitpro link?

 

http://www.windowsitpro.com/Articles/ArticleID/93954/93954.html?Ad=1

[sidewinder]

DONT USE IT!

 

It works, but you have to be so careful about removing printers the right way

 

Considering how easy a script is, especially when so many have been posted on this site, its not worth the hassle

[cookie_monster]

sidewinder is right that script are a better way but the console still has other handy features and is still worth installing IMHO

[Southwell]

We use scripts at the moment but we are going across two networks with different domains. We are halfway through a project to combine the curriculum subnet with admins new one. This wont be happening until summer and the printers keep dropping the passwords so teachers are finding it difficult to print to the curriculum side.

 

Iam going through that website, but it seems to just state what to do, i cannot find any instructions on what to do if you havn't got the component.

[cookie_monster]

Have you installed the R2 CD do you see options to add any other R2 features like the File server resource manager?

[Southwell]

It looks like we need to upgrade the schema in AD, this will have to be a half term job though. Thanks everyone for your comments and help.

[cookie_monster]

You might want to do a test run on a spare server but the schema update is tiny and took about 30 seconds when we did it and no reboot was required. It could be an after school or weekend job.

[Southwell]

Is there a problem with replication to our main Admin server though? We are currently doing this on our backup admin domain controller. Or should we be doing this onto our main DC and allowing it to replicate out?

[cookie_monster]

There are no main or secondary servers in Active Directory all server are writable so that shouldn't be a problem. You could try to add it on another R2 server just in case but if you haven't updated the schema that is likely the problem.

[Southwell]

Ok thanks for that, i will let my manager know and see what he wants to do. Apparently he already told my colleague it was the schema, but my colleague forgot

[Michael]

You only need to update the schema on your domain controller. You can install Server 2003 R2 without a reboot and then add Print Management from within Add/Remove Programs.

 

The only thing I noticed is that "R2" isn't displayed when viewing Help > About Windows from My Computer, but once you perform a reboot R2 is displayed.

 

In my experience, you must always update the domain controller first and then any member servers (as required). Doing it the other way round just creates errors. It depends how your network is setup. Your DC may also be a print server (for example), but you may have delegated this task to another server if you have a lot of network printers to manage, hence you'd need to update two servers to R2.