Creating a sub directory “SubDir” and a symlink to it, called “SymLinkSubDir”, results in the following folder view: Mode LastWriteTime Length Name However, that is no solution because the same issue holds true for symbolic links to folders. Of course, you can look at the item’s length. You can immediately see what is bothering me: You don’t recognize that you have a symbolic link. Now, try to check the folder’s content by using Get-Childitem: Mode LastWriteTime Length Name You could of course also use the “good old” cmd prompt, which offers mklink.exe command. You can use the PowerShell Command New-Item -Name C:\MyDir\MySymLinkFile.txt -ItemType SymbolicLink -Value C:\MyDir\MyFile.txt For simplicity, let’s put it in the same directory: Then, you want to have a symbolic link to that file. Imagine the following scenario: You have a certain file, let’s call it “MyFile.txt” and it is located in C:\MyDir\MyFile.txt Let me show you what I mean before I will explain a possible workaround: It is quite common for admins to use symbolic links, but unfortunately the way they are shown in PowerShell is not what I would consider optimal. However, as much as I like PowerShell, I have got one issue with it: The way it handles symbolic links. #SAPonMS admins can use PowerShell to administrate their systems and improve their daily work flows, just like the developers in our team use it regularly in all kinds of situations. It is fairly easy to learn and use, while allowing you to be extremely efficient. PowerShell is a great framework for system administrators.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |