AD User Discovery (msDS-PrimaryComputer)

We would like to pick up an AD attribute with Active Directory User Discovery, but the attribute isn't listed as an available attribute.
The attribute we are trying to pick up is msDS-PrimaryComputer. We want to be able to report on this AD attribute and compare it against the User Device affinity data already available within SCCM.
Has anyone been able to successfully discover this attribute?
Any feedback is greatly appreciated.

Done.
If anyone else feels this should behave differently, please share
https://connect.microsoft.com/ConfigurationManagervnext/feedback/details/840653/ad-user-discovery-with-custom-attributes-msds-primarycomputer
Thanks

Similar Messages

User Discovery attribute added but not showing up in v_R_User

Hi - working in 2007 here. I added two attributes for user discovery, mail and telephoneNumber. v_r_User.mail0 column came in fine but tel # did not show up. Can someone point me to where I should troubleshoot this? Thanks.

Yea, I didn't mention that. The log only said it failed to get the optional attributes. It ended up being right under my nose. The container set was the root and was set to exclude groups. So that attribute was not available
in the location it was searching. As soon as I set to include groups I kicked off a discovery, re-ran the select for v_r_user and the column was there and starting to populate.

Multi forest User discovery

Hello All,
I currently have a scenario where we have SCCM 2012 R2 sitting in domain A, forest A.
We have another domain, domain B in forest B, that we also want to manage using our SCCM in Domain A.
We have a one-way outgoing external trust from domain A towards domain B.
This means that we can use resources from domain B in domain A.
From my SCCM server in Domain A, I want to discover users in domain B.
I've setup a new Active Directory Forest in the administration pane for domain B and have assigned a domain admin account from domain B as the connection account.
In the Active Directory Users Discovery method, I've added an entry for the Domain B to discover users in a LDAP specific pathand have added that same domain admin account to discover the users in Domain B.
However, when I run the Active Directory Forest Discovery method, the ADForestDisc.log displays the following:
ERROR: [ForestDiscoveryAgent]: Failed to connect to forest DomainB.infra. This can be because of disjoint DNS namespaces, network connectivity or server availibility issue. Error Information The specified forest does not exist or cannot be contacted.
The adusrdis.log displays the following messages:
ERROR: Failed to read account (DomainB\FILIPADMIN) from site control file (0x87D20702)
ERROR: Failed to enumerate directory objects in AD container LDAP://OU=USERS,OU=***NAME***,DC=DomainB,DC=INFRA
I've added the domain suffix to the hosts file of my SCCM Server, so it should be able to resolve the suffix..
Can anyone help me on this?
How can I get discovery going?
Thanks!
Filip

Hello Jörgen,
The issue is fixed in the meantime.
The account I was using had an underscore in the netbios domain name.
I updated this to the FQDN of the domain (domain_old\account -> domain.infra\account)
Next I also found the following article from Anoop:
http://anoopcnair.com/2013/05/23/configmgr-2012-tip-on-untrusted-forest-ad-system-discovery/
I updated my discovery job to include one of the DC's and now it is working.
For now, I have added the DC to the hosts file of the computer.
How would you correctly set up name resolution?
Kind regards,
Filip

Remove Active Directory User Discovery

We're looking at enabling Active Directory User Discovery in our Config Mgr 2012 instance as as part of testing Intune. If we decide to not implement Intune, will we be able to disable Active Directory User Discovery, and remove that information from
the database?
If so, is there good documentation on how to do this?
Thanks

The easiest is to disable the Active Directory User Discovery
and than delete all the users from the All Users collection.
My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude

AD User discovery issues

I have a specific OU selected for User discovery but its discovering all User OU's and User groups. I've deleted all users out of SCCM and rediscovered and same thing. Is there a way to only discover the specific OU I'm pointing to?
Thanks
Chris

Also make sure you've configured your AD group discovery correctly also as it will also discover members.
Jason | http://blog.configmgrftw.com | @jasonsandys

ACS Unknown User Discovery

All,
Can ACS send an event/snmp trap when it discovers unknown users?
How will ACS administrators get notified when ACS discovers unknown users?
Stephanie

Hi Stephanie,
Unfortunately there is no way to do this ACS use SNMP only for logging.
ACS does not have this kind of alert. I will suggest to contact your account manager and open a new feature request.
Regards,

User Discovery getting the Office property

If I navigate to a user account in AD, on the general TAB of properties, there is a property, Office, how can I get that data into configuration manager? I went through the additional AD attributes and I don't see Office.

I added office as a Custom field and I am getting an error. Here are the steps
Here is the field I am after
Here is the attribute added to the discovery

User attributes checked by Delta Discovery in SCCM 2012

