Forum Discussion
Microsoft Security Compliance Toolkit 1.0 - Script File for 2012 R2
My customer is looking for the local script files for Microsoft Security Compliance Toolkit 1.0, which are missing. These are available on Windows 2016 up but not on Windows 2012 R2. If you can tell...
Use the LGPO.exe tool with /g and the root path of the GPO you want to apply. GPOs\{631572F1-2CE9-481D-8FAB-A1553A4DBD56} is the Domain Controller baseline; GPOs\{AB1A03CA-A251-4FDC-9C95-3BFE14EF9A54} is the Member Server baseline. Optionally add /v to the LGPO.exe command line for verbose output.
Xuefeng_L
Microsoft
MicrosoftHi Aaron, the customer said that their target server is a stand-alone server. Not a domain controller nor joined to domain.
I recognized that the following policy should be applied based on the above assumption, is this correct?
GPOs\{AB1A03CA-A251-4FDC-9C95-3BFE14EF9A54}
GPOs\{AB1A03CA-A251-4FDC-9C95-3BFE14EF9A54}
I recognized that the following policy should be applied based on the above assumption, is this correct?
GPOs\{AB1A03CA-A251-4FDC-9C95-3BFE14EF9A54}
GPOs\{AB1A03CA-A251-4FDC-9C95-3BFE14EF9A54}
Xuefeng_L AaronMargosis_Tanium
Dear Aaron, hope you doing well!
CX raised concern that target server is a standalone server, non-domain joined, there is no such baseline for a standalone server neither, the point here is that whether LGPO can functions as a workaround for local script which was missing in the tookit package, and whether baseline listed below can work as a solution? Namely, can baseline for DC or member server functions as a workaround for standalone server? Appreciate your reply.
