BGInfo Template background for windows client PC’s


C:\Windows\Bginfo.exe C:\Windows\ABG.bgi /timer:0 /silent /nolicprompt

Hive HKEY_CURRENT_USER
Key Path Software\Microsoft\Windows\CurrentVersion\Run
Value Name BGINFOVDI
Value Type REG_SZ
Value Data C:\Windows\Bginfo.exe C:\Windows\ABG.bgi /timer:0 /silent /nolicprompt

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

https://docs.microsoft.com/en-us/sysinternals/downloads/bginfo

Ldap Admin

Software Inventory Logging


the Software Inventory Logging feature introduced in Windows Server 2012 R2 that helps datacenter administrators easily log Microsoft software asset management data for their deployments over time. Before using Software Inventory Logging on Windows Server 2012 R2, make sure that Windows Update KB 3000850 and KB 3060681 are installed on each Windows Server 2012 R2 system that will be inventoried. This feature runs locally on each server to be inventoried. It does not collect data from remote servers.

https://technet.microsoft.com/en-us/library/mt572043(v=ws.11).aspx

https://blogs.technet.microsoft.com/hybridcloudbp/2016/02/09/spla-reporting-installing-sila/

Active Directory Recycle Bin

Microsoft-nic-teaming

When using Force Domain Controller Removal


The removal of a domain controller only if the domain controller has no connectivity with other domain controllers. Because the domain controller cannot contact other domain controllers during the operation, the Active Directory domain and forest metadata is not updated automatically as it is when a domain controller is removed normally. Instead, you must manually update the metadata after you remove the domain controller. For information about performing metadata cleanup, see Clean Up Server Metadata.

dcpromo /unattend /uninstallbinaries /forceremoval /demotefsmo:yes

/username:<domain admin> /userdomain:<domain>


/password:<DA password> /administratorpassword:<local admin


password>

Following methods that you can use to forcefully remove a domain controller:

  1. Forcing the removal of a domain controller by using the Windows interfaceTo use the Windows interface, you must start the Active Directory Domain Services Installation Wizard at the command line by running the dcpromo /forceremoval command.
  2. Forcing the removal of a domain controller by using the command line
  3. Forcing the removal of a domain controller by using an answer file

For example:

dcpromo /forceremoval /demotefsmo:yes /administratorpassword:Password1

https://technet.microsoft.com/en-us/library/cc816826(v=ws.10).aspx

https://docs.microsoft.com/en-us/windows-server/identity/ad-ds/deploy/demoting-domain-controllers-and-domains–level-200-#BKMK_Workflow

Note :

Dcpromo command no more available after 2012 server versions.

When you perform metadata cleanup


Metadata cleanup is a required procedure after a forced removal of Active Directory Domain Services (AD DS). You perform metadata cleanup on a domain controller in the domain of the domain controller that you forcibly removed. Metadata cleanup removes data from AD DS that identifies a domain controller to the replication system. Metadata cleanup also removes File Replication Service (FRS) and Distributed File System (DFS) Replication connections and attempts to transfer or seize any operations master (also known as flexible single master operations or FSMO) roles that the retired domain controller holds.

Remove types:

noteNote
If you receive an “Access is denied” error when you use any of these methods to perform metadata cleanup, make sure that the computer object and the NTDS Settings object for the domain controller are not protected against accidental deletion. To verify this right-click the computer object or the NTDS Settings object, click Properties, click Object, and clear the Protect object from accidental deletion check box. In Active Directory Users and Computers, the Object tab of an object appears if you click View and then click Advanced Features.

 

%d bloggers like this: