• 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 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

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; }

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

Introduction

To start off, I built a Hyper-V virtual image of Windows Server 2008 R2 Standard server with the following hardware configuration:

• 6GB Memory
• 4 cores
• 127GB VHD
• 1 Network Adapter

After installing and updating Windows, I installed the .NET 3.5 SP1 framework, and installed the Web Services roles required.

Preparation Tool

The SharePoint 2010 Preparation Tool checks for the following

• Application Server Role, Web Server (IIS) Role
• Microsoft SQL Server 2008 Native Client
• Microsoft "Geneva" Framework Runtime
• Microsoft Sync Framework Runtime v1.0 (x64)
• Microsoft Chart Controls for Microsoft .NET Framework 3.5
• Microsoft Filter Pack 2.0
• Microsoft SQL Server 2008 Analysis Services ADOMD.NET

Installing

Use your own product key, your not getting mine

For my example I will choose.. the standalone option

click yes

SharePoint is now creating and configuring the database, configuring features, adding sample data and so forth.

My Installation said that it had failed, however all features within SharePoint seem to be working correctly.

On Wednesday Microsoft released their new Anti Virus solution. It is free, and looks like a great product. I myself will be installing it this evening, and updating this post with some comments on performance, and real time scanning.

Here is the link!

http://www.microsoft.com/Security_essentials/

Her post on http://www.vistax64.com/vista-networking-sharing/166833-problem-remoting-vista-enterprise-system.html 

In Remote Desktop Connection 6.0, server authentication verifies that you
are connecting to the correct remote computer or server, which may lead to
some incompatibility issue.
So, could you confirm if you use Remote Desktop Connection 6.0 client to
connect Vista?
Before Vista, Remote Desktop Connection 6.0 has been included in the
following OS:
Microsoft Windows Server 2003 with Service Pack 1 (SP1)
Microsoft Windows Server 2003 with Service Pack 2 (SP2)
Microsoft Windows XP with Service Pack 2 (SP2)
If so, please edit Default.rdp file as following steps to turn off the new
features in Remote Desktop Connection 6.0 to revert to the features in
Remote Desktop Connection 5.x.

To do this, follow these steps:
1. Click Start, click Run, type mstsc.exe, and then click OK.
2. Click Options, and then click the General tab.
3. Click Save As, and then type a file name in the File name box.
4. Select the location where you want to save the remote desktop file,
click Save, and then click Cancel.
Note The saved file has the .rdp file name extension.
5. Click Start, click Run, type notepad, and then click OK.
6. On the File menu, click Open.
7. In the Files of type list, click All Files.
8. In the Look in list, locate and then click the file that you saved in
step 4. Then, click Open.
9. Locate the line that resembles the following:
authentication level:i:n
Note The n placeholder represents the current authentication level.
10. Change the authentication level to 0 so that the line becomes the
following:
authentication level:i:0
Note When you set the authentication level to 0, RDP 6.0 does not check for
server authentication.
11. Add the following line to the end of the file:
enablecredsspsupport:i:0
Note When this line is present, you do not have to provide credentials
before you establish a remote desktop connection.
12. On the File menu, click Save.

More information, please see:
Remote Desktop Connection 6.0 prompts you for credentials before you
establish a remote desktop connection
http://support.microsoft.com/kb/941641
In addition, please also install hotfixs for Remote Desktop Connection 6.0
client, which can be achieved from:
Remote Desktop Connection 6.0
http://technet2.microsoft.com/window…-7038-4e82-a32
c-4bc10ffe56ab1033.mspx?mfr=true

To fix this annoyance is really easy.

EXAMPLE: Windows Live Messenger taskbar icon

1. If you have Windows Live Messenger running, close all conversations and exit Windows Live Messenger.
2. Browse to the Windows Live Messenger folder; they will be in different locations, depending on which version OS you are running.

x86 System (32bit) C:\Program Files\Windows Live\Messenger\msnmsgr.exe

x64 System C:\Program Files (x86)\Windows Live\Messenger\msnmsgr.exe
3. Right click on the msnmsgr.exe file, and go to "Properties"

4. Next, click the "Compatibility" tab shown in the image below.

5. Click "Run this program in compatibility mode for:" Windows Vista (any option other than Windows 7 works fine)

5. Click on OK.
6. Open Windows Live Messenger to see it’s icon location now. (Messenger may seem to be installing something, don’t freak, everything is fine.

Enjoy using messenger the way it was meant to be!

Something Microsoft has always been lacking in vs Mac and Linux OS has been theme’s, and appearance.

Although this isn’t really a big deal, and ad’s no real functionality, it is a very nice visual enhancement, and if your on your PC all day, it’s nice to switch it up every now and again.

With the launch of Windows 7 due shortly, I’ve been using RCO for quite some time now, and just stumbled across this today. Great themes, and the greatest thing is that most of them come with multiple desktop backgrounds that are very appealing, and automatically change (to a time you can set, default 15 minutes)

I find it really enjoyable, and figured I’d share it with you all!.

You can visit the page here.

http://windows.microsoft.com/en-US/windows7/downloads/personalize?T1=tab01

It has a tremendous amount of other useful tools that I haven’t played with yet, but if they work any bit as good as the “Transform – Transparent” feature I’m sold!

Props to iaza.. Great tool guys!

Automating IIS7 backups with vbs script.

Dim fileName
Dim WSHNetwork
Dim shareName: shareName = WScript.Arguments(0)
Dim xmldom : set xmldom = CreateObject("Msxml2.DOMDocument")
Dim fpc : set fpc = WScript.CreateObject("Fpc.Root")
Dim array : set array = fpc.GetContainingArray
set WSHNetwork = CreateObject("WScript.Network")
fileName=shareName & "\ISA Config – " & WSHNetwork.ComputerName & " – " & _
Year(Now) & "-" & Month(Now) & "-" & Day(Now) & ".xml"
array.Export xmldom, 0
xmldom.save(fileName)

copy above script into notepad, save the file as filename.vbs

The solution my friend is "DiskPart".

Open a command prompt window (start –> run –> type in the run window cmd

In the command prompt type "diskpart"
Type "list volume"
this will list all the drives on your computer and give them all volume numbers.
Next you want diskpart to set focus on the write protected drive "select volume #" which ever volume is the disk in question.
Now enter "attributes disk clear readonly" and then type "attributes volume clear readonly"

Check the drive in question, you should now be able to access the disk with full permissions. Hope this helps.

wevtutil.exe qe System /q:"*[System[Provider[@Name='Microsoft-Windows-Hyper-V-Hypervisor'] and (Level=2)]]" /rd:true /f:text /c:5

Example output of a system with NX not running:

Event[0]:
  Log Name: System
  Source: Microsoft-Windows-Hyper-V-Hypervisor
  Date: 2009-05-20T19:19:24.891
  Event ID: 52
  Task: N/A
  Level: Error
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: uhura
  Description: Hyper-V launch failed; No-execute (NX) or DEP not enabled on processor 0×0 (check BIOS settings).

For the Guest operating system I will be using the Windows 7 RC0 released on TechNet early last week. The guest is configured with 2GB of memory, 1 network adapter connected to my local network. The processor is configured to use 4 core’s, and the VHD file is living on the Hosts C:\ drive.

Here are some screen shots during the installation.. I will explain the performance and usability I received while demoing Windows 7 Ultimate.

at this point it hung for about 9 minutes on “Preparing your desktop” (not sure if it’s maybe doing the performance testing at Vista does?

Although the Operating System is getting closer to release, I fail to see any major improvements. I will continue my investigation by using it on my desktop where I will be doing everything from photo editing in Photoshop, web design in expressions, heavy office and RSAT usage. A follow up post to come.

By default, when you open My Computer, the drive-letter for the disk drives appear after the drive description, such as:

" Local Disk (C:) "

Display the drive-letters first

To display drive-letters first, followed by the drive description, use these steps:

· Click Start, Run and type Regedit.exe

· Navigate to the following location:

HKEY_LOCAL_MACHINE \ SOFTWARE \ Microsoft \ Windows \ CurrentVersion \ Explorer

· If not already exists, create a REG_DWORD value named ShowDriveLettersFirst

· Double-click ShowDriveLettersFirst and set its Value data to 4

· Exit the Registry Editor.

Here are the other possible data for ShowDriveLettersFirst registry value:

Value Data	Description
0	Show drive letters after description (default)
1	Show network drive letters before description, and local drive letters after description
2	No drive letter is displayed
4	Show drive letters before description

]]> http://blog.eternalnetworx.com/2009/04/07/my-computer-show-drive-letters-first/feed/ 0 Mark Torng http://blog.eternalnetworx.com/2009/02/10/iis7-will-not-re-install/ http://blog.eternalnetworx.com/2009/02/10/iis7-will-not-re-install/#comments Tue, 10 Feb 2009 20:33:03 +0000 Mark http://marktorng.wordpress.com/2009/02/10/iis7-will-not-re-install/ ]]>  

Got this error when I tried to install IIS7 on a 2008 x64 Standard web server using NLB in a Hyper-V image.

The work around is to uninstall “Windows Process Activation Service” located under features.

Reboot, Then try to install IIS7 again. Worked for me

Web Server (IIS)

<Informational>: <a href="wsrm.chm::/html/c5b76d56-99b1-4ad7-875c-417b63118454.htm">Find out more about Windows System Resource Manager (WSRM) and how it can help optimize CPU usage</a>

Web Server

Common HTTP Features

Static Content

Default Document

Directory Browsing

HTTP Errors

Application Development

ASP.NET

.NET Extensibility

ASP

CGI

ISAPI Extensions

ISAPI Filters

Server Side Includes

Health and Diagnostics

HTTP Logging

Request Monitor

Security

Request Filtering

Performance

Static Content Compression

Web Server (IIS): Installation failed

<Error>: Attempt to install Request Filtering failed with error code 0×80070643. Fatal error during installation

<Error>: Attempt to install Request Monitor failed with error code 0×80070643. Fatal error during installation

<Error>: Attempt to install ISAPI Filters failed with error code 0×80070643. Fatal error during installation

<Error>: Attempt to install ISAPI Extensions failed with error code 0×80070643. Fatal error during installation

<Error>: Attempt to install HTTP Logging failed with error code 0×80070643. Fatal error during installation

<Error>: Attempt to install Server Side Includes failed with error code 0×80070643. Fatal error during installation

<Error>: Attempt to install Directory Browsing failed with error code 0×80070643. Fatal error during installation

<Error>: Attempt to install Default Document failed with error code 0×80070643. Fatal error during installation

<Error>: Attempt to install Static Content failed with error code 0×80070643. Fatal error during installation

<Error>: Attempt to install Static Content Compression failed with error code 0×80070643. Fatal error during installation

<Error>: Attempt to install CGI failed with error code 0×80070643. Fatal error during installation

<Error>: Attempt to install HTTP Errors failed with error code 0×80070643. Fatal error during installation

<Error>: Attempt to install .NET Extensibility failed with error code 0×80070643. Fatal error during installation

<Error>: Attempt to install ASP failed with error code 0×80070643. Fatal error during installation

<Error>: Attempt to install ASP.NET failed with error code 0×80070643. Fatal error during installation

The following role services were not installed:

Web Server

Common HTTP Features

Static Content

Default Document

Directory Browsing

HTTP Errors

Application Development

ASP.NET

.NET Extensibility

ASP

CGI

ISAPI Extensions

ISAPI Filters

Server Side Includes

Health and Diagnostics

HTTP Logging

Request Monitor

Security

Request Filtering

Performance

Static Content Compression

Full log (for troubleshooting only)

Eternal Photography has posted a new websites hosted on our servers

www.eternalphotography.ca

annualadawards.com

calgariesweddingphotography.com

calgaryweddingphotographyonline.com

calgarywedphotography.com

blog.eternalphotography.ca

eternalphotos.ca

Easy.. go to this site, follow the instructions, and don’t worry.. be happy

http://www.xml-sitemaps.com

HELM restore tool uses HELM’s database to handle DNS zones. So if you have any zone settings outside HELM, my experience might come handy.

This is for MSDNS only.

1.) I always setup MSDNS to use files, not registry, because files are much easier to migrate and make backup.
To set MSDNS to use DNS zone files only, right click you server in DNS console, select Properties -> Advanced and set "Load zone data on startup" = From File
Then restart DNS
2.) If you want to setup your new SECONDARY DNS, this script might come handy. It scans your primary DNS and copies all zones to secondary DNS server. It also secures zone transfer settings to allow transfers only to servers, listed in NS tab, with automatic notify option, so secondary’s are updated almost in real time.

