Microsoft Security Compliance Toolkit 1.0 - Script File for 2012 R2

AaronMargosis_Tanium
Iron Contributor
Dec 06, 2022
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
  Dec 06, 2022
  Hi 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}
  - Gary_666
    Former Employee
    Dec 06, 2022
    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.
- AaronMargosis_Tanium
  Iron Contributor
  Dec 06, 2022
  Note that Windows Server 2012 R2 goes completely out of support in less than a year from now:
  https://learn.microsoft.com/en-us/lifecycle/announcements/sql-server-2012-windows-server-2012-2012-r2-end-of-support
  - Xuefeng_L
    Microsoft
    Dec 08, 2022
    Hi AaronMargosis_Tanium , we would appreciate if you could share your knowledge.

Forum Discussion

Microsoft Security Compliance Toolkit 1.0 - Script File for 2012 R2