My IT Blog

What is an Inventory? An Inventory is the process of mounting media in the drive and reading the media label, which is then displayed in the  Devices  view. If this is the first time that Backup Exec ™ has encountered this media, the media label is also added to the  Media  view. Note : Each time new tape is introduced in the tape drive or robotic library, it must be inventoried so that the Backup Exec database gets updated with the new tape Information. To Inventory a Tape/Robotic Library: 1. Insert the tape 2. Click the  Devices  tab 3. Select the correct tape drive/robotic library slot 4. Right-click on the tape drive/robotic library slot and select  Inventory  (Figure 1) Figure 1 The inventory will complete and should display the correct tape name. What is a Catalog? When cataloging a tape, Backup Exec reads the header information from the tape and stores it in a file on the hard drive. The information contained in the catalog includes, but is not limited

Instead of configuring a virtual machine as a DHCP server, you can use the virtual DHCP server for your virtual network. To configure the virtual DHCP server: 1. Open the  Virtual Server Administration Website . 2. Under  Virtual Networks , select Configure  and then click the virtual network. 3. In  Virtual Network Properties , click  DHCP server . 4. Check the  Enabled  checkbox, then configure the necessary DHCP server options. 5. Click OK.

When the Remote Desktop Client is exited by pressing the ‘X’ on the control panel the remote session continues to run on the server even though no client is connected. Next time the user connects the desktop session will appear exactly as it was left before. To end the session select Start in the remote desktop session, click on the right arrow button in the bottom right hand corner of the menu and select Log Off. This will close down the remote desktop session and close the remote desktop client.

I always wonder how many throughput does a Virtual Machine consume when running in Hyper-V Host. Not always we dedicate a NIC for a Virtual Machine. For better consolidation, we always share several Virtual machine within a 1 Gbps NIC. Let say, you have 4 Virtual Machines running and share on 1 Gbps NIC. Will each Virtual Machine consume and limited to 250 Mbps? Well not really. Some VM will consume more throughput than 250 Mbps and will eventually impact the performance for the rest of the VM. This is what i found out when testing Hyper-V Vnext which seem like solving this case. On Virtual Network, you can configure to set minimum and maximum throughput per Mbps on each virtual machine. Great right…I’m excited to wait this feature available on next release of Hyper-V.

The Simple Network Time Protocol (SNTP) is a simpler version of the Network Time Protocol (NTP). SNTP synchronizes the time between networked computer systems and is relied on when data is being transferred via the Internet. The NTP protocol is one of the most established protocols still used on the Internet. It uses a GPS or radio clock to tell time and is accurate past the seconds place. Why is the SNTP Necessary? The need for precise time synchronization has continued to increase with the evolution of computer technology over the past several decades. In the networking field, network servers and their client computers require precision to the millisecond and beyond in order to ensure data file transfers occur without errors. Computers also require specific time synchronization in order to ensure data packet and email delivery in the proper sequence to destination networks and email recipients. The importance of the SNTP and NTP protocols exponentially expands with the number of

Before installing the first Windows Server 2008 R2 domain controller (DC) into an existing Windows 2000, Windows Server 2003 or Windows Server 2008 domain, you must prepare the AD forest and domain. You do so by running a tool called  ADPREP . ADPREP extends the Active Directory schema and updates permissions as necessary to prepare a forest and domain for a domain controller that runs the Windows Server 2008 R2 operating system. Note : You may remember that ADPREP was used on previous operating systems such as Windows Server 2003, Windows Server 2003 R2 and Windows Server 2008. This article focuses on Windows Server 2008 R2. What does ADPREP do? ADPREP has parameters that perform a variety of operations that help prepare an existing Active Directory environment for a domain controller that runs Windows Server 2008 R2. Not all versions of ADPREP perform the same operations, but generally the different types of operations that ADPREP can perform include the following: Updating the

If you remote onto a Windows server with any kind of regularity, you will probably have come across a scenario where the number of concurrent connections has reached the limit. This is often followed by shouting across the office or sending an email asking people if they are connected and whether they can log off so you can get on. Well, shout no longer as you can find out who's logged onto a machine by running this simple command in command prompt. In this example, the server name is "YOURSERVERNAME". query session / server : YOURSERVERNAME And if you find out that someone has logged in and then left the country, you can kick them off too - the above command will tell you each user's session id and you can use this to boot them off the box. In this example, the session id is 1. rwinsta / server : YOURSERVERNAME 1

The Auditing Option 1: 1. Enable Auditing on the domain level by using Group Policy:       Computer Configuration/Windows Settings/Security Settings/Local Policies/Audit Policy       There are two types of auditing that address logging on, they are  Audit Logon Events  and  Audit Account Logon Events .       Audit "logon events" records logons on the PC(s) targeted by the policy and the results appear in the Security Log on that PC(s).       Audit "Account Logon" Events tracks logons to the domain, and the results appear in the Security Log on domain controllers only 2. Create a logon script on the required domain/OU/user account with the following content:      echo %date%,%time%,%computername%,%username%,%sessionname%,%logonserver% >>         \\SERVER\SHARENAME$\LOGON.LOG 3. Create a logoff script on the required domain/OU/user account with the following content:      echo %date%,%time%,%computername%,%username%,%sessionname%,%logonserve