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

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"

• Windows 2000 RTM with all Service packs = Schema version 13
• Windows Server 2003 RTM with all Service packs = Schema version 30
• Windows Server 2003 R2 RTM with all Service packs = Schema version 31
• Windows Server 2008 RTM with all Service packs = Schema version 44
• Windows Server 2008 R2 RTM with all Service packs = Schema version 47

Check the schema version in the Registry:

HKLM\SYSTEM\CurrentControlSet\Services\NTDS\Parameters\<Schema Version>

Check the schema version with dsquery:

dsquery * CN=Schema,CN=Configuration,DC=Root-Domäne -Scope Base -attr objectVersion

To enable IIS 6.0 in Windows Server 2003 or IIS7 in Windows Vista RTM with the appropriate MIME Types, add:

• .xap     application/x-silverlight-app
• .xaml    application/xaml+xml
• .xbap    application/x-ms-xbap

Adding MIME Types by a simple VB script:

• Here is a VBS script you could run to enable each of these types:


Const ADS_PROPERTY_UPDATE = 2
'
if WScript.Arguments.Count < 2 then
WScript.Echo "Usage: " + WScript.ScriptName + " extension mimetype"
WScript.Quit
end if
'
'Get the mimemap object.
Set MimeMapObj = GetObject("IIS://LocalHost/MimeMap")
'
'Get the mappings from the MimeMap property.
aMimeMap = MimeMapObj.GetEx("MimeMap")
'
' Add a new mapping.
i = UBound(aMimeMap) + 1
Redim Preserve aMimeMap(i)
Set aMimeMap(i) = CreateObject("MimeMap")
aMimeMap(i).Extension = WScript.Arguments(0)
aMimeMap(i).MimeType = WScript.Arguments(1)
MimeMapObj.PutEx ADS_PROPERTY_UPDATE, "MimeMap", aMimeMap
MimeMapObj.SetInfo
'
WScript.Echo "MimeMap successfully added: "
WScript.Echo " Extension: " + WScript.Arguments(0)
WScript.Echo " Type: " + WScript.Arguments(1)

• If you copy and paste the code above into a VBS file and save it as ADDMIMETYPE.VBS the syntax to add each type would be:

ADDMIMETYPE.VBS .xap application/x-silverlight-app ADDMIMETYPE.VBS .xaml application/xaml+xmlADDMIMETYPE.VBS .xbap application/x-ms-xbap

or you could add it very simple over the IIS Manager.

• First I created a Image of the old server with Symantec Backup Exec System Recovery 2010, this could be done online. I just stopped all the Sharepoint, SQL and Web Services so that no new data could be written in the time I created this Image.
• After I moved this Image to the Microsoft Hyper-V Host Server, I started to convert the v2i Image with Symantec Backup Exec System Recovery 2010 to a Microsoft VHD.
• I created a new Virtual Machine on the Hyper-V Server and added this existing VHD. (Important here: I tried to create the same Hardware environment for the VM which I had as physical Hardware before. (Dual Core with 2048MB memory) So I had basically no problem to start the Virtual Machine.
• Now its time to install the Hyper-v integration components (the VM Drivers) which can only be installed on Windows Server 2003 with SP2 or later. I turned off the Virtual Machine again and attached the VHD File offline on my Hyper-v Server, so I had file access to the Virtual Hard Disk. I simply added the Servicepack 2 file to the root of the VHD.
• After unmounting the VHD, I started my Virtual Machine again and installed the Servicepack 2 and the Hyper-v Integration components.
• Now I added more Hardware to the Virtual Machine (Quad-Core and 4GB memory). I also change the Legacy Network Adapters to normal Network Adapters (higher Network performance)

The performance of the new Hyper-v is just pretty impressive.

The Event Log shows the following information:

==============================

Event Type: Information

Event Source: RsyncServer

Event Category: None

Event ID: 0

Date: 22.12.2009

Time: 08:30:52

User: WEB-WIN-xxx-xxx\SvcCWRSYNC

Computer: WEB-WIN-xxx-xxx

Description:

The description for Event ID ( 0 ) in Source ( RsyncServer ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: RsyncServer: PID 1856: `RsyncServer’ service stopped, exit status: 11.

==============================