Read only domain controller report


Get-ADDomainController -Filter {ISReadonly -eq $true}

—————————————————————————-

$DomainName = “xyz.com”

Get-ADDomainController -Filter * -Server $DomainName | ? {$_.IsReadOnly -eq $True } | select -ExpandProperty Hostname

Trusting


Trusting

To allow users in one domain to access resources in another, Active Directory uses trusts.[17]

Trusts inside a forest are automatically created when domains are created. The forest sets the default boundaries of trust, and implicit, transitive trust is automatic for all domains within a forest.

Terminology

One-way trust
One domain allows access to users on another domain, but the other domain does not allow access to users on the first domain.
Two-way trust
Two domains allow access to users on both domains.
Trusting domain
The domain that allows access to users from a trusted domain.
Trusted domain
The domain that is trusted; whose users have access to the trusting domain.
Transitive trust
A trust that can extend beyond two domains to other trusted domains in the forest.
Intransitive trust
A one way trust that does not extend beyond two domains.
Explicit trust
A trust that an admin creates. It is not transitive and is one way only.
Cross-link trust
An explicit trust between domains in different trees or in the same tree when a descendant/ancestor (child/parent) relationship does not exist between the two domains.
Shortcut
Joins two domains in different trees, transitive, one- or two-way.
Forest trust
Applies to the entire forest. Transitive, one- or two-way.
Realm
Can be transitive or nontransitive (intransitive), one- or two-way.
External
Connect to other forests or non-AD domains. Nontransitive, one- or two-way

P2V Conversion of 2 physical servers


Prerequisite:

1. Make a note of IP address, subnet mask/W and DNS server IP address.
2. System, application and file system backup should be ensured.
3. The respective application should be stopped before P2V conversion.
4. Shared folder access should be stopped from the respective VM before P2V.
5. P2V ports should be opened by Security team between vCenter server & Physical server also Physical server & ESXi server.
6. Root credential required.
7. We don’t have free space for 2nd server to convert. We need to do SvMotion prior to activity.
8. Please cross check any LUN’s mapped from storage end to physical server.
9. Note down NIC MAC and HBA details.

NOTE: Screenshot added with Port Numbers to be enabled

 

 

 

Step1 :

1. Login to server 172.16.0.31 on which the converter is already installed.
2. Launch the VMware vCenter Converter Standalone client. Click on “Convert Machine”.
3. Select the option Powered On (Select the type of machine either “Remote Windows Machine”, “Remote Linux Machine or This Local machine)
3. Select the source type as “Powered on”  and “Remote LINUX Machine. Specify the IP address and also the local administrator credentials of the remote windows machine. Click on Next.
4. Once converter agent is installed on the remote windows machine. Select “VMware Infrastructure virtual machine” from the destination type. Specify the vCenter Server 172.16.0.165 along with the admin credentials.
5. Once Converter connected to vCenter Server, It will display the vCenter Server inventory items. Specify the name of the destination VM and Select the datacenter location to deploy the virtual machine.
6. Select the ESXi host  172.16.0.203/127/97 (Depending on the resource availability) or cluster and Datastore to place the converted virtual machine. You can even choose the Virtual machine Hardware version from the drop-down.  Click on Next.
7. Wizard will display the current configuration.
8. Click on Destination volume to edit the disk information.  Click on Add Disk and move the partition to different VMDK disk. Click on Next.
9. Select the virtual machine port group to connect to the destination converted virtual machine. Click on Next.
10. Select the service startup mode for the destination virtual machine.  Click on Next.
11. Review all the Conversion parameters carefully. Click on Finish to start the P2V Conversion.
12. Once the P2V Migration is completed successfully. The converter agent on the source machine will be automatically uninstalled.

NOTE: Repeat the above steps for the second server.

Rollback:

1. If the VM is not required, we can delete the VM and use the physical machine as earlier.

2. If the conversion fails, the physical will not be impacted.

%d bloggers like this: