Eternal NetworX EnX Blog

Consider the following scenario:

• You install Internet Information Services (IIS) 7.5 on a computer that is running Windows Vista, Windows 7, Windows Server 2008, or Windows Server 2008 R2.
• You host some Portable Document Format (PDF) documents on an IIS Web site on this computer.
• You have a client computer that has the Adobe PDF Reader plug-in enabled on a Web browser.
• You use this Web browser to open one of the PDF documents that is hosted on the IIS Web site.

In this scenario, you cannot open the PDF document. Additionally, the Web browser may stop responding.
Note

• You may still be able to open other PDF documents on this IIS Web site when this issue occurs.
• This issue does not affect all versions of the Adobe PDF Reader plug-in.

CAUSE

This issue occurs because of a design change in IIS 7.5. When you try to open a…

This issue occurs because of a design change in IIS 7.5.
When you try to open a PDF document on an IIS Web site, the Adobe PDF Reader plug-in sends a request that includes multiple byte ranges to IIS 7.5. If the union of the multiple byte ranges is a single byte range, the response from IIS 7.5 contains the byte ranges merged into a single byte range (also known as a merged byte-range request). The response to this single byte range does not include the multipart/byteranges content type. However, the multipart/byteranges content type is expected to be included in a response to a merged byte-range request. This behavior causes the Adobe PDF Reader plug-in to handle the response incorrectly. Therefore, the PDF document cannot be opened.
Note The multipart/byteranges content type is included in a regular multiple byte-ranges response.

RESOLUTION

To resolve this issue, apply this hotfix on the computer that is running IIS 7.5…