Hi All,
Since I simply cannot find an answer to my question using google, will ask it here and hope you can help me.
Which EXACT User attributes does Delta Discovery check for in SCCM 2012? Is it possible to manipulate this, and add one more attribute?
Microsoft's answer to this question is a simple: Basic User Information, but that not an exact answer.
Here is the deal. We updated the extensionAttribute12 with computernames, so that we know what the primary device for a User is (I know this feature is present in CM12, but we will not use it for reasons). This information will be collected by User Discovery
and by using a nested query in the device collection, the Primary device will be added to it. This works like a charm, the only issue is time. We need that value to be checked by delta discovery if it has been changed, however this only works with FULL discovery
which is set to 1 week. If I lower this value that might cause serious backlogs, as the jobs get piled up in the inboxes due to the large amount of DDR files. Is there anything we can do? Powershell script, a configuration file in CM12 for delta discovery
or something. We really don't what to set the User discovery to run a FULL scan every 4 hours or so, as I don't know what would happen when checking for 24k Users.
Thank you in advance for any sort of feedback!
Regards,

Hi,
Well, I checked the attribute if its replicated to the GC and according to this line isMemberOfPartialAttributeSet: TRUE it does. Will run a test again with delta discovery, and if that failes, will try to change the SystemFlag on it.
dn:CN=ms-Exch-Extension-Attribute-12,CN=Schema,CN=Configuration
>objectClass: top
>objectClass: attributeSchema
>cn: ms-Exch-Extension-Attribute-12
>distinguishedName: CN=ms-Exch-Extension-Attribute-12,CN=Schema,CN=Configuration
>instanceType: 4
>whenCreated: 20050715092317.0Z
>whenChanged: 20110528160036.0Z
>uSNCreated: 6155
>attributeID: 1.2.840.113556.1.2.600
>attributeSyntax: 2.5.5.12
>isSingleValued: TRUE
>rangeLower: 1
>rangeUpper: 2048
>mAPIID: 35928
>uSNChanged: 6155
>showInAdvancedViewOnly: TRUE
>adminDisplayName: ms-Exch-Extension-Attribute-12
>adminDescription: ms-Exch-Extension-Attribute-12
>oMSyntax: 64
>searchFlags: 16
>lDAPDisplayName: extensionAttribute12
>name: ms-Exch-Extension-Attribute-12
>objectGUID: {5AC9437E-18AE-4EE6-909B-94CC1B6EF1C5}
>schemaIDGUID: {167757F7-47F3-11D1-A9C3-0000F80367C1}
>attributeSecurityGUID: {E48D0154-BCF8-11D1-8702-00C04FB96050}
>isMemberOfPartialAttributeSet: TRUE
>objectCategory: CN=Attribute-Schema,CN=Schema,CN=Configuration
>dSCorePropagationData: 16010101000000.0Z
>msDS-IntId: -1992421057

Double users after inter forest migration - sIDHistory in AD discovery

Hey,
we plan to perform an inter forest migration with ADMT.
There we will migrate about 6000 users.
Now we have the problem that after a user is migrated with ADMT the user account is not once but two times in SCCM.
One in old and one in new domain. In active directory the user is only one time (in new domain).
This causes the loose of all collection memberships and primary device assignments.
Having a look at the users we found that they have different SIDs.
In migration of sIDHistory is enable and we can see it successful in active directory.
It is not possible to include the sIDHistory propertiy in Active Directory User Discover of SCCM - or is this just a failure by our environment?
Does anyone have an idea or hint how to solve this or possible causes?
Thank you
mk-maddin

Hi,
Based on my experience, the maintenance tasks will delete the aged Discovery Data.
Delete Aged Discovery Data
Use this task to delete aged discovery data from the database. This data can include records resulting from heartbeat discovery, network discovery, and Active Directory Domain Services discovery methods (System, User, and Group).
Planning for Maintenance Tasks for Configuration Manager
http://technet.microsoft.com/en-us/library/e555d7e3-3681-440a-82d0-319d2b4bdd08#BKMK_PlanMaintenanceTasks
You can view the default list of object attributes returned by Active Directory User Discovery, and configure additional attributes to be discovered in the
Active Directory User Discovery Properties dialog box on the
Active Directory Attributes tab.
In addition to the basic information, you can configure the discovery of extended attributes from Active Directory Domain Services.
Active Directory User Discovery
http://technet.microsoft.com/en-us/library/gg712308.aspx#BKMK_ADUserDisc
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Report on Active Directory User Attributes in SCCM 2012

I need to output a list of all users in a collection, along with certain user attributes from Active Directory. I can get part of what I need with the following query:
SELECT v_FullCollectionMembership.ResourceID,
v_R_User.Windows_NT_Domain0,
v_R_User.Distinguished_Name0,
v_R_User.Full_User_Name0,
v_R_User.Mail0,
v_R_User.User_Name0
FROM v_FullCollectionMembership, v_R_User
WHERE v_FullCollectionMembership.ResourceID = v_R_User.ResourceID
AND v_FullCollectionMembership.CollectionID = 'SMS00002'
If possible I need to add:
Last logon timestamp
User account status (enabled or disabled)
I have added "lastLogon" and "lastLogonTimestamp" as additional attributesunder Active Directory User Discovery. This discovery method is enabled and I have run a full discovery about a month ago, and again today. I read in
another thread that these attributes should appear in the table v_R_User, however they have not. Is v_R_User the right place to look for this or is there another view or table I can query?
Once I have the above sorted out, how can I find the user account status in SCCM? I have done reports in the past directly from AD and used the 'useraccountcontrol' attribute and I noticed there is a column named 'User_Account_Control0' in v_R_User, however
the values do not match those found in Active Directory.
Thanks.

