Command Shell Wizardry: IT Admins' Key to Remote Management of Windows clients/servers
Вставка
- Опубліковано 25 тра 2022
- Learning to leverage Command Shell with remote tools like WinRS and conditional processing or sequential processing. I will demo solving everyday problems using skills that extend your tools. We will review command shell syntax and compare online references and our command line utilities’ help. This is a great beginning for IT students and help desk employees.
Please consider becoming a channel member:
• you get an early viewing of all our video content
• access to the complete series of videos for each subject
• links to video notes and PowerPoint slide deck both in MS-Word and PDF format
• Our eBook and resources folder
• Join our channel membership, it’s $2.99/month); see the “Join” button on our channel homepage. / @techsavvyproductions
"Everybody can be great... because anybody can serve. You don't have to have a college degree to serve. You don't have to make your subject and verb agree to serve. You only need a heart full of grace. A soul generated by love." Martin Luther King Jr.
Check out our UA-cam channel for more content!
UA-cam: / vanderl2796
Check out our Website: www.techsavvyproductions.com
Follow us on Twitter: @_TechSavvyTeam
Like us on Facebook: / tech-savvy-productions...
Mr.V Linkedin: / lowell-vanderpool-5797...
Links to Documentation
PowerPoints in *.pptx format:
docs.google.com/presentation/...
Slide Deck in PDF:
drive.google.com/file/d/1l9Z0...
Video Notes in *.docx:
docs.google.com/document/d/1s...
Video Notes in PDF:
drive.google.com/file/d/1Sfn2...
Check out more videos on TechSavvyProductions Channel:
1. Process Monitor, a powerful tool to troubleshoot applications and Windows • Unlocking Process Moni...
2. How-to: Connecting to network equipment via console, telnet, and SSH • Unlocking Network Acce...
3. Network Switch Explained: ASIC chips, Extending your LAN • LAN 2.0: How Network S...
4. OSI Layer 4 Explained • From Handshakes to Dat...
5. OSI Layer 6 Explained: Sharpen your Network Skills • From Confused to Confi...
6. Troubleshooting Windows 10 and Windows 11 Using Task Manager • Task Manager Unveiled:...
7. The Windows 10 Run Command You Forgot • The Windows 10 Run Com...
8. Practical Network Troubleshooting: Windows 10 • IT Ninjas: Mastering N...
Email: mrvanderpool@techsavvyproductions.com
More TechSavvyProductions Videos that you might enjoy:
We translate subtitles on our videos into the following languages: عربى, българскиB, 简体中文）, 中國傳統的）, Nederlands, Suomalainen, Pilipino, français, Deutsche, हिंदी , Magyar, bahasa Indonesia, 日本語, 한국어, norsk, Polskie, português, Română, русский, Española, Kiswahili, Svenska, and Tiếng Việt - Наука та технологія
LV is the man !
Thanks for watching!
Hi Lowell, once again some very interesting videos I wish I had when I was in the beginning of my IT carreer...
Two remarks from my side:
1) If I am right you can't run a WinRS command on a remote computer until you "allow" it via WinRM command, and this WinRM command won't be run remotely (unless a gpo exists) so you have to take control of the computer to enable WinRS so while you are at it you will do your CHKDSK stuff...
2) personnaly I prefer taking control of the remote computer and then run my powershell or CMD commands because the user will see something is in progress and won't try to open new programs or mess with the currently running stuff. When you do everything by remote command, as you said it will be not visible by the user so he will not know when the troubleshooting is over. Anyway when I was a N2 support tech I always asked the users to let me full control of the computer and go away have a coffee or something. I don't like when the user can interfere with my troubleshooting. I know a lot of techs who run a command and then do an other ticket, asking the first user to "not touch" but because they have no remote control anymore they can't verify if the user is not messing with the computer or not. Now I do servers administration only so the user part of the game is gone and that's a lot easier for the troubleshooting :):):)
Thanks for the || and && tips, I was not aware of that :)
Great comments: If you have remote management rights then it works fine or you are a "domain admin". You must have the Winrm service running and the firewall open which I should have mentioned, most domain do have this feature in their GPOs. You bring up a great point of the positives of having full control.
Thank you for taking the time to continue making videos, you have a lot of great content
I appreciate you watching!
Killer Course!! :) Powershell is a must!
Powershell is coming I promise
Brilliant. Thank for this amazing videos
Glad you like them! Thanks for watching!
Thanks for this informative video. Is it correct that for winrs to work correctly, you need to be a member of the Remote Management Users group on the local system in order for the command to work correctly?
If not using domain credentials then yes a member of remote management group
you're a windows wizard
Thanks for watching!