Today I ran into a problem where I needed to delete a folder structure which was setup incorrectly. Because of this the folder had a huge amount of empty subfolders.
Ok, no problem.. just select the root folder, and select DELETE.
Microsoft has disabled the Copy to functionality which allowed administrators to copy profiles to a central share and set security while doing this so all users can access this profile. This is (as far as I know) deliberant.
Well this posed me at first for a problem, because I had to define a Mandatory profile and one of the first steps was to copy the profile. Luckily enough I have a lot of colleagues that are smart and after a short discussion with one of them we came to the conclusion we have to create a mandatory profile the “old-fashioned” way.
Microsoft put an amazing (IMHO) poster online which provides you with a visual reference in order to understand key technologies in Windows Server 2008 R2. Focus areas are:
After playing around with several beta’s of vmware workstation 7, I decided to upgrade from 6.5 to 7.0 the minute it became available. Luckily enough vmware provided all beta testers with a discount code for 25% so that helped a little bit 
…
It seems I always run into this problem when converting a physical Windows Server 2003 System to a virtual machine. In 99,9% of these cases I have the issue that the ip-address I want to assign to the virtual NIC (which is the same as the ip-address assigned to the physical NIC) a warning pops up stating that this address is already assigned to another NIC. But when checking for NIC’s, I can only find the virtual NIC..