Print Management per-computer GPO delivery
Up until now to map network printers I've been using vbs login scripts mixed with GPO loopback functionality based on OU location but ideally want to use the Print Management console included in Win 2k3 R2 which uses pushprinterconnection.exe to deploy on a per computer level.
The way this is meant to work as I understand it is that if a computer is moved out of the applying OU, the pushprinterconnection.exe should remove the mapping. The problem I'm having is that when the computer is removed from the OU the printer mapping still remains even after multiple boots, forced group policy update and even manual deletion.
Googling this, it seems that this may be a bug when using this on a per-computer configuration and some mention that the mapping gets tattooed onto the users registry which is why this still appears even after manual deletion.
Has anyone else had any joy with this or found a workaround?