Posts

Showing posts from April, 2019

Windows Server 2016: Group Policy settings to trust a self signed certificate

Windows Server 2016: Group Policy settings to trust a self signed certificate 1) [Server Manager] > Tools > Group Policy Management > Group Policy Management - Forest: widget.internal - Domains - (right-click) widget.internal > Create a GPO in this domain, and Link it here > New GPO - Name: WorkCertTrust > OK > 2) [Server Manager] > Tools > Group Policy Management > Group Policy Management - Forest: widget.internal - Domains - widget.internal - (right-click) WorkCertTrust > (x) Link Enabled  | Edit > Group Policy Management Editor - WorkCertTrust (DC2.WIDGET.INTERNAL) - Computer Configuration - Policies - Windows Settings - Security settings > (left-hand side) Public Key Policies - (right-click) Trusted Root Certification Authorities > Import > File to import - File name: \\DC2\NETLOGON\work.pfx > Private Key Protection - Password:  xxx xxx  | (x) Mark this key as exportable. this will allow you to backup or transport your keys at

Windows Server 2012: Active Directory Certificate Services

Windows Server 2012: Active Directory Certificate Services 1) Server Manager > Manage > Add Roles and Features > Server Selection - Name: LON-CA1 | IP Address: 172.16.0.40 | Operating System: Microsoft Windows Server 2012 R2 > Server Roles - (x) Active Directory Certificate Services > Add Features > AD CS - Role Services - (x) Certificate Authority  | (x) Certificate Enrollment Policy Web service | (x)  Certificate Enrollment Web service | (x) Certification Authority Web Enrollment | (x) Network Device Enrollment Service | (x) Online Responder > Add Features > Next > Install > 1) i) Results - Configure Active Directory Certificate Services on the destination server > 1) ii) AD CS Configuration - Credentials - Credentials: LON-CA1\Administrator >  AD CS Configuration - Role Services - Select Role services to configure -  (x) Certification Authority > Next > Setup Type - (x) Standalone CA > CA Type - (x) Root CA > Priva

Windows Server 2012: Active Directory Domain Service Sites and Replication

Windows Server 2012: Active Directory Domain Service Sites and Replication // Creating site 1) [Windows Server 2012] > Server Manager > Tools > Active Directory Sites and Services > Active Directory Sites and Services - (right-click) Sites > New Site > Create in: Adatum.com/Configuration/Sites | Name: PARIS-SITE | Select a site link object for this site. Site link objects are located in the Sites/Inter-SiteTransports container:-             Link Name:                       | Transport (click)  DEFAULTIPSITELINK     IP 1) i)  OK > // Creating site subnet 2) [Windows Server 2012] > Server Manager > Tools > Active Directory Sites and Services > Active Directory Sites and Services - Sites - (right-click) Subnets >New Subnet > Create in: Adatum.com/Configuration/Sites/Subnets | Prefix: 172.16.4.0/24 | Prefix name in Active Directory Domain Services:  172.16.4.0/24 | Select a Site object for this prefix: PARIS-SITE > // Replication pr

Windows Server 2019: Install and configure DFS Replication (Part 2)

Windows Server 2019: Install and configure DFS Replication (Part 2) /* ==================================== Metadata: // Windows Server 2019 Domain Controller Host Name:  Win2K19-DC01 Role:  AD DS, DNS IP Address:  192.168.0.201 RAM: 4GB Domain:  VICTORINFOSOL.LOCAL // Windows Server 2019 DFS Server 01 (Primary) Host Name:  Win2K19-DFS01 Role:  DFS IP Address:  192.168.0.202 RAM: 8GB Domain:  VICTORINFOSOL.LOCAL // Windows Server 2019 DFS Server 02 Host Name:  Win2K19-DFS02 Role:  DFS IP Address:  192.168.0.203 RAM: 8GB Domain:  VICTORINFOSOL.LOCAL // Windows 10 PC Host Name:  Win10-CL01 IP Address:  192.168.0.151 RAM: 4GB ==================================== */ 1) [Win2K19-DFS02] > Server Manager > Local Server - Ethernet0 > Properties - IPv4:- IP Address:  192.168.0.203 Subnet Mask:  255.255.255.0 Default Gateway:  192.168.0.1 Preferred DNS Server:  192.168.0.201 Alternate DNS Server:  192.168.0. 1    // Router Gateway 2) [Win

