cloudneeti / os-harderning-scripts Goto Github PK

I use the AADLoginForWindows extension to log onto Azure VMs with my Pin
After hardening I get the error
"The remote computer that you are trying to connect to requires Network Level Authentication (NLA), but your Windows domain controller cannot be contacted to perform NLA"

The System Assigned join to AD was created when the VM was created
I have tried everything I know including re-installing
Can you think which aspect of the hardening may have caused this ?

I can get onto the machine using the non-AD route but the AD route would be better.

Thanks, Sean
p.s. thanks for the script

I am trying to run a script on a VM for WIndows Server 2019. I keep recieveing this error:

Any ideas to solve the issue?

Hello Folks,

I am using Microsoft Hyper-V Server 2019 (Version 1809 : OS build 17763.3653)

There are 2 scripts available for Hardening.
I am confused which one is better for my server and which one should I use. Please help me to select one of them.
Please help me resolve this issue.

Thanks and Regards,
Vikash Kumar Choudhary

After I execute the script and reboot policy has only 'Users'.
It should be 'Administatror, Local Service'

I am running this in Packer:

https://github.com/Cloudneeti/os-harderning-scripts/blob/master/Amazon_Linux2/CIS_Amazon_Linux2_Benchmark_v1_0_0_Remediation.sh

Here is the end of the output.

If I remove this script from running the time out does not happen.

Removing the script the

amazon-ebs.linux-2: Remediation script for Amazon Linux 2 executed successfully!!
amazon-ebs.linux-2:
amazon-ebs.linux-2: Summary:
amazon-ebs.linux-2: Remediation Passed: 106
amazon-ebs.linux-2: Remediation Failed: 0

==> amazon-ebs.linux-2: Uploading scripts/scap-harden.sh => ~/scap-harden.sh
amazon-ebs.linux-2: scap-harden.sh 711 B / 711 B [==================================================================================================] 100.00% 0s
==> amazon-ebs.linux-2: Provisioning with shell script: /tmp/packer-shell2229766949
==> amazon-ebs.linux-2: sudo: Password expired, contact your system administrator
==> amazon-ebs.linux-2: sudo: Password expired, contact your system administrator
==> amazon-ebs.linux-2: Created symlink from /etc/systemd/system/ctrl-alt-del.target to /dev/null.
==> amazon-ebs.linux-2: Uploading scripts/CtrlAltDelBurstAction.sh => ~/CtrlAltDelBurstAction.sh
amazon-ebs.linux-2: CtrlAltDelBurstAction.sh 3.54 KiB / 3.54 KiB [==================================================================================] 100.00% 0s
==> amazon-ebs.linux-2: Provisioning with shell script: /tmp/packer-shell766628997
==> amazon-ebs.linux-2: Uploading scripts/EnableFIPS.sh => ~/EnableFIPS.sh
amazon-ebs.linux-2: EnableFIPS.sh 550 B / 550 B [===================================================================================================] 100.00% 0s
==> amazon-ebs.linux-2: Provisioning with shell script: /tmp/packer-shell1654068675
==> amazon-ebs.linux-2: sudo: Password expired, contact your system administrator
==> amazon-ebs.linux-2: sudo: Password expired, contact your system administrator
==> amazon-ebs.linux-2: usage: sudo -h | -K | -k | -V
==> amazon-ebs.linux-2: usage: sudo -v [-AknS] [-g group] [-h host] [-p prompt] [-u user]
==> amazon-ebs.linux-2: usage: sudo -l [-AknS] [-g group] [-h host] [-p prompt] [-U user] [-u user]
==> amazon-ebs.linux-2: [command]
==> amazon-ebs.linux-2: usage: sudo [-AbEHknPS] [-r role] [-t type] [-C num] [-g group] [-h host] [-p
==> amazon-ebs.linux-2: prompt] [-T timeout] [-u user] [VAR=value] [-i|-s] []
==> amazon-ebs.linux-2: usage: sudo -e [-AknS] [-r role] [-t type] [-C num] [-g group] [-h host] [-p
==> amazon-ebs.linux-2: prompt] [-T timeout] [-u user] file ...
==> amazon-ebs.linux-2: sudo: Password expired, contact your system administrator
==> amazon-ebs.linux-2: Provisioning step had errors: Running the cleanup provisioner, if present...
==> amazon-ebs.linux-2: Terminating the source AWS instance...
==> amazon-ebs.linux-2: Bad exit status: -1
==> amazon-ebs.linux-2: Cleaning up any extra volumes...
==> amazon-ebs.linux-2: No volumes to clean up, skipping
==> amazon-ebs.linux-2: Deleting temporary keypair...
Build 'amazon-ebs.linux-2' errored after 4 minutes 47 seconds: Script exited with non-zero exit status: 1. Allowed exit codes are: [0]

==> Wait completed after 4 minutes 47 seconds
==> Some builds didn't complete successfully and had errors:
--> amazon-ebs.linux-2: Script exited with non-zero exit status: 1. Allowed exit codes are: [0]

==> Builds finished but no artifacts were created.

I even tried to update the SSH Timeout from 300 to 1200 and still times out.

Again, I remove the script from the run, the run works fine.

I use this script and it timesout.

Hi @rahulkhengare @aniket2710 @ankitsrao @lomaingali - Need your help!!

I am getting an error when I execute the the 2nd command to apply the MOF file. The VM is built (Windows Server 2019) using packer Image in Azure Compute Gallery and it does not occur when the VM is built from azure portal (clickops)

.\CIS_Benchmark_WindowsServer2019_v100.ps1 [Script will generate MOF files in directory]
Start-DscConfiguration -Path .\CIS_Benchmark_WindowsServer2019_v100  -Force -Verbose -Wait

Error:

PS C:\> Start-DscConfiguration -Path "C:\CIS_Benchmark_WindowsServer2019_v100" -Force -Verbose -Wait

VERBOSE: Perform operation 'Invoke CimMethod' with following parameters, ''methodName' = SendConfigurationApply,'className' = MSFT_DSCLocalConfigurationManager,'namespaceName' = 
root/Microsoft/Windows/DesiredStateConfiguration'.
The client cannot connect to the destination specified in the request. Verify that the service on the destination is running and is accepting requests. Consult the logs and 
documentation for the WS-Management service running on the destination, most commonly IIS or WinRM. If the destination is the WinRM service, run the following command on the 
destination to analyze and configure the WinRM service: "winrm quickconfig".
    + CategoryInfo          : ConnectionError: (root/Microsoft/...gurationManager:String) [], CimException
    + FullyQualifiedErrorId : HRESULT 0x80338012
    + PSComputerName        : localhost
 
VERBOSE: Operation 'Invoke CimMethod' complete.
VERBOSE: Time taken for configuration job to complete is 6.706 seconds