Script copyToSecondary.bat

Code:

@echo off
SET DNSCMDPATH="C:\Program Files\WebHost Automation\Helm\System\dnscmd.exe"
echo.
echo ###############################################################################
echo #                                                                             #
echo #                        MSDNS copy zone utility                              #
echo #                  Copyright 2006 Labsy @ seznam DOT org                      #
echo #                                                                             #
echo ###############################################################################
echo.

IF NOT EXIST %DNSCMDPATH% (
ECHO ERROR: dnscmd.exe not found in given path:
echo %DNSCMDPATH%
echo.
echo Please, install Windows Server Admin pack or get dnscmd.exe elsewhere
echo and update DNSCMDPATH in this script accordingly.
echo.
)
IF NOT "%1"=="/?" IF NOT "%1"=="/h" IF NOT "%1"=="?" GOTO skiphelp

echo This batch will copy PRIMARY DNS zones to SECONDARY server or repair primary.
echo It scans all PRIMARY FORWARD zones on this machine and then creates apropriate
echo SECONDARY zones on given secondary server.
echo.
echo This tool is very handy when setting up new secondary DNS servers.
echo.
echo IMPORTANT:
echo It works ONLY FOR MSDNS server!
echo You must have "dnscmd" utility installed. It is part of server admin pack.
echo Before first usage edit this file and set PATH to dnscmd in this script!
echo.
echo USAGE:
echo    copyToSecondary [SecName/IP] [SecDns] [PriIP] (optionally [DomainName])
echo    copyToSecondary [PriName/IP] updatemaster
echo where
echo    [SecName/IP] = Secondary Server NetBios Name or local IP (eg: ENGINE1)
echo    [SecDns]     = Secondary Server Dns Name (eg: ns1.domain.com)
echo    [PriIP]      = Primary DNS Server IP. This will be set as master DNS
echo    [DomainName] = Optional parameter, domain name for single zone transfer
echo.
echo    when used with "updatemaster" parameter
echo    [PriName/IP] = Primary DNS NEtBios name or IP
echo.
echo EXAMPLES:
echo To copy all zones from primary 123.123.123.123 to secondary SERVER5 (ns5):
echo.
echo    copyToSecondary SERVER5 ns5.domain.com 123.123.123.123
echo.
echo Same as above, but just for one particular domain:
echo.
echo    copyToSecondary SERVER5 ns5.domain.com 123.123.123.123 foobar.com
echo.
echo To update only master DNS and repair Zone transfer and notify settings:
echo (this will set AllowUpdate to servers listed in NS tab, and set to AutoNotify)
echo.
echo    copyToSecondary MASTER1 updatemaster
echo.
echo ###############################################################################
echo.
goto END
:skiphelp

