Tuesday, 31 May 2011

Move DHCP from Windows 2003

To move DHCP from a Windows 2003 server to a new server start by exporting the DHCP database on the old Windows 2003 server:
  1. Open a command prompt and enter 'netsh dhcp server export C:\dhcp.txt all'
  2. Copy c:\dhcp.txt to the new DHCP server
  3. Load the DHCP console, right click on the server and select Unathorize
  4. Load services and change the DHCP Server service to disabled then stop the service
On the new server:
  1. Install DHCP from Add/Remove computers and Windows Components
  2. Open a command prompt and enter 'netsh dhcp server import c:\dhcp.txt all'
  3. Load the DHCP console, right click on the server and select Authorize
  4. Wait 10-15 seconds, refresh the screen and verify you can see your records

Issue a SAN Certificate from a Private Certificate Authority

Without modification the Certificate Authority service built in to Windows does not support SAN certificates which are required for correct operation of Exchange 2007 and Exchange 2010. To support them you need to add an additional flag called EDITF_ATTRIBUTESUBJECTALTNAME2.

To check if the flag already exists on your Certificate Authority open a command prompt and run:
certutil -getreg policy\EditFlags

To add the additional flag run:
certutil -setreg policy\EditFlags +EDITF_ATTRIBUTESUBJECTALTNAME2

Finally you will need to restart the Active Directory Certificate Services service.

Upgrade Windows 2008 R2 or Windows 7 Versions

In Windows 2008 R2 and Windows 7 you can upgrade editions using the DISM tool. You need to enter the KMS Client Key rather, this will reset activation grace period to 3 days to allow you to enter your own product key.

To see what target editions are available run:
DISM /online /Get-TargetEditions
To upgrade to one of these editions run:
DISM /online /Set-Edition:<edition ID> /ProductKey:XXXXX-XXXXX-XXXXX-XXXXX-XXXXX
So to upgrade from to Windows Server 2008 R2 Enterprise from Standard you would run:
DISM /online /Set-Edition:ServerEnterprise /ProductKey:489J6-VHDMP-X63PK-3K798-CPX3Y
The KMS Client productkeys for Windows 2008 R2 are as follows:
Standard - YC6KT-GKW9T-YTKYR-T4X34-R7VHC
Enterprise - 489J6-VHDMP-X63PK-3K798-CPX3Y
Datacenter - 74YFP-3QFB3-KQT8W-PMXWJ-7M648
Itanium-Based Systems - GT63C-RJFQ3-4GMB6-BRFB9-CB83V
The KMS Client productkeys for Windows 7 are as follows:
Professional - FJ82H-XT6CR-J8D7P-XQJJ2-GPDD4
Professional N - MRPKT-YTG23-K7D7T-X2JMM-QY7MG
Enterprise - 33PXH-7Y6KF-2VJC9-XBBR8-HVTHH
Enterprise N - YDRBP-3D83W-TY26F-D46B2-XCKRJ
Enterprise E - C29WB-22CC8-VJ326-GHFJW-H9DH4

Thursday, 26 May 2011

Windows XP Remote Access Connections Binding Order

When using Remote Access Connections in Windows XP you may find that despite the connection being active no data traverses this connection and/or DNS requests for this connection do not get submitted to the the DNS server associated with the connection. You would expect it to use the device that is highest in the binding order however it is not doing so. To resolve this we can change the binding order in the registry:
  1. Click Start, Run and type regedit
  2. Navigate to KEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Linkage
  3. In the right pane, double-click Bind.
  4. In the Value data box, select the "\Device\NdisWanIp" item, press CTRL+X, click the top of the list of devices, and then press CTRL+V.
  5. Click OK, and then quit Registry Editor.
You may need to disconnect and reconnect to the VPN or restart the computer. If any changes are made to the network adapter bind order you may need to repeat these actions.

Thursday, 19 May 2011

Add NIC drivers to ESXi 4

You cannot add drivers to an ESXi installation during the setup process, they must be added after:

1.       Connect to the ESXi host using the vSphere Client and put the ESXi host in to maintenance mode

2.       Download and install the VMware vSphere Command-Line Interface
3.       Download the drivers for your hardware on to the local PC
4.       Load the VMware vSphere CLI and run the following command:
vihostupdate.pl –server [HOSTS IP] –username root –install –bundle [PATH TO FILES ON LOCAL PC]

5.       Restart the host, once it’s back up verify you can see the additional NICs and remove it from maintenance mode

Monday, 9 May 2011

Exchange 2010 Calendar Permissions from the Powershell

With Exchange 2010 came the ability to manage permissions on folders through the powershell, one of the most common tasks with this is managing calendar permissions. Here are a set of simple commands to aid managing them.

To get the permissions of a mailbox:
Get-MailboxPermission -identity "Dan Woodhouse"
To get the permissions of a subfolder in a mailbox:
Get-MailboxFolderPermission -identity "Dan Woodhouse:\Calendar"
To change permissions on a subfolder in a mailbox:
Add-MailboxFolderPermission -identity "Dan Woodhouse:\Calendar" -user "The Boss" -AccessRights Reviewer
To remove permissions on a subfolder in a mailbox:
Remove-MailboxFolderPermission -identity "Dan Woodhouse:\Calendar" -user "The Boss"
If we wanted to add permissions to every mailbox that matches a certain criteria we can use filters, in the example below we will grant The Boss Author permissions to every mailbox for users whos name starts with Dan and are based in the Birmingham office:
Get-mailbox -Filter {(Name -like 'Dan*' -and Office -eq 'Birmingham')} | ForEach-Object {Add-MailboxFolderPermission $_":\Calendar" -User "The Boss" -AccessRights Author}
To remove these permissions we could use:
Get-mailbox -Filter {(Name -like 'Dan*' -and Office -eq 'Birmingham')} | ForEach-Object {Remove-MailboxFolderPermission $_":\Calendar" -User "The Boss"}