Have you checked the attribute from the Active Directory in decimal format? Check that and compare it to the value ConfigMgr has stored in its 'User_Account_Control0'...
User Account Control tells you multiple things of the account, for example does the account have "Smart card login required" -option checked from the account properties.
The tricky part here is to actually get the report show you what you really want, because "useraccountcontrol" -attribute is a numeric value, you have to calculate what decimal combination means what in readable text.
More info on the attribute can be found from here
http://support.microsoft.com/kb/305144 and from there you can also find the values for different settings. For example:
account is enabled = 512
account is disabled = 514
account is enabled with smart card = 262656

User ID has sap* rights and I get this...

Synchronization started.
Connection set up (without proxy) to: http://ap-ccms-d01:50000/meSync/servlet/meSync?~sysid=DMI&
Successfully connected with server.
Processing of inbound data began.
Server logon failed.
Not experienced with SAP MI and I do not understand why it fails to log me on. I also have S_ME_SYNC and S_RFC authorizations. Has anyone encounter this issue? Please let me know how it can be solved.
Besides creating the roles, service users is there anyting else that needs to be done on the server side?
thanks,
.adrian

Hi,
This si the trace file:
[20050512 18:19:17:248] I [MI/API/Logging ] ***** LOG / TRACE SWITCHED ON
[20050512 18:19:17:248] I [MI/API/Logging ] ***** Mobile Engine version: MI 25 SP 09 Patch 00 Build 200409101427
[20050512 18:19:17:248] I [MI/API/Logging ] ***** Current timezone: America/Los_Angeles
[20050512 18:19:17:248] I [MI ] Trace severity: All (1000)
[20050512 18:19:17:248] D [MI/API/Runtime/JSP ] AbstractMEHttpServlet:dispatch request to '/jsp/trace/trace.jsp'
[20050512 18:19:23:248] D [MI/Core ] Set current application to 'MOBILEENGINE_JSP'
[20050512 18:19:23:248] D [MI/API/Runtime/JSP ] AbstractMEHttpServlet:doPost(...) called
[20050512 18:19:23:248] D [MI/API/Runtime/JSP ] AbstractMEHttpServlet:getEvent() done with event name = 'tracesendToR3'
[20050512 18:19:23:248] D [MI/API/Runtime/JSP ] AbstractMEHttpServlet:dispatch request to '/jsp/trace/trace.jsp'
[20050512 18:19:33:201] D [MI/Core ] Set current application to 'MOBILEENGINE_JSP'
[20050512 18:19:33:201] D [MI/API/Runtime/JSP ] AbstractMEHttpServlet:doGet(...) called
[20050512 18:19:33:201] D [MI/API/Runtime/JSP ] AbstractMEHttpServlet:getEvent() done with event name = ''
[20050512 18:19:33:201] D [MI/API/Runtime/JSP ] AbstractMEHttpServlet:dispatch request to '/jsp/home/home.jsp'
[20050512 18:19:34:123] D [MI/Core ] Set current application to 'MOBILEENGINE_JSP'
[20050512 18:19:34:123] D [MI/API/Runtime/JSP ] AbstractMEHttpServlet:doGet(...) called
[20050512 18:19:34:123] D [MI/API/Runtime/JSP ] AbstractMEHttpServlet:getEvent() done with event name = ''
[20050512 18:19:34:154] D [MI/API/Runtime/JSP ] AbstractMEHttpServlet:dispatch request to '/jsp/home/syncpassword.jsp'
[20050512 18:19:38:233] D [MI/Core ] Set current application to 'MOBILEENGINE_JSP'
[20050512 18:19:38:233] D [MI/API/Runtime/JSP ] AbstractMEHttpServlet:doPost(...) called
[20050512 18:19:38:233] D [MI/API/Runtime/JSP ] AbstractMEHttpServlet:getEvent() done with event name = ''
[20050512 18:19:38:264] P [MI/Sync ] Notify R3 called
[20050512 18:19:38:264] D [MI/Sync ] There is already a container for method WAF_REGISTRY and user ABERTISA in the outbound queue
[20050512 18:19:38:264] D [MI/API/Services ] MEResourceBundle:Constructor: Create MEResourceBundle(com/sap/ip/me/awtapps/home/mobile_engine, en_US, (null))
[20050512 18:19:38:264] D [MI/API/Services ] MEResourceBundle:Constructor: Use classloader com.sap.ip.me.core.Startup@1004901
[20050512 18:19:38:264] D [MI/API/Services ] CREATED MEPropertyResourceBundle com.sap.ip.me.api.services.MEResourceBundle$MEPropertyResourceBundle@1a85d38 for bundleName: com/sap/ip/me/awtapps/home/mobile_engine with Locale: _en
[20050512 18:19:38:264] I [MI/Sync ] Synchronize with backend called, Thread=Thread-28
[20050512 18:19:38:264] I [MI/Sync ] Thread=Thread-28 took lock for synchronizeation.
[20050512 18:19:38:264] D [MI/Sync ] Synchronisation: Fire SyncEvent 0
[20050512 18:19:38:264] P [MI/Core ] Thread Thread-28 switched context to MI2853484152454429 / MI2853484152454429 (User: (SHARED), MSD: Name: / MOBILEENGINE_JSP (V. 250900), Target=, Type=com.sap.ip.me.core.FrameworkApplicationType) (stack level 1)
[20050512 18:19:38:264] I [MI/API/Sync ] SyncEvent Performing com.sap.ip.me.sync.LogSender
[20050512 18:19:38:264] P [MI/Core ] original context restored
[20050512 18:19:38:264] P [MI/Core ] Thread Thread-28 switched context to MI4142455254495341 / MI4142455254495341 (User: ABERTISA, MSD: Name: / MOBILEENGINE_JSP (V. 250900), Target=, Type=com.sap.ip.me.core.FrameworkApplicationType) (stack level 1)
[20050512 18:19:38:264] I [MI/API/Sync ] SyncEvent Performing com.sap.ip.me.apps.jsp.SyncStatus
[20050512 18:19:38:264] P [MI/Core ] original context restored
[20050512 18:19:38:264] P [MI/Core ] Thread Thread-28 switched context to MI2853484152454429 / MI2853484152454429 (User: (SHARED), MSD: Name: / MOBILEENGINE_JSP (V. 250900), Target=, Type=com.sap.ip.me.core.FrameworkApplicationType) (stack level 1)
[20050512 18:19:38:264] I [MI/API/Sync ] SyncEvent Performing com.sap.ip.me.ccms.LastSuccessfulSyncAlert
[20050512 18:19:38:264] P [MI/Core ] original context restored
[20050512 18:19:38:264] P [MI/Core ] Thread Thread-28 switched context to MI2853484152454429 / MI2853484152454429 (User: (SHARED), MSD: Name: / MOBILEENGINE_JSP (V. 250900), Target=, Type=com.sap.ip.me.core.FrameworkApplicationType) (stack level 1)
[20050512 18:19:38:264] I [MI/API/Sync ] SyncEvent Performing com.sap.ip.me.services.os.AgentManager
[20050512 18:19:38:279] D [MI/API/Services ] CREATED parent MEPropertyResourceBundle for child bundle: com.sap.ip.me.api.services.MEResourceBundle$MEPropertyResourceBundle@1a85d38 using bundle name: com/sap/ip/me/awtapps/home/mobile_engine
[20050512 18:19:38:279] D [MI/API/Runtime/JSP ] AbstractMEHttpServlet:dispatch request to '/jsp/home/home.jsp'
[20050512 18:19:38:279] P [MI/Sync ] Created outbound container for user (SHARED) and method AGENT_PARAMETERS
[20050512 18:19:38:279] P [MI/Core ] original context restored
[20050512 18:19:38:279] P [MI/Core ] Thread Thread-28 switched context to MI2853484152454429 / MI2853484152454429 (User: (SHARED), MSD: Name: / MOBILEENGINE_JSP (V. 250900), Target=, Type=com.sap.ip.me.core.FrameworkApplicationType) (stack level 1)
[20050512 18:19:38:279] I [MI/API/Sync ] SyncEvent Performing com.sap.ip.me.core.StatusUpdater
[20050512 18:19:38:279] P [MI/Core ] original context restored
[20050512 18:19:38:279] P [MI/Core ] Thread Thread-28 switched context to MI4142455254495341 / MI4142455254495341 (User: ABERTISA, MSD: Name: / MOBILEENGINE_JSP (V. 250900), Target=, Type=com.sap.ip.me.core.FrameworkApplicationType) (stack level 1)
[20050512 18:19:38:279] I [MI/API/Sync ] SyncEvent Performing com.sap.ip.me.smartsync.core.SmartSyncRuntimeManager
[20050512 18:19:38:279] D [MI/Smartsync ] User has not been installed on MW, it is not ready for sync :ABERTISA
[20050512 18:19:38:279] P [MI/Core ] original context restored
[20050512 18:19:38:279] P [MI/Core ] Thread Thread-28 switched context to MI2853484152454429 / MI2853484152454429 (User: (SHARED), MSD: Name: / MOBILEENGINE_JSP (V. 250900), Target=, Type=com.sap.ip.me.core.FrameworkApplicationType) (stack level 1)
[20050512 18:19:38:279] I [MI/API/Sync ] SyncEvent Performing com.sap.ip.me.ccms.AlertManager
[20050512 18:19:38:279] P [MI/Core ] original context restored
[20050512 18:19:38:279] P [MI/Sync ] Synchronization started for user (SHARED)
[20050512 18:19:38:279] D [MI/Sync ] PackageManager: old package file C:\Program Files\SAP Mobile Infrastructure\sync\(SHARED)\out\package.out could not be deleted
[20050512 18:19:38:279] D [MI/Sync ] PackageManager: create package with maximum 2147483647 items
[20050512 18:19:38:311] D [MI/Sync ] PackageManager: filled package with 0 acknowledge received container(s)
[20050512 18:19:38:311] D [MI/Sync ] PackageManager: filled package with 0 acknowledge container(s)
[20050512 18:19:38:342] D [MI/Sync ] PackageManager: filled package with 72 container items or headers
[20050512 18:19:38:342] D [MI/Sync ] PackageManager: filled package with 1 notify container(s)
[20050512 18:19:38:342] D [MI/Sync ] Package file C:\Program Files\SAP Mobile Infrastructure\sync\(SHARED)\out\package.out exists and can be read
[20050512 18:19:38:342] P [MI/Sync ] Synchronisation started
[20050512 18:19:38:342] D [MI/Sync ] Dumping file 'C:\Program Files\SAP Mobile Infrastructure\sync\(SHARED)\out\package.out'
INH-H[1]=0103ccd845dc23221935;;R;AGENT_PARAMETERS;;;;;NEW_PROTOCOL;;0;;3;;&INB-B[1]=0103ccd845dc23221935;TIMESTAMP;0;000000;19700101&INB-B[2]=0103ccd845dc23221935;DEVICEID;0;&INB-B[3]=0103ccd845dc23221935;USER;0;ABERTISA&INH-H[2]=0103ccdaa04bda7b4f1e;;R;AGENT_PARAMETERS;;;;;NEW_PROTOCOL;;0;;3;;&INB-B[4]=0103ccdaa04bda7b4f1e;TIMESTAMP;0;000000;19700101&INB-B[5]=0103ccdaa04bda7b4f1e;DEVICEID;0;&INB-B[6]=0103ccdaa04bda7b4f1e;USER;0;ABERTISA&INH-H[3]=0103ccde64db45e939f9;;R;AGENT_PARAMETERS;;;;;NEW_PROTOCOL;;0;;3;;&INB-B[7]=0103ccde64db45e939f9;TIMESTAMP;0;000000;19700101&INB-B[8]=0103ccde64db45e939f9;DEVICEID;0;&INB-B[9]=0103ccde64db45e939f9;USER;0;ABERTISA&INH-H[4]=0103ccdf0487191e79ad;;R;AGENT_PARAMETERS;;;;;NEW_PROTOCOL;;0;;3;;&INB-B[10]=0103ccdf0487191e79ad;TIMESTAMP;0;000000;19700101&INB-B[11]=0103ccdf0487191e79ad;DEVICEID;0;&INB-B[12]=0103ccdf0487191e79ad;USER;0;ABERTISA&INH-H[5]=0103ccdfce6f7d45e0d3;;R;AGENT_PARAMETERS;;;;;NEW_PROTOCOL;;0;;3;;&INB-B[13]=0103ccdfce6f7d45e0d3;TIMESTAMP;0;000000;19700101&INB-B[14]=0103ccdfce6f7d45e0d3;DEVICEID;0;&INB-B[15]=0103ccdfce6f7d45e0d3;USER;0;ABERTISA&INH-H[6]=0103cce33f5e86b3c61f;;R;AGENT_PARAMETERS;;;;;NEW_PROTOCOL;;0;;3;;&INB-B[16]=0103cce33f5e86b3c61f;TIMESTAMP;0;000000;19700101&INB-B[17]=0103cce33f5e86b3c61f;DEVICEID;0;&INB-B[18]=0103cce33f5e86b3c61f;USER;0;ABERTISA&INH-H[7]=0103cce46b0db12ad014;;R;AGENT_PARAMETERS;;;;;NEW_PROTOCOL;;0;;3;;&INB-B[19]=0103cce46b0db12ad014;TIMESTAMP;0;000000;19700101&INB-B[20]=0103cce46b0db12ad014;DEVICEID;0;&INB-B[21]=0103cce46b0db12ad014;USER;0;ABERTISA&INH-H[8]=0103cce58d75c6d58d46;;R;AGENT_PARAMETERS;;;;;NEW_PROTOCOL;;0;;3;;&INB-B[22]=0103cce58d75c6d58d46;TIMESTAMP;0;000000;19700101&INB-B[23]=0103cce58d75c6d58d46;DEVICEID;0;&INB-B[24]=0103cce58d75c6d58d46;USER;0;ABERTISA&INH-H[9]=0103cce82371b7e5b68e;;R;AGENT_PARAMETERS;;;;;NEW_PROTOCOL;;0;;3;;&INB-B[25]=0103cce82371b7e5b68e;TIMESTAMP;0;000000;19700101&INB-B[26]=0103cce82371b7e5b68e;DEVICEID;0;&INB-B[27]=0103cce82371b7e5b68e;USER;0;ABERTISA&INH-H[10]=0103ccea96fa4a3b9652;;R;AGENT_PARAMETERS;;;;;NEW_PROTOCOL;;0;;3;;&INB-B[28]=0103ccea96fa4a3b9652;TIMESTAMP;0;000000;19700101&INB-B[29]=0103ccea96fa4a3b9652;DEVICEID;0;&INB-B[30]=0103ccea96fa4a3b9652;USER;0;ABERTISA&INH-H[11]=0103ccec012ca062e298;;R;AGENT_PARAMETERS;;;;;NEW_PROTOCOL;;0;;3;;&INB-B[31]=0103ccec012ca062e298;TIMESTAMP;0;000000;19700101&INB-B[32]=0103ccec012ca062e298;DEVICEID;0;&INB-B[33]=0103ccec012ca062e298;USER;0;ABERTISA&INH-H[12]=0103ccf565d51f7bd8f7;;R;AGENT_PARAMETERS;;;;;NEW_PROTOCOL;;0;;3;;&INB-B[34]=0103ccf565d51f7bd8f7;TIMESTAMP;0;000000;19700101&INB-B[35]=0103ccf565d51f7bd8f7;DEVICEID;0;&INB-B[36]=0103ccf565d51f7bd8f7;USER;0;ABERTISA&INH-H[13]=0103cdf4e3416d40815c;;R;AGENT_PARAMETERS;;;;;NEW_PROTOCOL;;0;;3;;&INB-B[37]=0103cdf4e3416d40815c;TIMESTAMP;0;000000;19700101&INB-B[38]=0103cdf4e3416d40815c;DEVICEID;0;&INB-B[39]=0103cdf4e3416d40815c;USER;0;ABERTISA&INH-H[14]=0103d16e551570169713;;R;AGENT_PARAMETERS;;;;;NEW_PROTOCOL;;0;;3;;&INB-B[40]=0103d16e551570169713;TIMESTAMP;0;000000;19700101&INB-B[41]=0103d16e551570169713;DEVICEID;0;&INB-B[42]=0103d16e551570169713;USER;0;ABERTISA&INH-H[15]=0103d192e748e435f81c;;R;AGENT_PARAMETERS;;;;;NEW_PROTOCOL;;0;;3;;&INB-B[43]=0103d192e748e435f81c;TIMESTAMP;0;000000;19700101&INB-B[44]=0103d192e748e435f81c;DEVICEID;0;&INB-B[45]=0103d192e748e435f81c;USER;0;ABERTISA&INH-H[16]=0103d193f55fbd794439;;R;AGENT_PARAMETERS;;;;;NEW_PROTOCOL;;0;;3;;&INB-B[46]=0103d193f55fbd794439;TIMESTAMP;0;000000;19700101&INB-B[47]=0103d193f55fbd794439;DEVICEID;0;&INB-B[48]=0103d193f55fbd794439;USER;0;ABERTISA&INH-H[17]=0103d22044f095f427f4;;R;AGENT_PARAMETERS;;;;;NEW_PROTOCOL;;0;;3;;&INB-B[49]=0103d22044f095f427f4;TIMESTAMP;0;000000;19700101&INB-B[50]=0103d22044f095f427f4;DEVICEID;0;&INB-B[51]=0103d22044f095f427f4;USER;0;ABERTISA&INH-H[18]=0103d22213987cabb3b4;;R;AGENT_PARAMETERS;;;;;NEW_PROTOCOL;;0;;3;;&INB-B[52]=0103d22213987cabb3b4;TIMESTAMP;0;000000;19700101&INB-B[53]=0103d22213987cabb3b4;DEVICEID;0;&INB-B[54]=0103d22213987cabb3b4;USER;0;ABERTISA&INH-H[19]=0103d22213e6f159009f;;N;;;;;;NEW_PROTOCOL;;0;;0;;&
[20050512 18:19:38:342] D [MI/Sync ] End of content of file 'C:\Program Files\SAP Mobile Infrastructure\sync\(SHARED)\out\package.out'
[20050512 18:19:38:342] P [MI/Sync ] Do not use http proxy (system properties update)
[20050512 18:19:38:342] I [MI/Sync ] GzipDataCompression: Gzip data compression is switched off
[20050512 18:19:38:342] P [MI/Sync ] Sending outbound file to server.
[20050512 18:19:38:358] P [MI/Sync ] Outbound file was sent.
[20050512 18:19:38:389] P [MI/Sync ] Receiving inbound file from server.
[20050512 18:19:38:389] P [MI/Sync ] Inbound file was received.
[20050512 18:19:38:389] P [MI/Sync ] Synchronisation successfully connected
[20050512 18:19:38:389] D [MI/Sync ] Number of pending inbound containers before inbound processing = 0
[20050512 18:19:38:389] D [MI/Sync ] SyncInboundContainer: closing reader for inbound file / stream
[20050512 18:19:38:389] D [MI/Sync ] Dumping file 'C:\Program Files\SAP Mobile Infrastructure\sync\(SHARED)\inbound.sync'
&WAF_SYNC&EXCEPTION_INFO_CODE=7&
[20050512 18:19:38:389] D [MI/Sync ] End of content of file 'C:\Program Files\SAP Mobile Infrastructure\sync\(SHARED)\inbound.sync'
[20050512 18:19:38:389] P [MI/Core ] original context restored
[20050512 18:19:38:389] D [MI/Sync ] Synchronisation: Fire SyncEvent 1
[20050512 18:19:38:389] P [MI/Core ] Thread Thread-28 switched context to MI2853484152454429 / MI2853484152454429 (User: (SHARED), MSD: Name: / MOBILEENGINE_JSP (V. 250900), Target=, Type=com.sap.ip.me.core.FrameworkApplicationType) (stack level 1)
[20050512 18:19:38:389] I [MI/API/Sync ] SyncEvent Performing com.sap.ip.me.sync.LogSender
[20050512 18:19:38:389] P [MI/Core ] original context restored
[20050512 18:19:38:389] P [MI/Core ] Thread Thread-28 switched context to MI4142455254495341 / MI4142455254495341 (User: ABERTISA, MSD: Name: / MOBILEENGINE_JSP (V. 250900), Target=, Type=com.sap.ip.me.core.FrameworkApplicationType) (stack level 1)
[20050512 18:19:38:389] I [MI/API/Sync ] SyncEvent Performing com.sap.ip.me.apps.jsp.SyncStatus
[20050512 18:19:38:389] P [MI/Core ] original context restored
[20050512 18:19:38:389] P [MI/Core ] Thread Thread-28 switched context to MI2853484152454429 / MI2853484152454429 (User: (SHARED), MSD: Name: / MOBILEENGINE_JSP (V. 250900), Target=, Type=com.sap.ip.me.core.FrameworkApplicationType) (stack level 1)
[20050512 18:19:38:389] I [MI/API/Sync ] SyncEvent Performing com.sap.ip.me.ccms.LastSuccessfulSyncAlert
[20050512 18:19:38:389] P [MI/Core ] original context restored
[20050512 18:19:38:389] P [MI/Core ] Thread Thread-28 switched context to MI2853484152454429 / MI2853484152454429 (User: (SHARED), MSD: Name: / MOBILEENGINE_JSP (V. 250900), Target=, Type=com.sap.ip.me.core.FrameworkApplicationType) (stack level 1)
[20050512 18:19:38:389] I [MI/API/Sync ] SyncEvent Performing com.sap.ip.me.services.os.AgentManager
[20050512 18:19:38:389] P [MI/Core ] original context restored
[20050512 18:19:38:389] P [MI/Core ] Thread Thread-28 switched context to MI2853484152454429 / MI2853484152454429 (User: (SHARED), MSD: Name: / MOBILEENGINE_JSP (V. 250900), Target=, Type=com.sap.ip.me.core.FrameworkApplicationType) (stack level 1)
[20050512 18:19:38:389] I [MI/API/Sync ] SyncEvent Performing com.sap.ip.me.core.StatusUpdater
[20050512 18:19:38:389] P [MI/Core ] original context restored
[20050512 18:19:38:389] P [MI/Core ] Thread Thread-28 switched context to MI4142455254495341 / MI4142455254495341 (User: ABERTISA, MSD: Name: / MOBILEENGINE_JSP (V. 250900), Target=, Type=com.sap.ip.me.core.FrameworkApplicationType) (stack level 1)
[20050512 18:19:38:389] I [MI/API/Sync ] SyncEvent Performing com.sap.ip.me.smartsync.core.SmartSyncRuntimeManager
[20050512 18:19:38:389] D [MI/Smartsync ] User has not been installed on MW, it is not ready for sync :ABERTISA
[20050512 18:19:38:389] P [MI/Core ] original context restored
[20050512 18:19:38:389] P [MI/Core ] Thread Thread-28 switched context to MI2853484152454429 / MI2853484152454429 (User: (SHARED), MSD: Name: / MOBILEENGINE_JSP (V. 250900), Target=, Type=com.sap.ip.me.core.FrameworkApplicationType) (stack level 1)
[20050512 18:19:38:389] I [MI/API/Sync ] SyncEvent Performing com.sap.ip.me.ccms.AlertManager
[20050512 18:19:38:389] P [MI/Core ] original context restored
[20050512 18:19:38:389] I [MI/Sync ] Synchronization finished, Thread=Thread-28
[20050512 18:19:48:326] D [MI/Core ] Set current application to 'MOBILEENGINE_JSP'
[20050512 18:19:48:326] D [MI/API/Runtime/JSP ] AbstractMEHttpServlet:doGet(...) called
[20050512 18:19:48:326] D [MI/API/Runtime/JSP ] AbstractMEHttpServlet:getEvent() done with event name = ''
[20050512 18:19:48:326] D [MI/API/Runtime/JSP ] AbstractMEHttpServlet:dispatch request to '/jsp/home/synclog.jsp'
[20050512 18:21:04:484] D [MI/Core ] Set current application to 'MOBILEENGINE_JSP'
[20050512 18:21:04:484] D [MI/API/Runtime/JSP ] AbstractMEHttpServlet:doGet(...) called
[20050512 18:21:04:484] D [MI/API/Runtime/JSP ] AbstractMEHttpServlet:getEvent() done with event name = ''
[20050512 18:21:04:484] D [MI/API/Runtime/JSP ] AbstractMEHttpServlet:dispatch request to '/jsp/home/home.jsp'
[20050512 18:21:05:531] D [MI/Core ] Set current application to 'MOBILEENGINE_JSP'
[20050512 18:21:05:531] D [MI/API/Runtime/JSP ] AbstractMEHttpServlet:doGet(...) called
[20050512 18:21:05:531] D [MI/API/Runtime/JSP ] AbstractMEHttpServlet:getEvent() done with event name = ''
[20050512 18:21:05:531] D [MI/API/Runtime/JSP ] AbstractMEHttpServlet:dispatch request to '/jsp/trace/trace.jsp'
[20050512 18:21:07:031] D [MI/Core ] Set current application to 'MOBILEENGINE_JSP'
[20050512 18:21:07:031] D [MI/API/Runtime/JSP ] AbstractMEHttpServlet:doGet(...) called
[20050512 18:21:07:031] D [MI/API/Runtime/JSP ] AbstractMEHttpServlet:getEvent() done with event name = ''
At some point is says:
User has not been installed on MW, it is not ready for sync :ABERTISA .
What is MW?
And I think that i will need to patch the instalation since I have Mobile Engine 09 but when I look in MI through the WebConsole (http://ap-ccms-d01.corp.se.sempra.com:50000/me/WebConsole/add) I do not see version 250900 for MOBILEENGINE_JSP. I only have version 250000 and 250400.
Is this a SP issue?
thanks for your help.

How to add user e-mail to a custom report?

Hello,
I am not a sql DBA, but trying to find out exact line that I should add to the query for any custom report, to show user e-mail address field as well.
For example, I use this query for all machines running unwanted software (found this query on google) :
Select
SD.Name0,
sys1.User_Name0,
SF.FileName
From v_r_system sys1
join v_gs_softwarefile sf on sf.resourceid=sys1.resourceid
left join v_R_User usr on usr.User_Name0=sys1.User_Name0
left Join v_R_System SD on SD.ResourceId = SF.ResourceId
Where SF.FileName Like '%Azureus%'
Or SF.FileName Like '%ABC%'
Or SF.FileName Like '%BitComet%'
Order By SD.Name0, SF.FileName, sys1.User_Name0
I do have user discovery enabled with mail attribute, and can see e-mail address getting collected for all the users.
Thanks in Advance

In case it's SQL/SSRS, which I assumed based on the initial query, then your query should look like this:
Select
SD.Name0,
sys1.User_Name0,
usr.Mail0,
SF.FileName
From v_r_system sys1
join v_gs_softwarefile sf on sf.resourceid=sys1.resourceid
left join v_R_User usr on usr.User_Name0=sys1.User_Name0
left Join v_R_System SD on SD.ResourceId = SF.ResourceId
Where SF.FileName Like '%Azureus%'
Or SF.FileName Like '%ABC%'
Or SF.FileName Like '%BitComet%'
Order By SD.Name0, SF.FileName, sys1.User_Name0
My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude

SMS_DISCOVERY_DATA_MANAGER Message ID 2636 and 620. Discovery Data Manager failed to process the discovery data record (DDR)

Hi
I'm seeing this critical error on my primary.
SMS_DISCOVERY_DATA_MANAGER Message ID 2636 and 620.
Discovery data manager failed to process the discovery data record (DDR)"D:\Prog.....\inboxes\auth\ddm.box\userddrsonly\adu650dh.DDR", because it cannot update the data source.
Where these ddr's are actually under ddm.box\userddrsonly\BAD_DDRS folder
I see a ton of DDR files in that folder. Not sure if I can delete them, so I moved them to a temp folder. AD User discovery keeps generating them.
Any help ?
Thanks
UK

Check the ddm.log file for more information.
My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude

Why is member count 100 for all users sccm collection

hello,
I have SCCM 2012 SP1 -4, and have enabled user discovery but "all users" collection does not goes above 100 member count.
I do have more 1500 users in AD, all related setting are at default.
Disable \enabling was no help,
no component shows warning or error.
Thanks

Hi. what about adusrdis.log? and are you correctly configuring AD user discovery? see this for example
http://www.windows-noob.com/forums/index.php?/topic/4428-using-sccm-2012-rc-in-a-lab-part-3-configuring-discovery-and-boundaries/

Discovery

Hello Everyone,
Am trying to configure system and user discovery but when i click path i get the error below, Please advise
Current security context is not associated with an Active Directory domain or forest.
System.DirectoryServices.ActiveDirectory.ActiveDirectoryOperationException
Current security context is not associated with an Active Directory domain or forest.
Stack Trace:
   at System.DirectoryServices.ActiveDirectory.DirectoryContext.GetLoggedOnDomain()
   at System.DirectoryServices.ActiveDirectory.DirectoryContext.IsContextValid(DirectoryContext context, DirectoryContextType contextType)
   at System.DirectoryServices.ActiveDirectory.DirectoryContext.isRootDomain()
   at System.DirectoryServices.ActiveDirectory.ActiveDirectorySchema.GetSchema(DirectoryContext context)
   at Microsoft.ConfigurationManagement.AdminConsole.ActiveDirectory.AttibutesPageControl.worker_DoWork(Object sender, DoWorkEventArgs e)
   at System.ComponentModel.BackgroundWorker.OnDoWork(DoWorkEventArgs e)
   at System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument)
Meshack

Hi,
It sounds like this is the same issue?
https://knowledgedirectory.wordpress.com/2012/05/08/sccm2012-system-discovery-fails-when-configure-cm-discovery-settings/
Are you logged on with a local account on the SCCM Server when you run the admin console? try log on with a domain acount instead.
Regards,
Jörgen
-- My System Center blog ccmexec.com -- Twitter
@ccmexec

AD User Discovery (msDS-PrimaryComputer)

Similar Messages

Maybe you are looking for