No problem. And I'd just about finished knocking up that PS script... :)
From: ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com] On Behalf Of drew.h...@worldvision.com.au Sent: Wednesday, 29 June 2011 2:27 PM To: ozMOSS Subject: RE: Help with AD field import into SP2010 Hi Paul BIG ID-10-T error over in my neck of the woods I've just realised that the reason I wasn't seeing all the AD values as I wasn't changing the value in step 4 to Sting (multi value), hence not seeing them in the Attributes field. So again thanks Cheers Drew All is fine, nothing to see here, move along From: drew.h...@worldvision.com.au<mailto:drew.h...@worldvision.com.au> To: ozMOSS <ozmoss@ozmoss.com<mailto:ozmoss@ozmoss.com>> Date: 29/06/2011 09:49 AM Subject: RE: Help with AD field import into SP2010 Sent by: ozmoss-boun...@ozmoss.com<mailto:ozmoss-boun...@ozmoss.com> ________________________________ Hi Paul Thanks for the process - I've been able to do that for mapped attributes but not for unmapped ones such as the user description attribute as it is not listed. Is it possible to expand step 7 in how to add existing AD attributes using powershell to the drop down list as I need to do this for several of them? Thanks in advance Drew From: Paul Noone <paul.no...@ceosyd.catholic.edu.au<mailto:paul.no...@ceosyd.catholic.edu.au>> To: ozMOSS <ozmoss@ozmoss.com<mailto:ozmoss@ozmoss.com>> Date: 29/06/2011 09:10 AM Subject: RE: Help with AD field import into SP2010 Sent by: ozmoss-boun...@ozmoss.com<mailto:ozmoss-boun...@ozmoss.com> ________________________________ If the attribute(s) are present you can just create a new property and map to it. 1. Open CA and go to the management page of your user profile service application. 2. Click on "Manage User Properties" 3. Click on "New Property" 4. Provide a "Name" and the "Display Name". 5. Select the data type of the property. (This should match the data type of the corresponding attribute in AD you want to map to.) 6. Select the synchronization connection from the "Source Data Connection" drop down. 7. Select your attribute from the "Attribute" drop down. (If it's not there you can create the mapping using PowerShell.) 8. Select the direction of the attribute. (i.e. Import) 9. Click Add 10. Click OK. Regards, Paul -- Online Developer/SharePoint Administrator, ICT Infrastructure Team CEO Sydney From: ozmoss-boun...@ozmoss.com<mailto:ozmoss-boun...@ozmoss.com> [mailto:ozmoss-boun...@ozmoss.com] On Behalf Of drew.h...@worldvision.com.au<mailto:drew.h...@worldvision.com.au> Sent: Wednesday, 29 June 2011 8:35 AM To: ozmoss@ozmoss.com<mailto:ozmoss@ozmoss.com> Subject: Help with AD field import into SP2010 Hi Guys/Gals I'm hoping someone might be able to point me in the right direction or the location of resources with on how to do the following... In AD we use the description field to identify the team a staff member belongs to. I'm wanting to add this as a custom property in the User properties, but the description attribute is not available from the list of attributes shown in the AD import source data connection. I also have several others AD properties that need to be mapped which do not appear in this list. Is there a way to include additional or all AD attributes rather than the default set that seem to be a reduced set. In SP 2007 this is not an issue as they all appear as part of the selection process. Cheers DrewThe contents of this email and any attachments may be confidential. It must not be used, distributed, copied or read by any person other than the intended recipient(s). Unauthorised use, disclosure, copying, or reliance on the contents and attachments of this email may be unlawful. If you have received this email in error, please notify the sender immediately by return email and delete the original message. The sender believes that this email and any attachments were free of any virus or other malicious code when sent._______________________________________________ ozmoss mailing list ozmoss@ozmoss.com<mailto:ozmoss@ozmoss.com> http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss The contents of this email and any attachments may be confidential. It must not be used, distributed, copied or read by any person other than the intended recipient(s). Unauthorised use, disclosure, copying, or reliance on the contents and attachments of this email may be unlawful. If you have received this email in error, please notify the sender immediately by return email and delete the original message. The sender believes that this email and any attachments were free of any virus or other malicious code when sent._______________________________________________ ozmoss mailing list ozmoss@ozmoss.com<mailto:ozmoss@ozmoss.com> http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss The contents of this email and any attachments may be confidential. It must not be used, distributed, copied or read by any person other than the intended recipient(s). Unauthorised use, disclosure, copying, or reliance on the contents and attachments of this email may be unlawful. If you have received this email in error, please notify the sender immediately by return email and delete the original message. The sender believes that this email and any attachments were free of any virus or other malicious code when sent.
_______________________________________________ ozmoss mailing list ozmoss@ozmoss.com http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss
