Problems after repairing corrupt User Profile (Win7)

About 2 weeks ago, a client went to work after a week off and powered up their PC and went to login; they were greeted with an error after typing in their password; something about the password having expired, or that the user profile was loaded incorrectly (I don't remember the exact message). I tried Safe Mode, and that didn't work. I then used a password reset PE-based CD to remove the password from the account and that resulted in the same error message. So, then I used the steps in "Option 1" in this article to fix the problem and now the user can login and just about everything works perfectly, except for connecting to the in-office network (I did not fix the PC in the users office; the PC was brought to me for repair). Apparently, the user cannot use Quickbooks anymore (it is installed on an in-office server so all employees can access it via the network), the user cannot use the shared network printer anymore, etc. Essentially, anything on the network is now inaccessible. They claim that the server has no password to login and that all attempts to connect to the server have been unsuccessful. I did not set up the office network and I know nothing about its configuration. The PC I worked on can access the internet and surf w/o problems so I know that it has the ability to use the network. So, I guess my questions are: how can using the steps in "Option 1" in this article prevent the user from accessing the in-office network since I made NO changes to ANYTHING related to networking? How would repairing the corrupt user profile service cause the networked Quickbooks to go haywire? How can this situation be remedied? I'm not really a networking "guru" but I do know the basics of networking like setting up a shared printer, shared hard drive, shared folders, etc; I am NOT a Quickbooks guy, I know nothing about it let alone how to use/configure it for network use.

THX!

(sorry for the length of the post :-o I had to describe exactly what was going on)

 

I've spent some time researching this and so far have found NOTHING to indicate that any repair(s) that I did were in any way responsible for any problems that now exist with connect this one PC to the in-office network .... so I think that the end user(s) just simply do not have the info required to connect to the network, and since I removed the user login password on the PC in question, all I can think is that they must configure the main user acct on the PC in question to have the exact same password and permissions it had before the user profile was corrupted, and they have to know what is required to login to the in-office server from a networked PC. I have none of the passwords or user acct info for ANY system in the office, so I think this is more of an end user issue than a "the guy that fixed my login problem screwed everything up" type of problem.

If ANYONE has ANYTHING to add, suggest, offer, whatever, please post!

THX!

and HAPPY HOLIDAYS!

 

Not sure if this will help. It is for XP but should be similar to Windows 7. Shows the relationship between the SID and the server. When the account profile in the registry was changed, maybe it has to be given full permissions as in step 1. Just throwing out guesses because this is really out of my comfort zone. Good Luck.

http://www.raygibson.net/kb/profile_migration/

 

As I suspected, it was nothing that I did "wrong", it was the end user's lack of knowledge. Once they realized what I meant by "you need the password that is used to login in to the server where the software/printer is installed", they figured it out pretty quickly.
:banghead