First, the
Standard Edition server requires enough disk space on your local drive for any meeting
content you may have. You can??™t install any OCS 2007 role on a domain controller. It??™s just
not supported. There are also several general issues regarding fully qualifi ed domain names
(FQDNs) that you should familiarize yourself with. Microsoft lists many of these gotchas in
its Planning Guide.
But as we??™re not going to get down and dirty here with a sample installation, but rather
are going to continue to discuss general issues you need to be prepared for when deploying
OCS 2007, let??™s turn our attention to the next area of concern: the deployment process. The
fi rst step of your deployment process should be to determine storage requirements, and to
create fi le shares to store the following:
?– Presentations to be downloaded or streamed by meeting attendees
?– Information used internally by the pool??™s Web Conferencing Server
?– Information used by the Address Book Server
?– Content logged for any compliance requirements
Make sure you have the following already installed and ready to go:
?– Microsoft Windows Server 2003 SP1 or R2 or later for OCS
?– Microsoft Windows 2000 SP4 or later for Active Directory Domain Services
?– Active Directory in Windows 2000 Server or later native mode in all domains
involving OCS 2007 (Windows Server 2003 native mode is recommended)
?– For Enterprise Edition, Microsoft SQL Server 2005 with SP2 (recommended) or
SQL Server 2005 SP1, SQL Server 2000 with SP4 on the computer where the
backend database will be deployed DNS
?– An Enterprise (recommended), Standalone, or public CA
?– IIS 6.
Pages:
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123