I read a recent post where someone was claiming the ISE was still there go to because they could not run specific lines of a script. If your PowerShell extension for vscode is even close to current… select the code you want to test and press F8 just like in the ISE.
Remember the Power Toys where you could add open prompt here? Did you know there is an even easier way?
Navigating the file system isn’t that hard in the Powershell CLI to start with considering tab completion and all of that but there is an even easier way….
In your file explorer window type powershell in the address bar. A new Powershell window will start and as the included video a simple get-location will show your working directory is same as the explorer window you launched powershell from. It may look different than what you expect when starting the Powershell CLI but you can change that with the window’s defaults settings.
A quick example (video) here.
This PowerShell script can be used to download some of the common cloud (Azure and AWS) management tools available on Windows Platform.
Earlier I had seen Download and Install SharePoint 2013 Prerequisites on Windows Server 2012. However this technet script uses Start-BitsTransfer cmdlet from BitsTransfer module. I was toying with similar idea while working on my last workshop (Cloud Automation Using PowerShell) preparation. Since some of the URLs do redirect the Start-BitsTransfer wasn’t working for me initially.
I started with simple Invoke-WebRequest cmdlet and added second variation to handle redirected URLs and pass it to Start-BitsTransfer. So let’s go through the script and output for the both the approaches.
I am using Downloads directory to store the files. For demo I have created CloudTools folder inside. I already have AWS Tools for Windows PowerShell downloaded in the folder.
I am already into the working directory where the script is saved.
View original post 607 more words
Great episode, especially if you are starting to use PowerCLI.
In This Episode
Tonight on the PowerScripting Podcast, we talk to Alan Renouf about PowerCLI!
This segment brought to you by Start-Automating
Start Scripting to Your Fullest Potential. At Start-Automating, we can help you unleash the full Power of PowerShell V2. You can use our deep PowerShell expertise to build rich PowerShell solutions, or we can train you to use PowerShell like a pro. Isn’t it time you Save-Time, Save-Money, and Start-Automating? Find out more at Start-Automating.com.
New-VIProperty from @lucd22: http://www.lucd.info/tag/new-viproperty/
PowerCLI Community at VMware: http://vmware.com/go/powercli
[21:53:59] <Josh_Atwell> ### ? for Alan…do you think PowerCLI would be as popular without the strong community it has?
[21:59:15] * BartekB blushing like teenage girl
[22:00:55] <JHofferle> ## How big can an environment get before you just *can’t* manage it without PowerCLI?
[22:03:30] <JHofferle> ## So vcheck…
View original post 65 more words
So I have been working at this new gig for over two weeks now. Personal note, my hesitation about being a contractor were valid for sure. So a few odd things as I started this new spot, Windows 7 on the desktop which in previous shops making the move to Windows 7 is probably a year away at least. In terms of Powershell, it would seem no one is using it and the one person I have encountered that does scripting, he shuns powershell and instead uses ASP and vbscript. I have started applying and showing how not just for scripting, Powershell could make some of their processes much easier. I will post more when I have some free time…
Yes, there are some duplicates from my other blog. Sorry about that but I am experimenting with moving my blog. The Go Daddy admin tools are just too tedious and with the constant wordpress updates, it just seems like time to explore an alternative.
First annoyance here is displaying code. Since this is primarily powershell code oriented, that is a big gotcha so I will be experimenting to see if I can work around it.
Interesting little discovery. Working an a new Windows2008 R2 Server I started working with the test-connection cmdlet. After testing some code I was ready to reduce some lines of code in some production scripts. I quickly found out that test-connection <machine name> –quiet doesn’t work. This would have helped because in current scripts there is an elaborate use of ping and reading the results which with Powershell V2 can be replaced with:
Well I will have to put this in the snippet library and put it into action when the full version 2 is available for XP.