Recently Microsoft has been taking security serious (well, they are at least trying). For those of you who have installed Exchange 2010 you know what I'm talking about. Previously when installing Windows (or Exchange) everything was wide open. Pretty much an "enable everything, close it later if you don't want it" type of mentality. Lately they have been closing or disabling services, not installing all components unless needed and turning on all software firewalls.
Recently I was installing software from a server that needed to connect to the admin$ share on a computer and install components. So i did my usual:
net share admin$ /users:5
I was able to connect but couldn't make a directory. After looking at the help I needed to add the admin$ share using this command:
net share admin$ /users:5 /grant:username,full
username being either a local or domain username. If using a domain username make sure to put the domain name followed by a backslash and then the username (ie, contesto\bsmith)
Subscribe to:
Post Comments (Atom)
Error 1312 when adding ssl cert
If you get an error when using netsh to add a cert thumbprint, make sure you have a private key attached to the cert. Also, make sure the c...
-
If you get an error when using netsh to add a cert thumbprint, make sure you have a private key attached to the cert. Also, make sure the c...
-
I was trying to connect to the Microsoft store to update my windows from 8.1 Preview to 8.1 and for the whole day i was getting: “We were...
-
Unfortunately we have some programs that require Windows Server 2003. While I hate having old deprecated servers n my environment, sometimes...
No comments:
Post a Comment