A
Ashith
I was trying to install Windows XP service pack 2 on one of the
machines
at my work place. I was not able to install as I was getting a "Win32
Access denied" error everytime I tried to install. Also, on some
machines with SP2 I could not see the "Network connections" and could
not access the dependancies tab in the Windows Installer service. My
colleague at work, Clerita finally found the soln. to the problem
thanks to some extensive searching and sleepless nights and some help
from the google groups.
The soln. to the problem is to change a few settings in the Default
Domain Policy on your server.
The relevant part of the Default Domain Policy that caused this is
shown in condensed form below:
Console Root
{Group Policy}
Computer Configuration
Software Settings
Windows Settings
Scripts (Startup/Shutdown)
Security Settings
Account Policies
Local Policies
Audit Policy
User Rights Assignment
Impersonate a client after authentication <MyGroup>.
Resolution: Change the above policy setting for Impersonate a client
after authentication to: Administrators, <MyGroup>, SERVICE.
Restart the workstation twice (once to pick up the change in Group
Policy and again to be affected by it at Windows startup).
And folks this thing really really works. This is not a very common
problem and the research we had done to find the needle in the haystack
was tremendous.
For complete update on this issue visit:
http://www.eventid.net/display.asp?eventid=4609&eventno=1993&source=EventSystem&phase=1
Thanks to all the people in the above newsgroup for their insight into
the matter.
machines
at my work place. I was not able to install as I was getting a "Win32
Access denied" error everytime I tried to install. Also, on some
machines with SP2 I could not see the "Network connections" and could
not access the dependancies tab in the Windows Installer service. My
colleague at work, Clerita finally found the soln. to the problem
thanks to some extensive searching and sleepless nights and some help
from the google groups.
The soln. to the problem is to change a few settings in the Default
Domain Policy on your server.
The relevant part of the Default Domain Policy that caused this is
shown in condensed form below:
Console Root
{Group Policy}
Computer Configuration
Software Settings
Windows Settings
Scripts (Startup/Shutdown)
Security Settings
Account Policies
Local Policies
Audit Policy
User Rights Assignment
Impersonate a client after authentication <MyGroup>.
Resolution: Change the above policy setting for Impersonate a client
after authentication to: Administrators, <MyGroup>, SERVICE.
Restart the workstation twice (once to pick up the change in Group
Policy and again to be affected by it at Windows startup).
And folks this thing really really works. This is not a very common
problem and the research we had done to find the needle in the haystack
was tremendous.
For complete update on this issue visit:
http://www.eventid.net/display.asp?eventid=4609&eventno=1993&source=EventSystem&phase=1
Thanks to all the people in the above newsgroup for their insight into
the matter.