Wireless network adapter remains disabled in Windows Server 2008 R2

by Shijaz Abdulla on 20.07.2011 at 14:23

I recently got myself a Belkin Wireless FSD7050 USB adapter for my Windows Server 2008 R2 test machine.

After installing the latest drivers from Belkin, the adapter is detected by Windows, but refuses to ‘enable’.

This is because wireless networking is disabled by default in Windows Server 2008 R2. To enable it, go to Server Manager > Features > Add Features > and add the Wireless LAN Service.

Also applies to: Windows Server 2008

RSAT tools for Windows 7

by Shijaz Abdulla on 14.10.2009 at 12:23

A commenter asked me today about the Windows Server 2008 RSAT tools not working on Windows 7. The answer is simple – there is a different build of the RSAT tools for Windows 7 available as a free download here.

 

image

SharePoint Server 2010 needs 64-bit SQL Server

by Shijaz Abdulla on 14.05.2009 at 15:51

64 bitSharePoint Server 2010 will require a 64-bit edition of SQL Server – more specifically either SQL Server 2005 or SQL Server 2008 running on Windows Server 2008.

SharePoint Server 2010 will not support Internet Explorer 6. Users will have to use Internet Explorer 7 or above. However, non-Microsoft  browsers such as FireFox 3.x (on Windows & non-Windows platform) and Safari 3.x (on non-Windows platform) will be supported.

The Office 2010 beta will be available in July, but SharePoint Server 2010 beta will not be made available at that time.

Enterprise Search in Office 2010 has been improved, with Microsoft’s recent acquisition of Fast Search & Transfer.

This information was revealed during the TechEd conference.

How to enable Remote Desktop remotely

by Shijaz Abdulla on 03.05.2009 at 17:54

This article used to exist on www.shijaz.com before it was taken down in May 2009. Originally published in January 2008.

This article explains how you can enable Remote Desktop on a server that you do not have physical access to.

You’ve built new servers, updated them with the latest service pack, and even run Windows Update. Proud of the good job you done, you move upstairs to the comfort of your office to do the rest of the installation, away from the freezing server room. And then you suddenly realize that you did not enable Remote Desktop connections on your new server. Aw, now you need to go back all the way to your data center to enable RDP. The situation is even worse if you pre-configured the server without enabling RDP and shipped it to your branch location in Timbuktu!

Well, here’s the good news. You can actually enable remote desktop remotely. All you need to do is open up the registry of that server remotely, and make some changes and then initiate a remote restart of the server. Well, that’s the only downside – you normally don’t need a restart if you enable it physically.
1. On your Windows workstation, open Registry Editor (Start –> Run –> Regedit.exe –> OK)
2. On the File menu, choose Connect Network Registry.

Regedit1
3. Select the name of the computer that you want to enable RDP on. Make sure the logged in user has administrator rights on the remote server.

enable1

 

4. On the remote computer, Navigate to the key HKLMSYSTEMCurrentControlSetControlTerminal Server. Find a value named fDenyTSConnection and change it to 0 (zero).

5. Restart the remote computer by typing the following command in the Command prompt of your workstation.

shutdown -m \myserver -r

where ‘myserver’ is the name of your server.

6. Wait for the server to restart and connect to it using Remote Desktop Connection (MSTSC) from your Windows PC.

Windows Server 2008 Foundation – For Very Small Businesses

by Shijaz Abdulla on 02.04.2009 at 00:16

Microsoft has released Windows Server 2008 Foundation, which is a flavor of Windows Server specifically designed for very small organizations, with up to 15 users. The cost for a complete solution including hardware will be less than US$ 1000.

The Foundation Server will offer basic functionality such as file sharing, printer sharing, IIS, Active directory, terminal services. The server can act as a domain controller or be a member server. All applications that are certified for Windows Server 2008 standard will work on Windows Server 2008 Foundation. However, the 15 user limit will always apply.

Unlike Small Business Server, the Foundation Server does not have any applications like Exchange Server included with the OS.

Windows Vista SP2, Windows Server 2008 SP 2

by Shijaz Abdulla on 07.03.2009 at 14:22

The 32-bit and 64-bit release candidate versions of Windows Vista Service Pack 2, and Windows Server 2008 SP2 are available for download on the Microsoft website.

Below are some of the enhancements that are available with SP2:

  • Support for Bluetooth v2.1
  • Ability to write data to Blu-Ray discs
  • Includes Windows Search 4.0
  • Provides Hyper-V as a fully integrated feature of WS08, including one free guest OS with WS08 Standard Edition, 4 free licenses with Enterprise Edition, and unlimited free licenses with Datacenter Edition.
  • and more

