smb
2 TopicsCheck (and modify) network drive mappings as an admin for other users
It does not appear that admins can check/modify a user's network drive mappings (e.g. from `\\server\shares` to a drive letter) via powershell? The various `Smb-` commands seem to be per user, and as far as I can tell, there is no way to run a powershell command as a different user without using their credentials (which seems to be poor security hygiene to ask users for their passwords), even if you are an admin. Am I missing something, or is this not possible? In case it helps clarify things, what I am asking about is the Windows equivalent to `sudo -u some_user some_command`.84Views0likes4CommentsWindows smb client and Zone.Identifier (WSL) authentication problem
hi together, we have an import process which import data from a csv file from a nas. I have change the nas server (from old to new server) and activate smb logging. Now i can see the following problems. We have on the nas a local user for application access and on the windows client side a other local user too (different names). Client machine is windows version 1809 build 17763.6414 (windows 10 enterprise ltsc). 1. problem - wrong Authentication Data for writing "Zone.Identifier" We configred the authentication data in the import process and the process used this data for access to the csv files. But it looks like that windows meta data process don't use this authentication data. I saw in tcpdump pcap file 4 smb sessions. First and secound smb sessions use the authentication data for the access to the 2 csv files. The third smb session use no authentication data. so that the access don't work. Whatevery windows in the third smd session will doing. The fourth smd session use a mix of source maschine name und destination user, which is not correct. I add read/write access for everbody, so that i can see, what is doing in the fourth session. Windows will writing/access to the Zone.Identifier file. 1. smb session: User: <nas>.<domain>\<nas_user> 2. smb session: User: <nas>.<domain>\<nas_user> 3. smb session: User: \ 4. smb session: User: <client machine name>\<nas_user> 2. problem - ignore "Do not preserve zone information in file attachments" setting now i activate this setting, so preventing writing of this kind of informations/files. But the windows client ignoring it. I have reboot the windows client and repeat the import process and windows tried to writing the zone information again. I change the setting about the following way. admin: gpedit.msc -> User Configuration > Administrative Templates > Windows Components > Attachment Manager and than enable the policy named "Do not preserve zone information in file attachments". Is this a know issue or hae sameone any idea? I would prevent the 3. and 4. smd session, so the access for the meta data proccesses. best regards Christian Voigt246Views0likes3Comments