farismalaeb / powershell Goto Github PK

No license is indicated in the script. I'm leery of using this script in production without knowing the license under which its distributed.

Running the Get-PscActiveDirectoryACL without any parameter returns the following error.

Get-PscActiveDirectoryACL: Parameter set cannot be resolved using the specified named parameters. One or more parameters issued cannot be used together or an insufficient number of parameters were provided.

To walkaround this, make sure to use the -ACLToInclude parameter.

Features

• Adding Switch to list a summary of the server's availability and which one is in maintenance mode.
• Remove the need for the IP-Less DAG option and make it auto-detect
• Detect New Updates

Bug Fixes

• Check -IgnoreQueue timeout issue.

Describe the bug
running Test-EmmReadiness returns multiple errors.

Checking SSL Certificate Validity Cannot index into a null array. At C:\Program Files\WindowsPoweTest-EmmReadinessrShell\Modules\EmmExDAGModule\2.2\EmmExDAGModule.psm1:542 char:18 + $cn = $matches[1] + ~~~~~~~~~~~~~~~~~ + CategoryInfo : InvalidOperation: (:) [], RuntimeException + FullyQualifiedErrorId : NullArray

get-cluster : The cluster service is not running. Make sure that the service is running on all nodes in the cluster

Get-Cluster : An error occurred opening cluster 'DAG19'. No such host is known At C:\Program Files\WindowsPowerShell\Modules\EmmExDAGModule\2.2\EmmExDAGModule.psm1:615 char:19 + $Status=Get-Cluster (Get-DatabaseAvailabilityGroup)| Get-Cl ... + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : NotSpecified: (:) [Get-Cluster], ClusterCmdletException + FullyQualifiedErrorId : Get-Cluster,Microsoft.FailoverClusters.PowerShell.GetClusterCommand WARNING: The number of available clusters is not enough, Please resume one node at least

To Reproduce
run Test-EmmReadiness

Expected behavior
able to check cluster and certificate.

Screenshots

PowerShell version:

• 5.1

Running on Windows :

• Windows Server 2019

Hello Faris,

I use a few different PS1 scripts I have found over the years to manage old exchange logs, and have recently found yours.

One "file delete" script I use has email notifications in its capability. This script is called "DeleteOld" and was written by Jaap Brasser. I am not sure if it can be found on the internet anymore, but I do have a copy of it. That script is not specific to Exchange. The reporting feature in it is useful though (log file is emailed, containing actions done, # files deleted, space recovered, etc). I am wondering if that feature could be added to your script. If interested, I can provide you with that PS1.

You've done a gret work for the community, thx a lot

Is it allowed to use those scripts commercially?
Is it allowed to use modified versions of those scripts commercially?
What license they are licensed under?

Is there a way to suppress the no active session error message that comes up everytime when querying computers with no RDP active users?

• Scan all DBs for Health
• Make the report exportable
• Add exclusion option for Certificate scanner.
• report stretched cluster config

Describe the bug
Start-PSCVMHostMM reporting the following error
Cannot convert the "System.Object[]" value of type "System.Object[]" to type "System.Int32".

Describe the bug
For some reason, PowerShell wont import the PS Module for Exchange server, even though its requested to do so once the module is imported to the PowerShell Session

To Reproduce
Steps to reproduce the behavior:

1. Open PowerShell 5.1 (As Admin)
2. Import the Module
3. try typing Get-Mailbox.
4. PowerShell return that the cmdlet is not exist

Expected behavior
The expected behavior is PowerShell should import the snapin and should be usable, typing Get-Mailbox, should return all the mailboxes

Running on Windows :

• Windows 10/11
• Windows Server 2016/2019
• Windows Server 2012
• Other

Workaroundt
If you face this issue, for now, manually add the Ps snapin by typing
Add-PSSnapin Microsoft.Exchange.Management.PowerShell.snapin
Make sure that the snapin loaded by typing
(Get-PSSnapin).Name
Make sure that the Microsoft.Exchange.Management.PowerShell.snapin is listed