echo IMPORTANT!
echo This script can modify your DNS server settings, so BE SURE you have BACKUP!
echo Press CTRL+C to stop and make BACKUP of your DNS zones first!
pause

IF NOT "%2"=="updatemaster" GOTO normal
if NOT "%1"=="" %DNSCMDPATH% %1 /EnumZones /Forward>allzones.txt
ECHO #----------------------------- PRIMARY UPDATE --------------------------------#
ECHO #                                  START                                      #
if NOT "%1"=="" FOR /f %%D IN (allzones.txt) DO (
IF NOT "%%D" == "Enumerated" IF NOT "%%D" == "Zone" IF NOT "%%D" == "." IF NOT "%%D" == "Command" (

ECHO  Updating master DNS for %%D ...
%DNSCMDPATH% %1 /ZoneResetSecondaries %%D /securens /notify
)
)
GOTO END
:normal
if NOT "%1"=="" %DNSCMDPATH% %1 /EnumZones /Forward>allzones.txt
if NOT "%4"=="" GOTO SINGLE
if NOT "%2"=="" FOR /f %%D IN (allzones.txt) DO (
IF NOT "%%D" == "Enumerated" IF NOT "%%D" == "Zone" IF NOT "%%D" == "." IF NOT "%%D" == "Command" (
ECHO #---------------------------- BULK ZONE UPDATE -------------------------------#
ECHO #                                 START                                       #

ECHO Processing zone %%D... 

ECHO  Adding %2 as DNS server on primary...
%DNSCMDPATH% %3 /RecordAdd %%D "@" NS %2

ECHO  Set Allow only secure zone transfers with autonotify on primary...
%DNSCMDPATH% %3 /ZoneResetSecondaries %%D /securens /notify

ECHO  Transfering zone %%D to %2...
%DNSCMDPATH% %1 /ZoneAdd %%D /Secondary %3 /file %%D.dns

ECHO #----------------------------------- END -------------------------------------#
)
)
GOTO END
REM C:\Program Files\WebHost Automation\Helm\System\dnscmd 81.29.69.137 /RecordAdd gradteater.com "@" NS ns5.hostmachine.net

