Extending Windows 2008 Trial

andy18    Windows-related    

By default, any edition of Windows Server 2008 may be installed without activation and evaluated for an initial 60 days. If you need more time to evaluate Windows Server 2008, the 60 day evaluation period may be reset (or re-armed) three times, extending the original 60 day evaluation period by up to 180 days for a total possible evaluation time of 240 days.

To reset the evaluation period,

1. Login to the server as an administrator
2. Click Start, and then click Command Prompt.
3. Type slmgr.vbs -dli, and then press ENTER to check the current status of your evaluation period.
4. To reset the evaluation period, type slmgr.vbs –rearm, and then press ENTER.
5. Reboot the server

This will reset the trial/evaluation for another 60 days.

Sorting Helm 3.x Database

andy18    Helm    

If you need to sort out the username, domain name and the package type hosted under a reseller, the following SQL query may help:

use HelmDBName
select PackageType.ResellerAccountNumber, Package.AccountNumber, HostDomain.DomainName,PackageType.PackageTypeName
from PackageType, HostDomain,Package
where PackageType.PackageTypeId = Package.PackageTypeId AND
Package.PackageId = HostDomain.PackageId AND
ResellerAccountNumber = ‘Reseller_Username‘ AND
HostDomain.SubDomainId = 0 AND
HostDomain.DomainAliasId = 0

Changing the default SQL 2005 data directory

andy18    SQL-related    

Default installation of SQL 2005 has the data directory set at C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data. However, if you are looking to setup another RAID volume that separate the database(s) data directory from the default, you may do this by firing up the SQL Server
Management Studio > Right-click the server in the object explorer and select Properties > Database Settings. Change the Data and Log directory to the disk drive that you wish to or any other folders.

Repairing .Net 1.1 on Windows 2003

andy18    Windows-related    

.Net cease from working on one of my testing box today and I am loosing track of where the problems comes from. Trying with the re-installation of the .Net Redistribute and without any luck which the Windows throws you the message saying the version has been installed on the server.

Here’s what I did to make the reinstallation a success after Googling around:

1. Fire up your registry editor by hitting “regedit” at your Windows > Run.
2. Navigate to the key HKLM\Software\Microsoft\Windows\CurrentVersion\Setup\OC Manager\Subcomponents and find one value called “netfx”. Delete it
3. Create a .inf by naming it netfx_repair.inf with the following content:

[Version]
Signature = “$Windows NT$”
DriverVer=10/01/2002,5.2.3790.0
[Components]
netfx=netfxocm.dll,UrtOcmProc,netfxocm.inf,,7

4. Launch your favorite command prompt and execute the following command:

sysocmgr /i:Path_to_your_ netfx_repair.inf

Usually I will prefer to put it in C:\, which you save your time from typing the full path

5. It will bring up a new installation Windows. Follow the on screen instruction. You may need your i386 folder ready in hand at your server as well. If you are prompted for a Source Path, point it to the i386 folder on your server and select the necessary files.

6. Once installation completed, you will need to register some of the assemblies back to the server by issuing:

%windir%\Microsoft.NET\Framework\v1.1.4322\gacutil.exe” /f /il %windir%\Microsoft.NET\Framework\v1.1.4322\assemblylist.txt

7. Restart your server if you are being asked for and .Net should be up and running back.

Windows 2008 RC -> Stable version?

andy18    Windows-related    

All Windows Server 2008 test versions (Beta 3, Release Candidate 0, Release Candidate 1, etc) expire on June 30th, 2008. No exceptions. If you want to use your Windows Server 2008 installation after June 30th, 2008 you will need to install a new copy of Windows Server 2008 (RTM) or upgrade your installation to Windows Server 2008 (RTM)

Recent Windows versions have different mediakits for different versions, like Trial, OEM, Full / Retail and Volume License. Product Keys for recent Windows versions are also different and as a rule of thumb can only be used in conjunction with the right mediakit. This means you cannot use an OEM Product Key with Volume License media or use a Trial Key with Full media.

Switching between Windows Vista short cut

andy18    Windows-related    

I have just formatted my Vista Business yesterday and was digging around if there’s any quick way for me to play around for the the short cut at my quick launch toolbar and I found this site. Generally, you can switch around the Quick Launch ToolBar by hitting {Windows} + 1, {Windows} + 2…etc to activate the quick launch.

Remove files older than x day

andy18    Linux-related    

The following command will remove all files older than x days:

find /path_to_files -mtime +x -exec rm {} \;

Full duplex or Half duplex?

andy18    Linux-related    

In Linux environment, you may check if your NIC is running in full/half duplex by executing the following command:

root@localhost [~]# ethtool eth0

Output of the result as:

Settings for eth0:
Supported ports: [ TP MII ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
Supports auto-negotiation: Yes
Advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
Advertised auto-negotiation: Yes
Speed: 100Mb/s
Duplex: Full
Port: MII
PHYAD: 1
Transceiver: internal
Auto-negotiation: on
Supports Wake-on: g
Wake-on: g
Current message level: 0×00000007 (7)
Link detected: yes

root@localhost [~]# dmesg | grep -i duplex

Output of the result as:

e100: eth0: e100_watchdog: link up, 100Mbps, full-duplex
e100: eth0: e100_watchdog: link up, 100Mbps, full-duplex
e100: eth0: e100_watchdog: link up, 100Mbps, full-duplex
e100: eth0: e100_watchdog: link up, 100Mbps, full-duplex

e100: eth0: e100_watchdog: link up, 100Mbps, full-duplex

WHM Account Transfer Error

andy18    Cpanel    

If you are getting the following error when you try to perform any account transfer from the WHM, make sure that the port are open on your server. Check the firewall configuration on your server.

Connecting to Remote Server Failed: Unable to connect to 123.111.222.333:1111: Bad file descriptor