To resolve this issue, apply this hotfix on the computer that is running IIS 7.5.

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.
If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support (http://support.microsoft.com/contactus/?ws=support)

Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

To apply this hotfix, you must be running Windows Vista, Windows 7, Windows Server 2008, or Windows Server 2008 R2.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

To make this easier for everyone, you can download the hotfix here:

KB Article Number(s): 979543
Language: All (Global)
Platform: x64
Location: (http://hotfixv4.microsoft.com/Windows%207/WindowsServer%202008%20R2/sp1/Fix311271/7600/free/408888_intl_x64_zip.exe)
Password: qmFj]I4

How to Enable Concurrent Sessions for Remote Desktop in Windows 7 RTM

How to Enable Concurrent Sessions for Windows 7 RTM

1. Download Concurrent Sessions enabler file

2. Once downloaded, extract the files into a directory (for the purposes of this guide, it will be assumed that the files have been extracted to the folder C:\Win7RDP )

3. Open Windows Explorer to the above folder

4. Right Click on “install.cmd” and select “Run as Administrator”

5. Wait for the script to run entirely. At the end, you should see something similar to the below…

That’s it.

PINGBACK – http://www.blogsdna.com/4560/how-to-enable-concurrent-sessions-for-remote-desktop-in-windows-7-rtm.htm

UPDATE TO THIS POST:

Baydon Rowe has create a nice little script to make these changes for you!

Download now

Kudos to Baydon for the hard work! You can visit his .NET blog here.

-     –     –     –     –     –     –     –     –     –     –     –     –     –     –     –     –     –     –     –     –     –     –     –    -     –     -

I find many a times, from lack of knowledge, or lavishness, people don’t configure their domain’s correctly. I’m currently repairing a DC for issues that we’re easily avoidable.

One of the things you should configure is your Time Source on your Domain Controller holding the PDC emulator FSMO role.

Here’s how to do it.

Configuring the Windows Time service to use an external time source

To configure an internal time server to synchronize with an external time source, follow these steps:

1. Change the server type to NTP. To do this, follow these steps:
   1. Click Start, click Run, type regedit, and then click OK.
   2. Locate and then click the following registry subkey:HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Parameters\Type
   3. In the right pane, right-click Type, and then click Modify.
   4. In Edit Value, type NTP in the Value data box, and then click OK.
2. Set AnnounceFlags to 5. To do this, follow these steps:
   1. Locate and then click the following registry subkey:HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Config\AnnounceFlags
   2. In the right pane, right-click AnnounceFlags, and then click Modify.
   3. In Edit DWORD Value, type 5 in the Value data box, and then click OK.
3. Enable NTPServer. To do this, follow these steps:
   1. Locate and then click the following registry subkey:HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\TimeProviders\NtpServer
   2. In the right pane, right-click Enabled, and then click Modify.
   3. In Edit DWORD Value, type 1 in the Value data box, and then click OK.
4. Specify the time sources. To do this, follow these steps:
   1. Locate and then click the following registry subkey:HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Parameters
   2. In the right pane, right-click NtpServer, and then click Modify.
   3. In Edit Value, type Peers in the Value data box, and then click OK.
      Note Peers is a placeholder for a space-delimited list of peers from which your computer obtains time stamps. Each DNS name that is listed must be unique. You must append ,0×1 to the end of each DNS name. If you do not append ,0×1 to the end of each DNS name, the changes made in step 5 will not take effect.
5. Select the poll interval. To do this, follow these steps:
   1. Locate and then click the following registry subkey:HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\TimeProviders\NtpClient\SpecialPollInterval
   2. In the right pane, right-click SpecialPollInterval, and then click Modify.
   3. In Edit DWORD Value, type TimeInSeconds in the Value data box, and then click OK.
      Note TimeInSeconds is a placeholder for the number of seconds that you want between each poll. A recommended value is 900 Decimal. This value configures the Time Server to poll every 15 minutes.
6. Configure the time correction settings. To do this, follow these steps:
   1. Locate and then click the following registry subkey:HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Config\MaxPosPhaseCorrection
   2. In the right pane, right-click MaxPosPhaseCorrection, and then click Modify.
   3. In Edit DWORD Value, click to select Decimal in the Base box.
   4. In Edit DWORD Value, type TimeInSeconds in the Value data box, and then click OK.
      Note TimeInSeconds is a placeholder for a reasonable value, such as 1 hour (3600) or 30 minutes (1800). The value that you select will depend upon the poll interval, network condition, and external time source.
   5. Locate and then click the following registry subkey: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Config\MaxNegPhaseCorrection
   6. In the right pane, right-click MaxNegPhaseCorrection, and then click Modify.
   7. In Edit DWORD Value, click to select Decimal in the Base box.
   8. In Edit DWORD Value, type TimeInSeconds in the Value data box, and then click OK.
      Note TimeInSeconds is a placeholder for a reasonable value, such as 1 hour (3600) or 30 minutes (1800). The value that you select will depend upon the poll interval, network condition, and external time source.
7. Quit Registry Editor.
8. At the command prompt, type the following command to restart the Windows Time service, and then press ENTER:net stop w32time && net start w32time

After you finish restarting the w32time service, check your system event log for the following two Information Logs for the w32Time Service.

1.The time service is now synchronizing the system time with the time source VM IC Time Synchronization Provider.

2.The time provider NtpClient is currently receiving valid time data from time.windows.com (ntp.m|0×1|10.0.0.67:123->207.46.197.32:123).

A simple vb script to create 500 test users.

You must configure your domain info, and how many users you would like to create

dim strUser
Dim objRootLDAP, objContainer, objNewUser, objGroup

set objRootLDAP = GetObject("LDAP://rootDSE")
set objContainer = GetObject("LDAP://cn=Users," & _
   objRootLDAP.Get("defaultNamingContext"))

set objGroup = GetObject(LDAP://CN=Users,DC=DOMAIN,DC=COM)

‘Modify number of users to create
for i = 01 to 500

  strUser = "USER NAME" & i
  set ObjNewUser = objContainer.Create("User", "cn=" & strUser)
  objNewUser.Put "sAMAccountName", strUser
  objNewUser.Put "cn", strUser
  objNewUser.Put "givenName", strUser
  objNewUser.Put "displayName", strUser
  objNewUser.Put "userPrincipalName", strUser & "@FQDN"
  objNewUser.SetInfo

  objNewUser.SetPassword("PASSWORD")
  objNewUser.AccountDisabled = FALSE
  objNewUser.SetInfo
  objNewUser = null

Next

.csharpcode, .csharpcode pre
{
font-size: small;
color: black;
font-family: consolas, “Courier New”, courier, monospace;
background-color: #ffffff;
/*white-space: pre;*/
}
.csharpcode pre { margin: 0em; }
.csharpcode .rem { color: #008000; }
.csharpcode .kwrd { color: #0000ff; }
.csharpcode .str { color: #006080; }
.csharpcode .op { color: #0000c0; }
.csharpcode .preproc { color: #cc6633; }
.csharpcode .asp { background-color: #ffff00; }
.csharpcode .html { color: #800000; }
.csharpcode .attr { color: #ff0000; }
.csharpcode .alt
{
background-color: #f4f4f4;
width: 100%;
margin: 0em;
}
.csharpcode .lnum { color: #606060; }

There’s a lot to think about before installing Exchange 2010 with the typical installation (one server). I figured I would post while building one out myself in a virtualized environment.

Starting with a Windows Server 2008 R2 x64 base operating system install configured with the following: (all configured within Hyper-V)

• Quad Xeon Processor (additional cores added)
• 8GB Memory
• 600GB Hard Disk (IDE)
• 1 Network Adapter (configured in the OS with static IP address)
• 

Pre-Requisites

Update your Active Directory Schema:

On the Exchange Server, in PowerShell (run as administrator), run the following command

ServerManagerCmd -i RSAT-ADDS

reboot after installation is complete.

Next lets RUN: services.msc, and the Net.TCP Port Sharing Service, open

Change to the following values (start up type to Automatic)

When you apply this setting, you will have the option to start the service, click start.

Install IIS:

Use the server manager to perform a default installation of IIS 7 or 7.5

Error:
Unable to read data from the Metabase. Ensure that Microsoft Internet Information Services is installed.
Recommended Action: http://go.microsoft.com/fwlink/?linkid=30939&l=en&v=ExBPA.4&id=a4a4d339-4009-4fb7-b842-ca2ba79f13f0

Error:
The World Wide Web (W3SVC) service is either disabled or not installed on this computer. You must exit Setup, install the required component, then restart the Setup process.
Recommended Action: http://go.microsoft.com/fwlink/?linkid=30939&l=en&v=ExBPA.4&id=9eeaa77f-4d46-4d9a-9c36-f262a075392b

Error:
Unable to read data from the Metabase. Ensure that Microsoft Internet Information Services is installed.
Recommended Action: http://go.microsoft.com/fwlink/?linkid=30939&l=en&v=ExBPA.4&id=a4a4d339-4009-4fb7-b842-ca2ba79f13f0

Error:
The World Wide Web (W3SVC) service is either disabled or not installed on this computer. You must exit Setup, install the required component, then restart the Setup process.
Recommended Action: http://go.microsoft.com/fwlink/?linkid=30939&l=en&v=ExBPA.4&id=9eeaa77f-4d46-4d9a-9c36-f262a075392b

Download and Install 2007 Office System Converter

Warning:
This computer requires the 2007 Office System Converter: Microsoft Filter Pack. Please install the software from http://go.microsoft.com/fwlink/?LinkId=123380.

Once you have all of this complete, lets move on to the installation!

Be-aware that the top exclamation mark is indicating that:

Warning:
Setup is going to prepare the organization for Exchange 2010 by using ‘Setup /PrepareAD’. No Exchange 2007 server roles have been detected in this topology. After this operation, you will not be able to install any Exchange 2007 server roles.

Your finished the basic installation for Exchange Server 2010