:SINGLE
if "%4"=="" goto END
ECHO #---------------------------------- START ------------------------------------#
ECHO Processing zone %4...
ECHO Adding %2 as DNS server on primary...
%DNSCMDPATH% %3 /RecordAdd %4 "@" NS %2

ECHO  Set Allow only secure zone transfers with autonotify on primary...
%DNSCMDPATH% %3 /ZoneResetSecondaries %4 /securens /notify

ECHO Transfering zone %4 to %2...
%DNSCMDPATH% %1 /ZoneAdd %4 /Secondary %3 /file %4.dns

ECHO #----------------------------------- END -------------------------------------#

:END
SET DNSCMDPATH=
echo.

Requirements for this script to work:

- secondary DNS must run MSDNS server

- secondary DNS must be inside local network (either LAN, either via VPN)

- you must run this script with Admin user, which has Admin privileges on both, primary and secondary server (I run it as HELM_ADMIN)

Do not forget to make a BACKUP of your DNS zone files before you go playing with this script!

The sample searches for all the applicable software updates and then lists those updates. Next, it creates a collection of updates to download and then downloads them. Finally, it creates a collection of updates to install and then installs them.

If you want to search, download, and install a specific update that you identify by using the update title, see Searching, Downloading, and Installing Specific Updates.

Before you attempt to run this sample, note the following:

• WUA must be installed on the computer. For more information about how to determine the version of WUA that is installed, see Determining the Current Version of WUA.
• The sample does not provide its own user interface.
• WUA prompts the user to restart the computer if an update requires a restart.
• The sample can download updates only by using WUA. It cannot download updates from a Software Update Services (SUS) 1.0 server.
• Running this sample requires Windows Script Host (WSH). For more information about WSH, see the WSH section of the Microsoft Platform SDK. If the sample is copied to a file named WUA_SearchDownloadInstall.vbs, you can run the sample by opening a Command Prompt window and typing the following command at the command prompt.

Example code: (To execute us cscript WUA_SearchDownloadInstall.vbs, or whatever you name your VBS script)

Set updateSession = CreateObject(“Microsoft.Update.Session”)
Set updateSearcher = updateSession.CreateupdateSearcher()

WScript.Echo “Searching for updates…” & vbCRLF

Set searchResult = _
updateSearcher.Search(“IsInstalled=0 and Type=’Software’”)
WScript.Echo “List of applicable items on the machine:”

For I = 0 To searchResult.Updates.Count-1
    Set update = searchResult.Updates.Item(I)
    WScript.Echo I + 1 & “> ” & update.Title
