please help. on the server i have created a shared folder called videos. i HAVED SHARED IT WITH EVRYONE and i am trying to assign a drive letter for it. i went to folder and tools mount drive it doesn't work
Printable View
please help. on the server i have created a shared folder called videos. i HAVED SHARED IT WITH EVRYONE and i am trying to assign a drive letter for it. i went to folder and tools mount drive it doesn't work
Error?
I assume you're trying to map a drive FROM a workstation to this location on the server?
No the file is on the server and i just want to create a drive letter for it so when staff log on to their machines the mapped drive is avalaible to them so they don't have go to my network places and find the shared resources.
simple script
net use x: \\server\videos
obviously alter x to whatever drive letter you want and \\server\videos to the correct network path
This may help - http://www.edugeek.net/wiki/index.ph...Network_Drives
Remember you not only have to give users permission in the Sharing tab, you also have to give them permission in the security tab aswell.
I agree this is most likely the problem, however in theory, the drive should still map, but you'd be denied all access to view it.Quote:
Remember you not only have to give users permission in the Sharing tab, you also have to give them permission in the security tab aswell.
only problem I had was I assigned it as the wrong script startup type ie startup / logon ( cant remember which one I started using ) but it gave me a red cross as though the drive was not available even though it was - easily enough fixed by changing it from one to the other and then it was fine :)
You should map drives in a logon script and not a startup script. You can only set permissions on user or security group and not a computer object.
Not true!!Quote:
Originally Posted by Michael
If you want a startup script to connect to a server resource and "do stuff" then it's perfectly possible to map a drive. What you can't do is map a drive as a startup script and expect it to be available for the user - it won't be.
Also, you can set permissions for computer objects - the commonest one is that if you're deploying software using group policies then the folder which stores the MSI needs to allow "domain computers" read access to it.
Computer objects have SIDs so they can be listed in Access Control Entries just like users and groups