Category: Microsoft

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.

Microsoft Assessment & Planning Toolkit

The Microsoft Assessment and Planning (MAP) Toolkit is an agentless toolkit that finds computers on a network and performs a detailed inventory of the computers using Windows Management Instrumentation (WMI) and the Remote Registry Service. The data and analysis provided by this toolkit can significantly simplify the planning process for migrating to Windows® 7, Windows Vista®, Microsoft Office 2007, Windows Server® 2008 R2, Windows Server 2008, Hyper-V, Microsoft Application Virtualization, Microsoft SQL Server 2008, and Forefront® Client Security and Network Access Protection. Assessments for Windows Server 2008 R2, Windows Server 2008, Windows 7, and Windows Vista include device driver availability as well as recommendations for hardware upgrades.

You can use MAP to inventory the following platforms:

  • Windows 7
  • Windows Vista
  • Windows XP® Professional
  • Windows Server 2008 or Windows Server 2008 R2
  • Windows Server 2003 or Windows Server 2003 R2
  • Windows 2000 Professional or Windows 2000 Server
  • VMware ESX
  • VMware ESXi
  • VMware Server

Reporting
– Identification of currently installed Windows client operating systems, their hardware, and recommendations for migration to Windows 7 and Windows Vista. The tool also reports if desktops have anti-virus and anti-malware programs installed and if the Windows Firewall is turned on.
– Identification of currently installed Windows Server operating systems, their hardware, and recommendations for migration to Windows Server 2008 R2 and Windows Server 2008.
– Identification of currently installed Microsoft Office software and recommendations for migration to Microsoft Office 2007.
– Detailed assessment and reporting of server utilization gathered using the Performance Metrics Wizard.
– Recommendations for server consolidation and virtual machine placement using Hyper-V
– Assessment of client machines, servers, and the technology environment for the implementation of Microsoft Application Virtualization (APP-V)
– Identification of machines where Microsoft SQL Server components are installed.
– Identification of virtual machines, their hosts, and details about each.
– Identification of Windows Server Roles

Hardware Requirements:
– Windows 2003 x86/x64 or Windows 2008 x86/x64
– 1,5 GB (2 GB 2008)

Software Requirements:
– NET Framework 3.5 SP1
– Windows Installer 4.5
– Microsoft Office Word 2007 or Word 2003 SP2
– MIcrosoft Office Excel 2007 or Excel 2003 SP2
– SQL Server 2008 Express Edition, SQL Server 2008, or SQL Server 2005

image image
image image

Download Microsoft Assessment and Planning (MAP) Toolkit HIER

Exchange Server 2010 SP1 is coming

Exchange Team announced that SP1 for Exchange 2010 is coming with a lot new features

I highlighted the things with I like from the coming update. It’s a whole list but i thing with this update is Exchange 2010 SP1 the best version ever!!! 😀

A list of al new things in Exchange 2010 SP1:

Archiving:
– Personal Archive to a different mailbox database from their primary mailbox 😀
– You can import historical e-mail data from .PST files, directly into Exchange
– delegate access to a user’s Personal Archive
– SP1 updates the Exchange Management Console with new tools to create Retention Policy Tags
– support access to a user’s Personal Archive with Outlook 2007 Coming with A update

Outlook Web App
– Delete, mark as read, and categorize operations running asynchronously, these actions feel instantaneous to the user
– Attaching a very large file, will not block the rest of the OWA experience
– Sharing calendars to anonymous viewers via the web if you enable this.
– OWA themes back
– Reading pane can be placed on the bottom or the right side

Mobile:
– Support for send-as
– Support for notifying the user if their device has been placed on block or quarantine by their admin
– Full implementation of conversation view
– To sync only unique parts of messages.
– Setting up mobile device to access mail via POP/IMAP/SMTP, information is available in OWA.

New Management UI
– Create/configure Retention Tags + Retention Policies in EMC
– Configure Transport Rules in ECP
– Configure Journal Rules in ECP
– Configure MailTips in ECP
– Provision and configure the Personal Archive in ECP
– Configure Litigation Hold in ECP & EMC
– Configure Allow/Block/Quarantine mobile device policies in ECP
– RBAC role management in ECP
– Configure Database Availability Group (DAG) IP Addresses and Alternate Witness Server in EMC
– Recursive public folder settings management (including permissions) in EMC

Read the whole article at HERE.

Exchange 2007 The exchange server address list service failed to respond. After Upgrading Domain Controllers to 2008 R2

I want to creat a new mailbox for a new user. But i get the following error: The exchange server address list service failed to respond.
image

Solution:
Go to Organization Configuration in EMC. Right click it in EMC and select Modify Configuration Domain Controller. Point it to your DC hosting the PDC

image 

After that restart the Microsoft Exchange System Attendant services on the mailbox server.

The Microsoft Exchange System Attendant Service does the following thing:

Forwards directory lookups to a global catalog server for legacy Outlook clients, generates e-mail addresses and offline address books, updates free/busy information for legacy clients, and maintains permissions and group memberships for the server. If this service is disabled, any services that explicitly depend on it will fail to start.

Translate »