Portal For Cloud, Citrix & VDI Technologies !!

Monday, 27 May 2019

AWS Route 53 Tutorial

AWS Route 53 Tutorial 


AWS Route 53 Part -I  


This is first part of Route 53 Tutorials in which I have described the basics of DNS, Resource records, Difference between CNAME and ALIAS records, and agencies involved in domain registration 



AWS Route 53 Part -II 


In This video I have demonstrated How to register a domain with ROUTE 53 in AWS, I have also shown some finer points to remember while configuring the registration of domain names. In the end of video we have checked the availability of our newly registered domain name as well by




AWS Route 53 Part -III 


This is the IIIrd video for ROUTE 53 series in which I have demonstrated how many types of routing policies are there in the ROUTE 53 and How to configure our first Simple routing policy, with demonstration



AWS Route 53 Part -IV 


In This Video I have demonstrated AWS Route 53 Weighted Routing Policy, along with the explanation of numbers we use to denote the weight of the resource records. The video also has a diagram to depict the EC2 Setup which has been used for configuring and testing the weighted routing policy.




AWS Route 53 Part -V  


In this video I have demonstrated the configuration of the Latency based routing and the points to remember while configuring the same in ROUTE 53





AWS Route 53 Part -VI 


In This Video I have demonstrated AWS Route 53 Failover Routing Policy, along with the explanation of Failover Routing I have also created and explained health check for your Active/Primary resource,





AWS Route 53 Part -VII  


In This video, we have demonstrated and configured the Geo-Location Routing in AWS Route 53. I have also discussed the use cases for using Geo location routing in Route 53,I have used Avira Phantom VPN to help in demonstration of this routing.




Share:

EC2 IAM Tutorials

EC2 IAM Tutorials 

Using IAM Roles over IAM Access Keys to sign AWS API requests has multiple benefits. For example, once enabled, you or your administrators don't have to manage credentials anymore as the credentials provided by the IAM roles are temporary and rotated automatically behind the scenes. 


You can use a single role for multiple EC2 instances within your stack, manage its access policies in one place and allow these to propagate automatically to all instances. 


Also, you can easily restrict which role a IAM user can assign to an EC2 instance during the launch process in order to stop the user from trying to gain elevated (overly permissive) privileges.

AWS IAM Part-1





AWS IAM Part-2 





AWS IAM Part-3 




AWS IAM Part-4 










Share:

Wednesday, 22 May 2019

EC2 PlacementGroups 2019|AWS EC2 Placement Group|Clustered, Partition, S...


EC2 PlacementGroups 2019|


AWS EC2 Placement Group|Clustered, Partition, S...




Share:

Thursday, 13 December 2018

AWS VPC Virtual Private Cloud

AWS VPC (Virtual Private Cloud):

  Hi Everyone here is a quick video about the AWS VPC basics, please find below the diagram I have referred to prepare this tutorial as well as the video where I have demonstrated the creation of VPC along with subnets and hosting the EC2 resources in those subnets.

AWS VPC Reference diagram


And here is the video for creating your own customized VPC with public and private facing subnets, along with an internet Gateway for the internet traffic.



Share:

X64 Images are not available to Client in WDS

X64 Images are not available to Client in WDS

You come across scenarios in your day to day Sys Admin life where you have set up youWDS (RIS) server correctly. You have uploaded images of X64, I64 and X86 architecture correctly and they are online.

When client boots up in PXE environment after pressing F12, OS image selection menu shows up and we see there is no X64 images are available for selection.

Try to run the following command on WDS server:

i) wdsutil /set-server /architecturediscovery:yes

The PXE specification states that each network-booting client computer must indicate its architecture by setting Dynamic Host Configuration Protocol (DHCP) option 93 to the appropriate value. However, on many x64-based client computers, the value may not be set. Or, the value may be set incorrectly. For example, the architecture may be specified as x86 even though the client computer is x64-capable. The following table lists the architecture values.
ValueArchitecture
0IA x86 PC
1NEC PC98
2IA-64 PC
3DEC Alpha
4ARCx8
5Intel Lean Client
6x64
When architecture detection is enabled, the client computer downloads a network boot program (Wdsnbp.com) from the server. Then, the network boot program reports the architecture of the client computer to the server. This operation occurs before the client computer downloads the default boot program for its architecture. Examples of the default boot program include Pxeboot.com and Pxeboot.n12.

Architecture detection may add time to the boot process, increase network traffic, and increase the load on the server. By default, architecture detection is turned off.

To review the server's architecture detection setting, type the following command at a command prompt, and then press ENTER:
wdsutil /get-server /show:config
For more information about WDS and the Wdsutil.exe command-line tool, visit the following Microsoft Web site:
http://technet.microsoft.com/en-us/windowsvista/aa905118.aspx
For more information about a similar issue, click the following article number to view the article in the Microsoft Knowledge Base:
222177
"File Not Found" when remote install client connects to server
Share:

Friday, 24 August 2012

GPO Processing Myth

GPO Processing Myth !!

This is my first post. I have come across various situations where user/System Admin and surprising enough even some trainers are not sure that what would be the processing and precedence order of the Active Directory GPO application. I would try my level best to simplify this overtly confusing topic.

First let us know the order of precedence of GPOs.
to make it easy if someone can recollect there was a Hindi movie sometime back called
L:Love
S:S**
D:Dhoka
Now you must be wondering what non-sense is this, hold your horses, this will help you to recollect the order of GPO Application, let see how:

L: Local policy will be applied first
S: Site policy will be applied next
D: Domain Policy would be the next

OU: finally the OU policies.
And remember that in GPO application always last writer wins i.e. OU policy will be applied last and will overwrite if find any conflicting settings applied by Local, Site or Domain Policy.

I hope it would clarify the GPO myth upto a reasonable extent..
Running short of time..

Would include examples soon,,,,,
Share:

LinkedIN