@mkanakos
Sign in to post a link or comment!
Mike Kanakos commented on
PowerShell script to display information about Active Directory users 1 year, 8 months agoHi Gokul,
The tool in this article does not accept pipeline input because i did not include the parameter to do so. This required to be able to pass a list to the function. Take a look at my website http://www.networkadm.in . I'll write up a newer version of this tool on my site this week.
-
Mike Kanakos commented on
PowerShell script to display information about Active Directory users 1 year, 8 months agoTuril,
I believe your getting this error because your running a constrained language mode session. I may be wrong but this article is a useful for troubleshooting
https://community.spiceworks.com/topic/1451109-srp-whitelist-causing-odd-behavior-in-powershell-v5
-
Mike Kanakos wrote a new post,
Monitoring Active Directory with the PowerShell module PSADHealth 2 years agoPSADHealth is a PowerShell module built to automate Active Directory health checks that should be done on a regular basis.
-
Mike Kanakos commented on
PowerShell script to display information about Active Directory users 2 years agoHi Dexter.... Let me see if I can answer your question...
Are you asking... How do I run this function for one user ?
Are you asking... How can I make the function prompt for a username to enter?The default parameter of the function is username and it is a required parameter. If you run the function with no input, it will require you to enter a username...
Take a look at the link below... I ran the function with no input and it prompts me for a username.
-
Mike Kanakos liked comment of Nelson Montes de Oca on Invoke-Command: Connecting to computers requiring different credentials. (So far, Nelson Montes de Oca has 1 likes for this comment.) 2 years ago
-
Mike Kanakos liked Windows Server 2016/2019 Group Policy security settings. (So far, This post has 2 likes) 2 years ago
-
Mike Kanakos liked Audit changes in the Windows registry. (So far, This post has 2 likes) 2 years ago
-
-
Mike Kanakos wrote a new post,
Invoke-Command: Compensating for slow responding computers 2 years agoSometimes, running remote code with the PowerShell cmdlet Invoke-Command can take a long time to run—and not for any reason having to do with your code itself. Connecting to older computers means that long bits of code take longer to run. Computers on the other side of slow WAN links will always be slower in responding than something close and well connected.
-
Mike Kanakos liked comment of Michael Pietroforte on Author and member of the year 2019 – Why DevOps still doesn’t rule the IT world. (So far, Michael Pietroforte has 1 likes for this comment.) 2 years ago
-
Mike Kanakos commented on Author and member of the year 2019 – Why DevOps still doesn’t rule the IT world 2 years ago
Congrats to Wolfgang Sommergut for a great year of work! 37 articles are a huge volume of writing.
I should also note it that Wolfgang, Adam Bertam, Vladan Seget combined for 120 articles this year. Congrats on all the writing! Quality work from an outstanding group of writers.
-
Mike Kanakos liked comment of Anthony Rawlings on Invoke-Command: Connecting to computers requiring different credentials. (So far, Anthony Rawlings has 1 likes for this comment.) 2 years ago
-
Mike Kanakos liked comment of Denis on Invoke-Command: Dealing with offline computers. (So far, Denis has 1 likes for this comment.) 2 years ago
-
Mike Kanakos wrote a new post,
Invoke-Command: Connecting to computers requiring different credentials 2 years agoConnecting to computers that require different credentials via the PowerShell cmdlet Invoke-Command is a common occurrence. This post explains how you manage these situations.
-
Mike Kanakos liked comment of PowerMe! on Invoke-Command: Dealing with offline computers. (So far, PowerMe! has 1 likes for this comment.) 2 years ago
-
Mike Kanakos liked comment of Michael Pietroforte on Invoke-Command: Dealing with offline computers. (So far, Michael Pietroforte has 1 likes for this comment.) 2 years ago
-
Michael,
I wouldn;t say your wrong but to me... remoting between WORKGROUP computers is not the norm. Since there is no central spot to handle the encryption and decryption with workgroup PCs it sort of makes sense that SSL is not on by default on a standalone PC.
Most readers of this blog are dealing with domains and the default config for domain joined computers differs greatly from workgroup pc's.
-
A few things to consider here some of which Jeff already mentioned:
- The ports for remoting are 5985 and 5986 with 5986 only coming into use when certificates are configured and can be resolved meaning you need an internal PKI infrastructure.
- All remoting traffic is encrypted by default with a 256 bit key; even over HTTP.
- Remoting only occurs when you use the correct commands. WMI is not considered remoting.
- SSL verifies the computer. Remoting is authenticated and takes care of resolving the user.
- Not everyone can use remoting. You need to have admin priv's on a box or be a member of the remote mgmt users group. The other option is JEA is in place but that's a higher level discussion.
- Remoting is very safe. if you have security concerns, it should not be with remoting. Chances are the user security on your client's is the security weakness.
- The article you referenced is 10 years old. Microsoft moved away from 80 and 443 because there's enough on those ports already, but doesnt imply there are security concerns with remoting.
- IT shops can AND should be using remoting. it is one of the safest methods for interacting with a remote PC and it the equivalent of SSH for Linux/mac clients.
-
I agree with both Jeff and yourself. This is one of those scenarios where there more than one way to testdepending on what results you need back and how well you know your computers.
However, I have a small issue with Test-WSman. For the record, I use Test-Wsman all the time and find it very useful. However, the output has to be parsed in order to make a determination in a script that the machine is configured correctly.
Contrast this with Jeff's first example or mine where the result is true or false. I agree Test-WSMan is the more complete test. But if you know your work environment well then maybe Test-WSMan is overkill. Also consider that in a domain situation, win8, win10, srv2012, 2016, and 2019 machines all have remoting on by default; so maybe test-WSMan is the better test, but is it necessary?
I think it depends on the task you are working on...
-
Mike Kanakos wrote a new post,
Invoke-Command: Dealing with offline computers 2 years agoWhen you need to run PowerShell commands against a large set of computers with the PowerShell cmdlet Invoke-Command, you often have to deal with offline computers. In this post, you will learn how to deal with unresponsive machines.
- Load More
