Windows 10 Client issues in 2003 Server Domain network.

I have recently installed Windows 10 Pro on my laptop (previously upgraded from Windows 8.1 but had to do a clean installation in the end) and have added to the Server 2003 Domain network at work.

Logging onto the network was an issue in Windows 8.1 but this seems to have resolved itself in Windows 10 ( well it used to take 7 mins to log on to the network and it now takes 3 minutes), but I can no longer shut down properly. I gave up after 20 mins yesterday and then just hit the off button.

If a log on to my local account, startup/shutdown isn't a problem.

The other clients are running Windows 7 Pro and use the same profile. My profile has been unchanged since I had Windows 7 as well.

Could the profile be the issue?

I tried removing the roaming profile once and it completely messed things up, hence why I had to install Windows 10 from fresh. We are due to upgrade the server to Windows Server 2012 in a couple off months so wondering if I have to grin and bear until then.

Any help would be appreciated.
Javed ChowdryAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Right now I see no connection to 2003.
Please remove the network cable - does that influence shutdown?

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Muhammad MullaSystems AdministratorCommented:
I would start looking at GPO.

Have a look at the client's event logs. They may indicate that group policy is being processed.

You can test by placing in a separate OU and applying your Group Policy Objects one at a time to diagnose the 'guilty' policy.
Javed ChowdryAuthor Commented:
Woorked a treat. Took just the 2 mins to shut down which is a definite improvement. Why would that be?
Why did you close already? :)
It could be, because of scripts that run at shutdown or at logoff.

Examine your logoff/shutdown scripts, let those run interactively.
Logoff scripts: run them as your user
Shutdown scripts: run them as system account like this:
1 download psexec (freeware by microsoft)
2 rightclick cmd.exe and select "run as administrator" ->cmd opens
3 type
psexec -s -i \\yourDC\sysvolshare\...\shutdownscript.bat

Open in new window

See what happens - you will be able to look for errors now and maybe it simply hangs at some step and asks for input. Then you can adjust your script and problem solved.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2003

From novice to tech pro — start learning today.