Install and configure IPv6 on Windows Server 2003

Posted on October 1, 2010 by Thomas Maurer

On Microsoft Windows Server 2003 there is no GUI to configure IPv6. So this article should show you how to configure IPv6 on a Windows Server 2003.

Install the IPv6 Protocol in the Network Adapter Properties or Control Panel
Open the console
Type “netsh” this is a command line program to configure network adapters
Here are some demo configurations

int ipv6
reset
add dns interface=”<Interface Name>” address=<IPv6 primary DNS IP Address>
add dns interface=”<Interface Name>” address=<IPv6 secondary DNS IP Address>
add route prefix=::/0 interface=”<Interface Name>” metric=0 nexthop=<IPv6 Gateway IP Address>
add address interface=”<Interface Name>” address=<IPv6 IP Address>

int ipv6
reset
add dns interface=”Local Area Connection” address=fec0:0:0:0:ffff::1
add dns interface=”Local Area Connection” address=fec0:0:0:0:ffff::2
add route prefix=::/0 interface=”Local Area Connection”metric=0 nexthop=fe80::1
add address interface=”Local Area Connection” address=fe80::2

int ipv6
reset
add dns “Local Area Connection” fec0:0:0:0:ffff::1
add dns “Local Area Connection” fec0:0:0:0:ffff::2
add route ::/0 “Local Area Connection” fe80::1
add address”Local Area Connection” fe80::2

Pagefile size limits on Windows Server 2003

Posted on September 22, 2010 by Thomas Maurer

Some moths ago I posted a Blogpost called “Pagefile size bigger than 4095MB on Windows Server 2003“. In this post I wrote about the pagefile size limit of 4096MB. Today I got a comment on this post which shows another solution for this.

If you use the /PAE (Wikipedia Link: Physical Address Extension) switch, the pagefile is not limited to 4096MB anymore. Using the PAE switch limits the pagefile to 16TB, this should be enough for the most Windows Server 2003 32-bit systems. If you don’t use PAE the limit of the Pagefile remains 4GB.

By the way, Windows Server 2003 x64 can also have pagefiles up to 16TB and Windows Server 2003 for IA64 systems can have pagefiles up to 32TB. And for all versions, Windows Server 2003 supports up to 16 pagefiles.

For more information on memory limits in Windows Server 2003 check out this TechNet Blog post.

Thank goes to Ethan Anderson for giving me this information.

Powershell: Changing registry key value

Posted on August 3, 2010 by Thomas Maurer

Powershell Header

After posting Pagefile size bigger than 4095MB on Windows Server 2003 I had the Idea to change this registry values with powershell.

First start powershell
You can get all PS Drives with the command
```
Get-PSDrive
```
Now you see the drive HKLM which stands for HKEY_LOCAL_MACHINE

Open this Registry Key

Set-Location 'HKLM:\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management'

With this command you get all the key values
```
Get-ItemProperty -path .
```

With the next command you can set the the key value

Set-ItemProperty -path . -name "PagingFiles" -value "D:\pagefile1\pagefile.sys 4096 4096"

And now the simple way with multiple entries:

$values = @"
D:\pagefile1\pagefile.sys 4096 4096
D:\pagefile2\pagefile.sys 4096 4096
"@
$keys = "HKLM:\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management"
$name = "PagingFiles"
Set-ItemProperty -path $keys -name $name -value $values

Pagefile size bigger than 4095MB on Windows Server 2003

Posted on August 3, 2010 by Thomas Maurer

UPDATE: If you can use PAE on your Windows Server 2003 you should check out this post: Pagefile size limits on Windows Server 2003

The pagefile size on Windows Server 2003 x86 and other Windows x86 platforms is limited to 4095 MB per pagefile. But a lot of Windows Server 2003 systems already have 4GB RAM and are using PAE (Physical Address Extension) to use them. So it would be useful to create more than 4 GB pagefiles.

Microsofts solution for this is to create multiple pagefiles. You can now create multiple pagefiles on different partitions. If you don’t have enough partitions or you just have one, you can create multiple pagefile in different folders by using the Windows Registry.

