Hello everyone,
For the first time in my life I have a spare computer that I can use to test things on. So I signed up for Windows Insider and installed Windows 10 on my laptop which I have been using on the regular bases. I'm not much of a writer so I won't even attempt to do a full review on my experience, but I did want to comment on the quality of people that I have found on the Microsoft reviewing forums.
The truth is that people are nasty. I went through quite a few posts and most of the posts was of people complaining and calling that Windows will be a failure. All because of the way that the UI looks. Instead of providing constructive criticism to help develop a better operating system we have people crying about the way that the task bar is, or the way the start menu looks, or the how the icons are flat! I mean come on people! We are all tech savvy here what does it matter what the system looks like as long as it works?
Windows is quite frankly implementing some really good features not only on their desktop environment but on the server environment, and so what if it looks different? We shouldn't be using the system for how it looks but for what we can do with it. After all we can always hack our way to change the way things look.
I do hope that people can change their outlook on how things are going with Windows 10. It will either be a success or a failure, and if its a failure its not like it was a few years back and we actually have options.
Kind regards,
Me.
Showing posts with label Windows. Show all posts
Showing posts with label Windows. Show all posts
Thursday, May 14, 2015
Get-DFSNFolderTarget
Hello!
I been wondering how I can find out where a DFS target is through PowerShell for quite some time now, and perhaps I didn't look hard enough because today I found the cmdlet in the subject.
Get-DfsnFolderTarget [-Path] <String> [[-TargetPath] <String> ] [-CimSession <CimSession[]> ] [-ThrottleLimit <Int32> ] [ <CommonParameters>]
It is a very handy command that will return the following output:
PS Microsoft.PowerShell.Core\FileSystem::\\DFS\SHARE\PATH> Get-DfsnFolderTarget \\DFS\SHARE\PATH | fl * Path : \\DFS\SHARE\PATH State : Offline ReferralPriorityClass : sitecost-normal NamespacePath : \\DFS\SHARE\PATH ReferralPriorityRank : 0 TargetPath : \\targetServer\Share PSComputerName : CimClass : Root/Microsoft/Windows/dfsn:MSFT_DfsNamespaceFolderTarget CimInstanceProperties : {NamespacePath, ReferralPriorityClass, ReferralPriorityRank, State...} CimSystemProperties : Microsoft.Management.Infrastructure.CimSystemProperties
However, I have found it to be less than helpful if I don't know exactly
where the DFS namespace ends and the targetPath begins, for example:
\\DFS\SHARE\PATH\Something\Folder
If I try to find the root using this path I receive the following error:
Get-DfsnFolderTarget : Cannot get DFS folder properites on "Microsoft.PowerShell.Core\FileSystem::\\DFS\SHARE\PATH\Something\Folder" At line:1 char:1 + Get-DfsnFolderTarget $((Get-Item .\).PSParentPath) + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : NotSpecified: (MSFT_DfsNamespaceFolderTarget:ROOT\Microsoft\...aceFolderTarget) [Get-Dfs nFolderTarget], CimException + FullyQualifiedErrorId : Windows System Error 1722,Get-DfsnFolderTarget Get-DfsnFolderTarget : A general error occurred that is not covered by a more specific error code. At line:1 char:1 + Get-DfsnFolderTarget $((Get-Item .\).PSParentPath) + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : NotSpecified: (MSFT_DfsNamespaceFolderTarget:ROOT\Microsoft\...aceFolderTarget) [Get-Dfs nFolderTarget], CimException + FullyQualifiedErrorId : MI RESULT 1722,Get-DfsnFolderTarget
I am not sure why though. It is simple enough to get the information form the
GUI so perhaps is my inexperience or lack of knowledge, but why can't it be
this easy on the cmd line as well?
I do hope that it is just my lack of knowledge and that maybe one of you
might show me the right way to get the DFSFolderTarget path.
Kind regards,
Me
Subscribe to:
Posts (Atom)