Category: Microsoft

Microsoft Application Compatibility Toolkit (ACT)

The Microsoft Application Compatibility Toolkit (ACT) 5.5 is a free tool from Microsoft. It helps customers understand their application compatibility situation by identifying which applications are compatible with the Windows 7 RC and Windows Vista® operating system and which require further testing. ACT helps customers lower their costs for application compatibility testing, prioritize their applications, and deploy Windows more quickly. You can use the ACT features to:

  • Verify an application’s compatibility with a new version of the Windows operating system, or a Windows Update, including determining your risk assessment.
  • Become involved in the ACT Community, including sharing your risk assessment with other ACT users.
  • Test your Web applications and Web sites for compatibility with new releases and security updates to the Windows® Internet Explorer® Internet browser.

Software Requirements:

Type of Software Type of Software
Operating Systems – Windows 7
– Windows Vista
– Windows Vista with Service Pack 1 (SP1)
– Windows XP with Service Pack 2 (SP2) or Service
   Pack 3 (SP3)
– Windows Server 2003 with Service Pack 2 (SP2)
– Windows Server 2008 R2
Database Components – Microsoft SQL Server 2008
– Microsoft SQL Server 2005
– Microsoft SQL Server 2008 Express
– Microsoft SQL Server 2005 Express
.NET Framework – ACT requires the .NET Framework 2.0 or newer.

Download HERE
image

Free eBook! Understanding Microsoft Virtualization R2 Solutions

There is a second release from: Understanding Microsoft virtualization Solutions updated for Windows 2008 R2. 480 Pages.

The ultimate virtualization guide for IT professionals and decision makers.

Download Click on the Picture

image

Hyper-V Updates for Windows 2008 R2

Knowledge Base Article

Name

Date

Required?

KB974598

“You receive a "Stop 0x0000007E" error on the first restart after you enable Hyper-V on a Windows Server 2008 R2-based computer”

10/1/2009

Yes, if you encounter this error and your server uses a “C-state” (lower power state) that is supported by the processor, but is not supported by Hyper-V.

KB974909

“The network connection of a running Hyper-V virtual machine is lost under heavy outgoing network traffic on a Windows Server 2008 R2-based computer”

10/21/2009

No.

KB975354

“A Hyper-V update rollup package is available for a computer that is running Windows Server 2008 R2”

11/10/2009

Yes, if you are running a backup or restore solution.

KB975530

“Stop error message on an Intel Xeon 5500 series processor-based computer that is running Windows Server 2008 R2 and that has the Hyper-V role installed: "0x00000101 – CLOCK_WATCHDOG_TIMEOUT"

11/20/2009

Yes, if you are running Hyper-V on the affected hardware.

KB974672

“Virtual machines stop responding (hang) during startup and the Vmms.exe process crashes on a Windows Server 2008 R2 computer that has the Hyper-V role installed“

10/14/2009

No.

KB977894

“MS10-010: Vulnerability in Windows Server 2008 Hyper-V could allow denial of service”

2/9/2010

Yes.

KB980856

“Stop error in Windows Server 2008 R2: "0x000000CA PNP_DETECTED_FATAL_ERROR"”

3/12/2010

Yes, if you store VHDs on non-PNP disks.

KB981618

“The computer stops responding or restarts during the Hyper-V Live Migration process in Windows Server 2008 R2” (relates to AMD Errata 383)

3/27/2010

Yes, if you are running Hyper-V on AMD processors.

KB 981836

“Network connectivity for a Windows Server 2003-based Hyper-V virtual machine is lost temporarily in Windows Server 2008 R2”

4/28/2010

Yes, if the server running Hyper-V has a virtual machine that is running Windows Server 2003.

KB981791

“"STOP: 0x0000001a" error message on a computer that has an Intel Westmere processor together with the Hyper-V role installed on Windows Server 2008 or on Windows Server 2008 R2”

5/5/2010

Yes, if you are running Hyper-V on Intel Westmere processors.

Source: http://technet.microsoft.com/en-us/library/ff394763(WS.10).aspx

EBook: Introducing Microsoft SQL Server 2008 R2

