‘Wet’ computer server could cut internet waste

New liquid-cooled Iceotope computer servers installed at the University of Leeds cuts energy used for cooling Internet servers by more than 80 percent. The whirring fans of traditional computers are replaced by the barely-audible trickle of liquid. The heat released can be piped out to radiators to warm a building. The developers say it could revolutionise the energy-hungry data centres that form the fabric of our online lives.

But don’t we all know that liquid and electronics don’t mix? Dr Jon Summers, from the University of Leeds’ School of Mechanical Engineering, shows what happens when you put an iPhone in a beaker of the secret ingredient: 3M (TM) Novec (TM) liquid.

WARNING: The phone experiment shown in this video is intended to demonstrate the special qualities of the liquid used in the Iceotope server. Putting an electronic device in liquid can cause problems other than a short circuit. Liquid is likely to be trapped and may affect the functionality of the device (eg. screen dimming or ghosting, speaker problems).

For more details on the Iceotope Servers at Leeds see: http://www.leeds.ac.uk/news/article/3374/wet_computer_server_could_cut_internet_waste

 

Outlook 2010 error 0x8004010f while trying to download the Offline Address Book (OAB)

exchange server outlook 2010 download oab

  1. Go to your Exchange Server 2010.
  2.  Start the Exchange Management Console
  3. Navigate to Microsoft Exchange > Microsoft Exchange On-Premises > Organization Configuration > Mailbox
  4. Select the Database Management tab page
  5. Right-mouse click a mailbox database, go to Properties
  6. In the Mailbox Database Properties go to the tab page Client Settings
  7. If the Offline address book is empty, click the [Browse...] button and select your OAB.
  8. Repeat step 5 – 7 for EACH mailbox database

When this is done, restart your Outlook 2010 application on the client.
You should now be able to download the OAB again via File > Account Settings > Download Address Book…

Have fun!
If this didn’t work for you, please comment how you fixed it.

Get information from Team Foundation Server (TFS) via C# code

This code shows you how you could interact with your team foundation server. In my case a TFS 2010.

Open a new console application in Visual Studio and add these references:

  • Microsoft.TeamFoundation.Client
  • Microsoft.TeamFoundation.VersionControl.Client
TeamFoundationServer tfs = new TeamFoundationServer("http://yourtfsserver:port/something");
List<string> changedFiles = new List<string>();

VersionControlServer VCServer = (VersionControlServer)tfs.GetService<VersionControlServer>();

try
{
string path = @"C:\Users\<username>\Documents\Visual Studio 2010\Projects\just the path to your solution";
VersionSpec version = VersionSpec.Latest;
int deletionId = 0;
RecursionType recursion = RecursionType.Full;
string user = @"domain\yourusername";

foreach (Changeset item in VCServer.QueryHistory(path, version, deletionId, recursion, user, null, null, Int32.MaxValue, true, false, true))
{
  foreach (Change c in item.Changes)
  {
	// c.Item.ServerItem;
  }
}
}
catch { }

Happy coding ;)

Windows Server: logging users logon and logoff via PowerShell

You are planning a migration and you want to track and monitor for a few weeks when your server is being used the most?

  1. Open Windows PowerShell ISE ( or notepad ;-) )
  2. Add this PowerShell line below and save the script as monitorlogon.ps1
  3. "logon {0} {1} {2:yyyy-MM-dd HH:mm:ss}" -f $env:username, $env:computername, (Get-Date) >> logon.log
  4. Create another script file, add the PowerShell line below and save it as monitorlogoff.ps1
  5.  "logff {0} {1} {2:yyyy-MM-dd HH:mm:ss}" -f $env:username, $env:computername, (Get-Date) >> logoff.log
  6. Start the Logal Group Policy Editor ([Windows]+[r] > gpedit.msc)
  7. Navigate to [User Configuration] > [Windows Settings] > [Scripts (Logon/Logoff)]
  8. Double click on the [Logon] name
  9. Navigate to the [PowerShell Scripts] tabpage
  10. Click the [Add] button and select your monitorlogon.ps1 script.
  11. Optionally you can select the execution order, default is set to “Not configured”.
  12. Repeat again from step 6. for the Logoff script.

You can change the >> filename.log part to >> \\MyShare\filename.log.

If you want to do this on a Windows Server 2003 where you can’t run your PowerShell you will need to save the file as an *.cmd:

  1. Create a new file and call it monitorlogon.cmd
  2. Enter the line below and save the script as monitorlogon.cmd:
  3. echo logon %username% %computername% %date% %time% >> C:\logon.log
  4. Repeat this for monitorlogoff.cmd and adjust the script line.
  5. Follow the steps from the PowerShell script.

All-In-One Script Framework

Microsoft All-In-One Script Framework is an automation script sample library for IT Professionals.  The key value that All-In-One Script Framework is trying to deliver is Scenario-Focused Script Samples driven by IT Pros’ real-world pains and needs.  The team is monitoring all TechNet forums, IT Pros’ support calls to Microsoft, and will start to monitor the script requests submitted to TechNet Script Repository soon. We collect frequently asked IT scenarios, and create script samples to automate the tasks and save some time for IT Pros. The team of All-In-One Script Framework sincerely hope that these customer-driven automation script samples can help our IT community in this script-centric move.

Find out more on: http://blogs.technet.com/b/onescript/

How to test an SQL Server connection

  1. Create a new empty text document (.txt) on your pc. (e.g.: on your desktop)
  2. Rename it to X.UDL
  3. Double click the file to open the Data Link Properties
  4. Select the correct provider on the [Provider] tabpage
    Fill in your connection details on the [Connection] tabpage
  5. Click [OK] to close the Data Link Properties window when you have a succesful connection (via [Test Connection])
  6. Now open the X.UDL with your favorite text editor (e.g.: notepad, notepad++)
    You should see your connection string now!

;-)