Create the folders on the drive where the pagefiles should be located. For example, C:\Pagefile1, C:\Pagefile2, and C:\Pagefile3.
Open regedit.exe
I would recommend to create a backup of the registry
locate this key:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\SessionManager\MemoryManagement
Edit the value “PagingFiles”
Remove the existing values and add the following values:
C:\Pagefile1\pagefile.sys 4096 4096
C:\Pagefile2\pagefile.sys 4096 4096
C:\Pagefile3\pagefile.sys 4096 4096
Save this

Note: It’s still recommended to have the Pagefiles on the same partition as the system

You can get more information in this Microsoft Knowledge Base entry: How to overcome the 4,095 MB paging file size limit in Windows

How to do this with Powershell: Powershell: Changing registry key value

Solved: Cannot download File from IIS6 FTP

Posted on July 22, 2010 by Thomas Maurer

Today we a ticket which was escalated by the second level support to the engineering. A customer could not download, remove or rename the file via FTP. The Hosting is running on a Windows Server 2003 R2 with IIS6. After checking the file on the filesystem I saw that the filename had a space in before.

Normalfilename:

“filename.html”

Wrongfilename:

” filename.html”

You cannot really name a file like that with a windows machine. But Linux and Unix systems like Mac OS X allow this.

After renaming the file to a normal Windows filename, the customer you download the file again.

Btw you can simple rename the file with powershell

Rename-Item " filename.html" "newfilename.html"

Genotec released Shared Hosting with .NET Framework 4

Posted on July 20, 2010 by Thomas Maurer

Last Monday we added support for the .NET Framework 4 to our Windows Shared Hosting Server at Genotec. Today the official Press release was published.

We also added support for:

.NET Framework 4
ASP.NET MVC 2.0
Silverlight 4
New Versions of Persits AspMail, AspPDF, AspJPEG

Genotec: .Net Freamwork 4 for Webhosting (German)

Der in Allschwil/Basel ansässige Internet Service Provider Genotec AG lanciert mit .NET Framework 4 die neueste Version des Microsoft Entwickler-Frameworks.

Mit dem Ziel stets neue Features und aktuelle Produkte zu integrieren, hat Genotec das .NET Framework 4 von Microsoft lanciert. Ab sofort steht allen Windows Webhosting-Kunden der Genotec dieses Angebot zur Verfügung.

«Die neue Version von .NET lässt Projekte im Windows-Umfeld noch einfacher und mit vielen neuen Features erstellen. Unsere Kunden werden grosse Freude daran haben.» so Thomas Betz, Entwickler bei Genotec. Die neue Version mit vielen Features überzeugt auf der ganzen Linie. Zu den wichtigsten Neuerungen zählen unter anderem Codeverträge, eine DLR (Dynamic Language Runtime), neue Diagnose und Leistungstools sowie eine verbesserte automatische Speicherbereinigung. Die komplette Abwärtskompatibilität rundet den sehr guten Eindruck des .NET Framework 4 ab.

Verfügbar ist das .NET 4.0 bereits ab dem kleinsten Angebot für CHF 9.90 pro Monat. Mit dem Shared Hosting Entry erhalten Kunden ein Webhosting mit bis zu 10 Domains, komplettes Mailhosting inkl. Webmail, tägliches Backup, Statistiken sowie der kompletten Integration ins Hosting Control Center von Genotec und weiteren Features.

Über Genotec AG:
Der Schweizer Internet Service Provider Genotec AG wurde 2001 gegründet. Das Unternehmen beschäftigt 36 Mitarbeitende und betreut in den eigenen Rechenzentren in Zürich, Basel, Bern und Allschwil über 50’000 Domain- und rund 500 Serverkunden. Genotec ist ein BAKOM-registrierter Provider und als «Microsoft Gold Certified Partner» zertifiziert. Genotec wurde von der simsa mit dem Gütesiegel «Swiss Quality Hosting» ausgezeichnet und ist providerliste.ch geprüft.

Seit 2008 ist Genotec neu bei Computerworld in den Top-500 der stärksten IT-Firmen der Schweiz gelistet.

Weitere Informationen zur Genotec: www.genotec.ch

Pascal Leu, Product Manager
Genotec AG
Binningerstrasse 95
CH – 4123 Allschwil
Tel. +41 (0)848 321 123

E-Mail: pressemitteilungen@genotec.ch