Microsoft released SQL Server 2008 R2 to manufacturing (RTM). To promote this new version they have released a free ebook: Introducing Microsoft SQL Server 2008 R2.
To download the ebook just click on the picture.

image

Exchange 2010 Build Numbers

If you open de Exchange Management Shell and you run the following powershell command:
Get-ExchangeServer | fl name,edition,admindisplayversion you get the Build Number from your Exchange 2007 Servers

Exchange Server 2010

Product name

Build number

Microsoft Exchange Server 2010 RTM

14.0.639.21

Update Rollup 1 for Exchange Server 2010

14.0.682.1

Update Rollup 2 for Exchange Server 2010

14.0.689.0

Update Rollup 3 for Exchange Server 2010

14.0.694.0

Update Rollup 4 for Exchange Server 2010

14.0.702.1

Exchange Server 2010 SP1 

Product name

Build number

Microsoft Exchange Server 2010 SP1

14.1.218.15
   
   
   
   

Exchange 2007 Builds Numbers

If you open de Exchange Management Shell and you run the following powershell command:
Get-ExchangeServer | fl name,edition,admindisplayversion you get the Build Number from your Exchange 2007 Servers

Exchange 2007 RTM

Product name Build number
Exchange 2007 RTM 8.0.685.25
Update Rollup 1 for Exchange Server 2007 8.0.708.3
Update Rollup 2 for Exchange Server 2007 8.0.711.2
Update Rollup 3 for Exchange Server 2007 8.0.730.1
Update Rollup 4 for Exchange Server 2007 8.0.744.0
Update Rollup 5 for Exchange Server 2007 8.0.754.0
Update Rollup 6 for Exchange Server 2007 8.0.783.2
Update Rollup 7 for Exchange Server 2007 8.0.813.0

Exchange Server 2007 Service Pack 1

Product name Build Number
Microsoft Exchange Server Exchange 2007 SP1 8.1.240.6
Update Rollup 1 for Exchange Server 2007 Service Pack 1 8.1.263.1
Update Rollup 2 for Exchange Server 2007 Service Pack 1 8.1.278.2
Update Rollup 3 for Exchange Server 2007 Service Pack 1 8.1.291.2
Update Rollup 4 for Exchange Server 2007 Service Pack 1 8.1.311.3
Update Rollup 5 for Exchange Server 2007 Service Pack 1 8.1.336.1
Update Rollup 6 for Exchange Server 2007 Service Pack 1 8.1.340.1
Update Rollup 7 for Exchange Server 2007 Service Pack 1 8.1.359.2
Update Rollup 8 for Exchange Server 2007 Service Pack 1 8.1.375.2
Update Rollup 9 for Exchange Server 2007 Service Pack 1 8.1.393.1
Update Rollup 10 for Exchange Server 2007 Service Pack 1 8.1.436.0

Exchange Server 2007 Service Pack 2

Product name Build Number
Microsoft Exchange Server 2007 SP2 8.2.176.2
Update Rollup 1 for Exchange Server 2007 Service Pack 2 8.2.217.3
Update Rollup 2 for Exchange Server 2007 Service Pack 2 8.2.234.1
Update Rollup 3 for Exchange Server 2007 Service Pack 2 8.2.247.2
Update Rollup 4 for Exchange Server 2007 Service Pack 2 8.2.254.0

Exchange Server 2007 Service Pack 3

Product name Build Number
Microsoft Exchange Server 2007 SP3 83.6

Restore an Windows 7 Capture with MDT 2010

Step1: Import the Capture Image.

You can find the capture file at  \\server\deploymentshare$\Capture or x:\deploymentshare\capture.

image image
If you have already imported Windows 7 DVD.
You can chose for Sysprep and Setup files are not needed. The Setup will copy them automatically when de Capture wil be deployed. 
image image
image  image

Step 2. Create a Normal Client Task with the OS Capture that you imported.

Capture an Existing Windows 7 install with MDT

You can With MDT capture an existing Windows 7 Install.
1. Creating the Task in MDT
2010-04-18_134159 2010-04-18_134127
Jou must Chose the OS version witch you want to capture.

