Once again, .NET 3.5 is a prerequisite for installing OCS 2007, and once again the installation for this failed. A tip for you might be to enable these things ahead of the installation of OCS. I do not remember having the same problem on OCS 2007 with Windows server 2003. It might be a 2008 issue as much as a R2 problem. If anyone do install this on Windows 2003, please let me know if you run into the same issues.
Now, off to the installation at hand. First of is the Back End server on which I just installed SQL.
If you are going to install everything on one box, you don't have to read much to install OCS (a basic understanding of the components involved is really helpful though). But if you are about to what I am, install an Enterprise installation with back ends, frontends and possibly balance loaders and several pools. Reading the docs is just for you! Also, make sure the right client tools are inplace, and server times are synchronized (I am using SQL 2008 on the back end, and the installation comes with 2005 client tools).
Installing BE is really just about "preparing" the environment. For those you who have not seen the wizard; This is a task of it's own. A few simple steps to complete.
Installing the FE is another matter. Again; If you are installing all on one box, there isn't too many pitfalls. But when you deploy to several servers, you need to keep your head straight when it comes to poolnames, servernames, sipdomains and certificates.... If you have a basic understanding, it should not be too hard, but still... whatch out for those pitfalls when assigning roles, names and certificates. My biggest obstacle was figuring out how to add the certificate to IIS. AS it turned out, the management tools were not installed (and are not by default).
Do you know any guide or tutorial baout how to install OCS 2007 R2?
ReplyDeleteI cant get the installation to work. But i think that there might be some prerequtis (cant spell that) that i missed.
Regards
Uran
Kind of hard to guess your problem, but actually, MS has created a few walkthroughs on their technet site.
ReplyDeleteFind your deployment model, and go through every step.
A hot tip: Get your certificates right, and create those DNS entries for auto enrollment.
Also; make sure clients trust the root CA
Oh, I forgot:
ReplyDeletehttp://technet.microsoft.com/en-us/library/ee323514(office.13).aspx
link to the library
Naushad:-
ReplyDeleteocs server 2007 r2 prerequisite
IIS
DOT NET 3.5 FRAMEWORK
SQL SEREVR 2005 WITH SP2
SRV RECORD IN DNS SEREVR (SIP/TCP/IP)
CERTIFICATE SERVER(MICROSOFT CA)
OCS SEREVR SOULD BE PART OF DOMAIN CONTROLLER.
My name is Jamie Mckee I was browsing internet and found your blog. The author did a great job. I will subscribe to your RSS feeds. Thank you for your contribution. I am a web designer myself. And here some examples of the websites that I designed for payday loan payday company.
ReplyDelete