Category: Microsoft

Enable the Change Password feature with Outlook Web Access on a Windows 2003 Exchange 2007 Server

First Step create the IISADMPWD virtual directory, do the following:

  1. Click Start, point to Programs, point to Administrative Tools, and then click Internet Services Manager.  
  2. Right-click the default Web site, point to New, and then click Virtual Directory. image
  3. In the Virtual Directory Creation wizard, type IISADMPWD in the Alias box, and then click Next.
    image 
  4. In the Directory box, type c:\windows\system32\inetsrv\iisadmpwd or the location where your hard disk is your default hard disk, and then click Next.
    image
  5. Verify that only the Read and Run script check boxes are selected, such as the ASP check box, click Next, and then click Finish.
    image  image
  6. Verify that the IISADMPWD virtual directory has only basic authentication is set
    image
  7. If you use Windows 2003/IIS 6.0, verify that the application pool is set to MSExchangeOWAAppPool
    image 
  8. Register the IISpwchg.dll file in the Iisadmpwd directory:
    Click Start, and then click Run.
    In the Open box, type the following, and then press ENTER:
    regsvr32 c:\windows\system32\inetsrv\iisadmpwd\iispwchg.dll
  9. Configure the PasswordChangeFlags property in the metabase to make sure that the Password Change functionality is enabled:
    Click Start, and then click Run.
    In the Open box, type cmd, and then press ENTER.
    Locate the C:\Inetpub\Adminscripts directory.
    Type the following command, and then press ENTER:
    cscript.exe adsutil.vbs set w3svc/passwordchangeflags 1

    0: This is the default value. This value indicates that you must use a Secure Sockets Layer (SSL) connection when you change the password.
    1: This value permits password changes on non-secure ports. This value is useful if SSL is not enabled.
    2: This value disables the Password Change functionality.
    4: This value disables the advance notification of password expiration.

  10. Do not forget to enable Active Server Pages.
    image 
    Source http://support.microsoft.com/kb/297121

Microsoft Deployment Toolkit (MDT) 2010 Update 1 is RTM

Microsoft has released a new version of MDT 2010 named Update 1.

It’s a great tool im loving it.

What new:

For System Center Configuration Manager 2007 users:

  • New “User Driven Installation” deployment method. An easy-to-use UDI Wizard allows users to initiate and customize an OS deployment on their PCs that’s tailored to their individual needs.

  • Support for Configuration Manager R3 “Prestaged Media.” For those deploying Windows 7 and Office 2010 along with new PCs, a custom OS image can easily be loaded in the factory and then customized once deployed.

For Lite Touch Installation:

  • Support for Office 2010. Easily configure Office 2010 installation and deployment settings through the Deployment Workbench and integration with the Office Customization Tool.
  • Improved driver importing. All drivers are inspected during the import process to accurately determine what platforms they really support, avoiding common inaccuracies that can cause deployment issues.

Bug Fixes and small improvements

  • LTI Wizard performance improvement. The LTI Wizard now takes less time to initialize and shows up faster.
  • Issue in validating connection to the server fixed. In a few scenarios, MDT 2010 used to report the error message, "A connection to the distribution share could not be made" when a task sequence is run. The Microsoft Support article, “Error message when you use MDT 2010: ‘Multiple connections to a server or shared resource by the same user, using more than one user name, are not allowed,’” at http://support.microsoft.com/kb/977566 describes this issue in detail. This issue has been fixed in MDT 2010 Update 1.
  • Support for installing Windows 7 roles and features. MDT 2010 Update 1 adds support for installation of Windows 7 operating system roles and features.
  • Looping issue with x64 custom Windows images fixed. In MDT 2010, ZTI–System Center Configuration Manager deployments could get into an infinite loop when deploying an x64 Windows image captured by LTI. This issue has been fixed in MDT 2010 Update 1
  • Error handling improvements in MDT task sequence templates. In MDT 2010, task sequences appear to finish successfully even when they really failed. These issues are fixed in MDT 2010 Update 1.

Download the new version HERE 😀

Deploy Office 2010 with Multiple Languages with MDT 2010

I Like Office 2010. For me it is the best Office version i ever worked with.
MDT 2010 it’s great tool that Microsoft created.
Now i will talk about how you deploy Office 2010 with Multilanguage packs with MDT 2010.

Step 1: Download the Office 2010 English version booth will be in x86 & x64

Step 2. Download the Office 2010 (language) Multilanguage iso only available from the Microsoft Volume Licensing site. Both in x86 en x64.

