Meant to post last week when I sorted the problem but was busy implementing it through all the labs and testing it.
To Domino and Localzuk, thanks for all your suggestions and help. You got me going in the right direction. To all who posted after my last post thanks for taking the time to help out and I'm sorry I didn't get back sooner to say its sorted.
As it turned out I found an older version of pmcmgmt.exe on the Microsoft site which was about 745KB instead of the 1MB version I was talking about in my post. When I ran this on my XP laptop it installed itself and then finished. I was a little perplexed but I did a search of my laptop for pushpushprinterconnections.exe after the install and I found it in C:\WINDOWS\pmcsnap and copied it to the server. I then setup the the pushprinterconnections.exe as per localzuk's post (the link gives instructions):
Once this was done I rebooted my test PC and it worked!! Thank God for that. I deployed the test printer to one of the computer labs not in use that afternoon and rebooted a few of them and sure enough they had the new printer installed when I logged in. There was a mock exam the following morning so I left it set up and the report back was everything worked.Quote:
Do you have the 'pushprinterconnections.exe' file set up? Deploy printers by using Group Policy
So thanks again to Domino and to localzuk.
To Bruce123 who said
I think this would be correct except the domain functional level is at server 2003. Could I upgrade that without any bad things happening? I'll have to look into that.Quote:
I know this has been expressed already, but I would personally forget about using pushprinterconnections.exe and use the Group Policy Preferences section in 2008/R2 to deploy your printers, instead.
Thanks to Sted who offered to send me a copy, I had obtained the right one by then but the offer is appreciated.
Great forum! I will try to help other here but as I'm only starting out in the server world I don't have much experience.
I'll be back :)