"Admin Shares" totally missing from Windows 10 x64, specifically C$ and ADMIN$.
We have a few pc's with various remote connectivity issues in Windows. One of them most perplexing is the abscense of the C$ and ADMIN$ shares (known as "admin" shares colloquially). I have tried to recreate them manually using the cmd format of "net share C$=C:\", but it only lets me recreate C$ not ADMIN$ and even C$ isn't contactable through a remote windows explorer session. I am hoping to script this so that I can add it to my "fix all the blasted remote connectivity stuff" batch script I have started. Does anyone know of a way to fix these so that you can connect via windows explorer on a remote pc again?
These machines are all Windows 10 x64 with Windows 1803 installed currently. Any assistance would be so truly appreciated. I really want to make it so we can remotely deploy software again to these poor folks. Thank you!
These machines are all Windows 10 x64 with Windows 1803 installed currently. Any assistance would be so truly appreciated. I really want to make it so we can remotely deploy software again to these poor folks. Thank you!
Assume you don't have the Windows Pro edition (or higher)? Then it's by design.
Admin Shares are available on Windows 10 Home (I checked first)
Yes, my apologies, disregard my comment.
Is c$ accessible on the local PC (\\localpcname\c$, on that same PC)? I know, not much sense in doing so, it's just a step to further any new conclusions)
Is c$ accessible on the local PC (\\localpcname\c$, on that same PC)? I know, not much sense in doing so, it's just a step to further any new conclusions)
ASKER
The PC is a Windows 10 Education Edition (almost the same as Enterprise functionally, but licensed for schools). It is a domain joined PC. C$ and ADMIN$ are both missing from the PC and I have no clue why. I tried a few things to fix it, but to no avail at all. Also no "AutoShareWorks" entry. Tried updating to 1809 hoping the update would fix it, no dice.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Hm, so this worked? That's weird.
Anyway, it should have been points for David or at least an even split, I only urged you to use it.
Anyway, it should have been points for David or at least an even split, I only urged you to use it.
ASKER
Awesome this worked! As a recap, I found that the entry for: HKEY_LOCAL_MACHINE\SYSTEM\
I am going to try to batch script this. I believe the entry: reg add "HKEY_LOCAL_MACHINE\SYSTEM
Thank you very much everyone and thank you McKnife for the final recommendation!
I am going to try to batch script this. I believe the entry: reg add "HKEY_LOCAL_MACHINE\SYSTEM
Thank you very much everyone and thank you McKnife for the final recommendation!
So the entry was there before, after all?
ASKER
The AutoShareWorks entry on that machine existed, but was set to "0". On all my other functioning machines the "AutoShareworks" entry isn't there at all whatsoever. Strange. Should it always be there?
It is not normally there, someone/something added it and set it to 0 to disable the Administrative Shares. Once it is set to 0 it must be set to 1 to re-enable the shares, Afterwards it can be removed if you are OCD otherwise it does no harm.
"The AutoShareWorks entry on that machine existed, but was set to "0".
That's what David thought and asked you to correct to "1"
You replied "Also no "AutoShareWorks" entry"
That looks funny now, doesn't it? That's why I asked for clarification, as it was the main suspect right from the start.
Setting it to "0" was surely a security measure by another admin.
Ok, good that it's solved.
That's what David thought and asked you to correct to "1"
You replied "Also no "AutoShareWorks" entry"
That looks funny now, doesn't it? That's why I asked for clarification, as it was the main suspect right from the start.
Setting it to "0" was surely a security measure by another admin.
Ok, good that it's solved.
ASKER
In my first post I had stopped one directory up from the "Parameters" directory in the registry tree. I didn't see the DWORD and figured it wasn't there. Saw my mistake later. Thank you all for your assistance.
Via registry
HKeyLocal Machine\SYSTEM\CurrentCont
if there is an entry AutoShareWks set it to 1, to disable set it to 0. This entry is not there automatically