Windows Server 2019: Install and configure DFS (Part 1)

Windows Server 2019: Install and configure DFS (Part 1) /* ==================================== Metadata: // Windows Server 2019 Domain Controller Host Name: Win2K19-DC01 Role: AD DS, DNS IP Address: 192.168.0.201 RAM: 4GB Domain: VICTORINFOSOL.LOCAL // Windows Server 2019 DFS Server Host Name: Win2K19-DFS01 Role: DFS IP Address: 192.168.0.202 RAM: 8GB Domain: VICTORINFOSOL.LOCAL // Windows 10 PC Host Name: Win10-CL01 IP Address: 192.168.0.151 RAM: 4GB ==================================== */ 1) [Win2K19-DFS01] > Server Manager > Local Server - Ethernet0 > Properties - IPv4:- IP Address: 192.168.0.202   Subnet Mask: 255.255.255.0   Default Gateway: 192.168.0.1 Preferred DNS Server: 192.168.0.201 Alternate DNS Server: 192.168.0. 1    // Router Gateway 2) [Win2K19-DFS01] > Server Manager > Local Server - Computer Name:- Change - Computer Name:  Win2K19-DFS01 | Member of Domain: VICTORINFOSOL.LOCAL > Windows Security - Computer Name

Windows Server 2012: Install Domain Controller in new Domain in existing forest

Windows Server 2012: Install Domain Controller in new Domain in existing forest 1) [Windows Server 2012] > [Server Manager] > Manage > Add Roles and Features > Server Selection - Name: LON-SVR4.Adatum.com  | IP Address: 172.16.0.24  | Operating System: Windows Server 2012 R2 > Server Roles - Active Directory Certificate Services > Features - (x) Group Policy Management > Install > 2) [Windows Server 2012] > [Server Manager] > Manage > Add Roles and Features > Server Selection - Name: LON-SVR4.Adatum.com | IP Address: 172.16.0.24 | Operating System: Windows Server 2012 R2 > Server Roles - Active Directory Domain Services > Add Features > Next > Install > Results - Promote this server to a domain controller > 2) i) Active Directory Domain Services Configuration Wizard > Deployment Configuration - Deployment Configuration > Select the deployment operation - (x) Add a new domain to an existing forest  | Select domain ty

Windows Server 2016: Configure NFS Share

Windows Server 2016: Configure NFS Share 1) [Windows Server 2016] > [Server Manager] > Add Roles and Features > Server Roles - Roles - File and Storage Services - File and iSCSI services - (x) Server for NFS > Add Features > Next > Install > Restart 2) [Windows Server 2016] > [Server Manager] > Tools > Services for Network File System (NFS) > Services for NFS - Server for NFS - 2) i) [Windows Server 2016] > create folder:- D:\BTNHD > BTNHD Properties - NFS Sharing > NFS Share Management - Manage NFS Sharing > NFS Advanced Sharing - (x) Share this Folder | > Apply > OK > Services for NFS Sharing:- Network Path:  BJ-NFS:/BTNHD 3) [Windows 10 PC] > Program and Features > Control Panel - Programs - Program and Features > Turn Windows Features on or off > Turn Windows Features on or off - (x) Service for NFS - (x) Client for NFS > OK > This PC - Map Network Drive > Map Network Drive - Drive: Z : | Folder:

Windows Server 2016: Work Folders

Windows Server 2016: Work Folders 1) [Windows Server 2016] > [Server Manager] > Add Roles and Features > Server Roles - File and Storage Services - File and iSCSI Services - (x) Work Folders > Add Features > Install // IIS used for signing self-signed certificate 1) i) [Windows Server 2016] > [Server Manager] > Add Roles and Features > Server Roles - File and Storage Services - (x) Web Server (IIS) > Add Features > Install 2)  [Windows Server 2016] > [Server Manager] > File and Storage Services > Work Folders > To create sync share for Work Folders, start the New Sync Share Wizard > New Sync Share Wizard - Select the server and path - Server and Path > // Server Name: Data | Status: Online | Cluster Role: Not Clustered 2) i) New Sync Share Wizard - Select the server and path - Server and Path >Locaton: (x) Select by file share:- Name: Test | Path: C:\Test > Next > // Anyone who is part of domain:-  Domain Users (W

