Comments on: Script to remove orphaned/stale printer objects http://www.jhouseconsulting.com/2008/07/29/script-to-remove-orphanedstale-printer-objects-31 Application and Desktop Virtualization Specialist with Microsoft, Citrix, VMware and Quest products Mon, 19 Dec 2011 01:21:56 +0000 hourly 1 By: jeremy http://www.jhouseconsulting.com/2008/07/29/script-to-remove-orphanedstale-printer-objects-31/comment-page-1#comment-6632 jeremy Thu, 01 Dec 2011 00:18:04 +0000 http://www.jhouseconsulting.com/index.php/jhouseconsulting/2008/07/29/script-to-remove-orphanedstale-printer-objects/#comment-6632 Hi William, Sorry for not responding earlier. I wrote this for a Citrix environment where it's been used and tested many times on a Windows 2003 server. I have not tested it on a Windows XP workstation. However, from your description the "Memory is locked" error occurs when it tries to enumerate the registry using the EnumKey method and the array it is trying to return. There may be better ways to write this so that errors like these may be avoided. I will try and review it at some stage in the future. Just Googling shows that commenting out the Option Explicit statement and all the Dim statements helps. That's not a good practice, but may help people overcome this issue until I've had time to re-write it. Cheers, Jeremy. Hi William,

Sorry for not responding earlier. I wrote this for a Citrix environment where it’s been used and tested many times on a Windows 2003 server. I have not tested it on a Windows XP workstation. However, from your description the “Memory is locked” error occurs when it tries to enumerate the registry using the EnumKey method and the array it is trying to return. There may be better ways to write this so that errors like these may be avoided. I will try and review it at some stage in the future. Just Googling shows that commenting out the Option Explicit statement and all the Dim statements helps. That’s not a good practice, but may help people overcome this issue until I’ve had time to re-write it.

Cheers,
Jeremy.

]]> By: jeremy http://www.jhouseconsulting.com/2008/07/29/script-to-remove-orphanedstale-printer-objects-31/comment-page-1#comment-6631 jeremy Wed, 30 Nov 2011 23:31:48 +0000 http://www.jhouseconsulting.com/index.php/jhouseconsulting/2008/07/29/script-to-remove-orphanedstale-printer-objects/#comment-6631 If you're referring to "Set oShell = Nothing", that's a very old habit and allows us to explicitly clean up the objects in the right order before they go out of scope. In this function there is only one object, so it's not a good example. However, if you had multiple objects and left it to the script engine to destroy them when they go out of scope, it may not do it in the desired order, and therefore destroy objects you're relying on in other areas within the procedures. Some will argue that it's unnecessary code. Others will argue that it's a best practice. Cheers, Jeremy. If you’re referring to “Set oShell = Nothing”, that’s a very old habit and allows us to explicitly clean up the objects in the right order before they go out of scope. In this function there is only one object, so it’s not a good example. However, if you had multiple objects and left it to the script engine to destroy them when they go out of scope, it may not do it in the desired order, and therefore destroy objects you’re relying on in other areas within the procedures. Some will argue that it’s unnecessary code. Others will argue that it’s a best practice.
Cheers,
Jeremy.

]]> By: Captain Obvious http://www.jhouseconsulting.com/2008/07/29/script-to-remove-orphanedstale-printer-objects-31/comment-page-1#comment-6630 Captain Obvious Wed, 30 Nov 2011 22:45:43 +0000 http://www.jhouseconsulting.com/index.php/jhouseconsulting/2008/07/29/script-to-remove-orphanedstale-printer-objects/#comment-6630 I do not quite understand why you disassociate a local variable from its object right before you exit a procedure. I do not quite understand why you disassociate a local variable from its object right before you exit a procedure.

]]> By: William DiDomenico http://www.jhouseconsulting.com/2008/07/29/script-to-remove-orphanedstale-printer-objects-31/comment-page-1#comment-6621 William DiDomenico Mon, 28 Feb 2011 16:38:25 +0000 http://www.jhouseconsulting.com/index.php/jhouseconsulting/2008/07/29/script-to-remove-orphanedstale-printer-objects/#comment-6621 I know this is an old post, but this script potentially does exactly what I need. However, running the script produces a "Memory is locked" error, citing line 66, character 3. The script is run against XP SP3 workstations. We need to remove printers from a test print server that were accidentally deployed in AD that are not removed by the more traditional RemovePrinterConnection function. I know this is an old post, but this script potentially does exactly what I need. However, running the script produces a “Memory is locked” error, citing line 66, character 3. The script is run against XP SP3 workstations. We need to remove printers from a test print server that were accidentally deployed in AD that are not removed by the more traditional RemovePrinterConnection function.

]]> By: J House Consulting / Script to remove printers http://www.jhouseconsulting.com/2008/07/29/script-to-remove-orphanedstale-printer-objects-31/comment-page-1#comment-864 J House Consulting / Script to remove printers Wed, 30 Jul 2008 13:04:33 +0000 http://www.jhouseconsulting.com/index.php/jhouseconsulting/2008/07/29/script-to-remove-orphanedstale-printer-objects/#comment-864 [...] If, however, you find that some printers just cannot be removed, try my other script to remove orphaned/stale printer objects. [...] [...] If, however, you find that some printers just cannot be removed, try my other script to remove orphaned/stale printer objects. [...]

]]>