This is a little dirty Windows Powershell script which exports or backups Windows Eventlogs. The script creates a .evt file which can be used with the Windows Eventlog Viewer.

# Config
$logFileName = "Application" # Add Name of the Logfile (System, Application, etc)
$path = "C:\temp\" # Add Path, needs to end with a backsplash

# do not edit
$exportFileName = $logFileName + (get-date -f yyyyMMdd) + ".evt"
$logFile = Get-WmiObject Win32_NTEventlogFile | Where-Object {$_.logfilename -eq $logFileName}
$logFile.backupeventlog($path + $exportFileName)

And with the next code it cleans up older exported Eventlogs.

# Deletes all .evt logfiles in $path
# Be careful, this script removes all files with the extension .evt not just the selfcreated logfiles
$Daysback = "-7"

$CurrentDate = Get-Date
$DatetoDelete = $CurrentDate.AddDays($Daysback)
Get-ChildItem $Path | Where-Object { ($_.LastWriteTime -lt $DatetoDelete) -and ($_.Extension -eq ".evt") } | Remove-Item

UPDATE: If you wanna clean the Eventlog after the export you can do that by using the Clear-Eventlog cmdlet. (Thanks to Michel from server-talk.eu)

Clear-Eventlog -LogName $logFileName

And here the whole “script”

# Config
$logFileName = "Application" # Add Name of the Logfile (System, Application, etc)
$path = "C:\temp\" # Add Path, needs to end with a backsplash

# do not edit
$exportFileName = $logFileName + (get-date -f yyyyMMdd) + ".evt"
$logFile = Get-WmiObject Win32_NTEventlogFile | Where-Object {$_.logfilename -eq $logFileName}
$logFile.backupeventlog($path + $exportFileName)

# Deletes all .evt logfiles in $path
# Be careful, this script removes all files with the extension .evt not just the selfcreated logfiles
$Daysback = "-7"

$CurrentDate = Get-Date
$DatetoDelete = $CurrentDate.AddDays($Daysback)
Get-ChildItem $Path | Where-Object { ($_.LastWriteTime -lt $DatetoDelete) -and ($_.Extension -eq ".evt") } | Remove-Item
Clear-Eventlog -LogName $logFileName

If you need to know which version of NTFS you are using you can do that with the fsutil.exe and the following command.

In my case I am testing my C:\ drive:

fsutil fsinfo ntfsinfo c:

More on NTFS Versions on wikipedia.

Summary

This Error is caused by the a know issue with permissions of the IIS metabase. The metabse ACL’s do not include the IIS_WPG group on the W3SVC/AppPools part in the metabase.

Solution

• Download metaacl.vbs
• Run the following command:
  cscript metaacl.vbs IIS://Localhost/W3SVC/AppPools IIS_WPG RE

More Information

• http://support.microsoft.com/?id=267904
• http://blogs.msdn.com/b/carloc/archive/2006/09/20/unable-to-get-the-private-bytes-memory-limit-for-w3wp-exe-process.aspx
• http://support.microsoft.com/?id=812614
• http://forums.iis.net/t/1057159.aspx

This little guide shows you how you can redirect http request to the https website using IIS Settings. You can do the same on other versions of IIS slightly different.

1. First set “require SSL” under the SSL Settings from the Website
   
2. Under the Error Page Settings edit the 403 Error Page
   
3. mark the Setting “Respond with a 302 redirect” and add the https URL
   

Today I was setting up my little lab, I decided to create a Windows PPTP VPN for my lab network which should give me more comfort. First I installed the Network Policy and Access Services Role and did the configuration. I also enabled PPTP Passthrough, added a port forwarding and a firewall rule to my Cisco Linksys RV042. I know the RV042 is not really a big deal, but you have a lot of jobs and if you don’t really need a lot of network options, like me in my lab, this is a pretty cool device.

I now tested the VPN Connection with my Windows 7 Client. Error 800 and 807 which basically means no connection through the firewalls with the VPN Server.

I checked again the Firewall Configuration on my RV042, and could not found any mistake. After a quick search with Google and Bing I saw a lot of posts with the same problem and the Linksys RV042.

After some search I came to a solution, I deactivated the SPI Firewall on the Device, and this caused the problem. After activating the SPI Firewall again, the error was gone and the VPN worked.

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.

1. Install the IPv6 Protocol in the Network Adapter Properties or Control Panel
2. Open the console
3. Type “netsh” this is a command line program to configure network adapters
4. 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

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.

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

1. First start powershell
2. You can get all PS Drives with the command

   Get-PSDrive

   

3. Now you see the drive HKLM which stands for HKEY_LOCAL_MACHINE
4. Open this Registry Key

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

5. With this command you get all the key values

   Get-ItemProperty -path .

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

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.

1. Create the folders on the drive where the pagefiles should be located. For example, C:\Pagefile1, C:\Pagefile2, and C:\Pagefile3.
2. Open regedit.exe
3. I would recommend to create a backup of the registry
4. locate this key:
   HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\SessionManager\MemoryManagement
5. Edit the value “PagingFiles”
6. 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
7. 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