Just last night i found entries in the default domain policy disabling all
kind of services. I haven't got the faintest idea where these came from. Most
of them seem to be ignored anyway, because most of them are running. DHCP
Client doesnt. The policy disables it, but on the VISTA machine it is
enabled. You just can't start because of an "access denied". It seems that
the password is messed up. The account it self seems to work, because other
services using that account are running.
I will remove all these senseless entries form GPO and then try again - the
thing is only that the VISTA macghine is mainly offiste and needs to go
on-site to update the whole policy settings, so it may take a while to find
"Ben Derr" wrote:
> Any domain based GPOs that touch these services?
> Benjamin Derr
> "Wolfgang Bures" <Wolfgang Bures@discussions.microsoft.com> wrote in message
> >I am having the same symptoms.
> > Did you get any responses or solutions?
> > "ZackMan18" wrote:
> >> I realize that this has been posted before, but no solution seems to be
> >> found. This is a HUGE problem and will abosolutely prevent any rollout
> >> of
> >> Vista in my organization if there is no solution to this problem.
> >> Basically,
> >> the problem is this:
> >> - New Vista setup (new install or upgrade using RC1) works fine until
> >> joined
> >> to the Win2K3 domain.
> >> - After joining the Win2K3 domain, Vista still OK after the first reboot,
> >> but after a subsequent shutdown/restart, the following happens:
> >> * DHCP Client service shuts down with a 1004 Access is denied error.
> >> * No IP address is leased from the DHCP server (since no DHCP Client
> >> service)
> >> * Machine is logged in with cached login information but no attempts
> >> to
> >> correct the network failures are successful.
> >> So far I have found no solution to this problem other than reinstall the
> >> O/S
> >> and all applications. I have tried saving a Restore point before joining
> >> the
> >> doimain and that is not sufficient for restoring the system to a working
> >> state.
> >> Additional information:
> >> - In addition to the DHCP Client not starting, the following "automatic"
> >> startup services are failing as well:
> >> * Base Filtering Engine
> >> * Diagnostic Policy Service
> >> * IKE and AuthIP IPsec Keying Modules
> >> * IPsec Policy Agent
> >> * Network List Service
> >> * Network Location Awareness
> >> * Thread Ordering Server
> >> * Windows Audio
> >> * Windows Firewall
> >> * Windows Time
> >> * Windows Media Center Service Launcher
> >> All of these services are set to Log On as "Local Service" except IPsec
> >> Policy Agent and Network Location Awareness - these are set to Network
> >> Service. Incidentally, there are about a dozen services which use the
> >> Local
> >> Service account that are starting correctly so I'm not sure what the
> >> problem
> >> is.
> >> Please Help.