Today I am installing the Unified Messaging role on my SBS2008 Exchange 2007 install. I am going to be implementing the excellent 3CX Phone software on our network for test (more on that later!).
During the installation of the Unified Messaging service I got prompted for the EXCHANGESERVER.MSI file because the SBS2008 installation gets rid of the files it temporarily creates during setup in C:Program FilesWindows Small Business ServerBinCMPNENTSEXCHSRVR80
Simple, I thought… just point it to the CDDRIVE:CMPNENTSExchange12 directory and we should be good to go… but alas, this is not the case. I ended up with this error:
Installing product E:CMPNENTSExchange12exchangeserver.msi failed. Fatal error during installation. Error code is 1603. Last error reported by the MSI package is ‘An installation package for the product Microsoft Exchange Server cannot be found. Try the installation again using a valid copy of the installation package ‘EXCHANGESERVER.msi’
Very odd.
After some research and general screwing around with things, I copied the Exchange12 directory from the CD to the hard drive, and pointed to that instead…. sure enough, the installation continued on without issue!
I am curious what steps you went through to install UM on SBS 2008. Did you just add the UM role and point it to the .MSI? I have always been under the impression you can not use UM on SBS but I really would like to get it working for the same reason you are, 3CX testing.
Thanks
yes, you can…..
You just add the feature in Programs and Features – Change on Exchange 2007 SP1.
From:
http://technet.microsoft.com/en-us/sbs/cc817589.aspx
Can I run Windows Small Business Server 2008 as a unified communications (UC) server?
It is possible, but there are considerations to be aware of. UC requires significant expertise and experience with enterprise messaging technology; this experience is not common in the marketplace and thus it cannot be recommended as a general solution for small businesses. UC also requires significant additional investment in hardware, software, and client licenses that put it out of the reach of nearly all small business owners. Smaller, more appropriately-scaled communications technologies such as Microsoft Response Point are a preferred solution for small businesses.
So yes…. but you need the enterprise CAL for Exchange.
Well, what do ya know. It worked. I never really considered using the Enterprise product key for SBS but it allowed me to install UM. I did not run into the issue you did as it let me use the DVD image (Using VMWARE) with no issues. Now..hurry up and configure the 3CX integration so I can see what you did! 🙂
Hey Danny,
I have already done it…. when I get a moment I will put up a video or something.
Thanks for this simple tip! I was having problems re-installing the Client Access Role and after all of the searching it was this one simple idea that fixed it!
Nice one Nick! That solved one of the problems I had on the long road to Exchange UM/Asterisk integration. I’ve got all the features working now, including “Play on Phone” option from Outlook. The one feature I really want is to be able to dial contacts directly from Outlook, but so far no joy.
You can do that with 3CX 🙂
See my new project:
http://www.g7eleven.com
I spoke too soon. Just found an Asterisk TAPI driver that supports Win 7 x64 and I am now officially in VOIP heaven! I like the look of 3Cx, but I enjoy the challenge of getting ethnically diverse(!) systems to talk to each other (ie Linux & Windows). Also, Asterisk has the advantage of being free.
Good luck with the new project, from my limited experience, VOIP can give you good margins but users are very intolerant of system downtime.
I have added UM to Exchange, install and have got things setup, but whenever we leave messages on the voicemail, it does not go to the email and the message service always says no new calls…. help!
Had this problem with Exchange SP3 on SBS 2008. The original installation was from the disk, not CD.
Anyhow… used http://technet.microsoft.com/en-us/library/dd285501(EXCHG.80).aspx to guide me. Step 4 is not possible, since the SP removes the actual files before upgrading (copying) the new files. I did set the services to start automatically.
At this point I tried it again in the GUI, to no avail.
Step 5, seems to have done the trick.
> setup.com /mode:upgrade
from the command line, installation seemed to get past whatever problems it was having in the GUI mode.
Hope someelse working late on a long weekend sees the answer to their problem. Ah, the beauty of software!