Recently had a problem un-installing the first Exchange 2003 Server in the organisation even after moving off all the Users, Offline Address Book, removing the RUS etc. etc.

“One or more users currently use this mailbox store. These users must be moved to a different mailbox store or be mail disabled before deleting this store”.

Doing an AD Search for Exchange recipients and either sorting by the Exchange Server I want to remove or explicitly searching for Exchange Home Server came up with nothing….. hmmm

Tried running an advanced AD find and hey presto, it found two users that seem to have some details of once being enabled on that Exchange Server. Once I had removed the Exchange attributes from those accounts I could un-install Exchange.

Here is how to perform the advanced search:

1. In Active Directory Users and Computers right-click your domain and choose ‘Find’
2. Click ‘Advanced’ and then choose ‘User’ from the Field menu
3. Now choose ‘Exchange Home Server’ from the list.
4. Set the condition to ‘Ends With’ and type the name of your Exchange Server
5. Click ‘Find’

Good luck

We came across an issue recently where-by we had a DL385 G1 running Windows 2008 R2. As this OS is not on the supported matrix for this Server it means that there isn’t a PSP for it and therefore no monitoring for us. If you run the setup you will received a ‘Failed Dependencies’ alert against the HP Insight Management Agents and HP Insight Diagnostics Online Edition and when you view those failures you will see them as listed below.

How do we fix this then? We need these dependencies on so we can monitor the status of the Server.

Easy peasy….. well, it is now I figured out how to do it  

Right-click the setup.exe file and properties, select the Compatibility tab and enable the ‘Run this program in compatibility mode for:’ option then select ‘Windows Server 2008 (Service Pack 1)’ from the drop down. Apply and Ok and you are now good to go.

Run the setup.exe again and this time it will meet the requisites and let you install all the agents etc.

Good luck.

Neil

When trying to deploy a Windows 7 image from WDS I was confronted by the above error. The error occurred whilst trying to deploy different Windows 7 images to different computers and laptops.

After routing through log files and the internet I was starting to get a little frustrated. At this point I thought that I would try using the install.wim that comes on the Windows 7 CD to see what happens. Whilst browsing the sources folder on the CD I noticed the boot.wim file. Now, although I have never needed to add multiple boot.wim files for the assorted OS’ I already deploy off this WDS Server I thought I would add the boot.wim (right-click Boot Image in WDS and select ‘Add Boot Image’. I labelled the new boot.wim file to ‘Windows 7 Deploy’ on import and then chose this option when PXE booting the Laptop.

Hey presto, it now works without any errors.

Hopefully this will save someone the headache I received getting to this point.

Good luck

Neil

Microsoft have now confirmed support of OCS 2007 R2 on Windows 2008 R2 – yay.

The following scenarios are also still not supported:

• Upgrading the OS of an existing OCS R2 installation to Windows 2008 R2
• Installing OCS R2 Group Chat on a Windows 2008 R2 Server or in a Windows 2008 R2 Domain

Thanks to ‘the UC Guys’ for the info.

Exchange 2010 Outlook Web Access now offers integration with OCS R2 in much the same way as Office 2010 (for those of you that have used it), in that you can now see your OCS buddy list. Whilst this can be really useful in Outlook Web Access some of the steps to get this working can be a little tricky and need to be done in a particular order.

Quick note, each of the following steps will need to be completed on all Exchange 2010 CAS Servers in your organisation.

Firstly, download the Microsoft Office Communications Server 2007 R2 Web Service Provider:

http://www.microsoft.com/downloads/details.aspx?familyid=CA107AB1-63C8-4C6A-816D-17961393D2B8&displaylang=en

Secondly, if you are running your CAS Servers on Windows 2008 R2 you will need the ‘UcmaRedist.msp’ patch:

http://www.microsoft.com/downloads/details.aspx?FamilyID=B3B02475-150C-41FA-844A-C10A517040F4&displaylang=en

Run the CWAOWASSPMain.msi and install it (default location is C:Web Services Provider Installer).

Copy UcmaRedist.msp to the C:Web Services Provider Installer folder.

You will now need to install the files in that folder in the following order:

vcredist_x64.exe

UcmaRedist.msi

(run an elevated Command prompt (run as Admin))

Browse to C:Web Services Provider Installer folder and install the following:

CWAOWASSP.msi

UcmaRedist.msp

You can now confirm that the installation has completed correctly by browsing to and checking for the following registry key:

HKLMSystemCurrentControlSetServicesMS Exchange OWAInstantMessaging.

If the InstantMessaging key does not exist under MS Exchange OWA then ensure you ran the CWAOWASSP.msi from an elevated command prompt.

Hopefully by this point you will have installed a FQDN Certificate off your internal CA for your CAS Server(s), if not, you will need to. OCS works entirely on Certs and checks the FQDN of the Server(s) you add against the cert that it is operating with – basically, the self-signed certificated that Exchange installs with will not with OCS.

Once you have a cert from your internal CA that matches the FQDN of your Server you will need to launch Exchange Powershell and run the following command:

Get-ExchangeCertificate | fl

Details you will require:

Issuer	CN=Server Root CA, O=Company Limited etc.
SerialNumber	00FF4A82B8779966333CB2A177046F44C3
Services	IIS (only needs IIS but can have others)

(Keep this screen open as you will need the information from the certificate registered for IIS in the next step.)

Now browse to C:Program FilesMicrosoftExchange ServerV14ClientAccessOWA and edit the ‘web.config’ file with notepad.

You will need to complete the following sections:

IMPoolName

IMCertificateIssuer

IMCertificateSerialNumber (this needs to in two octet sets as per below)

example:

Now you need to enable the CAS Server to use OCS for IM, to do this run the following from the Exchange Powershell:

Get-OwaVirtualDirectory | Set-OwaVirtualDirectory –InstantMessagingType OCS

Once the command has completed you will need to perform an ‘IISReset’

 

Now, connect to your OCS R2 Server and bring up the Front-End properties of the pool and select the Host Authorisation tab. Click Add.

Add the host name as the FQDN of the CAS Server(s) that are being configured for IM (this will be need to be the same as the FQDN certificate registered on the CAS servers for IIS). Tick the boxes for ‘Throttle as Server’ and ‘Treat as Authenticated’.

Once you have restart the OCS R2 Front-End Service it should all be working.

Found this useful link on a blog by the good people at communicationsserverteam.com and thought it was worth a mention.

Article: http://communicationsserverteam.com/archive/2010/01/25/726.aspx

Basically free high-level overview for following features:

• Instant Messaging
• Presence
• Contact Management
• Audio and Video
• Desktop Sharing
• Office Application Integration
• Add a Live Meeting
• Communicator Web Access

You can register for these sessions on the following link:

https://events.livemeeting.com/967/15027/reg.aspx?pc=05

Neil Cruickshanks

After downloading and attempting to install the French language pack for Exchange 2010 UM I was less than pleased to the receive an error:

It took me a few moments to digest what was occurring but after reading the error (always a good start) and looking through the Exchange setup logs ([ERROR] Could not find a part of the path ‘C:SupportUM,Language,Packsfr-FR’), it would appear that if the Language Pack is in a folder that contains spaces it will not install.

If you look at the error above you will note that the spaces in my folder name have been replaced by comma’s ‘,’.

Resolution

Remove the spaces in the folder containing the Language Pack

 

Neil Cruickshanks