![]() The set command is only good for the current session, setx will set a persistent, system-wide variable. ![]() You can do this in the GUI by going to Advanced System Properties, or you can do it on the command line using setx. ![]() And you can do it machine-wide, so that it affects all users. But you can add whatever path you want to this environment variable. Now I know that you only see a user-specific directory up there. PS C:\Users\ryan> $Env:PSModulePath -split ' 'Ĭ:\Users\ryan\Documents\WindowsPowerShell\ModulesĬ:\Windows\system32\WindowsPowerShell\v1.0\Modules\Ĭ:\Program Files (x86)\Microsoft SQL Server\110\Tools\PowerShell\Modules\ You put your modules in one of the directories specified in your PSModulesPath environment variable, that isn't System32\WindowsPowershell\v1.0\Modules. So where should you put your custom Powershell modules? The answer is simple. (i.e., C:\Windows\System32\WindowsPowershell\v1.0\Modules) As in the video that I posted in the comment to your original question, you shouldn't put your modules in the same place where Microsoft puts their modules.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |