Thanks for the responses guys - however PH's solution didn't work upon further investigation.
As stated above, while "For Each" line was still freezing, I was able to evaluate the colDomains.count w/o freezing.......but on further investigation, the colDomains.count property always ends up...
That didn't get me by the freeze on the "For Each" line, however it was able to get me to the point where evaluating colDomains.count didn't freeze, and I'm fortunate in that when this problem occurs, that ends up being an empty value.
Therefore I can evaluate the count, and skip the For Each...
Bringing this back to the surface with some detail....
Used to have a ton of issues making remote WMI calls and it freezing my script. I wasn't even able to trap an error to make a decision from - it just froze.
I've since found the following line w/ an error trap as a good method to verify...
I have a script where I'm remotely querying some registry keys, and for some reason the ID I'm running this script under continues to populate security events into the remote machines' security event log even after I set the WMI object to Nothing. Don't laugh at my coding, but the following is...
Been searching through this and other forums, to no avail.
Most desktop machines in my environment are running W2K, WXP, and a few NT's. I keep running into an issue with performing a WMI query, where it appears the script hangs (current test been hanging on line for 70 mins). I assume This is...
Does anyone happen to know the correct registry key to prevent the "A package is currently being installed in the background." window from popping up from PCM?
Steve Koehler
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.