It's possible to create Lync account by managing Attributes in the AD. I checked. But, I remember vaguely that it's not supported that way. Is it true? Is there any problem with that?  Is there any reason for using Enable-CsUser and Set-CsUser instead of writing attributes in the AD directly?

It looks like this is working fine...

1. get-aduser -identity "test" >> Result...

  2. get-csuser -identity "test" >> no result

  3. Set AD attributes with ADUC attribute editor:
  msRTCSIP-FederationEnabled = True
  msRTCSIP-InternetAccessEnabled = True
  msRTCSIP-UserEnabled = True
  msRTCSIP-OptionFlags = 257
  msRTCSIP-UserPolicies = 0=1103749707
  msRTCSIP-PrimaryHomeServer = "defaultPrimaryHomeServer"
  msRTCSIP-PrimaryUserAddress = "sip:" & accountName & "@" & mdwDomainDn
  msRTCSIP-DeploymentLocator = SRV:
  msRTCSIP-ArchivingEnabled = 0

  4. get-csuser -identity "test" >> result...

Hi,

The supported is to use Lync Server Management Shell or Lync Server Control Panel to enable Lync users.

If you create Lync account by managing Attributes in the AD, it may miss several Lync attribute. So it may work but not the supported method.

Best Regards,

Eason Huang

Hi,

Can anyone make it hard? What's Microsoft's point of view about it? I have the same opinion but I want to make my meaning harder, supporting it with facts.

Is the use of Enable-CsUser or the Lync server GUI mand

Yes, you have to use PowerShell or GUI.  The reason is the user account is more than AD attributes, entries are created in the front end pool database where the user lives related to the user, this contains general client settings and contact list information.  That's why most automated user provisioning requires the use of PowerShell.