W2k8 R2 AD - Home Folder not created on HP Desktop dc5800 clients (Windows 7)

Hi all,

We have a brand new Windows server 2008 R2 domain set up. Approx 30 clients, all now upgraded to Windows 7.

In AD, all users are set up to connect H: to the share \\server\users$\%username% and to map the drive G: to \\server\common using Group Policy.

This works fine for all clients (mostly Acer and dell dektops/laptops), but two HP Compaq dc5800 machines does not map H: or G:

If I try to map G: and H: manually from these clients by typing the URL, it works fine.

If the users of this clients log on to another (non-hp) client, everything is ok.

Everything else works though... Like AD printer mapping, shortcut creation...

I have tried to set the "Always wait for the network at computer startup and logon" to Enabled in GPeditor, but this did not help.

I think it is a problem with the network card in the HP machines. HP support keep asking me "Have you tried to reboot the client?", so I have given up calling them ;-)

Anyone else had this problem or any tips on what to try next?



bedardAsked:
Who is Participating?
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.

NJComputerNetworksCommented:
Have you tried to reboot the client?

0
NJComputerNetworksCommented:
Just kidding...

"If the users of this clients log on to another (non-hp) client, everything is ok. "  so... it seems that there is not an error in the profile settings in the domain...

"If I try to map G: and H: manually from these clients by typing the URL, it works fine."  I'm assuming that you are doing this as the user (not as admin)... so, we can rule out a problem with NTFS rights or something of that nature...

I would attempt this..

1) reboot the client
2) try to login to the domain on the problematic machine

Check event viewer for errors... especially in the security log.  Also go to the server and check for errors with an emphasis on the security logs.  (also enable security logging if not already enabled)


A double check here...  "In AD, all users are set up to connect H: to the share \\server\users$\%username% and to map the drive G: to \\server\common using Group Policy."

Are you setting the H: drive in the profile or are you configuring the H: drive mapping in custom script?

Are the other workstation OS's in your environment Windows 7?  Maybe this is not an HP vs other hardware... but a Windows 7 vs Windows XP?
0
bedardAuthor Commented:
--> "If I try to map G: and H: manually from these clients by typing the URL, it works fine."  I'm assuming that you are doing this as the user (not as admin)... so, we can rule out a problem with NTFS rights or something of that nature...

This is done as the user, so its not a NTFS rights issue.

--> Are you setting the H: drive in the profile or are you configuring the H: drive mapping in custom script?

This is done in a group policy setting as follows (works fine on all other clients)

Preferenceshide
Windows Settingshide
Drive Mapshide
Drive Map (Drive: G)hide
G: (Order: 1)hide
Generalhide
Action Create
PropertiesLetter G
Location \\Gramo-fil\Felles
Reconnect Disabled
Use first available Disabled
Hide/Show this drive No change
Hide/Show all drives No change

--> Are the other workstation OS's in your environment Windows 7?  Maybe this is not an HP vs other hardware... but a Windows 7 vs Windows XP?

Yes, all clients are Windows 7. They are all set up in the same way using w2k8 r2 Windows deployment services.

--> 2) try to login to the domain on the problematic machine

Check event viewer for errors... especially in the security log.  Also go to the server and check for errors with an emphasis on the security logs.  (also enable security logging if not already enabled)

There is one relevant error in the Application event viewer of the problematic machines. I have to translate from norwegian...

1. Could not redirect the home folder to %homeshare%\users\<username>

Source: Folder Redirection
Event ID: 502
Level: Error

This error is expected as the home folder is not mapped.

There is also an "error" in the security log: (Translated from Norwegian using google translate):

Code integrity determined that the image hash of a file is not valid. The file may be corrupted due to unauthorized modification, or invalid hash could indicate a potential disk device error.

File Name: \ Device \ HarddiskVolume1 \ Windows \ System32 \ drivers \ wpshelper.sys

Source: Microsoft Windows security
Event ID: 5038
Level: Information



0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

NJComputerNetworksCommented:
was seeing this error in several windows Vista environments where folder redirection was being used. Upon giving the user ownership of their redirected folder, the error disappeared.
0
bedardAuthor Commented:
Setting the owner did not solve the problem.

If the user log on to any "non hp" machine, all mappings work fine.

If I log on to the hp machine, it does not work. It works fine on my Dell laptop and on a Acer workstation I also use.

Weird problem....

0
NJComputerNetworksCommented:
it is strange... you can try the old... remove machine from the domain and re-add it trick..
0
bedardAuthor Commented:
There ia allways a simple soulution...

The HP Desktops have a buildt-in Card-reader which uses the driveletters E: through I:

The drives did not show up in "My computer" due to no windows 7 driver...

I re-mapped the drive letters for the Card-reader to R: etc and now its all working like a charm.

0

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
NJComputerNetworksCommented:
So letters were already in use by the card reader...  lol einstien
0
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 7

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.