1. Before you reinstall your OS (this tutorial is for Vista and Windows 7) make sure you have backup of your data.
2. Go to this folder of your original (crashed) system and copy all from it to some folder in your new OS filesystem:
   C:\Users\[SOME_USER]\AppData\Roaming\Mozilla\Firefox\Profiles\[SOME_RANDOM_CODE].default\

   where:
   [SOME_USER] is your current logged user’s username
   [SOME_RANDOM_CODE] – some random Firefox profile code like: mhwibcep.default

3. Now, go to the new Firefox folder on your reinstalled OS:
   C:\Users\[SOME_USER]\AppData\Roaming\Mozilla\Firefox\Profiles\[OTHER_RANDOM_CODE].default\

   where:
   [SOME_USER] is your current logged user’s username
   [OTHER_RANDOM_CODE] – some other random Firefox profile code from your new Firefox installation like: bbtibcep.default

4. Copy all files from Step 2 into Step 3

Happy surfing!

We have found following post here.

Unless licensing is configured during the initial installation of the Remote Desktop Services role on Windows Server 2008 R2, a 120 day grace period is provided before a license server needs to be installed and activated.

Installing the Remote Desktop Services License Server

The first step is to install the Remote Desktop Services License Services server role. The license server does not necessarily have to be installed on a system which is acting as a Remote Desktop Server. The installation can be performed using by selecting Roles from the tree in the left hand panel of the Server Manager tool.

If the server is already configured with the Remote Desktop Services role, scroll down the Roles summary page to the Remote Desktop Services section click on the Add Role Services link. In the resulting dialog titled Select Role Services select the check box next to Remote Desktop Licensing and then click Next to proceed to the Configure discovery scope for RD licensing screen as illustrated in the following figure:

In the first version of Windows Server 2008, it was necessary to specify a method by which RD Session Host servers (or Terminal Servers as they were known then) would auto-detect the server running the licensing server. With Windows Server 2008 R2, this approach is discouraged, and Microsoft now recommends that each RD Session Host be manually configured with information about the license server. In keeping with this recommendation, leave the Configure a discovery scope for this license server option unselected. Note, however, that this setting may be changed at a later time if required via the RD Licensing Manager tool. Click Next to proceed to the confirmation screen.

On a server which is does not have the Remote Desktop Services role installed, open the Server Manager, select Roles from the tree in the left hand panel and select Add Roles. Click Next on the initial screen if it appears so that the Select Server Roles screen is displayed. From the list of roles select the check box next to Remote Desktop Services and click on the Next button.

Read the information screen and then proceed to the Select Service Roles screen. Check the box next to Remote Desktop Licensing, click Next and follow the steps outlined above.

On the confirmation screen, verify that the information matches your expectations and click Install to initiate the installation process.

Activating the RD License Server

Once the RD License Server has been installed the next task is to activate it. This task is performed using the RD Licensing Manager which may be launched via Start -> All Programs -> Administrative Tools -> Remote Desktop Services -> Remote Desktop Licensing Manager. Once started, the Remote Desktop Licensing Manager dialog will appear containing a list of detected license servers on the network. The only license server listed in the following figure is the one on the local server. Because this has yet to be activated it is listed with a red circle containing an X mark next to it:

https://activate.microsoft.com web site using a browser and enter the product ID. Alternatively, if an internet connection is not available or a firewall prevents such access the activation may be performed over the telephone. If Automatic connection is selected, the following dialog will appear as the wizard attempts to contact Microsoft:

Once the Microsoft activation server has been located a new dialog will appear prompting for user, company and geographic location information. Complete these details and click Next to proceed. The second screen requests more detailed, but optional information. Either complete this information or click Next to skip to the activation process. Once again the wizard will contact Microsoft and complete the activation. Once completed, the following completion screen will appear:

Note that the Start Install Licenses Wizard now check box is selected by default. If you are ready to begin installing Client Access Licenses (CALs) now click on Next.

