Cisco Cisco Unified MeetingPlace Web Conferencing
Release Note, Cisco MeetingPlace Web 3.0 (Release 4.2.7.106)
Page 33 of 39
OL-6038-01 Cisco Systems, Inc.
Revision Date: 5/17/04
13 Addendum I – Updates since 4.2.7.92 GA Release
13.1 New Features and Changes:
13.1.1 IIS Lockdown:
Microsoft IIS Lockdown can now be deployed with MeetingPlace Web. However, you MUST use the
IIS Lockdown install package that is bundled with the MeetingPlace Web Gateway.
1. Open Explorer and navigate to <drive>:\Latitude\MPWEB\IIS Lockdown
2. Double-click on iislockd.exe
3. Following the screen instruction. At the point where it ask you what install option you want,
2. Double-click on iislockd.exe
3. Following the screen instruction. At the point where it ask you what install option you want,
select “MeetingPlace Web Conferencing”
4. Continue to click Next and IIS Lockdown implementation will begin
5. When implementation has completed, click Finish.
5. When implementation has completed, click Finish.
For full details, please download the Tech Notes
Configure MPWeb to work with Microsoft IIS Lockdown
Utility from Cisco.com.
13.1.2 Change password during upgrade to MPWeb 4.2.7:
Previously, when you upgraded an existing MeetingPlace Web that uses the sa account with a blank
password, you cannot change the password during the installation. With this release, if you are upgrading
a pre-4.2.7 installation and the password is blank, you will see a dialog box during the upgrade that will
allow you to change the sa password.
password, you cannot change the password during the installation. With this release, if you are upgrading
a pre-4.2.7 installation and the password is blank, you will see a dialog box during the upgrade that will
allow you to change the sa password.
13.1.3 Enforce Meeting Password requirement (CR16537)
In previous version of MeetingPlace Web, the Meeting Password requirement was not enforced when
users schedule through the web. In other words, even if the user profile's “Require Password” is set to
“YES”, the user is not prompted to enter a meeting password during the scheduling operation. A new key
has been added to 4.2.7, which controls this behavior.
HKEY_LOCAL_MACHINE\SOFTWARE\Latitude\MeetingPlace
WebPublisher\Meetings\EnforcePasswordsForAll
EnforcePasswordsForAll is a DWORD and has default value of 0, which means password requirement is
not enforced. Change this value to 1 to enforce password requirement for meetings scheduled.
users schedule through the web. In other words, even if the user profile's “Require Password” is set to
“YES”, the user is not prompted to enter a meeting password during the scheduling operation. A new key
has been added to 4.2.7, which controls this behavior.
HKEY_LOCAL_MACHINE\SOFTWARE\Latitude\MeetingPlace
WebPublisher\Meetings\EnforcePasswordsForAll
EnforcePasswordsForAll is a DWORD and has default value of 0, which means password requirement is
not enforced. Change this value to 1 to enforce password requirement for meetings scheduled.
13.1.4 ExternalServerHostname registry value:
ExternalServerHostname, which is required on the Internal MPWeb server so that users can be re-directed
to external DMZ server for DC, has now been removed from registry. The new value is now moved into
the SQL database and configured through the Rollover Admin UI.
to external DMZ server for DC, has now been removed from registry. The new value is now moved into
the SQL database and configured through the Rollover Admin UI.
13.1.5 Invitee list:
Invitee list used to be visible as soon as you access the Meeting Details page. It has now been changed to
a link and moved to the right, under the Attachments page link.
a link and moved to the right, under the Attachments page link.