My IT Blog

Prerequisites This article assumes that you are familiar with the overall functionality of ARR and know how to deploy and configure ARR with disk cache. If you have not done so already, it is strongly recommended that you review the following walkthrough before proceeding: Configure and enable disk cache in Application Request Routing If Application Request Routing Version 2 has not been installed, you can download it at: Microsoft Application Request Routing Version 2 for IIS 7 (x86)  here . Microsoft Application Request Routing Version 2 for IIS 7 (x64)  here . Follow the steps outlined in  this  document to install ARR Version 2. This walkthrough also assumes that secondary cache drive has been added to ARR for caching. If not, please follow the Configure and Enable Disk Cache in Application Request Routing walkthrough. Scavenge.exe tool in ARR Scavenge.exe is a command line tool that can be used for managing the secondary drive by the administrators. The exe is

A new white paper about Windows Storage Server 2008 R2 Architecture and Deployment (including the Microsoft iSCSI Software Target 3.3) has just been published. Here's an outline of this content:     Introduction     Windows Storage Server 2008 R2 Overview         Comparing Windows Server Operating System Storage Offerings             Comparing Windows Storage Server with Windows Server             Identifying Windows Storage Server Features             What’s New in Windows Storage Server 2008 R2         Comparing Windows Storage Server 2008 R2 with Windows Server 2008 R2         Windows Storage Server 2008 R2 Editions         Identifying Storage Challenges             Identify Scalability Storage Challenges             Identify Availability Storage Challenges             Identify Security Storage Challenges             Identify Manageability Storage Challenges             Identify Data Recovery Storage Challenges         Identifying Windows Stora

One of these was something that I used for my convenience over a VPN connection from home. You see, the internal order processing application that I wrote uses some shared folders to store some temporary data, such as e-mails that are generated but not yet released to Exchange, or a local copy of images that are available on the Web site. This software–and our users–are used to referring to Windows file shares as  \\COMPUTER-NAME\SHARE-NAME ; for example,  \\CYRUS\Pickup Holding , because for some reason some of the older servers are named after my boss’s dead cats. When connecting through VPN to SBS 2008, however, that “suffix-less” name resolution was not working. So when  \\CYRUS\Pickup Holding  failed to resolve to anything, \\cyrus.skiviez.com\Pickup Holding  would work fine. This was super annoying. The reason this worked previously with our SBS 2003 installation is that it was acting as a WINS server, which provided this type of computer name resolution for us. SBS 2008

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.

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

1. Verify the new server's TCP/IP configuration has been pointed to the current DNS server. 2. Make the new server become a member server of the current Windows Server 2003 domain first. 3. Upgrade the Windows Server 2003 forest schema to Windows Server 2008 schema with the "adprep /forestprep" command on old server. Please run the "adprep.exe /forestprep" command from the Windows Server 2008 installation disk on the schema master. To do this, insert the Windows Server 2008 installation disk, and then type the following command: Drive:\sources\ADPREP\adprep.exe /forestprep 4. Upgrade the Windows 2003 domain schema with the "adprep /domainprep" command on old server. Please run the "adprep.exe /domainprep" command from the Windows Server 2008 installation disk on the infrastructure master. To do this, insert the Windows Server 2008 installation disk, and then type the following command: Drive:\sources\ADPREP \adprep.exe /domainprep 5.