Phones and Devices Optimized for Microsoft Office Communicator

Optimized for OCSAn important part of implementing Unified Communication in an organization is to use equipment that is supported by OCS. Products that are Optimized for Microsoft Office Communicator can be found over at technet using this link: http://technet.microsoft.com/en-us/office/ocs/bb970310.aspx.

I have tested a lot of the Polycom products, including CX-5000 (Round Table), the Microsoft webcams and the Jabra  bluetooth headset. All these products works right out of the box when using Office Communicator, and my customers are really impressed by how simple it is to use these products.  To quote what one customer said: “I knew these products where easy to use, but when it worked right out of the box and without the need to restart the communicator client surprised me. This is something my users will adopt really quick.” 

How to Modify a Database Size Limit

The default database size limit for Exchange 2007 Standard Edition RTM is 50 gigabytes (GB). In Exchange 2007 Standard Edition SP1 the limit is 250GB. There is no default database size limit for the Exchange 2007 Enterprise Edition. The Exchange store process checks database size limits periodically and dismounts a database when the size limit is reached. A warning is logged using Event ID 9685 which tells you that the  database has exceeded the size limit. You can modify the database size limit by adding or changing a value in the registry.

Database Size Limit is a useful way for administrators to have control over their Exchange environment. The Exchange server will react by dismounting the store if the size gets out of hand, and it is a good way to be sure that the database size never outgrows the logical partition it resides on.

Procedure

  1. To use the Registry Editor to modify a database size limit
  2. Start Registry Editor (regedit).
  3. Locate the following registry subkey:
    1. HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeIS\<SERVER NAME>\Private-<database GUID>
    2. You can get the GUID of a database by running the following command in the Exchange Management Shell: Get-MailboxDatabase -Identity “<server name>\<storage group name>\<database name>” | Format-Table Name, GUID
  4. If the Database Size Limit in GB DWORD exists for the subkey, change its value to the desired size in gigabytes.
  5. If the Database Size Limit in GB DWORD does not exist for the subkey, create a new DWORD with that name, and then set its value to the desired size in gigabytes
  6. Restart the Microsoft Exchange Information Store service
  7. Check evenviewer for the following events:
    1. Event ID 1216 which tells you how much size is allocated and what the current physical size is

Source: http://technet.microsoft.com/en-us/library/bb232092.aspx
See this great post about Exchange database size and limits: http://blog.sembee.co.uk/archive/2009/07/21/105.aspx

Save password in MOC

If you have users with computers that are not joined to the same domain that their OCS account is homed to, the users always have to type the password when logging on using Communicator. This is the default setting in Communicator. There is a registry setting for enabling the “remember password” checkbox in the Communicator sign in dialog. I have tested it with non domain joined computers and it works like a charm. Here’s what you do

  1. Open Registry editor
  2. Locate the following key
    1. HKLM/Software/Policies/Microsoft/Communicator
  3. If the key is not there
    1. Create the Communicator folder
    2. Create the key as DWORD and give it the name SavePassword
  4. Set SavePassword=1.  
  5. This enables a checkbox to save password in MOC login dialogue.
  6. After the password is entered it is saved into the registry
  7. HKCU/Software/Microsoft/Communicator/AccountPassword
  8. This registry key store in hashed value. Changing the hash requires re-entering the password.

Original article found over at OCSpedia.com http://www.ocspedia.com/FE/How_to_Save_Password_MOC.htm

OCS Quality of Experience (QoE) – Quick Facts

Here is a blog that covers some facts about QoE using the monitoring OCS role. I noticed three points in the blog that I found useful

  • The OCS 2007 R2 Monitoring Role service and database can be collocated with a computer running Standard Edition (very small deployments only). If you do this, the full edition of SQL Server must be installed on the server (instead of the SQL Server Express Edition that is normally used).
  • 2005 Reporting Services SP1 or SP2 on the backend QoE / Monitoring role SQL database to get reports
  • For the OCS R2 Monitoring Role, you need to install the optional Report Pack for Monitoring server component
    • When installing the Report Pack you must point to a SQL server with Reporting Services installed
    • Reporting Services does not have to be installed on the SQL server hosting the monitoring database, you can point to any SQL server with Reporting Services installed in your domain

Visit the full post for more information here, http://blog.insideocs.com/2009/04/27/ocs-quality-of-experience-qoe-quick-facts/

Migrate from Server 2000 DC to Server 2008 DC

I was doing some research before a domain migration at a customer site when I found this great forum post over at the techarena forum. http://forums.techarena.in/server-migration/1010582.htm

The general steps to migrate from Windows Server 2000 to Windows Server 2008 is almost the same as the steps to migrate from Windows Server 2003 to Windows Server 2008.