Step 3. Add the Office 2010 English version to MDT 2010 here office-2010-uitrollen-met-mdt-2010

Step 4. Extract the Office 2010 (language) Multilanguage iso with 7zip in the same application folder witch you created in Step 3.

Step 5. When you open MDT 2010 management console and you go to the Office 2010 Application that you added in step 3. You wil see that MDT sees more the one language. In my case it was en-us and nl-nl. The Screenshot is from the older MDT 2010 you MDT sees Office 2010 as Office 2007. MDT 2010 beta 1 supports Office 2010. I found till now no issues deploying Office 2010.

 image

Step 6. Check the languages that you want. Check the Screenshot how i did it.

Step 7. Deploy the a Windows XP or Windows 7 client with Office 2010 Multilanguage versions.

Step 8. You can check with Microsoft Office 2010 Language Preferences or the languages that you configured are installed.
image

Step 9. Use Group Policy to set the language settings for users

    1. Download the Office 2010 policy template files to your computer. You will find them HERE

    2. Make a new GPO named Office 2010 languages settings it is a user policy.

    3. Under User Configuration in the console tree, right-click Administrative Templates.

    4. Click Add/Remove Templates, and then click Add.

    5. In the Policy Templates dialog box, click the template that you want to add, and then click Open.

    6. After you add the Office 2010 templates, click Close.

    7. Open the Group Policy object (GPO) for which you want to set policy.

    8. Double-click User Configuration and expand the tree under Administrative Templates.

    9. Locate language-related policies in the Microsoft Office 2010 \ Language Settings node.

    10. Select the languages that you want to use for each setting.

    11. Save the GPO.

    12. Go Testing

    Exchange 2007 SP3 is released

    What’s New in SP3 for Exchange 2007


    Windows Server 2008 R2 Support

    Exchange Server 2007 SP3 supports all Exchange 2007 roles on the Windows Server 2008 R2 operating system.

    Windows 7 Support

    Exchange 2007 SP3 supports the installation of the Exchange 2007 management tools on a computer that is running Windows 7. Additionally, Exchange 2007 SP3 provides support for the installation of the Exchange 2007 Management Tools together with the Exchange Server 2010 Management Tools on the same Windows 7-based computer.

    Improved Password Reset Functionality

    Exchange 2007 SP3 introduces password reset functionality for Internet Information Services (IIS) 7.

    To enable the password reset feature

    1. Log on to the Exchange server that is running the CAS role by using an account that has local administrator rights.

    2. Start Registry Editor, and then locate the following registry subkey:

      HLKM\SYSTEM\CurrentControlSet\Services\MSExchange OWA

    3. Create the following DWORD value if it does not already exist:

      Value name: ChangeExpiredPasswordEnabledValue type: REG_DWORDValue data: 1

    4. Exit Registry Editor.

     Updated Search Functionality

    Exchange 2007 SP3 includes updates to the Exchange Search (MSSearch) component. MSSearch provides support for creating full text indexes for Exchange stores. Exchange 2007 SP3 updates the MSSearch binary files to MSSearch 3.1.

    Schema Changes

    Exchange 2007 SP3 includes Active Directory schema changes for certain Unified Messaging (UM) mailbox attributes. For more information, see Active Directory Schema Changes (SP3).

    Support for Right-to-Left Disclaimer Text

    Exchange 2007 SP3 includes support for Right-to-Left text in e-mail message disclaimers in a right-to-left language, such as Arabic. In earlier versions of Exchange, when you use a transport rule to create a disclaimer in a right-to-left language on an Exchange 2007 Hub Transport server, the text appears incorrectly when you view it from Outlook 2007.

    Exchange 2007 SP3 adds functionality to the transport rule setting to fully support right-to-left text in disclaimers.

    Download here SP3 for Exchange 2007

    Database Availability Group (DAG) in Exchange 2010

    One of the new features of Exchange 2010 is DAG Database Availability Group. The Customer were i work now wants Exchange 2010 in a dag cluster because they have a datacenter for failback.
    Because i going to implement Exchange 2010 at the customer i created a test setup.

    Configuration:

    Server 1 – HYPERVDC-01
    OS: Microsoft Windows 2008 R2 Standard x64
    IP: 192.168.150.90
    Roles: Active Directory / Hyper-V

    Server 2 – CHEK10-01
    OS: Microsoft Windows 2008 R2 Standard x64
    IP: 192.168.150.91
    Roles: Exchange 2010 HT / CAS

    Server 3 – CHEK10-02
    OS: Microsoft Windows 2008 R2 Standard x64
    IP: 192.168.150.92
    Roles: Exchange 2010 HT / CAS

    Server 4 – DAGEK10-01
    OS: Microsoft Windows 2008 R2 Enterprise x64
    IP: 192.168.150.93
    Roles: Exchange 2010 MBX

    Server 5 – DAGEK10-02
    OS: Microsoft Windows 2008 R2 Enterprise x64
    IP: 192.168.150.94
    Roles: Exchange 2010 MBX

    Creating the DAG

    clip_image002
    clip_image004

    Groupname: DAG01
    Witness Server: CHKEK10-01 (Microsoft says use one of the CAS or Hub Servers. You cannot use a DAG Server! If you want use a non Exchange 2010 server you must at the Exchange Trusted Subsystem group at the local administrators group.
    Witness Directory: C:\DAG01
    clip_image006

    Add a MB server to a DAG

    clip_image008clip_image010

    clip_image012clip_image014

    clip_image016clip_image018

    clip_image020

    Setting a IP address on a Database Availability Group

    With the following command you can set the DAG Database Availability Group an IP address. Set-DatabaseAvailabilityGroup -Identity DAG01 -DatabaseAvailabilityGroupIpAddresses 192.168.150.96

    Rollup 4 for Exchange Server 2010

    The Exchange team has released Update Rollup 4 for Exchange Server 2010 RTM (KB 982639)

    KB 982639 lists all the fixes included in this rollup. Here are some of the product improvements and critical bug fixes we’d like to call out starting with 5 improvements we made to prevent crashes in very unique scenarios.

    • KB 980852 The RpcClientAccess process on an Exchange Server 2010 server crashes when you access a mailbox by using a MAPI application
    • KB 979801 An error message is generated in Exchange Server 2010 when you use Exchange Troubleshooting Assistant
    • KB 980364 The Exchange Transport service on an Exchange Server 2010 server crashes when a certain message is processed
    • KB 980353 A MAPI application that is used to access Exchange Server 2010 mailboxes crashes when the application accesses an address book
    • KB 979790 An IMAP4 client crashes when accessing an Exchange Server 2010 mailbox

    We corrected a few replication issues some of you encountered.

    • KB 980149 The Add-MailboxDatabaseCopy command fails when it is used to add a database copy to a Database Availability Group in an Exchange Server 2010 environment
    • KB 981961 Event ID 4033 is logged and the Free/Busy replication from an Exchange Server 2003 server to an Exchange Server 2010 server fails
    • KB 979921 You cannot replicate a public folder from one Microsoft Exchange Server 2010 server to another, and Event ID 3079 is logged on the target server

    Important:
    Microsoft Update does not detect Update rollups on Exchange Server 2010 Mailbox servers that are part of a database availability group (DAG).

    Download Rollup 4 for Exchange 2010 HERE

    Checking Microsoft Office 2010 KMS Activation Status

    Before you start you must al ready have a kms server.
    On the KMS server you need to install the Office 2010 KMS Host License Pack on the KMS Server.
    Launch Microsoft Outlook 2010
    Click to the File tab. Click Help.

    Office is not activated
    clip_image002
    Determining Which Activation Method Office is Using – KMS or MAK

    Click the start menu and enter cmd /k cscript “%programfiles%\Microsoft Office\Office14\ospp.vbs” /dstatus in the search box.

    If running 32 bit Office 2010 on 64 bit Windows, %programfiles% above should be replaced with %programfiles(x86)%.

    Not Activated

    clip_image004

    Checking if a DNS Domain is Configured for KMS Auto-Discovery

    To check if a DNS domain is configured for KMS auto-discovery, check that a SRV record exists.

    nslookup -type=srv _vlmcs._tcp.wardvissers.nl

    If a SRV record exists for the domain, the DNS server will detail the SRV record. 

    

    C:\>nslookup -type=srv _vlmcs._tcp
    

    Server:  ward-dc02.wardvissers.local
    

    Address:  192.168.150.6
    

    Non-authoritative answer:
    

    _vlmcs._tcp.wardvissers.local SRV service location:
    

              priority       = 0
    

              weight         = 0
    

              port           = 1688
    

              svr hostname   = ward-dc2.wardvissers.local
    

    If no SRV record exists for the domain, the DNS server will return an error 
    

    Verifying that a Windows Computer can Communicate with the KMS Activation Server 
    

    KMS activation requires that the machine to be activated has TCP port 1688 open for outbound communication to the activation server.
    

    Verifying that outbound TCP port 1688 is open to the KMS server 
    

      

    1. Download and install the utility portqry.exe from Microsoft. It is a command line utility from Microsoft that reports the port status of a remote host.

    2. From a command prompt, run the command: 
      3. 

    

    portqry.exe -n ward-dc02.wardvissers.local -p tcp -e 1688
    

    The command will return “TCP port 1688 (unknown service): LISTENING” if the computer is able to communicate with the KMS server.
    

    clip_image006
    

    If the command returns “TCP port 1688 (unknown service): FILTERED” then the computer is unable to communicate with the KMS server 
    

    Manually Specifying the KMS Activation Server
    

    1. Type cmd in the search bar to locate the command window.. 
    2. At the command prompt, type cd\Program Files\Microsoft Office\Office14. 
    

    If running 32 bit Office 2010 on 64 bit Windows, Program Files above should be replaced with Program Files (x86). 
    Run the command cscript ospp.vbs /sethst:ward-dc02.wardvissers.local to manually specify the KMS activation server. 
    clip_image007
    

    Run the command cscript ospp.vbs /act to activate Office with the KMS server. 
    

    clip_image007[1]
    

    Launch Microsoft Outlook 2010 agein
    Click to the File tab. Click Help. 
    

    Office is activated 
    

    clip_image001
    
	
    

	
	


    


    
	
	
    
		
    Where to find the right MDT 2010 logs
    	
    

	
    
		
    Each MDT 2010 script automatically creates log files during its execution. The names of these log files match the name of the script—for example, ZTIGather.wsf creates a log file named ZTIGather.log. Each script also updates a common master log file (BDD.log) that aggregates the contents of the log files that MDT 2010 scripts create. MDT 2010 log files reside in C:\MININT\SMSOSD\OSDLOGS during the deployment process. Depending on the type of deployment being conducted, the log files are moved at the completion of the deployment to either %WINDIR%\SMSOSD or %WINDIR%\TEMP\SMSOSD. For Lite Touch Installation (LTI) deployments, the logs start in C:\MININT\SMSOSD\OSDLogs. They end up in %WINDIR%\TEMP\DeploymentLogs when task sequence execution is complete. 
    

    MDT 2010 creates the following log files: 
    

    BDD.log: This is the aggregated MDT 2010 log file that is copied to a network location at the end of the deployment if you specify the SLShare property in the Customsettings.ini file. 
    

    LiteTouch.log: This file is created during LTI deployments. It resides in %WINDIR%\TEMP\DeploymentLogs unless you specify the /debug:true option. 
    

    Scriptname.log: This file is created by each MDT 2010 script. Scriptname represents the name of the script in question. 
    

    SMSTS.log: This file is created by the Task Sequencer and describes all Task Sequencer transactions. Depending on the deployment scenario, it may reside in %TEMP%, %WINDIR%\System32\ccm\logs, or C:\_SMSTaskSequence, or C:\SMSTSLog. 
    

    Wizard.log: The deployment wizards create and update this file.  
    

    WPEinit.log: This file is created during the Windows PE initialization process and is useful for troubleshooting errors encountered while starting Windows PE. 
    

    DeploymentWorkbench_id.log: This log file is created in the %temp% folder when you specify a /debug when starting the Deployment Workbench.
    
	
    

	
	


    


    
	
	
    
		
    Configuring Client Access Array for Exchange 2010
    	
    

	
    
		
    When you want to use the Client Access Array function from Exchange 2010. You have to options.    
    1. Use the NLB function in Windows. Check this article that i blogged: Configuring NLB for Exchange 2010 for Cas load balancing.     
    2. When you have 2 physical load balancers in combination with a DAG cluster.
    

    I haven’t any pre-Created CAS arrays in my hyper-v.local domain. But you would to check of there is any pre-created CAS Arrays. Run the command below. if you didn’t create a CAS Array before, you will get nothing .
    

    Get-ClientAccessArray     
    clip_image002     
    

    Then you should create new Client Access Array. Run below Cmdlet in Exchange Management Console
    

    New-ClientAccessArray –Name “CasArray1” –Fqdn casarray.hyper-v.local -Site “Default-First-Site-Name”      
           
    clip_image004     
    Now we have finished creating a CAS array. Then we must associate databases with this CAS Array.     
    Use below CMDLet to add mailbox database to CAS array. We can attach all mailbox databases at once as shown as shown  below
    

    

    Get-MailboxDatabase | Set-MailboxDatabase -RPCClientAccessServer “casarray.hyper-v.local”     
    clip_image006
    
	
    

	
	


    

	
		
    
	
    


	
    

	


    


    Translate »