2010-04-18_134151 2010-04-18_134213
2010-04-18_134231 2010-04-18_134317
2010-04-18_134327 2010-04-18_134336

2. Create a copy from the Customsettings.ini
    Edit the Customsettings.ini with de following text.

[Settings]
Priority=Default
Properties=MyCustomProperty

[Default]
OSInstall=Y
SkipAppsOnUpgrade=YES
SkipCapture=NO
SkipAdminPassword=YES
SkipProductKey=YES

4. Connect to the deployement share \\server\deploymentshare$ and go to the folder script and double click on LiteTouch.vbs
2010-04-15_162332 2010-04-15_162453

2010-04-15_1626352010-04-15_162645

2010-04-15_162659
4. Don’t forget after the Capture to restore the original customsettings.ini file.

Solution for "Multiple connections to a server or shared resource by the same user, using more than one user name, are not allowed"

When you use MDT you see many times the following error:
"Multiple connections to a server or shared resource by the same user, using more than one user name, are not allowed"

Solution 1:
To fix the problem you should edit the ztiutility.vbs file in the deployment share under the scripts folder.  Open the file in notepad and replace the following code in the MapNetworkDriveEX function:

Case Else
‘ Case &h800704C3 ‘ Multiple connections to a server or shared resource by the same user, using more than one user name, are not allowed.
‘ Case &h8007052E ‘ Logon failure: unknown user name or bad password.
‘ There was a some kind of fatal error.
If ErrDesc <> "" then
             MapNetworkDriveEx = ErrDesc
Else
             MapNetworkDriveEx = "Unable to map UNC Path " & sShare & " :" & "( 0x" & hex(HasError) & " ) "
End if
oLogging.CreateEntry MapNetworkDriveEx & "", iLogType
Exit function
End select

With this code:

Case Else
Err.Clear
On Error Resume Next
oNetwork.MapNetworkDrive  chr(sDrive)&":", sShare, False
HasError = err.number
ErrDesc = err.Description
On Error Goto 0
If Err.Number <> 0 Then
‘ There was a some kind of fatal error.
             If ErrDesc <> "" then
                                        MapNetworkDriveEx = ErrDesc
             Else
                                        MapNetworkDriveEx = "Unable to map UNC Path " & sShare & " :" &    "( 0x" & hex(HasError) & " ) "
             End if
             oLogging.CreateEntry MapNetworkDriveEx & "", iLogType
             Exit function
Else
      Exit Function
End If 

End select

Solution 2

Download ZTIUtility.7z and replace the ztiutility.vbs with the one in the ZTIUtility.7z. You need 7zip to unpack the file.

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

Configuring Forefront Protection 2010 for Exchange Server 2010

imageimage  
For the best performance for Forefront Protection 2010 download Microsoft Forefront Protection 2010 for Exchange Server Best Pratices Analyzer.

Want to check if you have enough Capacity. Read the Following blog post: Forefront Protection 2010 for Exchange Server (FPE) Capacity Planning Guidance v. 2

When you deploy  Forefront Protection 2010 for Exchange Server the next table is very handy

Maintain the Submission Queue Length at zero.

Apply the following script:
\MSExchangeTransport Queues(_total)\Submission Queue Length

Maintain CPU utilization at less than 75%.

Plan and conserve amount of resources required to maintain acceptable level of service.

Light-emitting diode (LED) light needs to be monitored for blinking.

The hard drive LED should maintain a blinking state. Any other state (light always on) indicates thrashing. It is important to maintain adequate disk input/output and utilize memory swapping to prevent thrashing.

FPE (or FSE) databases should be monitored and routinely maintained.

Clean/purge database to reduce size.

Enable retention policies.

Note: If you are expecting the incident database to grow soon, it is a good idea to allocate more free space for the database.

Apply service packs as required.

Perform update for all required service packs on a regular basis.

Note: Exchange Server fixes are distributed in service packs. Service packs keep the product current. Service packs include updates, system administration tools, drivers, and additional components. If you do not stay up to date on service packs, performance and product functionality are seriously compromised.

Translate »