On the domain controller of the root forest , you may follow the steps to configure the Windows Time service to sync time with the authoritative time source.

Open a Command Prompt.

Type the following command to display the time difference between the local computer and a target computer, and then press ENTER: (without quotation mark) “w32tm /stripchart /computer: time.windows.com /samples:5 /dataonly”

Open UDP port 123 for outgoing traffic if needed.

Open UDP port 123 (or a different port you have selected) for incoming NTP traffic.

The computers that are joined to a domain are configured to synchronize from a manual time source. Please use the following procedure to configure a client computer that is currently synchronizing with a manually specified computer, to automatically synchronize time with the domain hierarchy. You may follow the steps to configure a client computer for automatic domain time synchronization

Open a Command Prompt.

Type the following command and then press ENTER: w32tm /config /syncfromflags: domhier /update

Type the following command and then press ENTER: net stop w32time

Type the following command and then press ENTER: net start w32time

You may also use Group Policy to make all the domain clients to sync time with PDC emulator in the domain. You may find the Group Policy settings used to configure W32Time in the Group Policy Object Editor snap-in in the following locations:

I recently started working with a new company maintaining their network. Because the old network admin left of bad terms I was tasked with documenting the network and getting things back in align. Because I was in an unknown environment I didn’t know where the WSUS server was located. There are two main ways to find out what server is the WSUS server.

Registry – Using the regedit tool you can find this registry entry. It will tell you where it’s located – HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate

Group Policy – You will need to open up the “Group Policy Management” look through all the “Group Policy Objects” entries and figure out which one is responsible for WSUS. The setting is located in “Computer Configuration – Policies – Administrative Templates – Windows Components – Windows Updates”.

1. Download Linux Integration Components v2.1

b. Extract the .exe file into a temp folder. You will need only LinuxIC v21.iso file.

c. Place the LinuxIC v21.iso file into your VM host server where you can mount the ISO as a CDROM for your Centon Virtual Machine.

2. Installation

You will need Development Tools installed to be able to compile the Integration Components. You could do that by running yum:

yum groupinstall "Development Tools"

NOTE: This command will try to use your network connection to download and if you used Synthetic Network Adapter for your Hyper-V machine you will not have internet connection. So make sure to install Development Tools during your Centos initial installation.

Now make sure you added LinuxIC v21.iso file to your Hyper-V CDROM as Image.

As the root user, mount the CD in the virtual machine by issuing the following commands at a shell prompt:

mkdir /mnt/cdrom mount /dev/cdrom /mnt/cdrom

Copy Linux Integration Services to the virtual machine and unmount CDROM that no longer needed:

When installing Windows Server 2008 R2 on a laptop, it’s often useful to make use of the Wireless networking – usually quickly picked up by Windows 7 – but needing some config to get it working for Windows Server 2008.