Restoring Selfimage’s partition image to a greater partition

Windows 7, Windows Server 2003, Windows Server 2008 and 2008 R2, Windows XP | Posted by p_lider December 19th, 2010

Sometimes you must restore you partition images made by programs like SelfImage to a greater partitions – for example after buying new greater hard drive and setting the partitions’ sizes to greater values as they were in original drive.

The problem with such operation is that after restoring for example 20GB partition image to a partition which has 40GB, you will see, that the file system says that there is only 20GB of total partition’s space. This is caused due to old partition size information saved inside internal filesystem’s structures, which was made during the format of the partition on the original drive. Fortunately, the DISKPART utility built in Windows XP and newer systems can fix that problem. To do that follow the following steps after you restore the image to the new, reater partition:

  1. Launch the diskpart command line utility.
  2. Execute “select volume <number>” command, where “<number>” is a number of the volume containing the restored partition image (the list of all volumes and their numbers can be retrieved by executing “list volume” command).
  3. Execute “extend filesystem” command.
  4. And this is all – now exit the diskpart utility by executing “exit” command and the system will correctly see the real partition size.

Thanks to this tip you can use programs like SelfImage not only for making backups but also for moving entire partitions (including system partitions) to other hard drives even, when they size do not match.

HYPER-V and wrong time measurement in virtual servers

HYPER-V, Windows Server 2003, Windows Server 2008 and 2008 R2, Windows XP | Posted by p_lider December 3rd, 2010

If you have a virtual server which has more than 1 virtual processor and is hosted by HYPER-V technology then you can face problems during time measurement. As the result you can see that login to such server can take quite long time and you can see strange errors in EventViewer saying something like “Windows cannot obtain the domain controller name for your computer network” etc.

The solution to such problems is quite easy – you only have to add /usepmtimer switch to your server’s boot.ini file and restart the virtual server. This will cause a different approach during time measurement and will fix mentioned problems.

VPN connection and internal DNS names

Windows 7, Windows Server 2003, Windows Server 2008 and 2008 R2, Windows XP | Posted by p_lider December 3rd, 2010

Sometimes after you connect to your VPN network by means of any VPN client (CiscoVPN, OpenVPN, etc.) you are not able to access network resources using their names, however you can access them using IP addresses. This is caused by the DnsCache service, which sometimes may cache wrong IP addresses for your internal network names.

To fix this irritating behavior clearing the dnscache will not always work. The best way to cope with this problem is to stop DnsCache service – after doing that every time you try access any network resource by its name, the DNS name query will be passed directly to your DNS servers omitting your local cache.

EDIT:

After some time I noticed one more problem with DNS especially when using VPNs established using RRAS. Simply the names were not being resolved by DNS servers provided by RRAS but they were trying to be resolved by DNS servers outside of VPN. This prevented accessing VPN network resources using names. The problem can be fixed by following the following steps:

  1. Go to Network Connections in Control Panel.
  2. Go to Menu: Advanced -> Advanced Settings -> Adapters & Bindings
  3. Move DialUp connections to the top of the list.
  4. Save changes by clisking OK button.
  5. In Windows XP & 2k also follow the instructions described under the following link: http://support.microsoft.com/default.aspx?scid=kb;en-us;311218
  6. Reboot your computer.

After performing the above operations you should not have any DNS issues when using VPNs on your computer.

Installing OS using DRAC cards having damaged DVD with OS physically inserted into server’s DVD-ROM.

Hardware, Windows 7, Windows Server 2008 and 2008 R2 | Posted by p_lider November 7th, 2010

If your server is equipped with DRAC card and you have also a DVD with an operating system inserted into server’s DVD-ROM, installing the OS remotely is quite an easy operation. However, problems occur when the inserted DVD is damaged and makes the OS installer to stop – without physical presence in the server room, you will have to install the OS using Virtually mounted DVD through network. There would be no problem with that if the Windows Installer would be ignorring the inserted physical DVD – unfortunately it does not ignore it.

So even when you request the server to boot from Virtual media, during the installation the Windows Installer will be using the physically inserted DVD as a source. To avoid that sick behavior you have to disable any optical drives in server’s BIOS setup for the time of installation.  After disabling them, Windows Installer will look for source files only on virtual media and not on physical DVD allowing you to successfully install the OS.

Reconnecting Dell PawerVault MD1000 Enclosure

Hardware | Posted by p_lider November 7th, 2010

If you will ever need to disconnect and then reconnect the Dell PawerVault MD1000 Enclosure from any of your servers, for example while moving whole server room to a different location, then make a detailed note of how it was connected before to the RAID controllers. Reconnecting the enclosure to a different controller or to another connector in the same controller will cause the RAID configuration to be LOST!!! After that, the only way to make the RAID work again will be to import old RAID configuration manually (if previously exported or memmorized) or to create new RAID from scratch and restore the data from a backup.

Mapping orphaned database users to SQL Server 2005 logins

SQL Server | Posted by p_lider October 4th, 2010

If you have many users defined in your MS SQL Server 2005 database, then if you will backup your database and then restore in a new, clean SQL Server instance, you will not be able to map database users with logins in your SQL Server instance. This is because of different SID numbers between the source and destination SQL Server instances. So even creating logins named exactly the same as users in a restored database will not help.

Fortunately, I found a solution. The SQL scipt below will map orphaned users in databases to logins in SQL Server instance even when their SIDs do not match:

sp_change_users_login @Action=’update_one’,
@UserNamePattern=’<database user name>‘,
@LoginName=’<sql server instance login name>
GO

Double clicking the disks icons opens search window instead of their contents

Windows Explorer, Windows Server 2003, Windows XP | Posted by p_lider September 6th, 2010

If the default action for disk drives in “My Computer” window is “Search” instead of “Open” and you cannot change this behavior using “File Types” tab in “Folder Options” then you must set the default value for HKCR\Drive\Shell registry key to none and restart the explorer.exe process.

Mentioned problem sometimes arises after some malware installation – the disinfection not always repairs that problem automatically.

“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.