Joining Vista Prof. to domain



Why does it take so long for Vista to join a domain?

I have a vista pro machine. Locally everything works fine
local user signs on builds the desktop quickly.

From the local profile I join a domain. It finds the domain
quickly, then asks to reboot.. I reboot sign on as the
admin of the domain.. Next step is to build the desktop
for the user I'm signing on as.. It just sits on the welcome
screen spinning.

I do not experience this problem on XP machines joining
this same domain. I've also tested it on a Windows 7 machine
and did not experience this problem.. I can't figure out why
it takes so long on Vista.. I actually never get to the point
of building the desktop..I don't really see any hard drive
activity either?

Anyone experience this?


further more I check DNS the comptuer is listed there. It's also listed
computers in Active Directory Users and computers..


More info to report.. After doing some google searching.

I have a Windows 2008 Domain.. In there I want to use GROUP POLICY
to map printer and drives..

After researching the issue on google. Some people were reporting that the
long logon times to a domain have to do with Group Policy..

My group policy is rather simple. It maps a couple of printers and maps a
of drives to shares..

To test out the slow login. I removed ALL mapped drives and ALL printers
the group policy on the Windows 2008 server. I then went to the VISTA
and tried to sign on. It signed on as expected and created the desktop

If I put in the mapped drives and printers in the group policy the VISTA
does not sign on at all it just sits there on the welcome screen..

Why is this?? I know on XP machines I had to install Group Policy client
side extensions and
XML Lite.. After that my drive mappings and printer mappings all worked

Do I need something for VISTA? I'll give it a shot and see what I come up

The poster formerly known as 'The Poster Formerly

On 3/8/2010 10:56 AM, George wrote:


When you get to the point when vista gets stuck on the welcome screen,
try hitting ctrl+alt+del and bring up the task manager and see what
happens - see what is taking up most of the cpu cycles, and report back.

Peter Foldes

You should be posting this to the windows.server.networking. Read the posts .Last
week a similar issue was posted and answered correctly. Basically the fault and the
resolution lies with the W2K8 and not with vista


Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question