Next

If searchResult.Updates.Count = 0 Then
 WScript.Echo “There are no applicable updates.”
 WScript.Quit
End If

WScript.Echo vbCRLF & “Creating collection of updates to download:”

Set updatesToDownload = CreateObject(“Microsoft.Update.UpdateColl”)

For I = 0 to searchResult.Updates.Count-1
    Set update = searchResult.Updates.Item(I)
    WScript.Echo I + 1 & “> adding: ” & update.Title
    updatesToDownload.Add(update)
Next

WScript.Echo vbCRLF & “Downloading updates…”

Set downloader = updateSession.CreateUpdateDownloader()
downloader.Updates = updatesToDownload
downloader.Download()

WScript.Echo  vbCRLF & “List of downloaded updates:”

For I = 0 To searchResult.Updates.Count-1
    Set update = searchResult.Updates.Item(I)
    If update.IsDownloaded Then
       WScript.Echo I + 1 & “> ” & update.Title
    End If
Next

Set updatesToInstall = CreateObject(“Microsoft.Update.UpdateColl”)

WScript.Echo  vbCRLF & _
“Creating collection of downloaded updates to install:”

For I = 0 To searchResult.Updates.Count-1
    set update = searchResult.Updates.Item(I)
    If update.IsDownloaded = true Then
       WScript.Echo I + 1 & “> adding:  ” & update.Title
       updatesToInstall.Add(update) 
    End If
Next

WScript.Echo  vbCRLF & “Would you like to install updates now? (Y/N)”
strInput = WScript.StdIn.Readline
WScript.Echo

If (strInput = “N” or strInput = “n”) Then
 WScript.Quit
ElseIf (strInput = “Y” or strInput = “y”) Then
 WScript.Echo “Installing updates…”
 Set installer = updateSession.CreateUpdateInstaller()
 installer.Updates = updatesToInstall
 Set installationResult = installer.Install()
 
 ’Output results of install
 WScript.Echo “Installation Result: ” & _
 installationResult.ResultCode
 WScript.Echo “Reboot Required: ” & _
 installationResult.RebootRequired & vbCRLF
 WScript.Echo “Listing of updates installed ” & _
  “and individual installation results:”
 
 For I = 0 to updatesToInstall.Count – 1
  WScript.Echo I + 1 & “> ” & _
  updatesToInstall.Item(i).Title & _
  ”: ” & installationResult.GetUpdateResult(i).ResultCode   
 Next
End If

Each Server node would randomly have a blue screen of death and reboot for no reason.

After much troubleshooting and searching I found that KB953828 resolves the issue.

http://support.microsoft.com/kb/953828/en-us

Microsoft Hyper-V Server 2008 R2 Beta Installation Prerequisites

