sarahstacey Posted May 16, 2016 Posted May 16, 2016 Hello, I've upgraded about 30 pc's to Windows 10 Pro from Win 7 Pro. I'm having trouble with users connecting to home drives, shared drives and also group policy being applied. Generally the home drive error is 'bad username or password' and the shared drive error is 'device name is already in use' Looking at event viewer group policy is failing to be applied with 'the specified network password is incorrect' I have searched for help and tried a few different things but nothing has worked. Can anyone help, I'm on the verge of rolling back to Windows 7 Thanks in advance Sarah
DJ-1701 Posted May 16, 2016 Posted May 16, 2016 Hello, I've upgraded about 30 pc's to Windows 10 Pro from Win 7 Pro. I'm having trouble with users connecting to home drives, shared drives and also group policy being applied. Generally the home drive error is 'bad username or password' and the shared drive error is 'device name is already in use' Looking at event viewer group policy is failing to be applied with 'the specified network password is incorrect' I have searched for help and tried a few different things but nothing has worked. Can anyone help, I'm on the verge of rolling back to Windows 7 Thanks in advance Sarah Question, how are you mapping the drives are mapping drives using Group Policy Preferences? or an old Batch file?
DJ-1701 Posted May 16, 2016 Posted May 16, 2016 Using group policy preferences Odd, that should be working... I have set our mapped drives with the following settings which are compatible with Windows 10. How do yours compare?
sarahstacey Posted May 18, 2016 Author Posted May 18, 2016 Thanks for the reply, I've compared your settings with mine and made some changes. It looks like GP setting for mapped drives is not being applied due to 'The specified network password is not correct' I'm really confused with it all, I'll hopefully get some time later today to have another look.
tmoon-mint Posted May 18, 2016 Posted May 18, 2016 What build of Windows 10 is it? We had an issue with an earlier build where this would happen for people with blank passwords.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now