Scenario:
Old server: Windows Server 2000 box
New server: Windows Server 2008 box

  1. Verify that Windows 2000 SP4 have been installed on the old server and Windows Server 2008 SP1 have been installed on the new server.  Note: the domain functional level should be in Windows 2000 native mode for the Windows 2000 domain
  2. Upgrade the Windows 2000 forest schema by running “adprep /forestprep” command on old server. Note: you can copy the adprep folder from the Windows Server 2008 installation disc to the old server to run “adprep /forestprep”. The location is \source\adprep on the installation disc.
  3. Upgrade the Windows 2000 domain schema by running “adprep /domainprep” command on old server
  4. Verify the new server’s TCP/IP configuration has been pointed to existing DNS server.
  5. Add new server to existing Windows 2000 domain as a member server.
  6. Run dcpromo on new server to promote it as an additional domain controller in existing Windows 2000 domain, afterwards you may verify the installation of Active Directory.
  7. Enable Global Catalog on new server and manually Check Replication Topology and afterwards manually trigger replication to synchronize Active Directory database between 2 replica.
  8. Disable Global Catalog on old server.
  9. Use NTDSUTIL utility to transfer all the 5 FSMO roles from old server to new server. You’d better transfer FSMO roles via GUI method instead of using NTDSUTIL.
  10. Install DNS component on new server and configure it as a new DNS Server(Active Directory Integrated-Zone is preferred). Note: all the DNS configuration need to be transferred from the existing DNS Server.
  11. Migrate DHCP service from Windows Server 2000 to Windows Server 2008. Migrate File Sharing service. You can also use robocopy.exe from the Windows Server Resource kit to copy the files and maintain NTFS permissions.
    For the shares, the shares definitions and permissions are stored in the following registry key on the server: “HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanserver\Shares”. If you export out the whole key and import in the new server, and if you have the files and folders in the same path as in the old server, then you will retain all you shares and share permissions.
  12. It’s better to make the old DC offline for several days and check whether everything works normally with the new server online. If so, you may let the old DC online and run DCPROMO to demote it.

For more information, please refer to:

Administration of Public Folders with the introduction of Exchange 2007

There are some key commandlets to use when using EMS to administer Public Folders in Exchange 2007. Here is a short list of useful commands

  • For Public Folders
    • Get-publicfolder -recurse |fl name,replicas
  • For System Folders
    • Get-public folder \non_ipm_subtree |fl name, replicas

To Move replicas to Exchange 2007

Moveallreplicas.ps1 –server<sourceserver> -newserver<destinationserver>

Note: Scripts are found at %SystemDrive%\Program Files\Microsoft\Exchange Server\Scripts. To run a script, type the following in the Exchange Management Shell:

[PS] C:\>cd $exscripts

[PS] C:\Program Files\Microsoft\Exchange Server\Scripts>.\Moveallreplicas.ps1

To add or remove a server from a public folder replica’s properties including subfolders you can use the following two scripts:
RemoveReplicaFromPFRecursive.ps1 –TopPubicFolder <\folder> –Server toRemove <servername>

AddReplicatoPFRecursive.ps1 –TopPulblicFolder <\folder> -ServerToAdd <servername>

For more information see this post: http://msexchangeteam.com/archive/2007/06/25/445429.aspx

SensorLock for HTC Touch Diamond/Pro

SensorLock is a locking program designed for the HTC Touch Diamond/Pro. Locking and unlocking is done by rotating the phone and unlike most other locking programs, it does not interfere with or remove focus from running applications. A great feature is when the stylus is pulled out when device is asleep, autolock no longer locks the device. I am using this application now and it works as advertised.

Check for new versions and download it here, http://forum.xda-developers.com/showthread.php?t=422871

G-Alarm, Sophisticated Alarm clock for Windows Mobile

G-Alarm is a reliable and very powerful alarm clock with probably more features than any other alarm software. You can define unlimited alarms of different types, you can set your own music files to wake you up (mp3, wma, wav, ogg, mp4, aac), customize the look and optionally choose between two special wake-up mechanisms: If you want to, you can set G-Alarm to force you to guide a ball through mazes or solve a calculation task or simply shake the phone before you can snooze or stop the alarm.

Supported devices: all devices with Windows Mobile 5, Windows Mobile 6 and Windows Mobile 6.1 (with touchscreen only!)

Download the freeware here, http://www.ageye.de/index.php?s=galarm/about

Spb Phone Suite for Windows Mobile

Spb Phone Suite is a collection of all phone features you missed in Windows Mobile. These are features like profiles, call filtering, missed call notifications, reject and reply with SMS, etc. I use this application to give my Pocket PC a profile feature which updates the profile based on what kind of meeting I have and what time it is.

For example if a calendar item have the custom category of business I have set it up so that the phone goes in silent mode which means that it wont play a sound nor vibrate. I have also set it up to ring at max volume when I have it in my car so I may hear it when I drive. Other profiles I use is that it turns off bluetooth after work, but i I drive the bluetooth comes on etc. The possibilities are endless and I reckon you get the picture :)

This is a great application and really a must have for Windows Mobile. It supports Windows Mobile 5 Phone Edition and Windows Mobile 6 Professional

Go here to download and try it, http://www.spbsoftwarehouse.com/pocketpc-software/phonesuite/

Spb Phone SuiteSpb Phone Suite

Spb Diary for Windows Mobile

I use SPB Diary solely for the extended calendar functionality on my Today screen. It gives me the freedom to show the calendar for up to 7 days ahead, and helps me plan my week. As a consultant I attend a lot of meetings and therefor my calendar controls my day and it is important that I have a full calendar view which this application gives me. It’s a must have.

SPB Diary supports Windows Mobile Pocket PC and Smartphone from 2003 and forward.

Download and try the applicatino here, http://www.spbsoftwarehouse.com/pocketpc-software/diary/screenshots.html