Installing Client Access Licenses (CAL)

A Client Access License (CAL) is required for each client requiring access to Windows Server 2008 R2 Remote Desktop Services. Once an RD License Server has been installed and activated the next step is to install the CALs. This can be performed as a continuation of the RD License Server activation process as outlined above, or at any other time by opening the RD Licensing Manager, right clicking on the appropriate license server in the list and choosing Install Licenses from the popup menu.

Once the Install Licenses wizard has started, click Next on the welcome screen to select the type of license program being used. Select the appropriate license type from the drop down list depending on how the licenses were acquired and then click Next to enter the license codes. On the License Program screen enter each code and press the Add button:

Select the license program corresponding to your license and click next to proceed to the License Code screen:

Enter each license key into this screen followed by the Add button. Once all the license codes have been added click on the Next button to complete the license installation process.

Configuring Licensing Settings on RD Session Hosts

Assuming that you followed Microsoft’s recommendation to manually configure the license server information for each RD Session Host it will now be necessary to perform this task. On each RD Session Host invoke the Remote Desktop Session Host Configuration tool by selecting the Start -> All Programs -> Remote Desktop Services -> Remote Desktop Session Host Configuration menu option. Within this tool, double click on the Remote Desktop licensing mode entry located in the Edit settings box listed under Licensing. In the resulting Licensing tab of the properties dialog select the appropriate licensing mode (per device or per user). Having defined the licensing mode, the next task is to specify the licensing server. Beneath the mode selection area, click on the Add… button to display the Add License Server dialog as illustrated in the following figure:

All known license servers will be listed in the left hand box. If the required servers are listed, select them and add them to the list of specified servers by clicking on the Add> button. If a server is not listed, manually type the name or IP address of the server in the text box provided and click the corresponding Add> button. Once all the required servers have been specified, click the OK button to commit the changes and dismiss the dialog.

Diskpart tool is excellent way to do this task. If you don’t have Diskpart, you can download it here.

Format the thumb drive

1. from a DOS prompt execute: diskpart
2. list disk
3. select disk 1 (assuming disk 1 was your thumb drive in the above list disk command)
4. clean
5. create partition primary
6. select partition 1
7. active
8. format fs=fat32
9. assign
10. exit

Copy the Win2008 install files

1. xcopy d:\*.* /s/e/f e:\ (assumes your dvd is drive D: and your thumb drive is drive E:\, adjust accordingly)

control keymgr.dll

and click on “OK” to open the windows credential manager which allows you to manage and delete passwords saved in Windows.

This procedure works for Windows XP, Vista and Windows 7.

Standard Security alternative syntax
Server=myServerAddress;Database=myDataBase;User ID=myUsername;Password=myPassword;Trusted_Connection=False;

Trusted Connection
Data Source=myServerAddress;Initial Catalog=myDataBase;Integrated Security=SSPI;

Trusted Connection alternative syntax
Server=myServerAddress;Database=myDataBase;Trusted_Connection=True;

Connecting to an SQL Server instance
Server=myServerName\theInstanceName;Database=myDataBase;Trusted_Connection=True;

Trusted Connection from a CE device
Data Source=myServerAddress;Initial Catalog=myDataBase;Integrated Security=SSPI;User ID=myDomain\myUsername;Password=myPassword;

You can not do this using IIS7 GUI manager.

Instead of this use IIS7 console programme:

"C:\Windows\System32\inetsrv\appcmd.exe" set config "Default Web Site/sicer08" -section:system.webServer/staticContent /+"[fileExtension='.exe.config',mimeType='application/octet-stream']"

One more problem we expirienced on Windows 2008 Server 64-bit is that you can not see configuration files. They should be in C:\Windows\System32\inetsrv\Config\ but you can not see them using Windows Explorer, 32-bit application on 64-bit system so you need to find and install Microsoft IIS Admin Tool in order to manage these files (you will get one new icon in IIS7 Management Studio when you click on you IIS webserver and its name is Configuration Editor – you can edit then in Notepad – oh no…).