Hyper-V Remote Administration

by Shijaz Abdulla on 27.01.2009 at 14:30

January 27, 2009

When you connect to a Windows Server 2008 computer running Hyper-V from a Windows Vista client, the mouse input is not captured when you connect to a guest machine unless you install the Integration Services on the guest machine. You receive the following message:

image

Mouse not captured in Remote Desktop session.

It is however, possible to remotely manage Hyper-V from within a Windows Vista MMC snap-in upon installation of an optional update. To download the Hyper-V Remote Management Update, follow these links.

Upon installation, you will find a ‘Hyper-V Manager’ icon in the Administrative Tools folder on your Start Menu.

image

Outlook prompting for credentials when OAB Web-based publishing enabled

by Shijaz Abdulla on 25.01.2009 at 10:17

January 25, 2009

If you have enabled web-based publishing of your Offline Address Book (OAB) and your Outlook users get continuously prompted to enter their passwords, you need to check a couple of things:

  • Make sure Autodiscover is working perfectly before you made the OAB change.
  • Hold down the CTRL button and right click on the Outlook icon on the task bar, then select Test Email Autoconfiguration. Unselect GuessSmart and Secure GuessSmart and keep Use Autodiscover selected. On the Log tab, make sure Autodiscover is successful and that it was able to bind to an SCP.
  • Make sure that the autodiscover.domain.com entry is added to your certificate’s Subject Alernative Names list.
  • If you are facing problems with Autodiscover, you should correct that first before attempting the steps mentioned below.
  • Make sure that you have defined the External and Internal URLs for the OAB virtual directory in your client access server.

Once you have made sure that Autodiscover is working OK, and that the credentials are being prompted for the OAB URL (and not the mailbox server), you need to check the IIS Authentication setting on the client access server.

  • On the Client Access Server running Windows Server 2008, open IIS Manager console.
  • Click on Default Web Site
  • Open Authentication
  • Note that only Anonymous Authentication is enabled. All other authentication methods should be disabled.
    • Temporarily enable Windows Authentication
    • Right click on Windows Authentication and choose Advanced Settings
    • Uncheck Enable Kernel Mode Authentication and click OK
    • Disable Windows Authentication
    • Do an IISRESET

image

Also make sure that kernel-mode authentication is disabled for the RPC virtual directory.

Restart Outlook. You should no longer get the prompt for credentials. Test the configuration with Outlook Anywhere clients as well, if you have enabled Outlook Anywhere on your Client Access Servers.

You may need to repeat this configuration on all Client Access Servers that are enabled for Web-based publishing of Offline Address Book (OAB).

Exchange 2003: Support ending April 2009

by Shijaz Abdulla on 10.11.2008 at 09:35

Mainstream support for Exchange Server 2003 will end on April 14, 2009. This means that you cannot contact PSS for supporting problems on Exchange Server 2003 after this date, unless you sign up for ‘extended’ support at an additional cost.

Maybe this is a good time for organizations to seriously start thinking about upgrading to Exchange Server 2007 and make use of the new, advanced features.

For those who have made it to Exchange Server 2007 SP0, here is a shocker: Mainstream support for Exchange Server 2007 SP0 (i.e. Exchange Server 2007 with NO service pack installed) will end on January 13, 2009. Yes, that’s about two months from now.

For those who are still wary of installing SP1 on Exchange Server 2007, it’s time to take a call on the chicken-and-egg upgrade dilemma between Windows Server 2008 and Exchange Server 2007 SP1.

Some more information:

  • Windows Server 2003 and Windows Server 2003 R2 will go out of mainstream support on July 2010.
  • Windows XP will go out of mainstream support on April 14, 2009.

Unlocking files that are in use

by Shijaz Abdulla on 22.10.2008 at 21:20

Sometimes you cannot delete or rename a file that is currently in use. You might receive an access violation error, or simply a message telling you that your action could not be completed because the file is open in another program.

image

You may have already come across the Unlocker freeware tool that lets you "unlock" files that are in use by some application.

Here is another way (let’s call it the ‘techie’ way) to unlock files that are in use. It makes use of the Process Explorer tool from Windows SysInternals.

  • Download the Process Explorer tool. Execute procexp.exe
  • Choose Find > Find Handle or DLL option

image

  • Type the name of the file you want to unlock and hit Search.

image

  • The process EXE locking the file and the path to the file are listed. Double click on the result.

image

  • The file handle will be highlighted. Right-click on it and choose Close Handle.

Your file is now unlocked and can now be deleted, moved or renamed.

A little disclaimer here, closing handles might cause data inconsistency, loss and/or other undesirable effects. Make sure you understand what you’re doing before you do it.

< Previous posts