AWS EBS Snapshots Automation (Disaster Recovery) from Windows PowerShell

AWS EBS Snapshots Automation (Disaster Recovery) from Windows PowerShell

It is always a good idea to reduce hardware dependencies by moving your data to the cloud. Cloud is much more flexible than traditional hardware infrastructure including VMWare. But you still have to consider the ability of recovering data as and when required. This always helps you to keep your business running with minimal interruption. In AWS, there are several

Restrict Creator/Owner from altering NTFS permission

Restrict Creator/Owner from altering NTFS permission

Target: Restrict creator / owner from altering any NTFS permission on newly created files & folders. Scenarios: Regardless of NTFS permissions, the owner, which is by default the person who creates the folder/files, can always alter the permissions. This actually causing a lot’s of problem, with this special privilege users can also block inherited permission and alter current permission. This

NTFS Permission issue with TAKEOWN & ICACLS

NTFS Permission issue with TAKEOWN & ICACLS

Most of us using TAKEOWN or ICACLS for taking ownership from command prompt, and both of them are simple to use. We generally use TAKEOWN or ICACLS with following switches to taking the ownership. takeown /F “PATH” /R /D Y /A icacls “PATH” /T /setowner Administrators But unfortunately, TAKEOWN & ICACLS both might failed on certain scenario, as there are

WINDOWS 2008 R2 FAILOVER CLUSTER on VMWARE

WINDOWS 2008 R2 FAILOVER CLUSTER on VMWARE

For windows 2003 cluster, check my old tutorial on following link. https://technochat.in/2008/11/configure-cluster-on-vmware-using-iscsi/ Windows 2008 R2 Cluster Requirements: 1. Two Systems with Same Hardware Configuration. 2. Two Network Card 3. Windows 2008 R2 Enterprise Edition on both systems with same patch level. 4. Active Directory 5. Shared Storage( SAN or iSCSI) 6. Both servers should be the member of same domain.