Just run these 4 command and restart IIS and application pools:

1) %windir%\system32\inetsrv\appcmd.exe set config -section:system.webServer/globalModules -[name='PasswordExpiryModule'].preCondition:bitness64

2) %windir%\system32\inetsrv\appcmd.exe add apppool -name:RpcAppPool -enable32BitAppOnWin64:false

3) %windir%\system32\inetsrv\appcmd.exe set app “Default Web Site/Rpc” -applicationPool:RpcAppPool

4) %windir%\system32\inetsrv\appcmd.exe set app “Default Web Site/RpcWithCert” -applicationPool:RpcAppPool

http://support.microsoft.com/kb/970259

taskkill /F /IM MyProgram.exe

If you host Silverlight 2.0 application in IIS you might find that the silverlight object is not loading. If that’s the case, first thing you should check is the MIME type list. By default, the Silverlight package extension *.xap is not included.

To resolve that, go to IIS Manager, properties of your web site and check the “Http Headers” tab.

Then click the MIME Types button. You should see a list as bellow.

If the .xap extension is not in the list then click New… and add the following entry:

Extension: .xap
MIME type: application/x-silverlight-app

Now, check your site. You should get the silverlight objects properly.

http://weblogs.asp.net/mschwarz/archive/2008/03/07/silverlight-2-not-working-on-production-web-server.aspx

Silverlight 2 not working on Production Web Server

http://learn.iis.net/page.aspx/262/silverlight/

Featured IIS 7.0 Web Hosting

Windows 2008/IIS 7.0 Hosting is Here!

• Starting at $10/mo
• Windows 2008 Servers w/ IIS7
• Access to Microsoft IIS7 Manager
• Trust Level Control
• Pipeline Mode Selector Tool
• ASP.NET 3.5/2.0
• LINQ, AJAX, PHP5

Get 3 Months Free of IIS 7 Hosting Now

advertise here

Introduction

Microsoft® Silverlight^TM is a cross-browser, cross-platform plug-in for delivering the next generation of .NET based media experiences and rich interactive applications for the Web. Silverlight offers a flexible programming model that supports AJAX, VB, C#, Python, and Ruby, and integrates with existing Web applications. Silverlight supports fast, cost-effective delivery of high-quality video to all major browsers running on the Mac OS or Windows.

In most cases, hosters do not need to perform particular deployments to support Silverlight. However, check for the following basic items that could prevent Silverlight from functioning correctly.

MIME Types

In Windows Server 2008 IIS 7.0

All MIME types needed to support Silverlight are implemented by default in Windows Server 2008 IIS 7.0 and Windows Vista SP1.  Windows Vista RTM customers can add mime types by running “IIS Manager”, clicking on “Mime Types”, then clicking “add” and adding the following mime types:

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

Alternatively, you can add the following mime types to your %windir%\system32\inetsrv\config\applicationHost.config file in the <staticContent> section.

<mimeMap fileExtension=”.xaml” mimeType=”application/xaml+xml” />
<mimeMap fileExtension=”.xap” mimeType=”application/x-silverlight-app” />
<mimeMap fileExtension=”.xbap” mimeType=”application/x-ms-xbap” />

In Windows Server 2003 IIS 6.0

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

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

Using the IIS Manager User Interface in Windows Server 2003 IIS 6.0

1. Go to Start\Administrative Tools and run IIS Manager, see figure below:

2. Right click on the server name and select “Properties”, see figure below:

3. In the Properties Dialog, click on the “MIME Types” button, see figure below:

4. In the “MIME Types” Dialog, click the “New” button, see figure below:

5. In the “MIME Type” Dialog enter one MIME Type at the time:

You do not have permission to view this directory or page due to the access control list (ACL) that is configured for this resource on the Web server.

Then you should enable on Windows Server 2008 following rights:
Everyone group (or anonymous access account explicitly) should have Read permission to this  ‘folder’