Archive for the ‘Operating Systems’ Category

“Object Required” error while changing passwords using OWA

IIS, MS Exchange, Windows Server 2003 | Posted by p_lider September 6th, 2010

After deploying MS Exchange 2003 server in your organization and configuring OWA to let users change their domain passwords you can face a strange issue. When users try to change their passwords, after clicking “OK” button they see an error message saying “Object Required” and their password are not being changed. This enigmatic error message means, that the MS Exchange cannot find a properly registered COM object in the registry. To solve the problem you must manually register the “iispwchg.dll” library on the MS Exchange server. The full command to do this is:

regsvr32 %windir%\system32\inetsrv\iisadmpwd\iispwchg.dll

The reason why MS Exchange does not register mentioned library by itself during the installation is unknown for me. However I noticed, that MS Exchange installers are written is such a way, so the administrators can demonstrate their knowledge and skills <ironic> before the MS Exchange product can start fully working.

OmniPass software and Windows 7

Software, Windows 7 | Posted by p_lider September 6th, 2010

If you want to install the OmniPass software version which was designed for Windows Vista in Windows 7 think twice before making this mistake. Doing so can result in a very long delays during the logon of the user’s profile who installed the software. This can even cause some of your user profiles to be unable to login constantly showing the “Welcome” message on the screen.

So do not install the OmniPass software (the version which was designed for Vista) in Windows 7 if you want to have your system to be usable.

Bind v9.2 does not warn about configuration syntax errors

Linux/UNIX | Posted by p_lider September 6th, 2010

Some time ago I faced a very strange issue with Bind 9 DNS server. Everything was working fine until I rebooted the DNS server. After the reboot server started to return “SERVFAIL” errors instead of resolving the names. It took me more than 2 hours to fix the problem. The problem had been caused by small syntax error in Bind’s zone config file. OK, you can say that that was me who was responsible for the situation. Well, partially, because the changes to the config file had been made many months before I rebooted the server. I remember, that the Bind server did not warn me of any problems while reloading the configuration after I made changes to the zone config file. Moreover, there was no entry in log files about problems with Bind or its configuration either after reloading Bind’s configuration or after rebooting the server.

So, if you make any changes to zone config files for Bind 9 servers make note, that if you do some syntax errors in the config you will not be warned and as the result, the DNS server after the reboot or Bind’s service restart will be unusable constantly throwing “SERVFAIL” errors because it will not be able to load its configuration properly.

Completely disabling the autorun feature in Windows XP/2003

Windows Server 2003, Windows XP | Posted by p_lider August 27th, 2010

Nowadays many viruses and malware spread using portable media like pendrives, players or DVDs. This is possible thanks to the autorun feature which is in every Windows operating system (95 or newer). You can find a lot of guides in the internet telling how to disable the autorun in Windows. However I noticed, that in most cases the guides are not accurate – they do disable the autorun yet they don’t prevent the autorun.inf file from being analyzed by the system. Thanks to that, the system will not execute commands from autorun.inf file by itself but if you double click the removable disk icon, the system will execute the default command from autorun.inf file and thus install the malware.

Fortunately, I found a way to prevent the system from reading the autorun.inf file at all resulting in completely disabled autorun feature. It is done by creating a new key in the registry. The key that must be created is:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\IniFileMapping\Autorun.inf
with its default value set to:SYS:DoesNotExist

After creating mentioned key and restarting the shell by killing explorer.exe process, logging out or rebooting, the autorun feature in the whole system will be completely disabled allowing everyone to plug any portable devices without worrying about malware anymore.

Sharing folders in XP by anyone

Windows Server 2003, Windows XP | Posted by p_lider August 23rd, 2010

By default, only members of “Power Users” or “Administrators” groups can share folders or printers. Sometimes this is not enough – sometimes we want to allow specific users to have a possibility to share some folders but nothing more. Unfortunately there is no graphical tool in Windows XP or in any other version of Windows, which can give us a possibility to do that.

However, there is a great tool called “TweakUI” (created by Microsoft), which can change specific Access Lists in the registry, so we can give anyone we want the right to share folders or printers. To make this happen you must do the following steps:

  1. Download and install TweakUI (you can get it from here: http://www.microsoft.com/windowsxp/downloads/powertoys/xppowertoys.mspx)
  2. Launch it and go to “Access Control” tab.
  3. Now give the same rights for the users or groups you want to be able to share folders, like they are set for “Power  Users” in the following categories:
    • Manage file/print server connections
    • Manage file shares
    • Manage print shares
  4. Apply the changes and reboot the system.

From now, the specified in step 3 users or groups will have the right to share folders. It is wise, to create a group called for example “Share Creators”, give it the mentioned earlier rights and put all the users we want to share folders into that group.

“HP Compaq dc7600 CM” computers and Windows XP installation

Hardware, Windows XP | Posted by p_lider August 23rd, 2010

While installing the Windows XP operating system on some of the “HP Compaq dc7600 CM” computers I came to a strange problem – the Windows XP CD did not boot. The solution to this strange behavior was to disable the “Hard Disk Emulation” in BIOS for the first (text) phase of the Windows XP installation. After the text phase, the “Hard Disk Emulation” must have been re enabled because without it the system couldn’t boot from the hard drive.

This was strange and I don’t know what can be causing it. However, the mentioned trick does the job :)