R
Roy
I have a problem with xp. I know why it is happening but
need to know if there is a solution other than to rebuild
600 xp computers before migrating them to active
directory.
1. Connecting to the xp computer remotely using computer
management, comes up with access denied in device manager
and network path not found in event viewer and local
users and groups. I can connect to the xp system through
windows explorer and stop and start services remotely.
2. We are beginning to migrate our computers to Active
Directory. When an xp computer is moved to the AD domain,
group policies are not being applied. Events 1058 and
1030 appear in the app log.
All the xp systems have been built using ghost and
sysprep to build system images. As part of the image, the
computer is made a member of a domain. On the first
reboot, the mini-setup kicks in and only asks for the
computer name. Thats when the 2 problems above happen!
Removing the machine from the domain and back again does
nothing.
However, I have created a new image, where the computer
is not a member of a domain. After the computer is
restarted, it is then added to a domain and everything
works fine.
Probably not enough information, but does anybody have
any idea what is going on here? I am assuming there is
something being set in the registry but don't know where.
How can I fix 600 machines without rebuilding them all?
need to know if there is a solution other than to rebuild
600 xp computers before migrating them to active
directory.
1. Connecting to the xp computer remotely using computer
management, comes up with access denied in device manager
and network path not found in event viewer and local
users and groups. I can connect to the xp system through
windows explorer and stop and start services remotely.
2. We are beginning to migrate our computers to Active
Directory. When an xp computer is moved to the AD domain,
group policies are not being applied. Events 1058 and
1030 appear in the app log.
All the xp systems have been built using ghost and
sysprep to build system images. As part of the image, the
computer is made a member of a domain. On the first
reboot, the mini-setup kicks in and only asks for the
computer name. Thats when the 2 problems above happen!
Removing the machine from the domain and back again does
nothing.
However, I have created a new image, where the computer
is not a member of a domain. After the computer is
restarted, it is then added to a domain and everything
works fine.
Probably not enough information, but does anybody have
any idea what is going on here? I am assuming there is
something being set in the registry but don't know where.
How can I fix 600 machines without rebuilding them all?