Discussion Locked

C$ share local access

0 helpful
15 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I administer an NT4 domain with 60 PCs, two BDCs and a Unix server. A workmate imaged a workstation system to a larger hard disk using Power Quest Drive Image. The trouble is that after the user logs on the OS asks for username and password for the administrative share C$. It also asks for username and password when one of his desktop shortcuts is run, namely Act 2000. There is no problem when logging on as Administrator. It seems to be a permissions problem. Or is it something to do with the user profile. Is there a fix for it to avoid reloading the OS and apps?

15 replies

by Member 20192539

You could try adding a new share and give the user full access on the new share, since it will not let you modify the existing administrative share...

by Member 20192539

You could try adding a new share and give the user full access on the new share, since it will not let you modify the existing administrative share...

by david.funnell

Start svrmgr and remove the problem PC from the domain and then add it again (make sure that the PC is not in use at the time).

Rgds

David

by spioinu

I've seen this problem before with imaged drives. I just thought it was our crappy software dept. that did a loser job on the image! Maybe not. the only was i was able to fix this was to search the the drive for any shortcuts that listed the hidden share as part of the path. i.e: \\computer\C$\programe files\IE5\explorer. The search was every shortcut, and the whole registry. I think it had something to do with the default profile so every new profile would create shortcuts that had the same error in the shortcut path.
Good luck

by nettek

You cannot adjust the share permissions to the C$ share. However, go to the root drive's security permissions and make sure that the Administrator and System accounts have Full Control, and the Everyone Group has Change permissions.

by ð

Make sure all ur share drives are disconnected and take the PC out of the domain before u image it. U should try looking into using "SysPrep" with PQuest or Ghost. Sysprep is by Microsoft, it is a great utility. It strips down all the SIDs and regenerates new ones. U can also setup a simple unattend answer file to have it generate different computer names and rejoining it to a domain.

by mcarswell

Question?
I will assume this is a Windows NT box.
When the Original drive was imaged was this machine part of the domain and did you use sysprep?

If not I would recommend removing the machine from the domain Run Sysprep (For more information goto Microsoft KB) with the nosid switch and reboot the machine. This will take you in to the Gui setup of win2000 once this is finished you should be able to rejoin this machine back to the domain and log in successfully with out effecting any of your installed applications.

This discussion is closed to new replies.