I do not use the homegroup feature. I’ve got so many different computers here, running OSX, as well as various shades of linux and various shades of Windows that I cannot be bothered introducing that into the mix.

I think that, in my situation, that would break many things, and my situation is already complex enough that I don’t need more proprietary networking “features” that in reality add no real functionality into the mix.

Depending upon the specific version of Wi ndows that you’re running, that box may, or may not, show.

I didn’t come up with it obviously, but after searching endlessly I finally found a fix that worked for me. Sometimes when searching Google and all the other blogs it really makes a difference what you’re question is.

Anyway I thought on my last search to include HomeGroupUser$ as apart of my issue with the Credential Manager forgetting the settings.

Exact Search: credential manager forgets HomeGroupUser$

And I came across a site that seemed to indicate that the HomeGroup was the issue. Well for me, as it turned out, it was.

To fix it I had to remove / delete all my Windows 7 computers from the Home Group, then build a new one. Once I did that the system stopped reverting back to ‘incorrect’ settings.

One of the things I couldn’t wrap my head around was that even after deleting Credential Manager Credentials, they would invariably be right back to where they were after a reboot. Turns out that with the Home Group all the machines kind of handshake all that information. So by deleting and redoing the Homegroup on all machines, problem solved.

Hope this helps anyone else that all other solutions wouldn’t work for. Thanks.

I’m glad that you got it working, and thanks for the extra information that you’ve provided. Hopefully that will be useful to others..

I felt it was worth noting how I did it. Follow Gary’s procedure above and after you have completed it disconnect/delete your networked drive mapping then go into the credential manager and delete the credentials for that network resource. Once you have done this remap the network share you removed selecting the “Reconnect at logon” check box, I also checked the “Connect using different credentials” box because we are not using logon passwords on our PCs at home, not sure if this is necessary but it worked, I suspected windows might pass the blank password but again I’m not sure. Check the Credential Manager and look at the saved credentials, it should now say “Enterprise” after persistence and should survive multiple reboots!

Hope this helps someone!

Thanks again Gary!

I’ve not experienced what you’re describing; sorry.

BACKGROUND:
I have local Win 7 Pro 32bit workstations who login using the local user. These workstations have drive mappings on a Server 2008 32bit Standard edition. The local workstations change their passwords every 90days but the account on the server does not require the passwords to be changed. User names on WS and Server are the same but have different passwords. Every 90days after the local workstation has changed their password I need to enter the credentials again for the server because the entry (which has worked for the last 90days) is missing.

http://answers.microsoft.com/en-us/windows/forum/windows_7-networking/windows-7-home-premium-laptop-does-not-see-imac/046aea63-d26d-4917-822e-b25f9155baec

but the dword value should be 2, not 1

Next, delete all mappings and credentials related to those mappings. Reboot.
Create a credential with the actual IP address and not the name of the server. Use your regular name and password without the domain prefix.
You’ll notice that the credential now has an enterprise persistence state.
Lastly map the network drive using the IP address instead of the name i.e. \\192.168.0.3\movies

Good luck,

This took me 3 hours to get working!

-Devan

Cheers

Take care.

I just have one problem now… I can’t access gpedit.msc on a PC using Windows 7 Home edition. It works on the Windows 7 Ultimate edition only.

Glad to help.