Category Archives: HTTP Concepts

Virtual Desktop Infrastructure vs Remote Desktop Service

Desktop virtualization has become an inevitable option for businesses to optimize resources, provide mobility solutions, and deliver a higher level of performance.

Virtual desktop infrastructure (VDI) is virtualization technology that hosts a desktop operating system on a centralized server in a data center. VDI is a variation on the client-server computing model, sometimes referred to as server-based computing.

Remote Desktop Services (RDS) is an umbrella term for features of Microsoft Windows Server that allow users to remotely access graphical desktops and Windows applications. 

For desktop virtualization, companies can choose between VDI or RDS: either a virtual desktop infrastructure (VDI) or a remote desktop service (RDS).

While both these technologies have their own strengths and weaknesses, they each have a specific purpose, and businesses need to choose the right solution for their desktop virtualization requirements based on their present and future business needs. 

Benefits of VDI:

  • Utilization of Same Image.
  • Management of a Single OS Can Reduce Costs.
  • Processing moves from individual workstations to a VDI server.
  • Troubleshooting Problems is Easier.
  • Data is More Secure.

Benefits of RDS:

  • Single point of maintenance.
  • Install once, use many.
  • Reduced licenses expense.
  • Solid Security.
  • Lower Costs.

VDI is different from RDS in various ways:

  1. In a RDS environment multiple users can access a single environment, which could be customized on a per user basis but resources are not dedicated to a particular user. Whereas, In a VDI environment each user either accesses their own centrally hosted physical PC or VM or they can access a shared VM.
  2. Also, In a VDI environment physical CPU, Memory and Disk capacity can be allocated to particular user which stops one user’s actions affecting other users.
'Coz sharing is caring

How to sync server time with Network Time Protocol server

Sync server time on Linux with NTP

What is NTP?

An Internet protocol is used to synchronise clocks of computers, for instance linux server. This protocol is known as NTP (Network Time Protocol).

Following steps shows how to sync time using the terminal. Before we start login to the server via terminal and follow the steps given below.

Step 1: Check whether NTP is installed

Use the ntpstat command to view the status of the NTP service on the instance. It may happen that you get an error message prompting that NTP is not installed. In that case you have to install it on the server.

# sudo ntpstat
-bash: ntpstat: command not found

Step 2: Install NTP

Use the following command to install NTP on server.

# sudo yum install ntp

Step 3: Start NTP

After the installation is complete we need to start NTP by using the following command.

# sudo systemctl start ntpd

Note!

Enable NTP to start at boot:

# sudo systemctl enable ntpd

Stop NTP:

# sudo systemctl stop ntpd

Restart NTP:

# sudo systemctl restart ntpd

Step 4: Sync Time

For this use the following command.

# sudo ntpdate -q 0.rhel.pool.ntp.org

And restart NTP

# sudo systemctl restart ntpd

…and the server time will be synced.

Sync server time on Windows with SNTP

What is SNTP?

Simple Network Time Protocol (SNTP) is a simplified version of Network Time Protocol (NTP).  This is used to synchronize computer clocks on a network. As name defines simplified version of NTP is generally used when full implementation of NTP is not needed.

SNTP is a simplified access strategy for servers and clients using NTP. This simplified protocol is widely used to synchronizes a computer’s system time with a server that has already been synchronized by a source such as a radio, satellite receiver or modem. 

Interestingly, SNTP supports unicast, multicast and anycast operating modes. In unicast mode, the client sends a request to a dedicated server by referencing its unicast address. Once a reply is received from the server, the client determines the time, roundtrip delay and local clock offset in reference to the server. In multicast mode, the server sends an unsolicited message to a dedicated IPv4 or IPv6 local broadcast address. Generally, a multicast client does not send any requests to the service because of the service disruption caused by unknown and untrusted multicast servers. The disruption can be avoided through an access control mechanism that allows a client to select a designated server he or she knows and trusts.

Use below code to sync server time on windows machine

@echo on & @setlocal enableextensions

@echo =========================
@echo Turn off the time service
net stop w32time

@echo =========================
@echo Set the SNTP (Simple Network Time Protocol) source for the time server

w32tm /config /syncfromflags:manual /manualpeerlist:"0.it.pool.ntp.org 1.it.pool.ntp.org 2.it.pool.ntp.org 3.it.pool.ntp.org"

@echo =========================
@echo ... and then turn on the time service back on

net start w32time

@echo =========================
@echo Tell the time sync service to use the changes

w32tm /config /update

@echo =========================
@echo Reset the local computer's time against the time server

w32tm /resync /rediscover

@endlocal & @goto :EOF
'Coz sharing is caring