Add xSPUserProfileSyncConnection resource about sharepointdsc

[camiloborges]

hello.

should we use Add-SPProfileSyncConnection? Is It Supported?

[BrianFarnhill]

Not supported outside of SharePoint Online as far as I'm aware, so I wanna try to find a way to get around it, we might need to use the server side object model in script to fill this functionality out right. Happy to hear your ideas.

[camiloborges]

Last I heard there was no supported way of creating sync connections.
I scripted it earlier on this year but I am under the impression we didn't use the script because of that.

So, question to MS: is there a supported way of creating sync connections? :)

On 24 Nov 2015, at 10:45 PM, Brian Farnhill [email protected] wrote:

Not supported outside of SharePoint Online as far as I'm aware, so I wanna try to find a way to get around it, we might need to use the server side object model in script to fill this functionality out right. Happy to hear your ideas.

—
Reply to this email directly or view it on GitHub.

[camiloborges]

I can't find the script I've written for that, but I am pretty sure I used this method here (Uses cnnMgr.AddActiveDirectoryConnection)

http://community.obilogic.co.uk/blogs/teamblog/archive/2015/04/20/sharepoint-2013-migrate-replicate-user-profile-service-application-configuration-between-farms-using-powershell-part-1.aspx

[BrianFarnhill]

@camiloborges you are correct, the blog post you have there looks like the way to do it. At a quick glance all of the API calls there are public methods, so we are fine from a support perspective on this one. I'll confirm this to be sure and let you know if there are any issues but to the best of my knowledge we'll be fine.

[camiloborges]

hey @BrianFarnhill please mark this as in progress

[BrianFarnhill]

All yours @camiloborges

[camiloborges]

Hello.
Updated schema:
[ClassVersion("1.0.0.0"), FriendlyName("xSPUserProfileSyncConnection")]
class MSFT_xSPUserProfileSyncConnection : OMI_BaseResource
{
[Key] string Name;
[Required] string Forest;
[Required] string UserProfileService;
[Required, EmbeddedInstance("MSFT_Credential")] String Credentials;
[Write, EmbeddedInstance("MSFT_Credential")] String InstallAccount;
[Required] string IncludedOUs[];
[write] string ExcludedOUs[];
[write] string Server;
[Write] boolean UseSSL;
[Write] boolean Force;
[Write] string ConnectionType ;
};

Force is just so resource can delete and recreate connection in case the forest is different.

[BrianFarnhill]

@camiloborges Can we be more specific on the Credentials property to be something like "ConnectionCredential" - that way its clear what its there for

[camiloborges]

I can certainly do that. I tried to shorten parameters name but some do need to be a bit more specific

[BrianFarnhill]

Lets go for longer names over ambiguous any time it comes up - thanks bud

[camiloborges]

any request on the other attributes?

[BrianFarnhill]

Should connection type be a fixed list of options there? The others seem obvious enough I think.

[camiloborges]

good point @BrianFarnhill . it should then be

[ClassVersion("1.0.0.0"), FriendlyName("xSPUserProfileSyncConnection")]
class MSFT_xSPUserProfileSyncConnection : OMI_BaseResource
{
[Key] string Name;
[Required] string Forest;
[Required] string UserProfileService;
[Required, EmbeddedInstance("MSFT_Credential")] String ConnectionCredentials;
[Write, EmbeddedInstance("MSFT_Credential")] String InstallAccount;
[Required] string IncludedOUs[];
[write] string ExcludedOUs[];
[write] string Server;
[Write] boolean UseSSL;
[Write] boolean Force;
[Write, ValueMap{"ActiveDirectory","BCS"}, Values{"ActiveDirectory","BCS"}] string ConnectionType ;

};
BCS might have to be changed to something else. I won't implement it right now, but I will makesure the ValueMap is correct.

[BrianFarnhill]

Put the BCS option in and have it throw an exception to say its not implemented yet. Add an issue here to state that it doesn't work and I'll tag it as technical debt for us to come back to later.

[BrianFarnhill]

Released in v0.10 - closing this issue