In my today’s topic, I discuss why PowerShell behaves like that. Specifically, I shed light on why you cannot run scripts or access a computer on a different domain. Also, I’ll take a closer look at how some cmdlets work.
Subscribe to my posts
- Deploying a Windows Server 2019 S2D Cluster using Azure Resource Manager Templates
- Creating a function in Windows PowerShell and saving it as module.
- Creating bulk user accounts in AD via PowerShell
- Combining Hyper-V and DC role on the same server: Why is this a bad idea
- Creating a Domain on Windows Server 2016 via PowerShell