Cmdlet Convert-Path can easy convert any indirect path into an absolute path value. It can event conver unix slashes into windows backslashes. It can convert disk drive letter to uppercase, just like it is in the result of Get-PSDrive. But it has one small shortage. When you give as a parameter a path, using case different from the original, e.g. c:\users\adam, then result is C:\users\adam. This is incorrect, it should be (on my system) C:\Users\Adam. Generally, any part of the path present in Convert-Path parameter (except drive letter) is not converted to correct case. It is used without change. It is possible to make a simple function to fil this gap...
Sorry Nancy I do not. Not something I have ever even looked at. A quick search tells me I would at least start here. support.office.com/en-us/article/Manage-Office-365-Groups-with-PowerShell-aeb669aa-1770-4537-9de2-a82ac11b0540 Only thing I would have to offer is contacting me through Bold Zebras and we could scope out what it would take to help you automate this as a consulting engagement. Thanks Shane
$LowerPath.replace($LowerPath.Substring(0,2),$Lowerpath.Substring(0,1).ToUpper()+":") Just a thought, instead of above line, you could also use this, right? that would make this bit simpler. $LowerPath.replace($LowerPath.Substring(0,1),$Lowerpath.Substring(0,1).ToUpper())
Sooooo boring....but often overlooked! Great video, keep 'em coming!
Just increase speed of the video. I like x1.5. :)
Cmdlet Convert-Path can easy convert any indirect path into an absolute path value. It can event conver unix slashes into windows backslashes. It can convert disk drive letter to uppercase, just like it is in the result of Get-PSDrive. But it has one small shortage. When you give as a parameter a path, using case different from the original, e.g. c:\users\adam, then result is C:\users\adam. This is incorrect, it should be (on my system) C:\Users\Adam. Generally, any part of the path present in Convert-Path parameter (except drive letter) is not converted to correct case. It is used without change. It is possible to make a simple function to fil this gap...
I am not sure. Sorry
Thank you very much Mr.Shane , do you have video for change file and folder NTFS permession on windows using powershell ?
I don't. Sorry. Maybe a topic for a future video.
Hey Shane hooe ur doing well
Want to know how is the > changing to red when it senses an incomplete command
I think I explain it here. th-cam.com/video/3jAH92mBbRk/w-d-xo.html
@@ShanesCows thanks Shane appreciate it
you could just use the .Tolower() or ToUpper() methods on the input of the user ..
Interesting idea.
There should be videos on all those other ways as well :D
Hi Shane, do you have a video for creating office 365 distribution lists in mass?
Sorry Nancy I do not. Not something I have ever even looked at. A quick search tells me I would at least start here. support.office.com/en-us/article/Manage-Office-365-Groups-with-PowerShell-aeb669aa-1770-4537-9de2-a82ac11b0540
Only thing I would have to offer is contacting me through Bold Zebras and we could scope out what it would take to help you automate this as a consulting engagement. Thanks Shane
thanks!! help me with my lab
Cool
$LowerPath.replace($LowerPath.Substring(0,2),$Lowerpath.Substring(0,1).ToUpper()+":")
Just a thought, instead of above line, you could also use this, right? that would make this bit simpler.
$LowerPath.replace($LowerPath.Substring(0,1),$Lowerpath.Substring(0,1).ToUpper())
I like it 😎