<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
you can ignore them. or touch these users in ccmadmin and update a
device association or some other use attribute that is stored in the
user profile. this will give the user a profile populated with
appropriate values.<br>
<br>
/wes<br>
<br>
Scott Voll wrote:
<blockquote
cite="mid:f84a38d30805050753h7afe214mdfa0413094d9bda4@mail.gmail.com"
type="cite">
<div>I got a good (warnings only) DMA TAR file. it looks like the
warning are all users that do not have any association to anything in
IPT. I also have some warnings related to address book / Fast dails.
I should be able to just ignore them?</div>
<div> </div>
<div>here are the two basic warning messages:</div>
<div> </div>
<div>Warning: PersonalPhoneBook: EndUser not found for
9597534665,OU=FastDialEntries,OU=USERNAME_HERE_info,OU=user_info,OU=CCN,O<br>
Condition: Either the user does not exist in the directory or has been
tagged invalid</div>
<div>Solution: Please verify that the user exists in the directory
and is a valid CCM user; ie. User with profiles</div>
<div> </div>
<div>and </div>
<div> </div>
<div>Warning: UserID:Username_Here: is invalid - Attribute
ciscoatUserProfileString is found empty. </div>
<div>Condition: The user does not contain a valid pointer to the User
profile</div>
<div>Solution: Please verify that the user is a valid CUCM user.
Please access the user through the CUCM Admin page and associate a
device to the user. Then disassociate the same device. This procedure
will create the required profile for the user<br>
</div>
<div> </div>
<div>Scott<br>
<br>
</div>
<div class="gmail_quote">On Sat, May 3, 2008 at 7:28 AM, Wes Sisk <<a
moz-do-not-send="true" href="mailto:wsisk@cisco.com">wsisk@cisco.com</a>>
wrote:<br>
<blockquote class="gmail_quote"
style="border-left: 1px solid rgb(204, 204, 204); margin: 0px 0px 0px 0.8ex; padding-left: 1ex;">
<div text="#000000" bgcolor="#ffffff">general rule for DMA is
errors must be corrected, warnings may be ignored. AD integrations
always generate plenty of warnings, for some reason data is just never
as consistent in AD.<br>
<br>
Couple of next steps:<br>
1) make sure you're using the latest DMA. Each version gets
incrementally better at autocorrecting errors and clarifying messages<br>
2) then open a tac case and let TAC lookup your errors and warnings.
cleanup as much as possible before upgrade so you have good data going
forward.<br>
<br>
/Wes<br>
<br>
Scott Voll wrote:
<blockquote type="cite">
<div>
<div class="Wj3C7c">
<div>I ran my DMA for the first time last night. 3 errors all
related and two many to count warnings. I looks like the majority of
the warnings are users in AD that are not associated to devices. What
is the best way to move forward? open TAC case with debug / traces /
logs or is there something on CCO I should be looking at?</div>
<div> </div>
<div>Thanks</div>
<div> </div>
<div>Scott</div>
</div>
</div>
<pre><hr size="4" width="90%">
_______________________________________________
cisco-voip mailing list
<a moz-do-not-send="true" href="mailto:cisco-voip@puck.nether.net"
target="_blank">cisco-voip@puck.nether.net</a>
<a moz-do-not-send="true"
href="https://puck.nether.net/mailman/listinfo/cisco-voip"
target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a>
</pre>
</blockquote>
</div>
</blockquote>
</div>
<br>
</blockquote>
</body>
</html>