Cisco Cisco Administrative Workstation Release Notes

Page of 90
39
Release Notes for Cisco IPCC/ICM Enterprise & Hosted Editions Release 7.0(0) Installer Update C November 24, 2008
New and Changed Information
  •
Multi-media products are expected to conform to ICM data restrictions.
Behavior Change in Node Manager Pending Shutdown / Windows Stopshut
In Windows Server 2003, Microsoft has disallowed local logon once a system shutdown has been 
initiated. Therefore, an ICM/IPCC Node Manager initiated shutdown can no longer be canceled (via 
"stopshut" or "shutdown /a") from the local machine unless a user with local administrative privileges 
is already logged in.
Cancellation of a pending shutdown (including that as initiated by the ICM/IPCC Node Manager) can 
be achieved by remote invocation from a remote host ("shutdown /a /m" if from Windows Server 2003; 
syntax varies by Windows operating system) assuming the remote login is properly authenticated as an 
administrator privileged for the domain.
Conversely, if Support Tools for ICM/IPCC is deployed, the standard tools "stopshut" option may be 
used to cancel shutdown on the node in question (Support Tools node agent required).
Remote Desktop can also be used to remotely establish a terminal session and issue the stopshut 
command.
This restriction is specific to the Windows Server 2003 environment and is due to a Microsoft change in 
local terminal access while a shutdown is pending. See CSCsa39018 for more detail.
UpdateAw Process Fails when domain\username is Greater than 30 Characters
When the domain\username is greater than 30 characters, the CMS node fails with the error:
 
"dis-cms Fail: The domain\username of the current user is longer than the maximum allowed (30 
characters)."
Since service logon accounts are always 20 characters in length, a NetBIOS domain name longer than 9 
characters will cause this error to occur.
The workaround is to manually shorten the netlogon account name, thus allowing more characters for 
the NetBIOS domain name.
This can be accomplished using the following steps:
1.
On the domain controller, using the Administrative Tool "Active Directory Users and Computers", 
browse to the ICM instance Organizational Unit.
2.
Locate, within the service, logon accounts for the logger and distributor on the system in question.
3.
For each, right-click on the account and select "Properties".
4.
Select the "Account" tab and shorten the "User logon name (pre-Windows 2000)" field enough so 
that its length, combined with the domain name, does not exceed 29 characters.
Active Directory Marks ICM Setup Login Users as Invalid, Preventing Login to ICM Setup
On occasion, ICM Setup is unable to login on Loggers and Admin Workstations. The error returned is: 
error 1057 (The account name is invalid or does not exist, or the password is invalid for the account name 
specified.).
Due to an unknown network triggering event, Active Directory users for Loggers and AWs (created to 
logon to the services in the OU) experience a replication issue and are marked as invalid by Active 
Directory. ICM Setup then creates a new user (instead of replacing the old). When Setup attempts to