Windows Server 2012: Dynamic Access Control

Windows Server 2012: Dynamic Access Control // LON-DC1 -> login as adatum/administrator // Configure Claims 1) [Windows Server 2012] > [Server Manager] > Tools > Active Directory Administrative Center > Dynamic Access Control - (double-click) Claim Types > (right-hand side) Claim Types - New > Create Claim Type - Source Attribute > Display Name: department | Value Type: String | Belongs to: user, computer | ID: Department > Display name: HR department  | Claims of this type can be issued for the following classes: (x) User   > OK > 2) [Windows Server 2012] > [Server Manager] > Tools > Active Directory Administrative Center > Dynamic Access Control - (double-click) Claim Types > (right-hand side) Claim Types - New > Create Claim Type - Source Attribute > Display Name: description | Value Type: Multi Valued | Belongs to: user, computer | ID: Description > Display name: description1  | Claims of this type can be issue

Windows Server 2019: Install and Configure Data Deduplication

Windows Server 2019: Install and Configure Data Deduplication // Install Data Deduplication 1) [Server 2019] > [Server Manager] > Add Roles and Features > Installation Type - (x) Role-based or Feature-based installation > Server Selection - Server Pool:- Name: vDC01.bjtechnewshd.edu | IP Address: 192.168.1.114 > Server Roles - File and Storage Services - File and iSCSI services - (x) Data Deduplication > Next > Confirmation - (x) Restart the destination server automatically if required > Install > 2) [Server 2019] > [Server Manager] > File and Storage Services - Volumes > Volume:-  (right-click) E: | File System Label: Storage | Provisioning: Fixed | Capacity: 1000 GB | Free Space: 99.9 GB > Configure Data Deduplication > Storage (E:\) Deduplication Settings - Data Deduplication: General Purpose File Server > Apply > // If Data Deduplication did not start automatically // Only run the below powershell command after of

Windows Server 2019: Promote Windows Server 2019 to be a Domain Controller

Windows Server 2019: Promote Windows Server 2019 to be a Domain Controller // Install Active Directory Domain Services 1) [Server 2019] > [Server Manager] > Add Roles and Features > Installation Type - (x) Role-based or Feature-based installation > Server Selection - Server Pool:- Name: Server2019 | IP Address: 192.168.15.118 > Server Roles - (x) Active Directory Domain Services > Add Features > Next > Install // The DNS Server IP must be the same as your current server IP // since this is the Domain Controller 1) i) Open Network & Internet Settings > Network & Sharing Centre > Control Panel - All Control Panel Items - Network and Sharing Centre > change Adapter settings > Ethernet - TCPIP v4 - (*) Use the following IP Address: IP Address:          192.168.15.252 Subnet mask:       255.255.255.0 Default Gateway: 192.168.15.1 (*) Use the following DNS server addresses: Preferred DNS Server:    192.168.15.252 Alternative DNS

Windows Server 2019: Install and configure IPAM (IP Address Management)

Windows Server 2019: Install and configure IPAM (IP Address Management) // Note: the full steps can be found at: https://newhelptech.wordpress.com/2018/12/02/implementing-configuring-ipam-in-windows-server-2016/ // Install IPAM Server 1) [Windows Server 2019] > Server manager > Manage > Add Roles and Features > Server Selection, Server Pool:- Name: vWINSVR2019.btnhd.edu | IP Address: 192.168.1.114 | Operating System: Microsoft Windows Server 2019 > Features - (x) IP Address Management (IPAM) Server > Add Features > (x) Restart the destination server automatically if required > Install > //  #################### // Configure IPAM Step {1} Connect to IPAM Server is auto configured:- //     Connected to VWINSVR2019.BTNHD.EDU | //     Connected as BTNHD\gbtnhd //  #################### // Configure IPAM Step {2} Provision the IPAM Server 2) [Windows Server 2019] > Server manager > IPAM - (click) {2} Provision the IPAM Server > Con