Let's say that I have created a share folder to specific user I want to test it and don't know how.
I mean I know I can right click on the folder and view the properties, but I want to "test it on live".
I tried window+R to open "Run" and then entered \\10.1.1.10 and it showed me the shared folder but I can't open it.
my question: how to open it with the user that specific user that binded to this folder?
Login to windows with the new user that you created, and then check if you have access to the folder via UNC
Related
I'm able to successfully list folder and contents when my dropbox developer app has full access, however, when I'm using scoped access only to a specific folder, it fails.
Now when I switch to scoped access to a specific folder I'm running into errors. This request should fail since the app does not have access to the folder.
Now when I put in the right folder path, I'm still getting the same error.
For reference I'm sharing my app details
It looks like you're using the App Folder permission. This will root all your paths relative to that app folder; your app will not be able to see outside of it.
For example, if the user sees the file as "/Apps/AppFolderAccess/myfile.txt", your app will see it as "/myfile.txt". By setting your path to /Apps/AppFolderAccess, it is effectively resolving as /Apps/AppFolderAccess/Apps/AppFolderAccess - which is not found.
If your application needs to see content outside its app folder, you should select full access.
Building on top of the other answer: you need to set the application permission to access type "Full Dropbox– Access to all files and folders in a user's Dropbox."
However, note that this requires you to delete your existing app and create a new one since it is not possible to change the scope of an existing app.
I've seen a lot of answers on copying files that use code to set a network share, with credentials, to copy to somewhere else. However I need a solution that will allow a user to copy from a network share they already have access for, to a local drive they don't have access to.
We run RDS servers and have locked down direct access to the local C:/ drive on the servers. We have been given a 3rd party program that needs to read data files that must be stored in a fixed path on the C:/ drive. These data files are updated once a month. Our users have read access but we do not want to give them direct write access to the root C:/ drive.
I need to write a piece of vb.net, or command line code in .bat file that will copy files to the Local C:/ whilst providing the details of a service account to provide the access.
As mentioned I've seen a lot about setting up a mapping to shared folder and passing creds, however we don't want to set the C:/ as mapped shared drive in this instance.
You don't want the user having access to the C Drive in general, is there any particular reason the permissions on the particular subfolder the files are going to can't have overriding permissions to allow writing to just that folder?
If that will not work, first thought that comes to mind is having a helper program that can be ran under a different user that does have that access. Set up an intermediate folder the user can write to, the program that they can launch drops the files into a folder they have access to. Helper program watches for files in the intermediate folder, moves them to where they need to be.
Set up would need to include adding a user that does have access to both locations, and then adding to task manager to launch the helper program under that other user at login.
Is there some easy way to permanently allow myself full access to all folders and files? I am the only user on a freshly formatted PC, and every answer I could find online seemed to be per folder and a one time solution.
An example of not being able to open a folder is the WindowsApps Folder in my D: Drive.
C:\Program Files\WindowsApps is a restricted folder used for the Windows Store apps. It's designed that way as a security feature to limit the access windows store apps have to your Windows OS. Not all apps on the Windows store are audited and checked to confirm their legitimacy. The folder is purposely designed to act as a little island separated from your user profile and sensitive data. You can gain ownership of it though...
You already found it by enabling show hidden items, so you can go to the folders properties > security > Advanced > Change > [enter your username] > check the box to 'Replace owner on subcontainers and objects' on the next screen. You should now have access to that folder.
I am trying to create a flow that links files on my company's onedrive for business account with our SharePoint site. The first time I tried this, when I clicked the bar beside "*Folder", it listed the folders on my onedrive account and I was able to select the one wanted to create the flow between.
View Creating Flow:
However. A week later, I resolved an unrelated issue with the process and tried to create a new flow, but now, when I try to click the bar, this is all I get. Root is not a file on my onedrive, and it doesn't expand into anything. I have tried, putting in, "/File Name", but it won't recognize the file name, and the flow fails when I test it. I am not sure what I am doing differently this time that is causing Flow not to recognize the onedrive folders.
There is no folder, "root" in my one drive, and root doesn't expand into anything:
Root means the primary (main) OneDrive folder. If you click on the > next to root, it will open up the primary OneDrive folder and list all of the subfolders, as well as, all of the documents in the root folder.
I am trying to upload files to my website.
Every time when upload dialog opens, it tries to open a default path "C:\Windows\system32\config\systemprofile".
This path is not accessible by every user on all the machines except Admin user.
I even tried to set this default path to "My Documents" but i am not able to get this path runtime.
Thanks in advance !
Don't use the My Documents folder, try using Default User's Documents folder instead.
Also check here for more information:
Exceptions in Yesod