Microsoft Hyper-V Server 2008 R2 Beta requires specific hardware. You can identify systems that support the x64 architecture and Hyper-V by searching the Windows Server® catalog for Hyper-V as an additional qualification. The Windows Server catalog is available on the Microsoft Web site (http://go.microsoft.com/fwlink/?LinkId=111228).

To install and use Microsoft Hyper-V Server 2008 R2 Beta, you need the following:

• An x64-based processor.
• Hardware-assisted virtualization. This is available in processors that include a virtualization option; specifically, Intel VT or AMD Virtualization (AMD-V).
• Hardware Data Execution Protection (DEP) must be available and be enabled. Specifically, you must enable the Intel XD bit (execute disable bit) or the AMD NX bit (no execute bit).

Additional considerations

• The settings for hardware-assisted virtualization and hardware data execution protection are available in the BIOS. However, the names of the settings may differ from the names identified previously.
  For more information about whether a specific processor model supports Microsoft Hyper-V Server 2008 Re Beta, check with the manufacturer of the computer.
• If you modify the settings for hardware-assisted virtualization or hardware data execution protection, you may need to turn off the power to the computer and then turn it back on. Restarting the computer may not apply the changes to the settings.

Setting the Administrator Password

During the first logon after the installation of Microsoft Hyper-V Server 2008 R2 Beta, you will be prompted to enter a user name and create a password.  The following instructions outline this process.

Note: This process will only occur during the first logon after the installation of Microsoft Hyper-V Server 2008 R2 Beta.

1.       Click on Other User.

2.       In the user name field type Administrator and then press ENTER.

3.       A message stating that “The user’s password must be changed before logging on the first time” appears. Click OK.

4.       Type a new password in the New password field.

5.       Type the same password again in the Confirm password field, and then press ENTER.

6.       You will see a confirmation that your password has been changed. Click OK.

Microsoft Hyper-V Server 2008 R2 Beta Configuration Tool

The Microsoft Hyper-V Server 2008 R2 Beta configuration tool is intended to support the administrator with a menu driven User Interface (UI) for configuration. The configuration tool starts automatically at login of the system administrator or it can be started manually.

To manually start the Microsoft Hyper-V Server 2008 R2 Beta configuration tool

1.       Change to the system drive.

2.       Type hvconfig.cmd and then press ENTER.

Figure 1: Microsoft Hyper-V Server 2008 R2 Beta Configuration Tool

Domain/Workgroup

The current Domain/Workgroup settings are displayed in the default Microsoft Hyper-V Server 2008 R2 Beta Configuration screen.

Computer Name

The current computer name is displayed in the default Microsoft Hyper-V 2008 R2 Beta Configuration screen.

Network Settings

Microsoft Hyper-V Server 2008 R2 Beta network settings can be assigned by a DHCP Server or an IP Address can be assigned manually.

1.       Type 3 and press ENTER to configure the server network settings.

2.       You will be presented with a list of available network adapters attached to your Microsoft Hyper-V Server.

3.       Type the Index# of the adapter you want to configure and press ENTER.

4.       You will be presented with the current configuration for the network adapter you selected.

5.       Type 1 and press ENTER to configure the IP address for the selected network adapter

6.       Type 4 and press ENTER to return to the default configuration page.

Add Local Administrator

Additional users can be added to the local administrators group on a Microsoft Hyper-V Server 2008 R2 Beta computer.

Windows Update Settings

The current Update settings are displayed in the default Microsoft Hyper-V Server 2008 R2 Beta Configuration screen.

Download and Install Updates

The current Update Status is displayed in the default Microsoft Hyper-V Server 2008 R2 Beta Configuration screen.

NOTE: You must be connected to the internet to receive Hyper-V Server updates.

7.       Type 6 and press ENTER to search for updates. 

Note: This may take some time.

Note: You may be prompted with “A restart is required to complete Windows Updates.  Restart now?” Click Yes to initiate a restart. By default, running virtual machines will automatically be saved prior to restarting the server.

1.       You will be returned to the Microsoft Hyper-V Server 2008 R2 Beta Configuration Tool and will see the current Hyper-V Update status next to “Download and Install Updates“.

Remote Desktop

The current Remote Desktop status is displayed in the default Microsoft Hyper-V Server 2008 R2 Beta Configuration screen.

Failover Clustering Role

The current Failover Cluster Role status is displayed in the default Microsoft Hyper-V Server 2008 R2 Beta Configuration screen.

Configure Remote Management

1.       Type 9 and press ENTER to configure the Microsoft Hyper-V Server 2008 R2 Beta remote management settings.

2.       Type 5 and press ENTER to return to the default configuration page.

Regional and Language Options

1.       Type 10 and press ENTER to configure or modify the Microsoft Hyper-V Server 2008 R2 Beta Regional and Language options.

2.       You will be presented with the Microsoft Hyper-V Server 2008 R2 Beta Regional and Language options dialog box.

3.       When you are finished configuring Regional and Language Options, click OK or Apply to commit the changes or Cancel to discard them.

Figure 2: Microsoft Hyper-V Server 2008 R2 Beta Regional and Language Options

Date and Time

1.       Type 11 and press ENTER to configure or modify the Microsoft Hyper-V Server 2008 R2 Beta Date and Time options.

2.       You will be presented with the Date and Time options dialog box.

3.       When you are finished configuring Date and Time options, click OK to commit the changes or Cancel to discard them.

Figure 3: Microsoft Hyper-V Server 2008 R2 Beta Date and Time Settings

Do not display this menu at login

1.       Type 12 and press ENTER to change the display options for the Microsoft Hyper-V Server 2008 R2 Beta Configuration menu.

2.       You will be prompted with “Disable the Microsoft Hyper-V Server 2008 R2 Beta Configuration menu from starting automatically at login?”

Log Off User

3.       Type 13 and press ENTER to log off the current user.

4.       You will be prompted with “Are you sure you want to log off?”

2.       Click Yes.

Restart Server

1.       Type 14 and press ENTER to restart the server.

2.       You will be prompted with “Are you sure you want to restart?”

3.       Click Yes.

NOTE: By default, running virtual machines will automatically be saved prior to restarting the server.

Shut Down Server

1.       Type 15 and press ENTER to shut down the server. 

2.       You will be prompted with “Are you sure you want to shut down?”

3.       Click Yes.

NOTE: By default, running virtual machines will automatically be saved prior to shutting down the server.

Exit to Command Line

1.       Type 16 and press ENTER to exit to the Command Line. 

NOTE: To return to the Microsoft Hyper-V Server 2008 R2 Beta Configuration Tool, type hvconfig and press ENTER.

Open a new Command Line window

1.       Press CTRL+Shift+ESC to open Task Manager

2.       In Task Manager click File -> New Task (Run) -> CMD.

Microsoft Hyper-V Server 2008 R2 Beta Remote Management

There are a few ways to remotely manage Microsoft Hyper-V Server 2008 R2 Beta:

·         Microsoft® Windows Server 2008 R2 Beta (full installation) with the Hyper-V Manager

·         Microsoft® System Center Virtual Machine Manager 2008

Choose which option is right for you and follow the corresponding steps below.

Microsoft Hyper-V Server 2008 R2 Beta Remote Management with Microsoft® Windows Server 2008 R2 Beta

To enable the Microsoft® Windows Server 2008 R2 Beta Hyper-V Manager MMC:

NOTE: The Hyper-V Manager MMC is automatically installed when the Hyper-V role is enabled on full installations of Windows Server 2008 R2 Beta.

1.       Launch Server Manager from the Start menu.

2.       Click Add Features.

3.       Under Remote Server Administration ToolsàRole Administration Toolsà

a.       Enable Hyper-V Tools and click Next.

4.       Click Install.

5.       After the reboot, go to Administrative Tools in the Start menu and click on the Hyper-V Manager.

6.       On the left side of the MMC window, click on Hyper-V Manager.

7.       From the Actions menu, click Connect to Server, select Another Computer and enter the name or IP address of the server you want to connect to.

Microsoft Hyper-V Server 2008 R2 Beta Remote Management with Microsoft® System Center Virtual Machine Manager

Currently, System Center Virtual Machine Manager 2008 does not provide support for managing Microsoft Hyper-V Server 2008 R2 Beta.  The System Center team is currently working to deliver an update to Virtual Machine Manager that will provide support for future versions of Microsoft Hyper-V Server 2008 R2.

Setup Microsoft Hyper-V Server 2008 R2 Beta virtual networks

Configure one or more virtual networks for virtual machines to access network resources.

Creating Microsoft Hyper-V Server 2008 R2 Beta Virtual Networks

From a system running Microsoft® Windows Server 2008, launch the Hyper-V Manager. 

1.       On the left side of the MMC window, click on Hyper-V Manager.

2.       From the Actions menu, click Connect to Server, select Another Computer and enter the name or IP address of the server you want to connect to.

3.       In the Actions menu click Virtual Network Manager…

4.       Under Create virtual network, select External and click Add.

5.       Type a name for the new virtual network, such as Corpnet and click OK.

NOTE: When you create a virtual network remotely, Microsoft Hyper-V Server 2008 R2 Beta creates the new virtual switch and binds it to the physical network TCP/IP stack. If the system is configured with only one physical network adapter, this may result in a dropped network connection. This is normal while the virtual network is being created.