Funny you mentioned this, I had just come across it and we have just set the DCOM permissions on this unit ensuring that the user has proper permissions(instructions had to be modified, of course for W2K). We will find out if it worked in a little while...
It was a folder permissions issue. After ensuring that the current user was in the proper local groups and also in the proper domain groups, all went well. I had to work with someone in our tech support department to fix this for a customer in the West Indies, so I am not quite sure of the specific fix, as we were extremely frustrated and on tight time restraints. So after a few attempts at other fixes, we made multiple permissions changes to minimize remote reboots.
I am sorry that I can't narrow it down to the very specifics, but I can say for sure that if you double, triple, quadruple check that all related users and groups have necessary permissions to all folders involved in the installation, the issue will be solved.
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.